You can use a Functional Requirement document to define a function of a software system and how the system must behave when presented with specific inputs or conditions. These may include calculations, data manipulation and processing and other specific functionality.

Use the Functional Requirements Document to:

  • Specify particular behaviors of a system.
  • Help the reader understand why a requirement is needed.
  • Track requirements through the development of the system.

Table of Contents

1 Introduction
1.1 Purpose of this document
1.2 Scope
1.3 Organization Profile
1.4 Assumptions
1.5 Constraints
1.6 Dependencies
2 Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 Operating Environment
2.4 User Characteristics
3 Functional Requirements
3.1 Functional Requirement n
3.2 Functional Requirement n
3.3 Functional Requirement n
4 System Requirements
4.1 Software Requirements
4.1.1 Software Functionality
4.1.2 Software Characteristics
4.2 Hardware Requirements
4.2.1 Hardware Functionality
4.2.2 Hardware Characteristics
4.3 User Requirements
4.4 Input and Output Requirements
4.5 Communications Requirements
4.5.1 Communications Hardware
4.5.2 Communications Software
4.6 Usability Requirements
5 Non-Functional Requirements
5.1.1 Accuracy
5.2 Audit Trail
5.3 Availability
5.4 Capacity Limits
5.5 Data Retention
5.6 Operational Requirements
5.7 Performance
5.8 Recoverability
5.9 Reliability
5.10 Security Requirements
5.11 Timing
6 Data Requirements
6.1 Data Structures and Relationships
6.2 Data Framework and Relationships
6.3 Data Inputs
6.4 Data Outputs
6.5 Inter-functional Data Definitions
6.6 Component Cross Reference
7 External Interface Requirements
7.1 Software Interfaces
7.2 Hardware Interfaces
7.3 Communications Interfaces
7.4 User Interfaces
8 Design Constraints
8.1 Software Design Constraints
8.1.1 Software Interfaces
8.1.2 Software Packages
8.1.3 Database
8.1.4 Operating System
8.1.5 Tolerance, Margins and Contingency
8.2 Hardware Design Constraints
8.2.1 Hardware Requirements and Environment
8.2.2 Hardware Standards
8.2.3 Hardware Interfaces
8.3 User Interface Constraints
8.3.1 User Characteristics
8.3.2 Environment/Operational Constraints
8.4 Memory Constraints
9 Improvements and Impacts
9.1 Improvements to Existing Capabilities
9.1.1 Upgrades and Enhancements to Existing Capabilities
9.2 Impacts
9.2.1 User Impacts
9.2.2 Operational Impacts
10 Requirements Traceability Matrix

If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Comments:

blog comments powered by Disqus