CpSc 372

Assignment 3

Software Architecture

Description:

The initial software architecture for the product line has been determined and documented in a two-volume description available on the website. Review the architecture by constructing scenarios, such as feature additions and modifications, and by identifying changes that must be made in order to (1) add pinball to the product line and (2) add the feature of saving the state of the game to a database.

Steps:

1. Start with the existing architecture model of the product line and the use cases you added in assignment 1.

2. Remember that for a game the highest priority non-functional requirement is smooth action (adequate performance).

3. Use the scenarios from the use cases you added in assignment 1 (you may modify those if you now see improvements that can be made).

4. Walk through the existing architecture using the scenarios to guide you.

5. Identify the user-visible changes that are needed to add pinball (See your pinball use cases from assignment 1)

6. Track those changes into the system (see the scenarios in the pinball use cases) and determine what classes need to be added.

7. Follow a similar procedure with the feature to SAVE the state of the system.

8. As you read these use cases, make additions that are required to improve the use cases.

9. Describe the architectural changes that are needed to accomplish both of these feature changes. You can start with the UML diagrams in the model you downloaded for assignment 1 and modify those. Also use text to describe these changes.

10. Hand in a zip file that contains the meeting log, modified model, text that describes changes that should be made, changed use cases.

This is a 4 person team assignment. Email is due Wednesday, September 24, 2003 no later than 4 pm.

Grading will be based on

1. Completeness

2. Correctness

3. Consistency with existing architecture

4. Any value added beyond the basic assignment

Points: 3