Computer Science Courses

Requirements Specification

The aim of this requirements specification is to generate a document that will give this project a clear direction and limit the scope of what is expected from the client.

This specification will be marked out of 100. And is worth 5% of the final mark (this is a group mark). A late penalty of 10% per day applies (these are working days). Also note this penalty is caped so it does not take your mark for this specification below 40 out of 100. This specification will not be accepted after the last day of semester 1. Extensions are possible in documented exceptional cases (e.g. medical certificate).

The specification must be at most 5 pages and contain the following:

• A title.
• Your names and student ids, the teams and project you are part of.
• Operational Requirements - an external view of the project. This should be about 1 page.
• List the the project stakeholders and how they relate to the project.
• Explanation of how the project fits into the organisation and why it is significant.
• Constraints on the project.
• System Requirements - these are derived from the operational requirements and detail the features and attributes the system must have to meet the operational requirements. As much as possible it should make it clear when the project is complete. The spec should include some base level requirements along with desirable features.
• Explanation about how the team would relate to different aspects of the project.

In-addition to the main 5 page spec you may attach appendices.

Use single column and a 11 point Times-Roman font. The spec must be in pdf format that is viewable on the lab machines.

Marks will be given based on:

• The extent, utility, and quality of the spec created.
• The clarity of the spec.

Assignment Submission

The assignment must be submitted via a computer in the CSIT labs (or remotely via ssh to partch or one of our servers). Only ONE member of your team of 4th years that have the same client needs to submit this specification. If you are in submit the assignment using the following command (replace CLIENT with a short tag for your client e.g. Clapper, Anatomy, Bill, RedHat, ...):

submit comp4500 req requirementsCLIENT.pdf

Note you may also need to give the workshop group you are in, this can be done with the -n option, so if you are in workshop group 2 it would be something like:

submit comp4500 req requirementsCLIENT.pdf -n w2

A few hits for submission:

• Don't have spaces in your file names (the submit program does not like them!).
• Copy the files to your home directory, rather, than having them mounted on a USB drive.
• You may submit as many times as you like, I will mark the most recent one that is not late.