DoIT RequirementsCollectionTemplate

8/20/2019 DoIT RequirementsCollectionTemplate

1/10

REQUIREMENTS COLLECTIONREQUIREMENTS COLLECTION

TTEMPLATEEMPLATE

A GUIDE FOR REQUIREMENTS GATHERING AND TRACE-ABILITYA GUIDE FOR REQUIREMENTS GATHERING AND TRACE-ABILITY

MATRIX DEVELOPMENTMATRIX DEVELOPMENT

R EVISION: 1.0


2/10

Department of Information Technology Requirements Collection Template

ABOUT THIS DOCUMENT.....................................................................................3

GUIDELINES FOR USING THE REQUIREMENTS COLLECTION TEMPLATE...................4

Requirement ID:..................................................................................................................4

Requirement Type................................................................................................................4Parent Requirement#:.........................................................................................................5Source and source Document:.............................................................................................5Dependencies:.....................................................................................................................5Defnitions o Priorities:.......................................................................................................5

Tracking Requirements and status.......................................................................................Status Options:................................................................................................................6Change History:...............................................................................................................6

!"arifcationspecifcation o Requirement...........................................................................Rationale:........................................................................................................................6

Acceptance/Fit Criteria:...................................................................................................6Dependencies:.................................................................................................................6

THE REQUIREMENTS COLLECTION TEMPLATE FORM..............................................7

REQUIREMENTS TRACEABILITY MATRIX...............................................................8

2


3/10


ABOUT THIS DOCUMENTABOUT THIS DOCUMENT

Requirements are the foundation of the project and the development of the product that the project has been organized to develop. The purpose of this document is to present a standardized

requirements collection template.

The template proposed in this document serves a variety of purposes. It is intended for all typesof project requirements:

• usiness

• !ser

• "ystem

• #unctional

• $on%#unctional

The template is useful for the development of a traceability matri& because it trac's a

requirement to its parent requirement( and requests the source and or document from )hich therequirement came.

The template also supports specific( measureable( attainable( realistic and testable requirements

by as'ing for supporting clarifications for the requirement.

Recognizing that not all requirements are included in the final product( the form also trac's the

priority and the history of the requirement.

The collection template is intended to be copied and pasted into the various documents that formthe chain from business requirements( to user( system requirements and operational

requirements. *art of the template references use cases if the project calls for them and traces

these bac' to a specific requirement.

3


4/10


GUIDELINES FOR USING THE REQUIREMENTS COLLECTIONGUIDELINES FOR USING THE REQUIREMENTS COLLECTION

TEMPLATETEMPLATE

REQUIREMENT ID:REQUIREMENT ID:

• Every requirement needs to be uniquely identified. The Requirement ID is the unique

label given to that requirement. Each team can develop its unique numberingconvention. Here is an eample naming convention!

• "usiness Requirement # "$a

o %"#"usiness& $#"usiness req. number& a#first revision'

o (ote! "usiness requirement number should al)ays be a )hole number

value.'

• *ser Requirement # *$.$a

o *#*ser& $#business req. number %detailed by this user requirement'& $#*ser req. number& a#first revision'

o (ote! *ser requirement number should al)ays follo) a business

requirement number& and al)ays be in the second position.'

• +ystem Requirement # +$.$.$a

o %+#+ystem& $#bus. req. num.& .$#*ser req. number %detailed by this

system requirement'& $ #+ystem req. number& a#first revision'

o (ote! +ystem requirement number should al)ays follo) a user

requirement number& and al)ays be in the third position

REQUIREMENT TYPEREQUIREMENT TYPE

#or requirements derived from the business( users( and system requirements( use the

requirements type field. This )ill enable you to place the form in the appropriate section of theuser and system requirements document.

Requirements Types!

• ,unctional Requirements

- "ehavioral

- Data- *ser Interface

• (on-,unctional Requirements


5/10


- Hard)are - *ser +ecurity

- +oft)are - /egal

- (et)or0 - 1rivacy

- Integration - +oft)are /icensing

- rchitectural - Documentation

- 1erformance - ultural41olitical

- Data 5anagement - Internationali6ation4/ocali6ation

- 1roduction +upport - +afety

PARENT REQUIREMENT#:PARENT REQUIREMENT#:

• Requirements have a natural hierarchy. They flo) from high-level business requirements

to user requirements& ultimately to system requirements. This field captures the higher

level requirement for the one described. %e.g.& The business requirement 7 %1arent' thata user requirement %child' provides additional detail for should be place in this field.

SOURCE AND SOURCE DOCUMENT:SOURCE AND SOURCE DOCUMENT:

• +ource )ould be individuals or groups )ho have proposed this requirement.

• The source document is any reference document that either generated the requirement

directly& or )as the impetus for its creation. %e.g.& user requirement developed from aprocess )or0 flo) model should reference the )or0 flo) model in this field.'

