Functional Requirement Document
Functional Requirements Specification
Version: 2.0
Date: 14.06.13
DOCUMENT APPROVAL
Name Position Title Signature Date
Arthur Scargill Users’ representative team /stakeholder group
Benvenuto Cellini Project Manager
Tim Finnegan Business Analyst
Contents
1. Purpose of this Document 4
2. Reference documents 4
3. Scope of the Functional Requirements Specification 4
4. Business Processes 5
User Roles 5
5. Functional Requirements 6
Business Process Name (eg. Receive Incoming Stock) 6
Sub-process Name (eg. Identify Order Details) 7
6. Data and Integration 8
Current Data Access Expectations 9
Governance 9
Known Data Issues 9
Data life cycle and archiving 10
7. Security Requirements 11
Access & Authorisation 11
Authentication 12
Assurance 12
8. Performance 13
9. Availability and Recovery 14
10. Capacity 17
End Users 17
Online Transaction Rates 17
Bulk or Periodic Transaction Rates 17
Data Volumes 19
Data Archive Requirements 19
11. Data Migration & Conversion 19
Data Sources 19
Acceptance Criteria 19
Decommissioning and Archive 19
12. Glossary of Terms 20
13. Document Control 20
Document Status and Revision History 20
Document Distribution 22
1. Purpose of this Document
This document specifies the functions that any proposed solution needs to support in order to meet the high level business requirements, set out in the Business Requirements Statement (BRS). For example a stated business requirement could be “enrol students’. Related functional specifications would include ‘enter, update and cancel student enrolments’ and the specifics for each. The development of the Functional Requirements Specification therefore should occur following the approval of the BRS.
If the solution involves changes to the existing business operation(s) the usual starting point is to create a model of this, identifying the current processes. Process modelling is a useful
Version: 2.0
Date: 14.06.13
DOCUMENT APPROVAL
Name Position Title Signature Date
Arthur Scargill Users’ representative team /stakeholder group
Benvenuto Cellini Project Manager
Tim Finnegan Business Analyst
Contents
1. Purpose of this Document 4
2. Reference documents 4
3. Scope of the Functional Requirements Specification 4
4. Business Processes 5
User Roles 5
5. Functional Requirements 6
Business Process Name (eg. Receive Incoming Stock) 6
Sub-process Name (eg. Identify Order Details) 7
6. Data and Integration 8
Current Data Access Expectations 9
Governance 9
Known Data Issues 9
Data life cycle and archiving 10
7. Security Requirements 11
Access & Authorisation 11
Authentication 12
Assurance 12
8. Performance 13
9. Availability and Recovery 14
10. Capacity 17
End Users 17
Online Transaction Rates 17
Bulk or Periodic Transaction Rates 17
Data Volumes 19
Data Archive Requirements 19
11. Data Migration & Conversion 19
Data Sources 19
Acceptance Criteria 19
Decommissioning and Archive 19
12. Glossary of Terms 20
13. Document Control 20
Document Status and Revision History 20
Document Distribution 22
1. Purpose of this Document
This document specifies the functions that any proposed solution needs to support in order to meet the high level business requirements, set out in the Business Requirements Statement (BRS). For example a stated business requirement could be “enrol students’. Related functional specifications would include ‘enter, update and cancel student enrolments’ and the specifics for each. The development of the Functional Requirements Specification therefore should occur following the approval of the BRS.
If the solution involves changes to the existing business operation(s) the usual starting point is to create a model of this, identifying the current processes. Process modelling is a useful