Page 186 - DCAP308_OBJECT_ORIENTED_ANALYSIS_AND_DESIGN

Object Oriented Analysis and Design

Notes
Refining Attributes for the SavlngsAccount Class
Add the checking attribute to the class. The purpose of this attribute is to implement the
association between the SavingsAccount and CheckingAccount classes.
Figure 1 shows a more complete UML class diagram for the bank system. At this stage, we
also need to add a very short description of each attribute or certain attribute constraints.
For example,
Class ATM Machine
#address: String (The address for this ATM machine.)
#state: String (The state of operation for this ATM machine, such as running,
off, idle, out of money, security alarm.)
Figure 1: A more Complete UML Class Diagram for the ViaNet Bank System

Question
Why do we not need the account attribute for the Transaction class? Hint: Do transaction
objects need to know about account objects?
Source: Bahrami, Ali, “Object Oriented Systems Development,” Tata McGraw-Hill Education

14.3 Summary

The class design phase determines the full definitions of the classes and associations used
in the implementation, as well as the interfaces and algorithms of the methods used to
implement operations.

After analysis, we have object, dynamic and functional model, but the object model is the
main framework around which the design is constructed.

An algorithm may be subdivided into calls on simpler operations, and so on recursively,
until the lowest-level operations are simple enough to implement directly without
refinement.

180 LOVELY PROFESSIONAL UNIVERSITY