17. The process of claim 16 wherein said diagrams and textual interactive dialogs receive and process requirements data from said designer which, if entered, articulate said attributes by defining for each attribute: a name; a formal attribute type of constant, variable or derived; a data type; a default value; whether the attribute is an identifier for distinguishing objects of the class to which it belongs; a length; whether the attribute is required when the object is created; whether the attribute can be assigned a null value; information about valuations that define as a formula how the value of the attribute is changed by the occurrence of an event; and optional information about user interface patterns to be applied in corresponding service arguments related to the attribute.
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.