|CSC 223||Grinnell College||Fall, 2006|
Class diagrams specify of the classes within a project from a static perspective. That is, class diagrams give a careful description of:
Use cases and sequence diagrams clarify how objects and classes interact during specific processing tasks. Normally, a user will initiate an action. This then triggers a program or method within the software. Processing proceeds through a series of method invocations, finally producing changes in a user display, a database, one or more files, or internal states within objects. Use cases and sequence diagrams differ in notation, format, and focus, but they both provide mechanisms to specify these dynamic interactions within a design.
For this lab, you are to work through the full range of activities that are part of your project.
Develop a list of use cases: normally, there should be a use case for each user interaction (each new screen, each click of a button).
For each use case, clarify (in outline form or in a sequence diagram):
In summary, the content of a sequence diagram should be specified for each use case, although you may use outline form or other verbal description rather than a sequence diagram, if you wish.
After writing a sequence diagram or equivalent, review each stage of processing:
This document is available on the World Wide Web as
created 8 August 2006|
last revised 27 September 2006
|For more information, please contact Henry M. Walker at email@example.com.|