CS4490z/4460z Requirements Report

    (for Software Projects only)

Due: Friday Nov. 21, 2008 at 5 p.m.

Weight: 10%

Hand in:  a single-sided paper document, either to my mailbox in the Computer Science main office (give it to the office staff in MC355) or to my office, MC416 (if I'm not there, slide it under the door).

Note: The Requirements Report must be signed by your supervisor(s) to indicate approval of the requirements content.

---

The Requirements Report should clearly and succinctly identify what the software is to do, what functions it is to support, and what interfaces are required.

The Requirements Report should contain at least the following:

• Title Page (see Report Format and Style Guidelines)
• Project description (purpose of the software system)
• Expected users of the system (what level of expertise?)
• Hardware and software environment required
• Functionality of the system includes:
•  expected inputs to the system
•  for each input, the expected output
•  interfaces

These may be described under the following three categories:

• Basic functions - functions or interface facilities which must be operational for the software to be considered working.
• Desirable functions - additional functions or interface facilities that would be useful.
• Optional functions - functions or interface facilities that would be nice, but are considered extras (i.e. bells and whistles).
  
  
• References (if applicable)

Approximate length:

All projects are different, but an approximate length of 4 to 6 pages (not including Title Page) is suggested. (This is not a hard and fast rule; it is just to give you an idea of the level of detail required for this document.)