Requirements Management

              A failure to understand, document and manage requirements often lies at the heart of problems with business and IT system change projects. While a structured, well-defined set of requirements will provide an excellent basis for a change project, problems can still occur if the requirements are not traceable. The traceability of requirements in a critical quality characteristic. There are two forms of tracebility.

       Which includes

•                                    Requirements identification
•                                    Requirements cross- referencing
•                                   Requirements origin and ownership
•                                   Software support
•                                   Change Control
•                                   Configuration Management

1.  Backwards from
2. forwards to          

Backwards from : Traceability involves the ability to trace the source of a requirement from any later point in the business change or software development lifecycle. Like 

• what was the source requirement for this feature of the solution and who raised it ?

                                  We need to be able to identify where a requirement originated so that we can seek clarification from the source where necessary.

Forwards to :  Traceability involves the ability to identify any requirement and track where it has been further developed and ultimately implemented. It answers the question 'What happened to this requirement ?' and should show that each requirement has been resolved satisfactorily.