Friday, 22 February 2019

Functional requirements document checklist | Project Templates

This checklist is provided as part of the evaluation process for the Functional Requirements Document (FRD) submitted to sponsors / top management.  The checklist assists designated reviewers to determine whether specifications meet criteria acceptable to sponsors upon the submission of the FRD.

The objective of the evaluation process is to determine if the document complies with project / customer requirements.

Attached to this document is the document review checklist.  Its purpose is to assure that documents achieve the highest standards relative to format, consistency, completeness, quality, and presentation.
Submissions must include the following three documents, and must be presented in the following order:

(1)    Document review checklist
(2)    Functional requirements document checklist
(3)    Functional requirements document.

The document author is required to complete the two columns indicated as author reference, page number and section, author comments before the submission. Last two columns marked as comply and reviewer comments. Do not complete it, since these are for the designated reviewers.

Define Purpose & Scope of Functional requirements document (FRD)

Purpose is to include in this subsection contains an explanation of the functional description. Scope is to include in this section describes the scope of the Functional Requirements as it relates to the project.

Describe the points of contacts.

Information: Provide a list of the points of organizational contact that may be needed by the document user for informational and troubleshooting purposes
Coordination: Provide a list of organizations that require coordination between the project and its specific support function.  Include a schedule for coordination activities.

Functional requirements document checklist template

Functional requirements document checklist template

What to include in functional requirements document checklist?

Provide background information concerning the uses and purposes of the system. The System Objectives and Current Functionality.  Provide the major performance requirements and goals of the proposed system.

Current Methods and Procedures: Describe the current methods and procedures that address the existing information requirements.  The following information is included in this explanation.

Proposed methods & Procedures

Summary of Improvements:  Explicitly identify the requirements to be satisfied by the new system. 1. Functional Improvements, 2. Improvements to Existing Capabilities, 3. Timeliness
Summary of Impacts: Summarize the anticipated impacts and associated costs of the proposed system on the existing organizational and operational environments

  • User Organizational Impacts 
  • The user Operational Impacts 
  • User Developmental Impacts

Assumptions and Constraints:  Describe any user assumptions and constraints that will affect development and operation of the system

Details of characteristics

Specific Performance Requirements: Describe the specific performance requirements for the system for all major functions or subsystems within it.

Accuracy and Validity:  Describe the accuracy requirements for the system
Timing.  Describe the timing requirements for the system
Capacity Limits:  Describe the estimated amount of transactions, storage requirements, concurrent users, or any other quantifiable information about capacity requirements.
Functional Area System Functions:  Describe by function the major processing steps.
Input and Output:  Provide a general description of each of the batch and online inputs and outputs
Failure Contingencies: Discuss alternative courses of action to satisfy the information requirements if the proposed system fails.

Design Consideration

(1) System Description:  Provide a general description of the design of the proposed system. (2) System Functions:  Discuss the functions of the proposed system. (3) Flexibility:  Discuss the capability for modification to the system to be incorporated in the design.


Equipment Environment:  Describe the equipment capabilities required for the proposed system.
Software Environment:  Describe the support software that the application software will interact with. Address authority approval of non-standard items
Communications Requirements:  State the general communication requirements of the system being developed

  • Communications Overview -  Provide a graphic representation or diagram, which shows the known communication requirements of the system
  • Communications Hardware -  List the known communication hardware required to support the system being developed.
  • Communications Software - List the known communication software requirements of the system being developed.
  • Interfaces:  Describe all interfaces with other application systems and subsystems
  • Summary of Impacts:
  • Organizational Impacts:  Describe the modifications of positional responsibilities that will be required by the proposed system
  • Operational Impacts:  Discuss impacts on the operational procedures of the information processing centers to implement the system
  • Developmental Impacts:  Describe the personnel and resources necessary for the development and testing of the automated system.

No comments:

Post a Comment