3. The process of claim 2 wherein said computer displays said tools in the form of diagrams and textual interactive dialogs of a graphical modeling environment which causes said editor program to act as a graphical editor for said Formal Specification, said computer being controlled by said graphical editor to display tools which are structured to allow said designer to enter requirements data defining an Object Model, a Dynamic Model, a Functional Model and a Presentation Model, and wherein said Object Model stores requirements data which defines a class architecture for said application program via class definitions for classes in said application program, and wherein said Dynamic Model stores requirements data which specifies the behavior of objects in said classes in response to the execution of services, triggers and global transactions wherein said behavior is specified by said designer entering requirements data in a state transition diagram and an object interaction diagram, and wherein said Functional Model store requirements data which defines the semantics of any change of an object's state for all objects in said classes defined in said Object Model, said computer displaying textual interactive dialogs which allow said designer to enter requirements data to specify a class, an attribute of said class and event, i.e., a single service of said class, and define a mathematical or logical formula that defines how the attribute's value will be changed when said event happens, and wherein said Presentation Model stores requirements data which selects patterns from a pattern language and selects and articulates elemental patterns which further define the selected patterns.
2. A process comprising: using an editor program to control a computer to display tools structured to allow a designer who is designing an application program to enter requirements data that comprises articulated conceptual patterns or building blocks from a meta model based upon a formal specification language, said building blocks defining a Conceptual Model that defines at least the desired class structure, behavior and user interface of said application program; and controlling a computer to automatically convert each said building block which has been articulated by requirements data entered by said designer using said tools to complete said Conceptual Model, said automatic conversion occurring as said requirements data of said building block is entered, said conversion resulting in conversion of each said articulated building block into a formal language counterpart thereof written in said formal specification language, and wherein said formal specification has rules of syntax and semantics, and controlling said computer to store said formal language counterparts as a Formal Specification in memory of said computer, and wherein said conversion of each articulated building block into its formal language counterpart occurs without a need for said designer to have any knowledge of how to write formal specifications of computer programs using said formal specification language.