Tracebility from use case-design-code

[sanlew96]

I am a user of EA adn i use the tool to write use cases for retail banking application. We have huge number of use cases and we face a problem in relating the use cases to design and then to the code. Can you suggest us a way in EA to map use cases to design to the code. Can you help me please. Tracebility has become a major issue for us. We need to trace every step in the use case to the design atleast at a high level. We need a way by which this can be do this in EA rather than in an excel sheet

[Marcelo Mrack]

Hi,

Look in Help file, searching for "Requirements". Then, open the first option link, the "Requeriments (EA User Guide)"

See how to Use Cases *realizes* the requirements. For each Use Case, you can attach (by realization or implementation links) the softwares components responsibilities.

Finally, using a Hierarchy View (by Control + Shift + 4) over the Use Case, you can trace responsibilities.

[Graham_Moir]

I would suggest that the relationship matrix (view menu)is a key tool to help with what you are trying to achieve.  

For example from the matrix you can check that use cases have been "realised" in downstream design - i.e. if there's no "X" in the box then the relationship doesn't exist and perhaps somethig has been missed.  

You can also use this matrix to add relationships very quickly which then will appear automatically on diagrams where the related elements appear.