User Tools

Site Tools


Sidebar

Welcome to DIDO WIKI

dido:public:ra:xapend:xapend.a_glossary:r:requirement_trceability

Requirement Traceability

Return to Glossary

Requirement Traceability is …

Requirements Traceability in particular, is defined as “the ability to describe and follow the life of a requirement in both a forwards and backwards direction (i.e., from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases)”. In the requirements engineering field, traceability is about understanding how high-level requirements – objectives, goals, aims, aspirations, expectations, business needs – are transformed into development ready, low-level requirements. It is therefore primarily concerned with satisfying relationships between layers of information (aka artifacts). However, traceability may document relationships between many kinds of development artifacts, such as requirements, specification statements, designs, tests, models and developed components.[7] For example, it is common practice to capture verification relationships to demonstrate that a requirement is verified by a certain test artifact.

Source: https://en.wikipedia.org/wiki/Requirements_traceability

dido/public/ra/xapend/xapend.a_glossary/r/requirement_trceability.txt · Last modified: 2022/01/27 06:26 by nick
Translations of this page: