In this exercise, you create the Account Operations functional area and the PiggyBank domain model diagram. The domain model diagram describes the domain of the PiggyBank system by using a class diagram that shows the main classes in the system.
The analysis model builds on the Account Operations functional area that you identified in Module 1. The Account Operations package contains the Account Operations Analysis Elements subpackage, as well as the Display Balance, Transfer Money, and Cash Check use case realizations. The Account Operations Analysis Elements subpackage contains the Rational Unified Process® (RUP®) analysis elements that you create when you model the static structure of the model. The package also contains the Account Operations analysis elements diagram, which is used as a workspace for creating the domain level diagrams.
The domain diagram is a type of class diagram that shows the main classes of the PiggyBank online banking system. The simple class diagram shows the main classes that you identified in the previous exercise, the attributes of the classes, and any relationships between the classes. The domain model describes only the domain of the system, and does not describe any details of the application itself. The domain model accomplishes this by modeling only the entity classes of the system and their relationships. The domain diagram is called static, because it models only the structure of the system. In this exercise, you create the entity classes and model their attributes. You identify and model the operations of each entity when you create the sequence diagram for each use case.
Modeling is an iterative process. Your domain model changes as you discover more information about the system that you are modeling. In this tutorial, you outline the basic domain diagram and you model all of the attributes for each entity.
Because the analysis model builds on the use case model, the Account Operations functional area stores the PiggyBank analysis elements and the use case realizations. You must create a new Account Operations functional area in the root of the model.
The Account Operations functional area contains the use case realizations and the analysis elements for the PiggyBank analysis model. The Account Operations Analysis Elements subpackage contains all analysis elements for the project. You can use the Account Operations Analysis Classes class diagram as a workspace to build the PiggyBank domain diagrams.
You create the domain model diagram in the Account Operations functional area, and then copy the visualized model elements into the «perspective» Overviews package of the analysis model template. The Account Operations Analysis Classes diagram is the workspace for creating diagrams, while the «perspective» Overviews package contains only the final copy of the diagrams, and not the classes.
You have created the PiggyBank Analysis Elements diagram. This diagram is a workspace in which you can create and visualize classes within the structure of the functional area. You should create your domain-level class diagrams in this package, and then drag the complete diagrams into the «perspective» Overviews package to complete the model.
The account class represents the PiggyBank user account. The account class describes the functional tasks that are associated with the account class such as getBalance and findForCustomer.
The Transfer class describes the transaction that occurs when a customer transfers money from one account to another. The Transfer class has two associations to the Account class.
You have modeled the Transfer class.
The Transfer class depends on the Account class.
You have modeled the relationships of the Transfer class. Your diagram should look similar to the following figure:
The Check class describes a check that is cashed at the PiggyBank.
You have modeled the Check class. Your diagram should look similar to the following figure:
The Check class depends on the Account class.
You have modeled the relationships of the Check class.
The Customer class describes a PiggyBank customer.
You have modeled the Customer class.
The Account class is dependent on the Customer class.
You have modeled the relationships of the Customer class. You also completed the basic outline of the domain diagram. Your diagram should look similar to the following figure:
The diagram models the basic domain of the system by describing the structure of the main classes of the system and the relationships that exist between them. For example, a customer, who is identified by a unique login ID and name, can own more than one account, but an account cannot belong to more than one customer.
You now create the PiggyBank domain model diagram in the «perspective» Overviews package. This is the final version of the diagram that provides overview and navigation information.
You have created the PiggyBank domain model diagram in the «perspective» Overviews package. This is the final version of your diagram. You can use the Account Operations Analysis Classes diagram as a rough workspace in which to create the use case participants diagrams.
To continue, proceed to Exercise 2.4: Creating the Account Operations use case realization overview diagram.