Hello everyone !
I would like to ask you about the
traceability features you are using with your EA CASE tool.
There are several
traceability strategies that can be applied according to
requirements management:
1) Use Case Model is the only statement of requirements and serves solely as a specification for the system.
2) Use Case Model is an interpretation of a traditional software requirements specification: Your customer supplies you with a formal specification as part of the software development contract. Use Cases are set up to complete and understand the requirements.
3) Features drive the Use Case Model: A central document stating all mandatory goals and needs of your customer is available. In addition the main features of the system to be developed are also listed in this document.
It would like to adopt the latter in my project since it is recommended by the Rational Unified Process.
Looking at case 3) the Use Cases need to be traced to features which need to be traced to project goals. The Use Case itself is only suitable if a certain feature is realised within it.
Now my question:
In general, a Use Case is made up of several parts (actor, pre- and postconditions, flow of events, results, scenarios, ...).
Is it possible to connect a feature with a certain part of the Use Case or with an activity diagramm that displays the flow of events and actions?Overview of traceability strategy 3: (please use the link below)
Link
Source:
"Traceability Strategies for Managing Requirements with Use Cases" by Ian Spence and Leslee Probasco
Rational Software Whitepaper
1998
