The likely classes in the application are defined and described in the form of an Object Relationship diagram and a Class Heirarchy Diagram. Abstract classes and inheritance are shown. Composite objects are identified and also collections eg, a business unit may have several employees.
The Object Relationship Diagram below represents the business objects and their relationships
Object Relationship Diagram
An Object Relationship Diagram (ORD) is used to define the likely classes in an application. It does not show the object's data attributes or their behaviour or methods. The ORD will be further refined into Class Hierarchy Diagrams.
Class Hierarchy Diagram Diagram below represents the hierarchy as super-classes and sub-classes and shows classes that contain other classes..
Class Hierarchy Diagram
Class Hierarchy Diagrams show:
Previous Chapter: Analysis & Design: Part Two (Entity/Data Modeling)
Next Chapter: Analysis & Design: Part Four (Business Process Modeling)
Should you wish to have Rodney Collins train your Systems Analysts in the use of SEWO at your premises (Greater Brisbane or South East Queensland), please contact Rodney via the 'Contact' page on this website.
Whether you need all of the Work Breakdown Stages mentioned in this website done from scratch for your next project or perhaps just some of the modeling tasks (e.g. to build 'process maps' from existing Business Requirements, or to document your application's Use Cases, etc, my services are for hire on a freelance basis.
Try my services free for one week - contact me to discuss an arrangement.