Requirements Analysis Document Template

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

<Your System Name>

Requirements Analysis Document


Team: <Your team>
Team Members: <Your team members>

Table of Contents
Introduction............................................................................................................................2
Purpose of the system.....................................................................................................................2
Scope of the system.........................................................................................................................2
Objectives and success criteria of the project.................................................................................2
Definitions, acronyms, and abbreviations.......................................................................................2
Current System.......................................................................................................................2
Proposed System.....................................................................................................................2
Overview.........................................................................................................................................2
Functional requirements.................................................................................................................2
Nonfunctional requirements...........................................................................................................2
Usability............................................................................................................................................................. 3
Reliability...........................................................................................................................................................3
Performance....................................................................................................................................................... 3
Supportability.....................................................................................................................................................3
Implementation...................................................................................................................................................3
Interface..............................................................................................................................................................3
Packaging........................................................................................................................................................... 3
Legal...................................................................................................................................................................3
System models................................................................................................................................3
Scenarios............................................................................................................................................................3
Use case model...................................................................................................................................................3

Glossary..................................................................................................................................3

1
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.
<You can add or remove subsections to this section as needed.>

Purpose of the system

Scope of the system

Objectives and success criteria of the project

Definitions, acronyms, and abbreviations

Current System
<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
Overview

<Overview presents a functional overview of the system.>

Functional requirements

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

Nonfunctional 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.>

2
Usability
Reliability
Performance
Supportability
Implementation
Interface
Packaging
Legal

System models

<System models describes the scenarios, use cases, object model, and dynamic models for the
system. This section contains the complete functional specification.>
<Although it is not required, you can add other sections, e.g., User interface mock-ups to
demonstrate how the system should be used.>

Scenarios

Use case model

Glossary
<A brief and substantial definition should accompany every subsystem and class name.>

You might also like