FUNCTIONAL REQUIREMENTS DOCUMENT (FRD) <ENTER PROJECT NAME>

Revision History
Version
1.0

Date
<enter date>

Author
Project Manager

Revision Notes
Document creation

TABLE OF CONTENTS
1.0 GENERAL INFORMATION 1.1 2.0 Objective

CURRENT SYSTEM SUMMARY 2.1 2.2 2.3 Background Current Functionality Current Methods and Procedures 2.3.1 Current Deficiencies

3.0

PROPOSED METHODS AND PROCEDURES 3.1 3.2 Summary of Improvements 3.1.1 Functional Improvements 3.1.2 Improvements to Existing Capabilities Summary of Impacts 3.2.1 User Operational Impacts 3.2.2 User Developmental Impacts 3.2.3 Packaging and Delivery to User Assumptions and Constraints

3.3 4.0 5.0

FUNCTIONAL REQUIREMENTS HW and SW REQUIREMENTS 5.1 5.2 Hardware requirements Software requirements

1.0

GENERAL INFORMATION

NOTE TO AUTHOR: Italicized text throughout this template is provided solely as background information to assist you in creating this document. You may delete all such text, as well as the instructions in each section, prior to submitting this document. Place N/A in sections that are not applicable to this project Functional requirements capture the intended behavior (functions or services) of the system. This behavior may be expressed as services, tasks or functions the application, service, or system is required to perform.

1.1

Objective

[Provide the overall objective for this FRD. The project plan should provide adequate detail for drivers behind developing this document]

2.0

CURRENT APPLICATION, SERVICE, OR SYSTEM SUMMARY

Describe the current application, service, or system (in non-computer-oriented language) the existing application, service, or system functions to establish a context for the proposed system. If the existing system is a manual process, describe that.

2.1

Background

[Briefly provide background information concerning the uses and purposes of the current application, service, or system. Refer to interfacing application, service, or systems when needed to enhance the general description.]

2.2

Current Functionality

[Provide a brief explanation of how the current application, service, or system interacts with the functional processes supported. Identify products from other application, service, or systems used with the current system.]

2.3

Current Methods and Procedures

[Briefly describe the current methods and procedures being employed to satisfy the existing information requirements.]

2.3.1

Current Deficiencies

[Briefly discuss deficiencies, including limitations, such as time delays with the current application, service, or system. Note deficiencies in all related systems and processes]

3.0

PROPOSED METHODS AND PROCEDURES

Describe proposed methods and procedures. If functions from an existing application, service, or system are to be incorporated, describe these functions. Explain (in non-computer-oriented language) how the

proposed application, service, or system will interact with the functional processes that the automated application, service, or system will support. Identify products from other application, service, or systems that will be used with, or become part of, the proposed system. If the proposed application, service, or system eliminates or degrades any capabilities in an existing application, service, or system, identifies these capabilities.

3.1

Summary of Improvements

[Explicitly identify the requirements to be satisfied by the proposed application, service, or system under 3.1.1 and 3.1.2]

3.1.1

Functional Improvements

[Discuss functional improvements and new capabilities]

3.1.2

Improvements to Existing Capabilities

[Discuss improvements and upgrades to existing capabilities.]

3.2 Summary of Impacts [Detail in the following subsections, the proposed system on the existing organizational and operational
environments of the user, as well as to the user during the development of the system.]

3.2.1

User Operational Impacts

[Identify the operational impacts to the organization during the use of the proposed. Include the proposed interface between the user and the primary or alternate datacenter centers; the impacts on the user to change from the current operational procedures; new data sources; quantity, type, and timeliness of data to be submitted for use in the application, service, or system and proposed methods for providing input data if these data are not already available.]

3.2.2

User Developmental Impacts

[Identify all user effort that will be required prior to implementation of the application, service, or system, such as development and modification of the database, or required training. Discuss any additional activities to be provided by the user to aid development and implementation.]

3.2.3

Packaging and Delivery to User

