Académique Documents
Professionnel Documents
Culture Documents
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
Req #
Functional Specification
1.1.01.1
Priority
Is this
Testable?
Requester
Owner
Is this
Ambiguous?
Yes
Ambiguity
Description
Status
1.1.01
Legal
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
Yes
Closed
1.2.01.3
P3-Low
Yes
1.2.01.4
Yes
1.2.01.5
Yes
Date
opened
Mandatory
Pending 12-Nov-10
details are not
hilighted
Rejected
Resolution
Date
Closed
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
S1-Critical; 17%
S2-Major; 17%
S5-T
rivial; 17% 33%
S3-Normal;
S4-Minor; 17%
P3-Low; 33%
P1-High; 33%
P2-Medium; 33%
iguity Severity
S4-Minor
S5-Trivial
Unclear
Incomplete
Inconsistent
Incorrect
uity Severity
S1-Critical; 17%
S2-Major; 17%
7% 33%
mal;
r; 17%
Incomplete; 40%
Incorrect; 20%
Unclear; 20%
Inconsistent; 20%