Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
Requirements Specification
Template
Project Name:
Business Analyst:
Date:
E-MERGE IS A PART OF WELLS GROUP
1
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
Table of Contents
Approvals ........................................................................................................................................................4
1
Introduction .............................................................................................................................................5
1.1 PROJECT PURPOSE (CAN PULL FROM WR) ................................................................................................................. 5
1.2 PROJECT SCOPE AND PRODUCT FEATURES .................................................................................................................. 5
1.2.1
Business Requirements: ...........................................................................................................5
1.3
1.4
1.5
1.6
1.7
OUT OF SCOPE...................................................................................................................................................... 5
PROJECT ACRONYMS, ABBREVIATIONS AND TERMS ...................................................................................................... 5
STAKEHOLDERS ..................................................................................................................................................... 5
IMPACT TO END USERS ...................................................................................... ОШИБКА! ЗАКЛАДКА НЕ ОПРЕДЕЛЕНА.
IMPACT TO INTERNAL USERS – EMPLOYEE WORKFLOW IMPACT ................................ ОШИБКА! ЗАКЛАДКА НЕ ОПРЕДЕЛЕНА.
Design Requirements .............................................................................................................................6
2.1
2.2
2.3
2.4
2.5
2.6
3
USER CLASSES AND CHARACTERISTICS ....................................................................................................................... 6
OPERATING ENVIRONMENT (OE) ............................................................................................................................. 6
USER / TRAINING DOCUMENTATION ......................................................................................................................... 6
GLOBALIZATION / LOCALIZATION REQUIREMENTS (GR) ................................................................................................ 6
ASSUMPTIONS (AS) ............................................................................................................................................... 6
DEPENDENCIES (DE) .............................................................................................................................................. 6
Usage Scenario(s) ..................................................................................................................................7
4
Business Rules (BSR) ............................................................................................................................8
5
Functional Requirements .......................................................................................................................8
2
5.1 FEATURE 1 NAME (INDIVIDUAL FEATURE/OUTPUT OR FEATURE/OUTPUT GROUP NAME) ................................................... 8
Description ...............................................................................................................................................8
6
External Interface Requirements ............................................................................................................9
6.1
6.2
6.3
6.4
USER INTERFACES OR REQUIREMENTS (UI)................................................................................................................. 9
HARDWARE INTERFACES OR REQUIREMENTS (HR) ....................................................................................................... 9
SOFTWARE INTERFACES OR REQUIREMENTS (SR)......................................................................................................... 9
COMMUNICATIONS INTERFACES (CI) ......................................................................................................................... 9
Other Nonfunctional Requirements ......................................................................................................10
7.1
7.2
7.3
7.4
PERFORMANCE AND RESPONSE TIMES (PE) .............................................................................................................. 10
SECURITY REQUIREMENTS (SE) .............................................................................................................................. 10
REGULATORY AND COMPLIANCE REQUIREMENTS (RE), (CP) ....................................................................................... 10
OTHER DATA STORAGE, ARCHIVAL, BACK-UP, RECOVER AND DESTRUCTION (STR) .......................................................... 10
Business Continuity Requirements ......................................................................................................11
8.1
8.2
8.3
9
RECOVERY TIME OBJECTIVE (RTO) ......................................................................................................................... 11
RECOVERY POINT OBJECTIVE (RPO) ....................................................................................................................... 11
INTERDEPENDENCIES ............................................................................................................................................ 11
Warranty Period....................................................................................................................................11
10
Glossary ...............................................................................................................................................11
11
Appendix ...............................................................................................................................................11
7
8
11.1
REFERENCE.................................................................................................................................................... 11
11.1.1 .....................................................................................................................................................11
E-MERGE IS A PART OF WELLS GROUP
2
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
Revision History
Version
.01
.02
.03
.04
1.0
Date
Revision Description
Approved Requirements
E-MERGE IS A PART OF WELLS GROUP
3
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
Approvals
We have carefully assessed the Requirements Specification for this project. This document has been
completed in accordance with the requirements of the System Development Methodology.
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
______ the document is accepted.
______ the document is accepted pending the changes noted.
______ the document is not accepted.
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 system is authorized.
(* = Required)
Executive Sponsor *
DATE
Quality Lead *
DATE
Business Analyst *
DATE
Project Lead or Technical Services Manager*
DATE
If any additional approvals are needed on a project by project basis, these should be added below.
E-MERGE IS A PART OF WELLS GROUP
4
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
1 Introduction
1.1 Project Purpose
1.2 Project Scope and Product Features
1.2.1
Number
BR 1
BR 2
BR 3
BR 4
Business Requirements:
Business Requirement Name
1.3 Out of Scope
1.4 Project Acronyms, Abbreviations and Terms
[List of project-specific terms referenced throughout requirements]
Term
Description
1.5 Stakeholders
Note: All end users are stakeholders, but not all stakeholders are end users. Include any 3 rd Party
stakeholders
Name
Role
Department / Client
E-MERGE IS A PART OF WELLS GROUP
Primary User,
Secondary User, or
Indirect
5
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
2 Design Requirements
2.1 User Classes and Characteristics
User Class
Name
Estimated
Number of
Users
Critical
(Y/N)
How They Use the System
2.2 Operating Environment (OE)
Number
OE 1
OE 2
Requirement
2.3 User / Training Documentation
Name
Description and Format
2.4 Globalization / Localization Requirements (GR)
Number
GR
1
GR
2
Requirement
2.5 Assumptions (AS)
Number
AS
1
AS
2
Assumption
2.6 Dependencies (DE)
Number
DE
1
DE
2
Dependency
E-MERGE IS A PART OF WELLS GROUP
6
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
3 Usage Scenario(s)
E-MERGE IS A PART OF WELLS GROUP
7
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
4 Business Rules (BSR)
Number
BS
1
R
BS
2
R
Requirement
5 Functional Requirements
5.1 Feature 1 Name (Individual Feature/Output or Feature/Output Group
name)
Description
Sentence(s): [Description and/or background information of this feature or feature group, including
assumptions and prerequisite conditions, if applicable. Requirements will be numbered using a three
letter abbreviation for each feature. For example: a look-up feature in the Order Manager Solution
may be labeled as OML-1].
XXX-1
Functional Requirement (The system shall…)
Screen Shots/ Mock-Ups/ Flows
[Insert graphical presentation of the requirements (e.g., screen shots and/or
mock-ups, process flows or models), if applicable. Otherwise you can
remove this section heading]
XXX-2
Repeat section above for each requirement.
XXX-2.1
Sub requirement for Requirement 2.
REPEAT SECTION FOR ALL FEATURES (5.2, 5.3, 5.4, etc.)
Include a section for required output / reports.
E-MERGE IS A PART OF WELLS GROUP
8
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
6 External Interface Requirements
6.1 User Interfaces or Requirements (UI)
Number
Field Name
Object
Type
Completion
Required
Comments
UI
UI
UI
UI
UI
UI
UI
UI
6.2 Hardware Interfaces or Requirements (HR)
[HR
HR
1
2
6.3 Software Interfaces or Requirements (SR)
Number
SR 1
SR
Requirement
2
6.4 Communications Interfaces (CI)
Number
CI 1
CI
Requirement
2
E-MERGE IS A PART OF WELLS GROUP
9
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
7 Other Nonfunctional Requirements
7.1 Performance and Response Times (PE)
Number
PE 1
PE
Requirement
2
7.2 Security Requirements (SE)
Number
SE 1
SE
2
SE
3
SE
4
SE
5
Requirement
7.3 Regulatory and Compliance Requirements (RE), (CP)
Number
RE 1
CP
Requirement
1
7.4 Other Data Storage, Archival, Back-up, Recover and Destruction
(STR)
Number
STR 1
STR 2
Requirement
E-MERGE IS A PART OF WELLS GROUP
10
Doc No :
Issue No :
CCP No :
Date :
QUALITY
TEMPLATE
EDS/QT-02
1
412
15/05/2014
8 Business Continuity Requirements
8.1 Recovery Time Objective (RTO)
Recovery Tier
Tier 1 – Intraday to Next Day Recovery
Tier 2 – Day 3-5 Recovery
Tier 3 – Next Week Recovery
Tier 4 – 2 Weeks+ Recovery
Specific RTO (e.g. 4 days)
Explain the reason(s) for the specified RTO:
8.2 Recovery Point Objective (RPO)
8.3 Interdependencies
9 Warranty Period
10 Glossary
Term
Definition
11 Appendix
11.1 Reference
11.1.1
Source
Location
E-MERGE IS A PART OF WELLS GROUP
11