4. The Requirements Specification
An Example
The previous page describes the details held within the Requirements Specification and it does seem quite detailed and complicated.
But if the system is simple, then so can the requirements document.
For example consider a system to catalogue a music collection of mp3 files held in a public library.
| Scope of the system | The system is intended to be only one part of the full library catalogue system. It will handle standard mp3 files but will not be expected to deal with any other file format. {So this section is describing how it fits in the organisation and what it will and will not do} |
| Objectives | * List all mp3 files in a defined folder * Extract title, artist, date from each mp3 file * Store the details in a database * Provide a browsing and search facility for the public to use {The main objectives are now defined, these can be added or changed as the project develops} |
| Timing | The project shall start on 1st September and be complete in three months. After the first month, there will be a review meeting to assess progress {the month-end meeting is a 'milestone' within the project. Most projects define milestones to keep track of progress and to authorise moving on with the project} |
| Inputs | a) The files may be located by the librarian using an 'Explorer' style browsing application. This will allow them it select the files they wish to catalogue on the hard disk. b) There will be an additional input form that allows the librarian to input the following information 1. First name 2. Other names 3. Today's date 4. Comment field {Some input details are described that the developer then needs to implement} |
| Outputs | a) Members of the public will be able to browse the catalogue online. To do this a web-based application will be developed. Output screens will include 1. A list of catalogues available (Classics, Pop etc) b) A reporting screen showing the librarian details of tracks played. {The main outputs of the system is described but not in great technical detail at this stage} |
| Processing requirements | The system will mainly include a database to store file records. Records include 1. Librarian details (from input form) 2. A list of files they selected (from the Explorer application) 3. File details extracted for each track 4. Table holding number of users who have listened to each track the database should be able to hold a million records. A track needs to be selected within two seconds.{ This describes what is done with the input data in order to provide an output, it also describes the performance expected of the system} |
Conclusion
As this example shows, a well structured user requirement specification very effectively sets out the aims of the project. It is mainly non-technical as it forms the 'contract' between the development team and the client.
challenge see if you can find out one extra fact on this topic that we haven't already told you
Click on this link: Requirements Specification