Requirements Analysis Document
Original base tempalte borrowed from:
- 1 Purpose
- 2 Audience
- 3 Template
- 3.1 Introduction
- 3.2 Current System
- 3.3 Proposed System
- 3.3.1 Overview
- 3.3.2 Functional Requirements
- 3.3.3 Non-Functional Requirements
- 3.3.4 Systems Models
- 4 Glossary
The first section of the RAD is an Introduction. Its purpose is to provide a brief overview of the function of the system and the reasons for its development, its scope, and references to the development context (e.g., reference to the problem statement written by the client, references to existing systems, feasibility studies). The introduction also includes the objectives and success criteria of the project.
Purpose of the System
Scope of the System
Objectives and Success Criteria of the Project
Definitions, Acronyms, Abbreviations
The second section, Current system, describes the current state of affairs. If the new system will replace an existing system, this section describes the functionality and the problems of the current system. Otherwise, this section describes how the tasks supported by the new system are accomplished now.
The third section documents the requirements elicitation and the analysis model of the new system.
The overview presents a functional overview of the system.
Functional requirements describes the high-level functionality of the system.
Nonfunctional requirements describes user-level requirements that are not directly related to functionality. This includes usability, reliability, performance, supportability, implementation, interface, operational, packaging, and legal requirements.
System models describes the scenarios, use cases, object model, and dynamic models for the system. This section contains the complete functional specification, including mock-ups illustrating the user interface of the system and navigational paths representing the sequence of screens. The subsections Object model and Dynamic model are written during the Analysis activity.
Use Case Model
Analysis Object Model
A glossary of important terms, to ensure consistency in the specification and to ensure that we use the client’s terms. A precurser to the Data Dictionary