CSE 436 Software Engineering Workshop
Architecture Specification Document Assignment
Draft due by 10am Tuesday March 20, 2007 (note new deadline)

Each team should please submit the first 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 March
19, 2007 (late submissions not accepted except in extreme cases).

Please give it a title that reflects the document’s purpose, a version
number, 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 provide:

1. a new version of your architecture diagram in which at least your
   project’s architecture (and, optionally the other teams
   architectures that appear in your SRS architecture diagram) is
   broken out into a sufficient number of modular components that each
   component has only a small number of closely related
   responsibilities;

2. please provide a list of the components in your architecture
specification, giving the following description of each component:

   a. the component’s name, 

   b. a brief description (a sentence or two) of the component’s 
      responsibilities, 

   c. the names of all other components on which it depends, 

   d. the names of all other components that depend on it, and 

   e. the numbers of the requirements from your revised SRS
      document which are mapped to that component (if you need 
      to break out requirements in your SRS further in order to 
      achieve this mapping, please provide a new version of your
      SRS when you submit your architecture specification).

3. a short narrative identifying and justifying each of your decisions
   in breaking out the different components in your architecture
   specification as you did; and

4. a short narrative explaining why you believe the responsibilities
   of each component in your architecture specification are similar
   enough that no further subdivision is needed (until the design
   stage when all decisions must be made).

We will grade the architecture specification documents according to the following rubric:
25% document’s clarity, readability, and understandability by a general audience
25% completeness of rationale for the revised architecture (are all subdivisions justified?)
25% how closely the responsibilities within each component are related
25% how well the SRS requirements map to the components of the architecture

We will assign each document a numeric score out of 100 possible
points, and will give feedback to the teams before and during their
meetings on Friday, March 23, 2007.