Requirements Trace Ability

8/7/2019 Requirements Trace Ability

http://slidepdf.com/reader/full/requirements-trace-ability 1/20

RequirementsRequirements

traceabilitytraceabilityVasu Sreenathan

Barnali ChakrabartyMaheswari Muthusamy



Background information:Background information:

Where do Requirements come from:

Business Requirements User / Functional Requirements

Software Requirements Specifications SRS is basis for coding activities



What is ³Requirements Traceability´What is ³Requirements Traceability´

y Trace the source of each unique productrequirement.

Sources:x Business Requirementx Functional Requirement

x User request (e.g. in JAD sessions)

x Business Rules

x Industry standards (e.g. PCI, NCPDP)

y Capture interdependencies of requirements.



Why do ³Requirements Traceability´Why do ³Requirements Traceability´

� Project Manager: How changes to requirementsimpact other requirements and downstreamsoftware development deliverables.

� Business analysts: Develop high quality System

requirement specifications.

� Developers: Trace back to original businessrequirements and its sources, if a systemrequirement is unclear.

� Testers: Develop integrated and high quality testcases.



How to do ³Requirements Traceability´How to do ³Requirements Traceability´

� Tabular columns:Bus Req ID Business Requirement Source

B_CLMS.500003.00 The system shall require vendor Bank Identification

Number (BIN) Number when processing claims.4-10 Specs Discussion

B_CLMS.500003.01 The system shall ensure that Group ID for all

programs is ³TXVDP.´ When processing claimsJAD 8

SystemRequirement

Description BusinessRequirement

S_CLMS_500003.00 If submitted Bin number (101-A1) is equal to 610084and Group ID (301-C1) is equal to µTXVDP¶

then continue;

ELSE post edit 01

Exception:4001

With message: <none>.

B_CLMS.500003.00

B_CLMS.500003.01




� Traceability matrix:




� COTS Products ± e.g. HP Quality Center



A good COTS product:A good COTS product:

Assigns and maintains unique tag / numberingscheme for each requirement type i.e. Businessrequirement, Functional requirement, Systemrequirement.

Allows for Backward and Forward Traceability

Allows for importing requirements documents

from Word and Excel.



IBM RequisiteIBM Requisite--ProPro



The user chooses parts of the referenceThe user chooses parts of the referencemodel that are relevant to him, adapts themmodel that are relevant to him, adapts themto the specific problem at hand, and tries toto the specific problem at hand, and tries tocome up with an overall solutioncome up with an overall solutionThe reference modelsThe reference models

Traceability Reference Models [Ram01]



1.The reference traceability models were based of several1.The reference traceability models were based of severalempirical studies.empirical studies. Study of these models were done for a spanStudy of these models were done for a spanof 3 yearsof 3 years

2.30 focus group discussions in 26 organizations, which were2.30 focus group discussions in 26 organizations, which wereconducted in a wide variety of conducted in a wide variety of industriesindustries

3.The participants had an average of 15.5 years experience in3.The participants had an average of 15.5 years experience inseveral key areas of systems developmentseveral key areas of systems development

The basis of Traceability Reference Models



Categories of Users andCategories of Users andModelsModels

1.Low-end users and Low End Traceability Model: typical complexityabout 1000 requirements, zero to two years of experience intraceability, traceability is understood as ³documenttransformation of requirement to design´

2.High-end users and High End Traceability Model: typicalcomplexity about 10000 requirements, five to ten years of

experience in traceability, traceability is defined as ³increases theprobability of producing a system that meets all customerrequirements and will be easy to maintain´



PR ACTICE GUIDE FOR REQUIREMENTSPR ACTICE GUIDE FOR REQUIREMENTS

TR ACEABILITY IN DEPARTMENT OFTR ACEABILITY IN DEPARTMENT OF

HEALTH AND HUMAN SERVICESHEALTH AND HUMAN SERVICESENTERPR ISE PERFOR MANCE LIFE CYCLEENTERPR ISE PERFOR MANCE LIFE CYCLE

FR AMEWORKFR AMEWORK



PR ACTICE OVERVIEWPR ACTICE OVERVIEW



y Best Practices

y Iterative ± Requirements Traceability is an ongoing, iterative process conductedthroughout the project lifecycle.

y Centralize ± Requirement Traceability should be documented centrally using some typeof log.

y Document ± Each requirement should be recorded independently and its relationship toother requirements documented.

y Review ± Regular reviews of requirements and the traceability log is good projectmanagement practice.

y Practice Activities

y Define ± Define functional requirements based on technical assumptions and/or clientneeds.

y Identify ± Identify and document an approach to tracing requirements through the lifeof the project.

y Tools ± Purchase or develop a requirements traceability log.

y Document ± Document and maintain requirements and traceability relationships.

y Record ± When a requirement moves through the system lifecycle, record data used totrack that requirement in the traceability log.

y Communicate ± Regularly (at least weekly) update the traceability log with new

information.

y Communicate ± Regularly (at least weekly) communicate with stakeholders about thestatus of requirements.

y Communicate ± Communicate to stakeholders that the requirement has been completed.



Conclusion :Why bother with Conclusion :Why bother with Requirements TraceabilityRequirements Traceability

1. Improve scope management.

2. Improve test coverage and test cost.

3. Improve change impact assessment.



DEMODEMO



ReferencesReferences

� 1.http://www.softwarequalityconnection.com/2011/01/requirements-traceability-why-bother/

� 2.http://www2.cdc.gov/cdcup/library/hhs_eplc/50%20-%20SLA%20and%20MOU/EPLC_SLA_MOU_Practices_Guide.pdf

� 3.Ramesh, B., Jarke, M.Toward Reference Models for Requirements Traceability� IEEE Transactions on Software Engineering, Vol. 27, No. 1, January 2001,

� pages 58-93

� 4.Factors influencing requirements traceability practice

B Ramesh - Communications of the ACM, 1998

� 6.Surfacing Root Requirements Interactions from Inquiry CycleRequirements Documents

by William N. Robinson , Suzanne Pawlowski (1997)



ThanksThanks

Requirements Trace Ability

Documents

Transcript of Requirements Trace Ability