CSE 436 Software Engineering Workshop
Architecture Design Assignment
Draft due by 10am Monday April 2, 2007

Each team should please submit a new design-level draft of their architecture specification document (in .doc, .txt, .ps, or .pdf format) to Professor Gill via e-mail at cdgill@cse.wustl.edu by 10am Monday April 2, 2007 (late submissions not accepted except in extreme cases).

Again, please give it a title that reflects the document’s purpose, a version number that should be greater than the version number of your original architecture specification document, and the date of submission.  Please also list the names of all the team members who contributed significantly to the development of the document.

For this assignment please start with you architecture specification document and:

1. update your architecture specification document to address the concerns, issues, and questions we raised in the feedback we provided to you on March 23.

2. provide a new version of your architecture diagram in which each of the components of your project’s architecture is further broken out into objects, so that each object has a single well defined purpose;

3. extend the list of the components in your architecture specification to say which objects within each component are responsible for which requirements. In general each object should be responsible for a single requirement, but it’s possible that an object could be responsible for a small number of very closely related requirements or that a requirement would be the responsibility of a small number of closely related objects – if you list more than one object for a requirement or more than one requirement for an object, please add a brief statement explaining why that multiplicity is appropriate; and

4. add a new section that provides detailed interface specifications for each of the objects – to save duplication of effort at the implementation stage, you may write your interfaces directly in Java and then for this section turn in either the interface code or javadoc generated from the interface code.

We will grade your architecture designs according to the following rubric:
25% document’s clarity, readability, and understandability by a general audience
25% rationale for the revised architecture (are component subdivisions and any
        multiplicity in the object–to–requirement mapping well justified?)
25% how complete and cohesive are the component and object responsibilities
25% how well the SRS requirements map to the components and objects

We will assign each document a numeric score out of 100 possible points, and will give feedback to the teams by Monday, April 9, 2007 (there will be no team meetings April 6).