Techno functional dcoument template v1.0

Design document template to track functional detail along with majority of design details. Useful to have single document for both functional specification and technical desing

1. 1 < Document Header >
TECHNO FUNCTIONAL
DOCUMENT
<Project Name>
<Month, Year>
Prepared By
<Name of Author(s)>

2. 2 < Document Header >
Functional and Technical Requirements Document
Authorization Memorandum
I have carefully assessed the Functional and Technical Requirements Document for the
(< Project >) .
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
We fully accept the changes as needed improvements and authorize initiation of work to
proceed. Based on our authority and judgment, the continued operation of this project is
authorized.
_______________________________ _____________________
NAME DATE
Business Analyst
_______________________________ _____________________
NAME DATE
Architect /Tech Lead
_______________________________ _____________________
NAME DATE
Lead
_______________________________ _____________________
NAME DATE
Developer
The document is not accepted
The document is accepted pending changes noted
The document Is accepted

3. 3 < Document Header >
TABLE OF CONTENTS
Page #
1.Revision..................................................................................................................................4
1.General Information.............................................................................................................5
1.1.Purpose...........................................................................................................................5
1.2.Scope..............................................................................................................................5
1.3.Exclusions........................................................................................................................5
1.4.Assumptions....................................................................................................................5
1.5.Project References........................................................................................................5
1.6.Acronyms and Abbreviations......................................................................................5
1.7.Points of Contact...........................................................................................................5
2.Current System Summary....................................................................................................6
2.1.Current Feature Details.................................................................................................6
2.2.Current Design (Workflow)...........................................................................................6
3.Functional/Technical Requirements..................................................................................6
3.1.Summary of Functions...................................................................................................6
3.2.Functional Details..........................................................................................................6
3.3.Functional Uses Cases...................................................................................................6
3.4.Design Details.................................................................................................................7
4.Impact Summary..................................................................................................................7
4.1.Development.................................................................................................................7
4.2.Functional.......................................................................................................................7
4.3.Operational....................................................................................................................7
5.Performance Requirements................................................................................................7
5.1.Specific Performance Requirements..........................................................................8
6.Data Correction/Utility Requirements................................................................................8
7.Additional System Requirements........................................................................................8
7.1.System.............................................................................................................................8
7.2.Integration......................................................................................................................8
8.Security...................................................................................................................................8
8.1.System Security..............................................................................................................8
8.2.Other Security................................................................................................................9

4. 4 < Document Header >
1.REVISION
Revision No.Primary Author(s)/Reviewer Description Date Completed
1.0 <Author Name> First Draft <Date>
2.0 <Author Name> First Revision <Date>
3.0
4.0

5. 5 < Document Header >
NOTE TO AUTHOR:
1.Highlighted text throughout this template is provided solely as background information to
assist developer in creating this document. Please delete all such text, as well as the
instructions in each section, prior to submitting this document. ONLY YOUR PROJECT-
SPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF THIS DOCUMENT .
The Functional Requirements Document provides the user a clear statement of the functional
and requirements of the system in order to address the problem or to accomplish the
enhancement.
2.Light blue highlighted text throughout this template identifies where your will need to inject
or customize the information.
1.GENERAL INFORMATION
1.1.Purpose
1.2.Scope
1.3.Exclusions
1.4.Assumptions
1.5.Project References
1.6.Acronyms and Abbreviations
1.7.Points of Contact
1.7.1.Information & Coordination
Provide a list of the point(s) of organizational contact (POCs) that may be needed by
the prospective solution provider for informational and coordination purposes. Include

6. 6 < Document Header >
type of contact, contact name, department and e-mail address (if applicable), and
project oversight function. Oversight responsibilities include, software implementation
and training, financial administrator, problem resolutions, etc.
Below is a list of Point of Contacts relevant to this project:
Contact NameContact TypeDepartment Email Oversight Function
Business
Analyst
Implementation
Problem Resolution
Operation
Engineer
Setup/Installation
Configuration
Training
2.CURRENT SYSTEM SUMMARY
This chapter will include summary of the project under enhancement with respective to
proposed <Project>. It will applicable for all <Project> except new <Project>.
2.1.Current Feature Details
2.2.Current Design (Workflow)
3.FUNCTIONAL/TECHNICAL REQUIREMENTS
In this section, list and describe the functions you want your <Project> to be able to do.
Describe proposed data collection and flow. If functions from an existing system are to be
incorporated, describe these functions. Explain (in non-computer-oriented language) how the
proposed system will interact with the service delivery system it is meant to support. Identify
products and other systems that could be used with, or become part of, the proposed system.
Describe the relationship between the project and other capacities being developed concurrently
(if any).
3.1.Summary of Functions
In this section describe high level listing of functional scope
3.2.Functional Details
Enlist all the functional details including DT, Validation, and Jobs etc
3.3.Functional Uses Cases

7. 7 < Document Header >
Uses from developers point of view
3.4.Design Details
Following are the design details can be included.
3.4.1.Component
If applicable
3.4.2.Activity/Flow
If applicable
3.4.3.Sequence
If applicable
3.4.4.ERD
If applicable
4.IMPACT SUMMARY
4.1.Development
Impact from code and database side
4.1.1.Key Additions/Changes in Code
4.1.2.Key Additions/Changes in Database
4.2.Functional
Enlist impact by module and feature wise
4.3.Operational
5.PERFORMANCE REQUIREMENTS

8. 8 < Document Header >
This section provides a detailed description (in non-computer-oriented language) of the
performance requirements of the proposed system
5.1.Specific Performance Requirements
5.1.1.Accuracy and Validity
In this section include the data quality assurance techniques, including but not limited
to:
·Input masks (data validations)
·Completeness requirements (Activity, Audit Log etc)
·Post/Pre processing (WQI, Correspondence)
5.1.2.Timing
5.1.3.Capacity Limits
6.DATA CORRECTION/UTILITY REQUIREMENTS
This section will highlight additional things required and which will be delivered as utility
(one time or on demand executable)
7.ADDITIONAL SYSTEM REQUIREMENTS
This chapter may be used to document additional technical requirements when they do not
directly relate to the functions and performance that is obvious to the user, and therefore have not
been described previously
7.1.System
7.2.Integration
8.SECURITY
8.1.System Security
8.1.1.User Authentication and Authorization Details

9. 9 < Document Header >
8.2.Other Security
8.2.1.Firewalls
8.2.2.Public Access
8.2.3.System Monitoring

10. 9 < Document Header >
8.2.Other Security
8.2.1.Firewalls
8.2.2.Public Access
8.2.3.System Monitoring