Book a Demo

Author Topic: How to relate requirements to multiple use cases  (Read 2306 times)

colinc

  • EA User
  • **
  • Posts: 62
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
How to relate requirements to multiple use cases
« on: June 16, 2005, 10:27:19 pm »
I have a series of use cases describing a new system being built.

I would like to be able to relate the technical requirements to the multiple use cases (/scenarios) they relate to.

I know that the external requirements link is actually a realisation list, when the link is created and the requirement is on the same diagram as the use case, the link shows up in project useage for the requirement.

If the requirement however is removed from the use case diagram (doesn't really belong there), the link disapears in project useage. Perhaps this is actually a bug????

Either way is there a way to link a requirement to multiple use cases without needing to build diagrams with a million realisation links ?

Thanks, Colin

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: How to relate requirements to multiple use cas
« Reply #1 on: June 16, 2005, 10:51:11 pm »
Colin,

The Project View (technically the Containment View) is actually about containment.  When you externalise a Requirement, as you say, you create a Realization link and place the Requirement into some arbitrary Package.
So the Requirement is "nested/contained" under the relevant Package, not Diagram.

When you move the Requirement, it is contained by a different Package and shows up in that Package's tree.  The Realization linkage is still there.

To show Relationships you should use the Relationships window or even the Hierarchy window (see under View menu). 8)

You can use the Relationship Matrix to link elements visually without regard to any Diagram. 8) 8)

HTH,

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!