- The Basics
- An Example Class Diagram
- The Details
- Conclusion
- Notes
This chapter is from the book
This chapter is from the book
This chapter is from the book
An Example Class Diagram
Figure 3-8 shows a simple class diagram of part of an ATM system. This diagram is interesting both for what it shows, and for what it does not show. Note that I have taken pains to mark all the interfaces. I consider it crucial to make sure my readers know what classes I intend to be interfaces and which I intend to be implemented. For example, the diagram immediately tells you that WithdrawalTransaction talks to a CashDispenser interface. Clearly some class in the system will have to implement the CashDispenser, but in this diagram we don't care which class it is.
)
Figure
3.8 ATM class diagram.
Note that I have not been particularly thorough in documenting the methods of the various UI interfaces. Certainly WithdrawalUI will need more than just the two methods shown there. What about promptForAccount or informCashDispenserEmpty? Putting those methods in the diagram would just clutter it. By providing a representative batch of methods, I've given the reader the idea. That's all that's really necessary.
Again note the convention of horizontal association and vertical inheritance. This really helps to differentiate these vastly different kinds of relationships. Without a convention like this it can be hard to tease the meaning out of the tangle.
Notice how I've separated the diagram into three distinct zones. The transactions and their actions are on the left, the various UI interfaces are all on the right, and the UI implementation is on the bottom. Note also that the connections between the grouping are minimal and regular. In one case it is three associations, all pointing the same way. In the other case it is three inheritance relationships all merged into a single line. The grouping, and the way they are connected help the reader to see the diagram in coherent pieces.
You should be able to see the code as you look at the diagram. Is Listing 3-1 close to what you expected for the implementation of UI?
Example 3-1. UI.java
public class UI implements
WithdrawalUI, DepositUI, TransferUI
{
private Screen itsScreen;
private MessageLog itsMessageLog;
public void displayMessage(String message)
{
itsMessageLog.logMessage(message);
itsScreen.displayMessage(message);
}
}