Precision

Examples of Functional Requirements

A. All users will access the system using a user id and a password.

B. The system shall support the following document formats: PDF, RTF, Microsoft Word 2010 and ASCII text.

C. Every transaction shall be allocated a unique identifier.

D. The system shall have a mechanism to help recover a user’s password.

Ambiguous requirements are interpreted in different ways by developers and users.

For example, ‘recover password’:

User intention – a mechanism that allows the user to view the password after going through an authentication procedure.
Developer interpretation – allowing the user to reset their password so that it can be set again (e.g. using an email link).

Thus, requirements shall be defined as precisely and clearly as possible.

Last updated 10 months ago