16. The process of claim 15 wherein said diagrams and textual interactive dialogs receive and process requirements data entered by said designer defining an Object Model, a Dynamic Model, a Functional Model and a Presentation Model which can include definitions of classes, relationships between classes, global interactions, global functions and views, and wherein said diagrams and textual interactive dialogs receive and process requirements data as part of said Object Model, Dynamic Model, Functional Model and Presentation Model, said diagrams and textual interactive dialogs enabling entry of requirements data defining: attributes; services; derivations; constraints; transaction formulas; triggers; display sets; filters; population selection patterns; a state transition diagram; formal interfaces; a name.
16. The process of claim 15 wherein said diagrams and textual interactive dialogs receive and process requirements data entered by said designer defining an Object Model, a Dynamic Model, a Functional Model and a Presentation Model which can include definitions of classes, relationships between classes, global interactions, global functions and views, and wherein said diagrams and textual interactive dialogs receive and process requirements data as part of said Object Model, Dynamic Model, Functional Model and Presentation Model, said diagrams and textual interactive dialogs enabling entry of requirements data defining: attributes; services; derivations; constraints; transaction formulas; triggers; display sets; filters; population selection patterns; a state transition diagram; formal interfaces; a name. 19. The process of claim 16 wherein said diagrams and textual interactive dialogs receive and process requirements data entered by said designer which, if entered, can further define each class by entering requirements data defining further defining each said derivation by specifying a list of condition-formula pairs and by specifying which formula will be applied under every condition; and by further defining 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 by further defining each trigger as composed of a trigger target specified as self, class or object, and by further defining a trigger condition and a triggered action comprised of a service and a list of possible agents to activate said service and a list of values associated with the arguments of the related service; and wherein said diagrams and textual interactive dialogs receive and process requirements data which further defines each said display set by defining which attributes of said class will be visible to the user; and which further defines each said filter as comprised of a formula and a list of auxiliary variables that are useful to define said formula; and wherein said requirements data further defines said population selection user interface pattern as defined by a display set and a filter; and wherein said diagrams and textual interactive dialogs receive and process requirements data which allows said designer to enter 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 actions can have preconditions which are entered by said designer by entering requirements data which defines formulas that need to be satisfied before an action can be executed.