11. The process of claim 7 wherein said diagrams and textual interactive dialogs receive and process requirements data which, if entered, further defines each class by defining derivations, constraints, triggers, display sets, filters and population selection user interface patterns, wherein said requirements data entered by said designer defines each derivation as a list of condition-formula pairs and specifies which formula will be applied under every condition, and wherein said requirements data entered by said designer further defines each constraint as a formula plus an error message the designer specifies which will be displayed when said constraint specified by said designer is violated, and wherein said requirements data defines each trigger as composed of a trigger target specified as self, class or object, a trigger condition and a triggered action comprised of a service and a list of possible agents to be activate said service and a list of default values associated with the arguments of the related service, and wherein said requirements data entered by said designer defines each display set by defining which attributes of said class will be visible to the user, and wherein said requirements data defines each filter as comprised of a formula and a list of auxiliary variables that are useful to define said formula, and wherein said requirements data defines said population selection user interface pattern by defining a display set and a filter, and wherein said diagrams and textual interactive dialogs receive and process requirements data defining a state transition diagram for each class which is a set of states and transitions between them where each transition occurs upon occurrence of an action that can change the state of an object in said class, and wherein said requirements data can be entered which defines said actions as having preconditions which are entered by said designer as formulas that need to be satisfied before an action can be executed.
12. The process of claim 11 wherein said diagrams and textual interactive dialogs receives and processes requirements data entered by said designer which specifies relationships between classes which can be either aggregation or inheritance, wherein each aggregation relationship is indicated by requirements data which specifies the composition of objects in the aggregation relationship and which specifies cardinalities and whether the aggregation is static or dynamic and whether the aggregation is inclusive or referential and whether the aggregation has an identification dependence and a grouping clause when the aggregation is multi-valued, and wherein each inheritance relationship is defined by requirements data entered by the designer which specifies specialization of objects and stores the name of the parent class, the name of the child class and whether the specialization is temporary or permanent, and if the specialization is permanent, stores a formula on constant attributes as a specialization condition, and, if the specialization is temporary, said requirements data indicates the condition or the list of events that activate or deactivate the child class, and wherein said diagrams and textual interactive receive and process requirements data that specifies a list of global interactions including the name of the global interaction, the formula and a list of arguments and allows said designer to enter a list of global functions including the name, a data type of a returned value and a set of arguments.