| Description: |
Defines
a base object model that reflects business needs and how they should be
supported by the solution. This provides some “straw-man” classes that
the Object Interaction Diagrams can be developed from. |
| Risk
& Impact: |
This
work needs to be performed. If not done as a separate task, it will be
done as a part of the Object Interaction Diagrams. Performing this task
prior to the Object Interaction Diagrams provides a more consistent and
well thought out approach to both the object model and the Object Interaction
Diagrams. Not performing this work prior to Object Interaction Diagrams
permits objects to be developed relative to a specific function instead
of cross functional and is therefore more less flexible. |
| Inputs: |
Requirements
Use Cases |
| Upstream
Tasks: |
Reuse
Analysis |
| Downstream
Tasks: |
Logical
Database Design |
| Questions
Asked: |
-
What are the actors defined in the use cases?
-
What are the properties of the actors in the use cases?
-
What are entities are implied by the use cases?
-
What entities does the application architecture and design imply?
-
What entities does the reuse analysis imply?
|
| Iterates
with: |
Requirements
Use Cases |
| Deliverables: |
Domain
Object Model – An object model diagram showing the candidate business
and technology entities and the associated properties. See
DOM Class Descriptions for details on the DOM
Classes. |