ITEA is a project that attempts to enable small business users and end users to generate the applications they want using simple visual tools. The application (as well as data) is described in an abstracted format that can be solidified by ITEA providers.
The primary goals of ITEA are:
1) End user owns the application. The user owns the abstract definition of the application and data, and is able to switch to different ITEA vendors INSTANTLY without needing to worry about losing any functionality or data. For example, an IT application owner may have chosen a Java ITEA vendor, then switch to .Net at a later time for whatever reason. Besides, the user can choose an ITEA provider that only provides stand-alone version at the beginning, and switch to another vendor that provides fully distributed system based on WCF when the application needs to be scaled up.
2) Instant integration. All ITEA applications can be literally integrated by copy-and-paste of application definition segments (or simply use references). Also, ITEA application owners can also leverage the integration connectors (such as SOA connectors) that ITEA vendors provide to achieve quicker integrations with other applications.
3) ITEA fills the vacuum for small businesses to find highly customizable applications, eliminating the risk of being bound to instable vendors (which are also usually small businesses). And as the ITEA provider can code once for potentially more customers, I’m hoping more larger-scale software vendors will see the value and provide more robust ITEA implementations.
The initial scope of ITEA is:
1) A practical simple application abstraction specification. The specification needs to be able to describe
a. A common CRUD application
b. A common resource management application (pictures, documents, school notes, etc.)
c. A common communication application (instant messaging, mail)
d. A common reporting and analysis application
2) Primary sample implementation of ITEA:
a. (Probably) based on .Net
b. Leverage Microsoft Enterprise libraries when appropriate
c. Use Microsoft DSL tools and dynamic languages when appropriate

Last edited Nov 26, 2007 at 4:59 AM by FriendlyDog, version 2