This assignment has two parts.

Part 1. Group Project Requirements Analysis

Each group is asked to do requirements analysis and build UML class diagrams and interaction diagrams for the group project. The goal is to complete the Requirement Analysis Document (RAD) as outlined in Figure 5-20 on page 200 of the textbook, by providing contents for sections 3.4.3 and 3.4.4 (which was left to be done from the previous assignment). Please read Chapter 5 of the textbook, and follow the steps and examples described in the textbook when doing the assignment.

In particular, class diagrams should be part of section 3.4.3, and interaction diagrams should be part of section 3.4.4. In addition, you are asked to pick at least one of the most complex objects and describe its behavior using a UML statechart diagram, and pick at least one of the most complex operations and describe its control flow using a UML activity diagram.

To build class diagrams, you need to identify and specify what you think are all the classes and relations in the system being built. Similar as for use case diagrams, it is not necessary to draw all classes and relations in one diagram. You should draw multiple diagrams grouping classes and relations that are closer related to each other together.

Also, you should draw class diagrams for existing systems that you plan to use (possibly with modification) as part of the system being built. For such systems, you only need to draw for the parts that your system needs to interact directly with.

For interaction diagrams, in general you should draw one diagram for each use case.

You are asked to draw these diagrams using UML tools. Rational Rose is installed on the machines in the Transaction Lab. You may use other UML tools if you prefer, but you need to specify exactly which tools you used and why you prefer it.

Finally, you are asked to start using the cvs server set up for the course, by first checking in all the documents you have so far about your project.

Part 2. What I did

Describe what you did for the course this week, as in Part 3 of Assignment 1. Please specify your group name along with other identification information at the top of your sheet.

Bonus

1. Of course, the requirements analysis part needs to be based on the requirements elicitation part you wrote last week. You can see now that if you have done a good job last week, then you have an easier time this week. If you do want to improve your document from last week, then please do and include the improved document in the handin; to receive extra credits, at the end of the RAD, you should explicitly state your problems from last week and refer to your fixes in the improved document.

2. As in the Bonus part of Assignment 1.

Handins

For Part 1, each group is asked to hand in a printout (or a handwritten solution, if you didn't succeed in using tools) in class. For Part 2, each person is asked to hand in a separate printout in class.

Grading

This assignment is worth about 4% of the course grade. Each of the two parts is worth 90 and10% of the grade, respectively.