CpSc 372

Assignment 5

Software Detailed Design

Description:

The initial software architecture has been determined to follow the pipeline simulation loop architectural style. In particular, we will use an integrated Model/View architecture (that is the position of the objects on the gameboard is kept by the objects themselves) to implement the pipeline simulation loop architectural style. There will be components that implement the interaction with the user and components that represent the core concepts - in this case the state of the game.

We are now doing detailed design so we are adding classes that implement the concept we found during domain analysis.

Steps:

1. Start with some of the implementation of the game product line

2. Add to your UML class diagram from the domain analysis. Do a detailed (all 3 window panes) description for each of our classes and only include library classes as a single pane with just the name. Add at least three new classes.

3. Identify the classes that have significant states and create a statechart (for at least 2 classes)

4. Write pre/post-conditions for each significant method in each of the classes

5. Take two use cases and use the sequence diagram notation to document how the system will react for each use case. Create a sequence diagram for the main scenario, one alternative scenario, and one exceptional scenario. Then combine these into an activity diagram. (One for each use case)

6. Examine the design and make suggestions for change. Justify your suggestions with specific criteria.

This is a 2 person team assignment. Hard copy is due Wednesday, October 9, 2002 no later than 4 pm. Turn in to the CS dept office.

Grading will be based on

1. Completeness

2. Correctness

3. Any value added beyond the basic assignment

Points: 4