Question

Maintaining traceability during requirements and subsequent activities is expensive, because of the addition information that must be captured and maintained. The followings four are the benefits of traceability that outweigh this overhead.

1. Ability to show that all requirements have been implemented.

2. Ability to show that all features in the system correspond to a requirement.

3. Ability to assess the impact of a change.

4. Ability to track the human source of a requirement.

Which of those benefits are directly beneficial to the analyst? Please write number (or numbers) which, you think, is (or are) beneficial to the analyst.

Answer 1

Requirement traceability

It is a kind of relationship of two requirements which implies the source, derivation, inter- dependencies between the two parts of the system.

In other words, traceability is a way of following the life of requirement.

Traceability lets the developer to make sure that system is complete. Testers get to know that system is within its requirements and maintainers keep getting to know the impact of change.

Although maintaining traceability during requirements is quite expensive, as additional information needs to be captured and maintained, but besides this there are many benefits of traceability which compensate its drawbacks:

Benefits of traceability

1. It shows that all the requirements have been implemented. System can be checked appropriately to test each of the requirements.

2. It has the ability to prove that the system has all those features which correspond to a requirement. This is done by checking each of the requirements individually and enumerating them.

3. Changes can be performed and their effect on the system can be found out only with the help of proper tracing.

4. It tracks the human source of a requirement that is it can be checked where the requirement has come from