Keeping traceability up to date as the project evolves

Question

During various projects, I needed to make sure that the use model developed by me at the analysis stage covers the requirements of the project. To do this, I was able to have some degree of traceability between requirement operators (uniquely identified) and use cases (also uniquely identified). In some cases, the ability to track involved some extra effort that I considered (and later proved) a good investment.

Now, the biggest problem that I encountered was to maintain this traceability later when things started to change (as a result of requests for change or as a result of changes if used).

Any ideas on best practices for tracking service?

(It can be applied to other elements of the project - for example, to use cases and test cases, or to requirements and acceptance tests)

Further edit Tools can help, but they cannot detect spaces or errors in tracking. Navigation ... is possible, but there is no guarantee that traceability is current or correct after changes are made.

Answer 1

I believe that traceability is one of the most difficult tasks for managing requirements, and secondly, to make sure that the requirements are first and foremost correct. In my experience, the best tracking tool is a person .

; , .

• , . , Sharepoint, ( -, , ). , , , .
• , . -, , , , , , , .
• . , , . , , , , .
• , : , . , .
• , , , , , . , , ? , / - , - :)

Answer 2

Rational . .

, . , , , .

---

, , .

---

, .

, (, ) .

, . , Excel!

---

, , , .
5 : , , , .
( , JOIN), , .

Answer 3

: , , ( ), , ..

Word, excel . , . . IBM Doors - , . . Ultimate Trace, .

Answer 4

# - , ( / ). , , / , , .

, / , , , ( case , , )

Answer 5

, - . , , .

(bugtrackers) (, ), .

SCM (.. ..), , .

There are tools to help with this, ut, I found that these “full-life” tools are really unusable because they do too much in one application or as related applications that “integrate” together and are incredibly expensive.