Recording Requirements as Structured Text

Recording Requirements as Structured Text
An Introduction

Prof. David Bernstein
James Madison University

Computer Science Department

bernstdh@jmu.edu

Overview

Desirable Properties of Individual Requirements

Well-Formed
- Atomized (i.e., isolated; written using simple declarative sentences not compound sentences, list, or paragraphs)
- Identifiable/Traceable (e.g., numbered)
- Use the Active Voice
- Use "must" (or the less preferred "shall")
Clear
- Easily understood
Verifiable
- The implementation of each requirement must be verifiable (e.g., testable)

Desirable Properties of the SRS

Uniform
- Similar requirements must be treated in similar ways
Consistent
- One product can satisfy all requirements
Complete
- Includes all relevant requirements (though the notion of relevant might be different in incremental and non-incremental processes)
Feasible
- The requirements can be realized

A Partial Example

Note: The information in parentheses provides a link back to the stakeholders' needs list.