[Provide an overview of the medium that will be used to implement any aspect of the product to end users.] y y y y y Delivery of the package to end users Manual System preparation required prior to receiving install package Behavior of the package, its size, performance, criteria checks , reboot Timing, from delivery to installation Communication Interfaces
y

Specific systematic notices to alert users

3.3

Assumptions and Constraints

[Describe any assumptions and constraints that will affect development and operation of the application, service, or system. Identify any limitations affecting the desired capability; any desired capabilities that will not be provided by the proposed application, service, or system, as well as any anticipated operational changes that will affect the proposed operation of the application, service, or system.]

4.0

FUNCTIONAL REQUIREMENTS

Provide a detailed description (in non-computer-oriented language) of the functions to be performed and the performance requirements of the proposed application, service, or system. Functional requirements capture the intended behavior (functions or services) of the system. This behavior may be expressed as services, tasks or functions the application, service, or system is required to perform. [Specify various requirements or any other quantifiable information about the application, service, or system]
Capacity
y y y y y

Anticipated Number of Users Anticipated Number of Concurrent Users Anticipated Number of Locations Anticipated Data Storage Requirements Anticipated Number of Daily Transactions

Have you included the information noted above (or marked it n/a) and added any additional Capacity requirements? Performance y Acceptable Transaction Response Times peak y Acceptable Transaction Response Times non-peak y Batch Processing Schedule Requirements Have you included the information above (or marked it n/a) and added any additional Performance requirements that are needed?

Application Interfaces (within ITICS or external systems) y Interface to Application 1 y Interface to Application X y Description of the operational considerations of data transfer y General description of the data transfer requirements to and from the system, and characteristics of communication media or systems used for transfer y The type of anticipated interface (manual/automatic) y Anticipated interface procedures, including telecommunication considerations Have you included all of the system interfaces, both physical and virtual that must be established for this project?

Input and Output

y y

Reports and queries to be generated by the system Online input, including data from presently used manual processes]

Have you included all reports and queries that need to be generated for this project and operations?

Security Limits y Limited administrative access by Level 2 support y No access by Level 1 support y Require a domain admin account to be operational y Only x - BU and ITICS support must have write access to the system Have you identified at the very least the minimum requirements to ensure the system security and integrity in protect according to company and business regulations? Data Retention y Address the company policy on records retention and how those relate to the requirements of this system Failure Contingencies
y y

Backup: Identify backup requirements for ensuring the continued achievement of system functions. Fallback: Identify fallback techniques for ensuring the continued satisfaction of the specific requirements of the system. Fallback indicates the use of another system to satisfy the system requirements. For example, the fallback techniques for an automated system might be manual manipulation and recording of data. Degraded Modes of Operation: State priorities for restoring the essential functional processing steps in the event that full processing capability is not available.]

Have you included all of the information above and added any additional details around Disaster Recovery? GUI Interfaces
y y y y

Start-up icon for the application is on the desktop and programs menu Application is in the foreground when launched Not appear to users in Add\Remove programs Have a removal executable for support purposes

Have you considered all software behaviors that must occur to meet your requirements?

User Communication Interfaces

y y y y

Start-up icon for the application is on the desktop and programs menu Application is in the foreground when launched Not appear to users in Add\Remove programs Have a removal executable for support purposes

Have you considered all software behaviors that must occur to meet your requirements?

5.0

HARWARE AND SOFTWARE REQUIREMENTS

[If available describe the new technical requirements for improving/correcting the current technical environment (include performance requirements, hardware requirements, and operating environment). Describe what technical requirements are necessary to meet the stated business requirements. Depending on the complexity of the system, these requirements may be a separate document or included in the Specification document. There is a separate Specifications template, as well as a Requirements and Specifications template for smaller systems/validations.]

5.1

HARDWARE REQUIREMENTS
<Requirements>

5.2

SOFTWARE REQUIREMENTS
<Requirement included specific language packs>

Approvers
Date Approver
<Name> <Name> <Name>

Role
Functional Owner Service Owner Project Manager