11. User requirements document

The 'User Requirements Document' does not define the hardware or software design but rather seeks to capture the essence of what needs to be done.

Some fairly standard headings within the document are:

An introduction ....

"The project has been developed in order to create a new invoicing system to replace the AIX400 computer system..."

The introduction gives a broad description of the project and its aspirations.

Context ....

"The project was developed in light of the up-coming new regulations and also the increasing awareness that the existing system could no longer meet customer expectations ...."

This section provides the background to the project.

Specific details required

Having provided a broad description and some context to the project this section deals with specific things that need to be included in the system.

Examples:

• The system will be able to use a query to create a mail merged personalised letter.
• The system must create an invoice in less than 3 seconds
• The system will be able to print a management report onto A4 paper, portrait layout.

Notice that these specific requirements are all measurable.

The document should NOT contain vague statements such as "The computer will run as fast as possible..." because you cannot know if 'as fast as possible' has been met when the system finally gets switched on.

The Requirements Specification is the 'contract' between project managers and the client. It will be used at the testing stage to confirm that the system performs as the client expects.