This document lists the features of the product and the various functionalities that must be available in the product. You can use this document to update the User’s guide and Online Help and other end user documents where the functionality of the system needs to be clearly explained.
Typical sections of the functional requirements document include the following:
- Purpose and scope – This section describes the basic purpose of the system, along with identification details of the system. It also includes the scope of the system and the performance of the system within this scope.
- Assumptions and constraints – This section provides a list of all technical, legal, and task-level assumptions and constraints that have an impact of the system. Assumptions include the details of situations that are beyond human control and have an impact on the success of the system. Constraints list the limitations within which the system must be designed. Legal requirements, business conditions, market situation, and other technical and socio-economic conditions fall under the category of constraints.
- User requirements – Along with providing a list of users and the different classes/categories of users, this section provides detailed description about all the users. All the functional requirements are related to the needs of the user. The user requirements can either be in the form of text or process flow diagrams.
- Data Flow Diagrams – A DFD is a graphical representation of the flow of the data through the various components in an information system. The data that flows within the components through the sub-components will also be depicted using DFDs.
- Functional requirements – This section includes the list of functions that are expected to be developed as a part of the system. You can use this information to understand the features of the system and develop the end user guides. However, you need to decipher information that is relevant to the end user in the context of your audience analysis.
- Performance requirements – This section includes the performance expectations from the system with regard to all the functional aspects of the system.