UC IRVINE - ICS 121 Software Tools and Methods
Assignment 5: Architectual Specification (15%)
|
Due in class Thursday, June 17, 1999 (Day of Final)
(If you turn in the assignment in on Friday June 11, we will attempt to
provide you feedback before the final.)
Instructions
You will create an architectual specification of the Traffic
Problem using Class and State Diagrams according to the UML
notation. You will use Argo/UML to draw the
diagrams. Please refer to the UML Distilled or Schach text to clarify
the syntax and semantics of the diagrams requested below. The
specifications document will consist of the following.
- Title Page.
- name
- student id
- date
- assignment name
- Summary. A two page summary of the contents of the specification document:
- Which apects of the use cases/scenarios (see below) are being
specified?
- Are there exceptions, problems, special considerations in
understand any of the specification diagrams that follow?
- Are there special conditions for testing any aspects of the system
specificied?
- Use Cases.
- Repeat use case diagrams from Assignment 4 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!
- Class Diagrams. Identify about 12-15 classes that are
relevant to one or more of the use cases you developed in Assignment
4.
- Draw one or more class diagrams to illustrate and specify the
class interactions.
- On a separate page, write a one-sentence description of each
class, association, attribute, and operation.
- Indicate which use case(s) a class diagram pertains to.
- State Diagrams.
For two of the classes above, draw state diagrams to illustrate potential changes in states over the possible course of interactions.
- Each state diagram should have several activities (states) and
actions (transitions).
- As appropriate, label the state transitions with guards (see
below).
- 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 more than half of all transitions to have guards.
ICS121
SQ99
David F. Redmiles
Home Page
Department of Information and Computer
Science
University of California, Irvine CA 92697-3425