The Concept Of Requirements Traceability

1551 Words7 Pages
1. THE CONCEPT OF REQUIREMENTS TRACEABILITY According to IEEE (Institute of Electrical and Electronics Engineers), “Requirements traceability refers to the ability to define, capture and follow the traces left by requirements on other elements of the software development environment and the trace left by those elements on requirements.” In general, traceability is a process of inter-relating the different requirements identified by the stakeholders at different levels of software development life cycle and various project artifacts. This inter-relation is used to establish the scenarios of a specific use case within a system or application and test those scenarios using test-cases. In any software development project, requirements should be easily traceable and for this, the origin of the requirements should be clear to follow. In other words, Requirements traceability is the ability to capture the traces of requirements within a system or between the integrated systems during its development life cycle. Traceability is required to manage changes at various stages of the SDLC and is a part of Requirements Management 2. MODES OF REQUIREMENTS TRACEABILITY There are different modes to perform requirements analysis based on the direction, before/after Requirements Specification phase of a project and the relationship between elements such as requirements and artifacts. 2.1 Forward and Backward Requirements Traceability Bidirectional Requirements traceability
Open Document