Skip to main content

Requirements Specification

A high-level requirements specification is required. The purpose of the requirements analysis is to identify requirements for the proposed system. The emphasis is on the discovery of user requirements. Each requirement (or problem) must be defined and documented in the requirements catalogue. Each requirement is recorded in the requirements catalogue on a requirements catalogue entry form. A copy of the form is in the appendix section of the standards manual. The form should be completed as follows:

  • Project/System - the proposed system name or an abbreviation of it.
  • Analyst - your name as the analyst on this project.
  • Date - the date the entry was made in the catalogue, whether it is a new entry or an amended entry, ie another version of an existing entry.
  • Version - a version number is assigned to a requirement. The initial version of a requirement is number one. However, the requirement may need to be updated in the course of the development of the project, so then the requirements catalogue entry will be replaced with the updated version of the requirement and the updated version number will reflect this change.
  • Status - the status of the requirement will be either ongoing or complete. When the status is ongoing the status box will be empty, and when the status is complete the status box will contain a tick (().
  • Page - page numbering will be maintained within the catalogue.
  • Source/Origin - is the originator of the requirement; the person with the responsibility for negotiation about the requirement.
  • Requirement Number - a unique requirement number is assigned to each requirement. The requirement number is an incremental number starting with one.
  • Priority - a priority is assigned to the requirement. The priority given is agreed between the originator and the analyst. There are three priority levels: high (H), medium (M) and low (L). High priority is assigned when the requirement is mandatory. Medium priority is assigned when the requirement is desirable. Low priority is assigned when the requirement is optional.
  • Functional Requirements and Non-Functional Requirements - see next page.
  • Related Documents - reference to any related documents, eg user documentation, data flow diagrams.
  • Proposed Solution - any possible solution or general comments.
  • Actual Solution - records how the requirement is resolved, eg implemented or abandoned. This section will be completed at a later stage when the requirement has reached the completed status.

Next: Functional and Non-Functional Requirements