CSE 436 Software Engineering Workshop
Instructions for Revised Requirements Definition Document
Due by 10am Monday March 5, 2007

Each team should please submit their revised requirements definition document (in .doc, .txt, .ps, or .pdf format) to Professor Gill via e-mail at cdgill@cse.wustl.edu by 10am Monday March 5, 2007 (late submissions not accepted except in extreme cases).

As for your first draft, please write for clarity, readability, and understanding by a wide audience including people who may never have heard about the project.  Please increase the document’s version number from the version number that was on the first draft, and please list the new date of submission.  Please revise your RDD as follows:

1. please address any concerns that we raised about the first draft of the document, according to the feedback we provided;

2. add (or update if you already had one) a table of contents that should appear after the title page, which lists the major sections and subsections of your document (including where to find the glossary – see next);

3. add (or update if you already had one) a glossary containing all the technical terms used in the document, which should list each term and give a concise but rigorous definition of its meaning; and

4. add a new section containing paragraphs that name and describe the external interfaces that your system will have, to the environment (including users of the system) and/or to other teams’ systems;

As before, please 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 revised requirements definition documents according to the same rubric we used to grade their first drafts:

25% how well the nature of the problem (which the core idea addresses) is captured
25% document’s clarity, readability, and understandability by a general audience
25% completeness of requirements for essential features (any key issues missing?)
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 9, 2007.