Home > Ask the Software Quality Experts > Software Requirements Questions & Answers > How important is requirements traceability?
Ask The Software Quality Expert: Questions & Answers
EMAIL THIS

How important is requirements traceability?

Karl E. Wiegers EXPERT RESPONSE FROM: Karl E. Wiegers

Pose a Question
Other Software Quality Categories
Meet all Software Quality Experts
Become an Expert for this site


Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 14 February 2007
Is requirements traceability important? If so, what's a good way to get started with traceability?

>
EXPERT RESPONSE
Requirements tracing is the process of recording logical links between individual requirements and other system elements. You can trace a single functional requirement backward to its origin, such as a use case, product feature or business rule. You can also trace that functional requirement forward into the bits of design, code and tests that were created because of that requirement.

Collecting requirements traceability information as development progresses makes it almost impossible to inadvertently overlook a planned requirement during implementation. Reliable traceability data facilitates making changes correctly and completely during maintenance, which improves the team's productivity. For example, suppose you have traced a business rule into various functional requirements that implement the rule. If that rule ever changes, the maintainers can follow those links to quickly make the necessary software modifications. You can also use traceability data when certifying a safety-critical product to show that all requirements were implemented and that all requirements are covered by specific tests.

To do requirements traceability, the analyst must write requirements in a fine-grained fashion and give every requirement a unique and stable identifier. (No bullets!) Most people start performing traceability by linking functional requirements to individual tests that verify the correct implementation of those requirements. On a small project you can do this manually using a spreadsheet to identify which tests connect logically to which requirements. However, larger projects need automated support for traceability, such as using a commercial requirements management tool. As tracing requirements becomes established in your organization, you can begin to record the design elements and code segments that satisfy each requirement to make your traceability data richer and more valuable.


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Software Requirements
How to determine a software modeling technique
Elicit software requirements using a variety of techniques
Use cases and SRS for requirements gathering
How to choose the right requirements tool
Why you should test requirements definitions
How to estimate change requests in requirements
Use cases: Who writes them, what data do you include?
How use cases facilitate the SDLC
Requirements engineering in an uncooperative environment
Scrum and requirements gathering

Software requirements management
Top 10 software requirements tips
Seven Steps to Mastering Business Analysis, Ch. 1
Integrating application lifecycle management (ALM) processes provides additional benefits
How to choose the right requirements tool
How to estimate change requests in requirements
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
Quality software performance doesn't happen accidentally
Software requirements elicitation and documentation

Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)
Pictures communicate software requirements without slowing development
REAL business requirements key to calculating ROI for a project
The role of user stories in agile software development
Business analysis skills you need for successful software requirements
How to determine a software modeling technique
Agile aims to bridge software requirements communications gap
Elicit software requirements using a variety of techniques
Simulation software a cure for hospital's requirements validation ills
Top 10 software requirements tips
Seven Steps to Mastering Business Analysis, Ch. 1

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
requirements analysis  (SearchSoftwareQuality.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Software Quality - Software Maintenance, Software Requirements, Software Standards
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts