CSE 436 Software Engineering Workshop
Software Requirements Specification Assignment
First Draft due by Monday February 26, 2007

Each team should please submit the first draft of their software
requirements specification (SRS) in .doc, .txt, .ps, or .pdf format
via e-mail to cdgill@cse.wustl.edu by 10am Monday February 26, 2007
(late submissions not accepted except in extreme cases).

Please use a title that reflects the team's core project idea and the
document's purpose, and states that this is the SRS rather than the
requirements definition document (RDD).

Please list a version number (which will increase with each draft of
the document that you submit), and the date of submission.

Please list the names of all the team members who contributed
significantly to the development of the document (all team members are
expected to do so).

Please make sure you provide:

1. a listing of the requirements from your RDD, with a numbered label
   on each requirement (e.g., 1, 2, 3);

2. a breakout of each requirement into several more in-depth
   sub-requirements, each with a numbered label that contains the
   label of the requirement from which it came (e.g., 1.1, 1.2, 1.3,
   and then 2.1, etc);

3. an initial architectural diagram consisting of the major subsystems
   of your project, and illustrating the external interfaces with your
   system's environment, external interfaces with other teams systems,
   and any internal interfaces among the major subsystems of your
   project that are indicated by your requirements breakout;

4. a mapping of the requirements breakout onto the subsystems of your
   project and onto the systems of other teams projects.  Additional
   architectural decomposition of other teams systems may be indicated
   by your requirements, and if so please decompose their system into
   subsystems as needed in your architectural diagram.

Please make sure to check your document for grammatical and spelling
errors before you submit it (treat it as though you were submitting it
as part of a professional product).

We will grade the software requirements specification according to the
following rubric:

25% the initial architecture decomposition and how well the
requirements map to it 

25% document's clarity, readability, and understandability by a
general audience 

25% completeness of requirements in terms of depth and breadth, and
allocation 

25% quality of requirements in terms of concreteness, un-ambiguity,
and cohesiveness

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 2, 2007.