

You use this information to assess the impact of proposed requirements changes on the system design and implementation.

You use this information to assess how many requirements are likely to be affected by a proposed change and the extent of consequential requirements changes that may be necessary.ĭesign traceability information links the requirements to the design modules where these requirements are implemented. Requirements traceability information links dependent requirements within the requirements document. When a change is proposed, you use this information to find and consult the stakeholders about the change. Source traceability information links the requirements to the stakeholders who proposed the requirements and to the rationale for these requirements. There are three types of traceability information that may be maintained: Traceability is the property of a requirements specification that reflects the ease of finding related requirements. When changes are proposed, you have to trace the impact of these changes on other requirements and the system design. There are also links between requirements and the underlying reasons why these requirements were proposed. There are many relationships among requirements and between the requirements and the system design. Tools that may be used range from specialist requirements management systems to spreadsheets and simple database systems. Traceability policies These policies define the relationships between requirements, and between the requirements and the system design that should be recorded and how these records should be maintained.ĬASE tool support Requirements management involves the processing of large amounts of information about the requirements. I discuss this process in more detail in the following section. Requirements identification Each requirement must be uniquely identified so that it can be cross-referenced by other requirements and so that it may be used in traceability assessments.Ī change management process This is the set of activities that assess the impact and cost of changes. During the requirements management stage, you have to decide on: For each project, the planning stage establishes the level of requirements management detail that is required. Requirements management is very expensive. Planning is an essential first stage in the requirements management process.
