Requirements Analysis Document

From SILO Knowledge Base
Jump to navigation Jump to search

Original base tempalte borrowed from:

https://www.cs.fsu.edu/~lacher/courses/COP3331/rad.html

Purpose

Audience

Template

Introduction

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

References

Overview

Current System

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.

Proposed System

The third section documents the requirements elicitation and the analysis model of the new system.

Overview

The overview presents a functional overview of the system.

Functional Requirements

Functional requirements describes the high-level functionality of the system.

Non-Functional Requirements

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.

Usability
Reliability
Performance
Supportability
Implementation
Interface
Packaging
Legal

Systems Models

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.

Scenarios
Use Case Model
Analysis Object Model
Dynamic Model
User interface --navigational paths and screen mock-ups

Glossary

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