After you complete the requirements gathering phase, and capture the important details of the system in the use case model, the project enters the analysis phase. The goal of the analysis phase is to create an analysis model that further describes the structure of the system that you are modeling.
The analysis model is a high-level object model of the system that describes the logical implementation of the functional requirements. In other words, the analysis model builds on the use case model by describing the basic structure of the system. You can think of the analysis model as a foundation of the design model, because it describes the logical structure of the application, but does not provide any information about the implementation. The analysis model describes the objects and processes that are described in the use case model, but does not provide technical information about the hardware or software system that is used in the PiggyBank online banking implementation uses.
The PiggyBank analysis model describes both the static and dynamic information that the use case model captures. The analysis model consists of a domain model that describes the static structure of the PiggyBank system, and a set of use case realizations that model the temporal details of the use cases as sequence diagrams. The domain model uses stereotypes to model the functioning parts of the system, called the controller, boundary, and entity classes. These classes are included in a diagram that describes both their structure and their relationship with other elements. The stereotypes describe actual parts of the system without specifying their implementation. The analysis model contains sequence diagrams that realize the use cases by describing the flow of events in a use case. The use case realizations model how the parts of the system interact with the context of a specific use case.
Note: Before you build the PiggyBank analysis model, you should import the PiggyBank use case model that you created in the previous model to ensure that you start the analysis model with a complete and correct use case model. If you import the PiggyBank use case model, it overwrites any previous model with the same name.
To import the use case model, click Import the use case model.
This module explains how to create the analysis model for the PiggyBank onine banking system.
Specifically, this module shows you how to do the following things:
This module takes approximately 1 hour and 30 minutes to complete.