Artifact: Analysis Model (Sketch)
The Analysis Model, an optional artifact, contains analysis level classes that describe the key abstractions in the project. This model may also include analysis level use case realizations.
Click the icons for definition
The Analysis Model provides a graphic representation of the key abstractions in the application and is valuable for documenting and communicating the application's analysis class structure. An Analysis Model contains classes representing abstractions of real world concepts in the problem domain and the relationships between those classes. For example, in an insurance application, an Analysis Model may contain classes for Policy, Insured, Accident, and Claim. The relationships between these classes indicate whether an accident can result in multiple claims and so on.
The Analysis Model's static aspects are captured in class diagrams. The dynamic aspects are captured in sequence or collaboration diagrams, which are used to document use case realizations (i.e., how objects of specific classes interact to provide the functionality defined in a use case flow).
The following roles use the Analysis Model:
- The Role: Requirements Analyst uses it to better understand the requirements and the problem domain.
- The Role: Software Architect and Role: Software Designer use it as the starting point for the software design.
- Optionally, the Role: Information Architect and Role: Test Designer may use the Analysis Model to gain a deeper understanding of the significant concepts and relationships described in the requirements.