CSE 436 Software Engineering Workshop

CSE 436 Software Engineering Workshop

Requirements Definition Document Assignment

First Draft due by Monday February 12, 2007

Each team should please submit the first draft of their requirements definition document(in .doc, .txt, .ps, or .pdf format) to Professor Gill via e-mail at by 10am Monday February 12, 2007 (late submissions not accepted except in extreme cases).

Please giveit a title that reflects the team’s core project idea and the document’s purpose.

Please lista 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 write for clarity, readability, and understanding by a wide audience including people who may never have heard about the project. In particular make sure you provide:

1. a description of what the core idea of your team’s project is, what problem that core idea addresses, and how the core idea addresses that problem;

1. an overview of how your team’s project fits with the other teams’ projects, including describing how any features of your project may depend on features of another project and vice versa (and noting for all such cases which of the features are essential and which if any are peripheral);

1. a listing of requirements for essential features of your team’s project (and optionally for any peripheral features that you would be likely to implement if you have time to do so – please mark those as being peripheral); and

1. a listing of any requirements for any features of other teams’ projects, upon which essential features of your team’s project are likely to depend.

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 requirements definition documents according to the following rubric:

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% qualityof 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, February 16, 2007.