Product Design
Tom Kelliher, CS 245
Sept. 25, 2006
Read SE Chapter 5.
Class diagrams and use case diagrams due Wednesday.
Structured walk-throughs on Friday: Professional, organized informative.
Use display PC, PowerPoint. Plan on 15-20 minutes each.
Unix lab III.
- Questions.
- Team exercises.
Class design.
- Consider the internal and external structure of a banking system
whose functionality and user interface are similar to those you encounter
at your bank's ATM. What elements make up the external structure?
- Outline an object persistence strategy for the previous question.
What characteristics of the banking system predicate your choices and why?
- Develop a deployment diagram that characterizes a very abstract view
of an ATM banking system.
- Create a state machine that portrays the information communicated
between an ATM banking client and a centralized server process that handles
transactions from the ATM.
- If you were to add ``Saved games'' (object persistence) to your
Galaxy Sleuth system, exactly what would have to be saved? What changes
would have to be made to accommodate saved games?
- The main client process will handle the user interface. A secondary
client process will listen for messages from the game server. Create a
state machine that illustrates the communication between the server
listener and the UI controller.
- Decompose two of the states show in Deliverable 4.6 on pg. 129. How
does your answer to the preceding exercise fit into this exercise?
- Using the user interface design principles outlined in the chapter,
critique your Galaxy Sleuth user interface design.
Thomas P. Kelliher
2006-09-24
Tom Kelliher