Reuse Risk

[AndyBo]

Risks as implemented are applied to an individual element in the model, much like an internal requirement.
A single Risk could apply to many model elements/project areas.
In managing risk I should want to identify and monitor such a pervasive risk.

1) Can risks be made "external" like requirements?

2) Rather than just the weighting I would want Impact (1-5) & Likelihood (1-5)as fields.
    From this I can generate a value to prioritise - especially if I can add the frequency (from 1 above)

3) Against a risk I want to record its mitigation.
    I know I can record this within the notes but from reporting perspective I would want it documented as a separate column.

4) Dreaming further - I would want the RTF risk report to be driven from the risks; listing what it applies to; akin to the requirements matrix but ordered by score (Impact * Likelihood * Frequency).

[Eve]

If you want this now, create a profile with a risk element.

[AndyBo]

Thanks Simon,

This is really stretching my use of EA.

I can just about cope with creating the stereotype with the additional attributes, but what is the best metaclass to base it on?
Requirements is the obvious one but that does not alow me to to report across the links. One of my requirements...
Activity sort of fits. It could have requirements & constraints too, but it does not need scenarios or behaviours. Is it possible to delete these unwanted tabs?
Class is definitely wrong because risks will not have attributes or operations.
The biggest issue is connecting the risk to another element in the model. All I want it to offer is one type of connector - along the lines (no pun intended) of trace or realize.
How can I reduce/define the connectors to be available from the metaclass in the newly created risk?

If I create such a Risk profile, is this the sort of thing that should be shared on the community site?
All help gratefully received
Thanks in advance