Is the traceability matrix any use for BAs or is it more of a development tool?
In terms of BA use, all I can see it of benefit for is to ensure that all functional requirements have been met, more of a list of individual requirements with acceptance criteria.
If each FR relates to a UR User requirement then what is the point in mapping a Use Case to each FR - it should be obvious from the documentation. All the BA needs to check is that every bit of fucntionality in the Use case diagram is considered in the acceptanc criteria, no?
Qwerty:
Great questions!
We are BA's - not developers. We have different needs in a tracability matirx (see my comment attached to the recenta article on Tracability)
Also, you ask: If each FR relates to a UR User requirement then what is the point in mapping a Use Case to each FR
Let me take it one step further. If all manual and automated behavioral-related requirements can be called the same thing (which they are using Data Flow Diagrams), why do we have functional requirements, business requirements, user requirements, etc.
Answer: There is no logical reason. The reason for so many requirements types is that most people can not envision a single set of integrated behavioral requirements.
brought to you by enabling practitioners & organizations to achieve their goals using: