Link Requirements to Stakeholders

[need2scuba]

I am new to EA so please forgive the basic question.  How do I link (or what is the best way) stakeholders to requirements.  I know I can link them on a diagram and see that link in the traceablity matrix.  But I really need to be able to run reports which contain all requirements  associated with a particular stakeholder.  I can't see how to do this from the traceablity matrix and I can't figure out how to get a view(search) setup to show all requirements associated to a given stakeholder(actor).

Thoughts?

[KP]

There are a number of ways...

Create a new diagram, drag one of the actors from the project browser onto the diagram, right-click it and select "Add > Related Elements" to add all requirements related directly to that actor.

Or, go "Edit > Find in Model", click Manage Searches, New Search, SQL Editor, and enter an appropriate SQL query. Something like:

Code: [Select]

SELECT Stakeholder.Name, Requirement.Name
FROM t_object AS Stakeholder, t_connector, t_object AS Requirement
WHERE Stakeholder.Object_Type = 'Actor'
AND Requirement.Object_Type = 'Requirement'
AND t_connector.Start_Object_ID = Stakeholder.Object_ID
AND t_connector.End_Object_ID = Requirement.Object_ID

[Dermot]

For a simple alternative you might try viewing this using the Hierarchy View ctrl-shift-4.
Wth reporting though -  RTF reports - use the RTF Sections Element::Connector::Target & Source - to show these Actors connected elements and set up a filter on the Relationship type (i.e. Realization).

[need2scuba]

Thank you both for the suggestions.  I have been able to get both to work for me and they have been very helpful.

Regards,

[paddler]

 HI

 I know this is "cheating" a bit but hear me out.
 If your client's main goal is linking requirements to STAKEHOLDERS in a report and not USE CASES for design then there are two ways to proceed that I have found

a> Create an Object Representing each stakeholder. Then, tack on their requirements to the object using the Object's requirement tab. If you create a report that then walks through all of the objects in a package and extracts the attached requirements and constraints then you are golden!

b> Another option may help. Create a package for each stakeholder and drop their specific requirements in their folders. Create a report that walks through packages and pulls out requirements and places them in a report. This lets you also link Requirements to Use Cases later on.

Hope this helps... the tricky part is writing the report

[«Midnight»]

IMHO this is certainly not cheating; in fact it is a very sound approach.

Note that the "Object" you use to represent the stakeholder could be an Actor element. [You could stereotype these if you wish, perhaps adding a shape script to make them visually distinct.]

The properties dialog for an Actor has a requirements tab, so you can add internal requirement here. If you want to use external requirement and segregate them on a separate diagram there are a few additional (to the excellent suggestion in the above post) you might consider.

First, you can make the Actor a composite element. To do this right-click the Actor and from the context menu select Advanced | Make Composite. This will create a 'child' use case diagram below Actor. You can navigate to this diagram via the Project Browser or by double-clicking the Actor. You can add Requirement elements from the Common section of the toolbox.

You could also use a different diagram type instead of an 'inner' use case diagram. There are two ways to do this. The first is to create a composite element as above and navigate to the child diagram. Then from the EA main menu choose Diagram | Change Type and set the new diagram type.

You can get a similar result by right-clicking the element (whether or not it is a composite element) and from the context menu choose Add | Add Diagram. Choose the diagram name and the type you want from the resulting dialog. You will not be able to use the double-click shortcut to reach this diagram, but you can add as many as you want.

Finally, you could simply create a diagram to show requirements. Once you have represented a stakeholder with an element in your project, you can reuse that element on many diagrams. [I mean you can drop the same element on several diagrams, not create additional element to represent the same stakeholder.] For example, you could have one diagram to show all (or some subset) of the stakeholders, perhaps with notes and such. You could then show one or more of these stakeholders on another diagram, which would also include requirements and link these to the stakeholders. This could be useful if some stakeholders have common requirements.

HTH, David