Due in class Tuesday, December 7, 1999 (Day of Final)

Instructions

You will create an architectual specification of the Cordless Phone using Class and State Diagrams according to the UML notation. You will use Argo/UML to draw the diagrams. The contents of the specifications document are described below.

Hint: inputting a new entry to the address book should be a rich source of classes and states/trasitions/etc (see below).

Note: Part 2 of the document gives you a choice of doing ONE of TWO things.

Note: Part 5 describes Testing, but it describes not a separate section of the document but things to do with the UML notation in Parts 3 and 4.

1. Title Page.
• name
• student id
• date
• assignment name
2. Use Cases or Mockups.
• Repeat either the use case diagrams from Assignment 4 OR the Mockups from Assignment 2 that you are choosing to further specify in this document.
• You do not need to repeat them all, only the ones that you will be refining specifications for.
• Please repeat the textual descriptions for these as well!
3. Class Diagrams. Identify about 12 classes that are relevant to one or more of the use cases you developed in Assignment 4.
• Draw one (more if you like) class diagrams to illustrate and specify the class interactions.
• On a separate page, write a one-sentence description of each class.
• Indicate which use case(s) or mockup segments a class diagram pertains to.
4. State Diagrams.
For one or more of the classes above, draw state diagrams to illustrate potential changes in states over the possible course of interactions. Do enough to have about 12 states and transitions.
• Each state diagram should have several activities (states) and actions (transitions).
• As appropriate, label the state transitions with guards (see below).
5. Test Cases. You will specify more detailed test cases in this assignment. Think in terms of planning for system and unit testing. Specifically attend to the following.
   • Be certain that the attributes in the classes have a type identified. If you need to specify a new type be sure it is defined somehow in your document.
   • Be certain that the class associations are labelled with their cardinality.
   • Label transitions with guard conditions as appropriate. You can expect about half of all transitions to have guards.