Everything About ___
Live briefing

Everything about Requirements traceability

Sub-discipline of requirements management

Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks. Wikipedia →

🧭 Start here: a 6-step reading path

  1. Read the overview: Requirements traceabilityA 5-minute orientation
  2. Skim a recent paper: A systematic literature review of pre-requirements specification traceabilityInfluential work since 2022
  3. Pick up a classic book: Theory and Practice of ComputationThe most-reprinted book on the subject
  4. Read the landmark paper: Toward reference models for requirements traceabilityCited 597 times
  5. Go sideways: Software visualizationA closely related topic
  6. Go sideways: Software requirementsA closely related topic

📖 Definitions

No dictionary entry for this exact phrase.

🏆 Landmark papers (most cited)

🆕 Influential since 2022

📚 Books worth reading

Ranked by number of editions on Open Library, a rough measure of how lasting a book is.

🔗 Related topics