The Rumbaugh method 1. it a very friendly and easy methodology. 2.

For traditional system analyst's, the Rumbaugh's methodology is the closest to the traditional approach to system analysis and design, and beginners will recognize familiar symbols and techniques. 3. The Rumbaugh methodology has its primary strength in object analysis but it also does an excellent job with object design. 4. Rumbaugh has three deliverables to the object analysis phase; the Object model, the Dynamic model, and the functional model. These three models are similar to traditional system analysis, with the additions for the object model, including definitions of classes along with the classes variables and behaviors. 5. The Rumbaugh object model is very much like an entity relationship diagram except that there are now behaviors in the diagram and class hierarchies. 6. The dynamic model is a "state transition" diagram that shows how an entity changes from one state to another state. 7. The functional model is the equivalent of the familiar data flow diagrams from a traditional systems analysis. The Booch method 1. Booch's methodology has its primary strength in the object system design. 2. Grady Booch has included in his methodology a requirements analysis that is similar to a traditional requirements analysis, as well as a domain analysis phase. 3. Booch's object system design method has four parts, the logical structure design where the class hierarchies are defined, the physical structure diagram where the object methods are described. In addition, Booch defines the dynamics of classes in a fashion very similar to the Rumbaugh method, as well as an analysis of the dynamics of object instances, where he describes how an object may change state. The Coad-Yourdon method Coad-Yourdon methodology has its primary strength in system analysis. Their methodology is based on a technique called "SOSAS", which stands for the five steps that help make up the analysis part of their methodology. The first step in system analysis is called "Subjects", which are basically data flow diagrams for objects. The second step is called "Objects", where they identify the object classes and the class hierarchies. The third step is called "Structures", where they decompose structures into two types, classification structures and composition structures. Classification structures handle the inheritance connection between related classes, while composition structures handle all of the other connections among classes. The next step in analysis is called "Attributes", and the final step is called "Services", where all of the behaviors or methods for each class are identified. Following analysis, Coad and Yourdon define four parts that make up the design part of their methodology. The steps of system design are:

The problem domain component - This will define the classes that should be in the problem domain. The human interaction component - These steps defines the interface classes between objects. The task management component - This is where system-wide management classes are identified. The data management component - This design step identifies the classes needed for database access methods.

The Shlaer-Mellor method Shlaer-Mellor methodology has its primary strength in system design and is considered somewhat weak on analysis. The Shlaer-Mellor methodology includes three models; the information model, the state model, and the process model. The information model contains objects, variables, and all the relationships between the objects, and is basically a data model for the system. The state model records the different states of objects and changes that can occur between the objects. The process model is really not much more than a traditional data flow diagram. Now that we have covered the basics of the object approach, let's take a look at how a real-world object is created by using these techniques.