Вы находитесь на странице: 1из 3

Enter Project Name Here

Enter Department Name Here

Requirements
The following sections document the business requirements of this project. The Requirement Identifiers (Req ID) and Descriptions should be tracked to ensure the design and Test Plans/Cases map to each requirement.
Req. ID

Date

Requireme
nt Type

High Level Requirement

Req #

Functional Specification

1.1.01.1

Priority

Is this
Testable?

Requester

Owner

Is this
Ambiguous?
Yes

Ambiguity
Description

Status

1.1.01

Legal

All Credit and Risk related information for


BOW needs to be sourced into the
Enterprise Data Warehouse as part of the
effort to meet regulatory compliance of the
Basel II accord.

P1-High

Yes

1.2.01

Functional

Extract data from the staging table and load 1.2.01.1 Example: Extract and load all entities and all P1-High
attributes for Teradata table as the data is
the data into the appropriate tables in the
available. The file is available monthly but may
EDW.

Yes

Open

1.2.01.2

Example: The Teradata table should be


P2created in accordance with the target table
Medium
requirements in <document>. The mapping
document also describes the transformation
rules to be applied to the data which is attached
in <section>.

Yes

Closed

1.2.01.3

Example: The CRV process is dependent on


loading this data. It is available within the first
ten business days of the month; however, the
previous months data should not be used to
calculate CRV.

P3-Low

Yes

1.2.01.4

Example: Retain the date of the load for each P3-Low


record to allow for historical tracking.

Yes

1.2.01.5

Example: There are no cleansing rules applied P2to the data.


Medium

Yes

Date
opened

Mandatory
Pending 12-Nov-10
details are not
hilighted

be refreshed mid-month if needed. This is


determined by the source of the data.

Rejected

Resolution

Date
Closed

Enter Project Name Here


Enter Department Name Here

Requirement Ambiguity Review Dashboard (Te


Requirements Distribution by Priority
Priority

P1-High

P2-Medium

P3-Low

# of Req

Requirements D

P3-Low; 33%

P2-Me

Ambiguity Status

Ambiguity Severity

Total

Open

Pending

Closed

Rejected

S1-Critical

S2-Major

S3-Normal

Ambiguity Status

Ambiguity Severity

Rejected; 25% Open; 25%

S1-Critical; 17%
S2-Major; 17%
S5-T
rivial; 17% 33%
S3-Normal;

Closed; 25% Pending; 25%

S4-Minor; 17%

Review Dashboard (Testable)


Distribution by Priority

Requirements Distribution by Priority

P3-Low; 33%

P1-High; 33%

P2-Medium; 33%

iguity Severity

Quality Attributes Summary

S4-Minor

S5-Trivial

Unclear

Incomplete

Inconsistent

Incorrect

uity Severity

S1-Critical; 17%
S2-Major; 17%
7% 33%
mal;

r; 17%

Quality Attributes Summary

Incomplete; 40%
Incorrect; 20%
Unclear; 20%

Inconsistent; 20%