DEPENDENCIES:DEPENDENCIES:

• Dependencies are other requirements %not contained in the parent-to-child relationship'

that are critical to successfully implementing the stated requirement. %e.g.& This systemfunctional requirement has a dependency on a specific data system requirement& in)hich if the data requirement is not satisfied& the functional requirement cannot besatisfied.'

• Dependencies are usually only captured for the same level of requirement hierarchy

%e.g.& user req. dependant on another user req.& system req. dependant on anothersystem req.'.

o (ote! It is not necessary to capture all requirement relationships in thissection. It is only required to capture critical dependencies.

8


6/10


DEFINITIONS OF PRIORITIES:DEFINITIONS OF PRIORITIES:

• Essential # +ystem not acceptable unless this requirement is provided in an agreed

manner.

• onditional # )ould enhance the system& but )ould not ma0e it unacceptable if absent.

• +ptional , -ight be )orth)hile if resources permit.

TRACKING REQUIREMENTS AND STATUSTRACKING REQUIREMENTS AND STATUS

SSTATUSTATUS OOPTIONSPTIONS::

$e)( agreed%to( base%lined into project documents( rejected.

CCHANGEHANGE HHISTORYISTORY::

This field is used to trac' any changes in )ording or detail including requirement status.

CLARIFICATION/SPECIFICATION OF REQUIREMENTCLARIFICATION/SPECIFICATION OF REQUIREMENT

R R ATIONALEATIONALE::

hat is the importance( value or purpose of the requirement/

AACCEPTANCECCEPTANCE/F/FITIT CCRITERIARITERIA::

0o) )ill )e 'no) if the requirement has been met/ 1re there measurements/

DDEPENDENCIESEPENDENCIES::

hat other requirements or factors )ill this requirement be dependent upon in the project/

9


7/10


THE REQUIREMENTS COLLECTION TEMPLATE FORMTHE REQUIREMENTS COLLECTION TEMPLATE FORM

This table belo) is intended to be copied into other documents such as a collection ofrequirements( the business requirements template( the user and system specifications document.

Requirement ID :*nique id 7; RequirementType

:+ee /ist "elo); Use Case # :*nique id 7;

Status New

:; Agreed- to

:; Baselined

:; Rejected :;

ParentRequirement #

:Enter the unique id 7%s' for each requirement that this requirement supports

%This field )ill be empty for high level requirements e.g.& business requirements';

Description :Enter concise description of requirement;

Rationale :1rovide a brief rationale& and or business value for the requirement.;

Source :(ame of Requirement.1rovider;

Source Document :filename;

Acceptance/FitCriteria

:1rovide a target that ma0es it possible to test if requirement )as satisfied;

Dependencies :/ist other requirement. Id7s that this requirement is dependent on;

Priority Essential :; Conditional :; Optional :;

Change istory :/ist history of changes to this requirement;


8/10


REQUIREMENTS TRACEABILITY MATRIXREQUIREMENTS TRACEABILITY MATRIX

!ltimately all the requirements that have been gathered need to be accounted for. "ome might be prioritized as being of lo) priority and rejected as they are revie)ed or later in the project. *art

of the accounting )ould be dealt )ith in the history section.

#or those accepted and base lined into the business( user and system requirements( each )illneed to have identified the parent requirement. This allo)s for a bi%directional traceability asillustrated belo) in a typical 2 chart.

The illustration belo) diagrams the process of moving from business requirements through tothe IT solution.

=


9/10


The Requirement Traceability -atri& 3RT-4

Requirement ierarchy !"ample

>

RT- Tracing

Req%5

Req%6

Requirement

"pecifications

Test Case

Design Item

Test Case

Design Item


10/10


Hierarchy ID "usinessRequirement ID

*ser Requirement

ID

+ystemRequirement ID

+ource

H-$ "R-$ *R-$.$ +R-$.$.$ 1ro?ect "rief

H-2 +R-$.$.2 1rocess 5odel

H-3 +R-$.$.3 Data 5odel @H- *R-$.2 +R-$.2.$ "usiness

A)ner H-8 +R-$.2.2 1rocess 5odel

"H-9 *R-$.3 +R-$.3.$ 1olicy 5anual

H-< "R-2 *R-2.$ +R-2.$.$ Boal 5odel

etcC

Trace Document !"ample

Traceability ID +ystemRequirement ID

*se ase ID Test ast ID +olution

T-$ +R-$.$.$ *-$.$ T-$.$.$ AbliT-2 T-$.$.2 Abli

T-3 *-$.2 T-$.2.$ Abli

T- T-$.2.2 Abli

T-8 T-$.2.3 Abli

T-9 +R-$.$.2 *-2.$ T-2.$.$ Aracle

T-< T-2.$.2 Aracle

EtcC

$

Documents

DoIT RequirementsCollectionTemplate