User Requirements Document

Name of the group (edit)

Version

Date

Author

Description

1.00 8.8.2005 Aaltio, Vanhanen  

Contents

1. Purpose of the document
2. Business goals
3. Main domain concepts
4. System overview
5. User groups
6. Functional requirements
7. Non-functional requirements (quality requirements, properties)
8. User requirements
9. Constraints
10. Solution ideas
11. Acronyms and abbreviations
12. References

1. Purpose of the document

The purpose of this document is to define requirements for system XXXXXXX (name of the system).

The intended audience of this document is described in table 1.

Table 1: Intended audience of this document.

Group of the readers

Reasons for reading

Users and customers

To give feedback about the requirements

System developers

To understand what functions and properties the system must contain

Testers

To test the system against the requirements

Writers of user manuals

To get material for user manuals

Project team

To follow-up the status of the project against the requirements

2. Business goals

This section describes the business problem (or business goals), in other words the reasons why the customer wants to develop a new system.

Describe shortly the current way of doing business and the potential improvements the customer expects from the new system.

3. Main domain concepts

This chapter gives a brief introduction to the problem domain. It might include

Table 2. Main domain concepts of the users

Concept

Description

Loyal Customer

Someone who has registered with Company xxx web site. Gets special prices and offers. All his orders are registered in the database.

 

 

4. System overview

This section is a high level description of the intended solution (=the system). It might include

5. User groups

This section describes intended users of the system.

Table 3. Users of the system

User group

Description

Number of users

User group A

 

n persons

User group B

 

 

6. Functional requirements

This section defines the functionality (services) that the system must provide in order to meet the business goals.

Functional requirements can be organized in several ways, e.g. by feature or by use case. The layout can be determined by each group – the example layout below can be used.

ID

Ver

Feature

Requirement

Source

Rationale

Priority

Status

Traces to use cases

F1

1

Ordering

The user shall be able to order any company xxx product.

Product Manager N.N.

With the current site, all products cannot be ordered. According to user interviews, users don’t want to order anything since they cannot order everything they want at the same time.

Must

Proposed

Order goodies

F2

1

Ordering

Loyal customers shall be able to get special prices and offers.

Product Manager N.N.

We want everybody to be loyal customers.

Must

Proposed

Order goodies, browse products,

7. Non-functional requirements (quality requirements, properties)

Non-functional requirements are documented in this section. The layout can be determined by each group – the example layout below can be used.

ID

Ver

Requirement

Source

Rationale

Priority

Status

Traces to use cases

S1

1

Only registered users are allowed to use the system

Security Manager S.M.

Confidential information must not leak out of the company.

Must

Proposed

Register, Login, Logout

O1

1

It shall be possible to use the system with a portable phone (wap).

Product Manager N.N.

The whole point of the new system is to enable customers to order wireless.

Must

Proposed

Order goodies

8. User requirements (use cases)

Use cases are strongly recommended to be used in documenting user requirements. The following sections are typically included in use case descriptions:

Name

Login

Summary

The user is requesting a function that requires the user to be registered. The user must be identified.

Actors

Any user.

Preconditions

-

Basic Sequence

1. The system requests an identification (username, password)
2. The user enters his username and password.
3. The system checks the validity of the username and password.
4. The system grants the user access to the system.

Exceptions

4a. If the identification is not valid, the message “You are NOT welcome here” will be given.
4b. If the identification is valid but the password has expired, the message “Your password has expired. Please enter new password” will be given. The user has to enter the new password twice identically. The password will be changed and the user will be granted access to the system.

Post Conditions

A valid user has been granted access to the system.

Priority

Must

Status

Implemented

Traces to requirements

S1

Traces to test cases

T1, T2, T3.

9. Constraints

In this section, solution constraints are listed. These might include

ID

Ver

Constraint

Source

Rationale

Priority

Status

Traces to use cases

C1

1

The user interface must run on any well-known browser including IE, Opera and Mozilla.

Technical Coordinator N.N

People have different browsers – we want to serve them all.

Must

Proposed

All use cases with browser interface

10. Solution ideas

A list of possible solution ideas that came up during requirements definition - and possibly a short description of each idea. Keep it short!

ID

Ver

Solution idea

Source

Rationale

Traces to use cases

SI1

1

Special offers could be shown in the left-most column - the way they are shown at amazon.com

Technical Coordinator N.N

This came up when our usability specialist evaluated several interesting sites where products are sold.

Order goodies

11. Acronyms and abbreviations

A glossary explaining the special terms and abbreviations used in this document are explained here.

Table x. Acronyms

Acronym/abbreviation/special term

Description

 

 

 

 

12. References

List here all the documents that have been used as an information source and are necessary for understanding of this document. List also other specifications that have been used as a reference.

Table x. A list of all other relevant documents

Name of the document

Short description of the document contents