|
|
Entity-Relationship diagrams with OOIE-style notation. | |
Object Interaction diagrams, ala Jacobson et al. | |
The Hatley-Pirbhai methodology (HPM). | |
OO Information Engineering builds upon OOAD, OMT, etc. | |
Entity-Relationship diagram. | |
Rumbaugh's Object Modeling Technique. | |
OO decomposition via Domains. | |
Grady Booch's infamous clouds. | |
The merger of Booch, Rumbaugh, Jacobson, et al. |
|
|
- Good modeling diagrams based upon Coad/Yourdon (OOA/D) and Rumbaugh's Class Diagrams (OMT).
- Favours Java conventions. - UI intuitive & allows designer to concentrate on OO-modeling vs drawing. - Useful for pre-design thru to implementation. - Inexpensive Windows (NT,95,Win32) shareware program! |
|
- Modeling supports Booch & Rumbaugh/OMT.
- Complete design model, including support for:
- UI intuitive & allows designer to concentrate on OO-modeling vs drawing. - Useful for design thru to implementation. - C++ Analyser converts source code into Class Models. |
|
- UML support includes:
- Useful for design thru to implementation. - Whiteboard is free (crippleware). - Other (not free) TogetherSoft products (Solo, Enterprise & ControlCenter) provide multi-user/team development, built-in CVS, document generation, code building, etc... |
|
- Good example palettes for UML, Booch, Jacobson, OMT, HPfusion, ...
and numerous other standard business & technical charts, forms & diagrams. - Intuitive and good drawing/modeling tools. - No capabilility to define class/object internals for code or data dictionary relationships. - Useful for pre-design or high-level diagrams & charts. - Inexpensive shareware with UNIX (Sun,HP) & Windows (NT,95) versions! |
|
- Not specifically designed for software modeling, thus favours no technique.
- UI fairly intuitive, but user must draw and cannot concentrate on design modeling. - Useful for simple, informal drawings. - Difficulties scaling non-trivial designs. |