www.reqexperts.

com

<Project Name> Business Requirements

Business Requirements and Attributes (select cell labels for explanation)

Business
Business Requirement Rationale Parent ID Source Groups Impacted Dependencies Conflicts
Requirement ID

[Enter a unique [Business Requirement] [A brief description as to why [Enter the parent id of the [The person or [Groups, individuals, [Factors that will have a [List of requirements
Business the requirement is needed] business requirement as business unit that business units that will direct effect on the to which there are
Requirement ID documented in Project specified the be effected or impacted requirement's realization] conflicts or potential
number] Scope or Business Case] need/requirement] by the requirement] conflicts with this
requirement]

Page 1 06/25/2021
 www.reqexperts.com

<Project Name> Business Requirements

Business Requirements and Attributes (select cell labels for explanation)

Business
Business Requirement Rationale Parent ID Source Groups Impacted Dependencies Conflicts
Requirement ID

[Enter a unique [Business Requirement] [A brief description as to why [Enter the parent id of the [The person or [Groups, individuals, [Factors that will have a [List of requirements
Business the requirement is needed] business requirement as business unit that business units that will direct effect on the to which there are
Requirement ID documented in Project specified the be effected or impacted requirement's realization] conflicts or potential
number] Scope or Business Case] need/requirement] by the requirement] conflicts with this
requirement]

Page 2 06/25/2021
 www.reqexperts.com

<Project Name> Business Requirements

Business Requirements and Attributes (select cell labels for explanation)

Business
Business Requirement Rationale Parent ID Source Groups Impacted Dependencies Conflicts
Requirement ID

[Enter a unique [Business Requirement] [A brief description as to why [Enter the parent id of the [The person or [Groups, individuals, [Factors that will have a [List of requirements
Business the requirement is needed] business requirement as business unit that business units that will direct effect on the to which there are
Requirement ID documented in Project specified the be effected or impacted requirement's realization] conflicts or potential
number] Scope or Business Case] need/requirement] by the requirement] conflicts with this
requirement]

Page 3 06/25/2021
 www.reqexperts.com

<Project Name>: <Level> (System, Subsystem, Subassembly, etc.) Requirements

<Level> Requirements and Attributes (select cell labels for explanation)

Ops Phased
Trace to Parent
Requirement ID Requirement Statement Rationale Verification Concept/Use Allocate to Source Priority Groups Impacted Dependencies Conflicts implmentation - Status
Reqt ID
Case ID Release #
[Enter a unique [Requirement statement] [A brief description as to why [Verification method] [Use Case ID [Enter the name of [Enter the parent [The person or [Assign [Groups, individuals, [Factors outside of this [List of requirements [Enter the release [Denote
requirement ID the requirement is needed] Enter: Test, Analysis, number] the piece of requirement at the business unit that priority business units that will requirement that will have a to which there are number in which whether the
number) Inspection, Demonstration. If the source of system/product next higher level defined the (relative be effected or impacted direct effect on the conflicts or potential this requirement will requirement is
Thinking about how a the requirement is architecture at the to which this requirement] importance) to by the requirement.] requirement's realization] conflicts] be met. This field is Approved,
requirement is to be verified an Operational next lower level to requirement the to be used in cases Rejected,
helps to ensure that the Concept, Use which this traces] requirement. where functionality Designed,
requirement can be verified Case (or requirement is High, Medium, is to be released in Developed,
as written. If you have Scenario), enter allocated. Low or 1 phases (or stages)] Deployed.]
ambiguities (robust) it can't the corresponding Example, a (High), 2
be verified and needs to be reference number system level (Medium, 3
rewritten. for tracing requirement for an (Low) or
purposes. aircraft might be prioritize using
allocated to "Flight your
Control company's
Instrumentation" standard.]
at the next lower
level]

Functional Requirements (Data, UI, Reporting Internal and External), Printing (Internal and External, Exception Processing, etc.)
1.1
1.2
1.3

Non-functional Requirements
Performance (speed, accuracy, volumes, throughput, reliability, availability, safety, etc.)

Look and Feel

Usability

Security

Legal

External Interface

Environmental

Physical

Page 4 06/25/2021
 www.reqexperts.com

<Project Name>: <Level> (System, Subsystem, Subassembly, etc.) Requirements

<Level> Requirements and Attributes (select cell labels for explanation)

Ops Phased
Trace to Parent
Requirement ID Requirement Statement Rationale Verification Concept/Use Allocate to Source Priority Groups Impacted Dependencies Conflicts implmentation - Status
Reqt ID
Case ID Release #
[Enter a unique [Requirement statement] [A brief description as to why [Verification method] [Use Case ID [Enter the name of [Enter the parent [The person or [Assign [Groups, individuals, [Factors outside of this [List of requirements [Enter the release [Denote
requirement ID the requirement is needed] Enter: Test, Analysis, number] the piece of requirement at the business unit that priority business units that will requirement that will have a to which there are number in which whether the
number) Inspection, Demonstration. If the source of system/product next higher level defined the (relative be effected or impacted direct effect on the conflicts or potential this requirement will requirement is
Thinking about how a the requirement is architecture at the to which this requirement] importance) to by the requirement.] requirement's realization] conflicts] be met. This field is Approved,
requirement is to be verified an Operational next lower level to requirement the to be used in cases Rejected,
helps to ensure that the Concept, Use which this traces] requirement. where functionality Designed,
requirement can be verified Case (or requirement is High, Medium, is to be released in Developed,
as written. If you have Scenario), enter allocated. Low or 1 phases (or stages)] Deployed.]
ambiguities (robust) it can't the corresponding Example, a (High), 2
be verified and needs to be reference number system level (Medium, 3
rewritten. for tracing requirement for an (Low) or
purposes. aircraft might be prioritize using
allocated to "Flight your
Control company's
Instrumentation" standard.]
at the next lower
level]

Design and Construction

Other (Rules, Regulations, Audit, Scability, Maintenance and Support, Disaster Recovery, Packaging, Installation, Training, etc.)

Page 5 06/25/2021
 www.reqexperts.com

<Project Name>: <System Name> Requirements: Lifecycle Traceability Matrix

select cell labels for explanation

System Test
Business Code line / Unit Test Case
Business Requirement Use Case # System Requirement ID(s) System Requirement Design Case
Requirement ID program Number
Numbers
[Enter a unique [Business requirement] [Enter the Use Case #(s) that [Enter the unique [This column contains the [Identify the [Code line / [Enter the Unit Test [Enter the
requirement ID addresses this specific business requirement ID number(s) system requirement "shall" location where program. case # that tests the System Test
number) requirement] that address the statements that address the this requirement Identify the code functionality of this Case #(s) that
corresponding business corresponding business is addressed - line(s) / specific requirement] tests the
requirement] requirement] reference the program(s) in functionality of
section number, which this this specific
paragraph requirement is requirement]
number or page satisfied]
of Design Doc
XXX version
yyyy]

1.2
1.3
1.4

Page 6 06/25/2021
 www.reqexperts.com

<Project Name>: <System Name> Requirements Traceability Matrix

select cell labels for explanation

Child Parent
Child Requirement Child Requirement Rationale Parent Requirement Parent Requirement Rationale
Requirement ID Requirement ID

[Enter child Child requirement Child requirement rationale [Enter parent Parent requirement Parent requirement rationale
requirement ID requirement ID
number) number)

Page 7 06/25/2021