Analyzing Changing Requirements

[baybiz]

Hi,

 We are currently in the process of evaluating the EA. So we would like to know if there are any examples
on how modifying a particular use case will affect others.

Let's say for example.

There is a use case by name "Create an Order".

There could be many other use cases performed by different actors which might depend on "Creation of an Order"

We would like to know if this tool tells by changing
"Create an order" what other use cases are going to be impacted in the system

Thanks
Sri

[thomaskilian]

Hi Sri,
as a quick answer I would suggest to use a trace association between use cases. Here you can note which dependency you have between use cases. EA also has a pretty nice feature: View/Relationship Matrix. Here you can manage which use cases are dependent to each other.

[baybiz]

Hi,

 Let's say I have 1 use case model with 3 use cases in it
 I create a second use case model and in which I created another use case. For this newly created use case I want to create a link or trace to the one sitting in the other use case model.

Not sure how to do this on 3.51

Thanks
Sri

[baybiz]

Hi,

 Basically I am not able to use dependency between two use cases sitting across two Use Case Models.

Sri

[Rob_M]

A couple of ways to do that.

First, I assume your use case 'models' are in the same database, and you're just talking about different diagrams in different packages.

One way is simple drag the use case from one the browser onto the diagram, containing the other use cases. Create the dependency link between the two. Then delete the use case you just dragged. The link still exists between them, but it is no longer displayed on the diagram.

As mentioned the link can be viewed on the relationship matrix.

A second way to do this is right click on the use case in the project browser. Select create link. In this way you can create any type of link between any type of element.

Rob

[thomaskilian]

Assuming that Rob's assumption is right   you can also create the link via the relationship matrix.