Home > Ask the Software Quality Experts > Software Requirements Gathering, Analysis, Quality and Testing 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?

>
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 Gathering, Analysis, Quality and Testing
Problems caused by skipping analysis stage of SDLC
Software development life cycle phases, iterations, explained step by step
Waterfall versus iterative development misconceptions
Differentiating between Functional and Nonfunctional Requirements
Writing a software requirements specification (SRS) for a portal app
Should QA check changes from outside the requirements document?
Software testing metrics for a medium-sized project
Template for requirements use cases
What should a business analyst's requirements document include?
Is a requirements freeze in a software project a bad idea?

Software requirements management
How to improve software project requirements estimates tutorial
Expert shows seven ways to improve your project management abilities
Five roles test managers play in agile development: Tutorial, part one
Quality assurance (QA) and testing's role in requirements
Defining requirements during software project feasibility analysis
How to avoid requirements creep
Software development lifecycle (SDLC) trends 2009: Requirements, agile
Is a requirements freeze in a software project a bad idea?
Top 10 software requirements tips
Seven Steps to Mastering Business Analysis, Ch. 1

Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)
Why business analysts are application development key players today
Defining report requirements with use cases
When it comes to requirements, what is 'just enough'?
How requirements use cases facilitate the SDLC
GatherSpace beefs up cloud-based requirements management
Software development life cycle phases, iterations, explained step by step
How to deliver, implement testable software requirements
Excelling in the art and science of requirements elicitation
Software requirements: Moving beyond use cases
Mastering key requirements phases

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 technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




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