Author Topic: Modeling Risk Analysis  (Read 643 times)

A.Russell

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Modeling Risk Analysis
« on: August 04, 2007, 01:23:52 am »
Does anyone have any best practices concerning modeling risk analysis with uml? I can't find a good example.

I can see that risks can be noted in the Project window for individual elements, and that a metric can be assigned in Project Indicators. What is really needed is somewhere all the risks can be viewed and ranked. Does anyone have a good method of managing this?

Furthermore, is it possible for this documentation to be discluded from reports.


« Last Edit: August 04, 2007, 01:50:34 am by A.Russell »
----------------------
Software Consultant
Analyst Programmer/ PM

A.Russell

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Modeling Risk Analysis
« Reply #1 on: August 16, 2007, 06:06:47 pm »
Since assessing and mitigating risk early is one of the tenets of a Rational Unified Process I thought someone might have some ideas.

What I have done is created a special folder for risk assesment and used Issues to note risks and their mitigation. I then added links to them from the use cases or requirements that they concern.

The only problem with that is how to incorporate them into the project estimate.

Anyway, I just thought I'd share that. If anyone has any better ideas, I'd like to hear them.
----------------------
Software Consultant
Analyst Programmer/ PM

thomaskilian

  • Guest
Re: Modeling Risk Analysis
« Reply #2 on: August 16, 2007, 11:44:44 pm »
More or less I do it the way you described it. The analysis of the impact is something that *could* be supported by some machine. However, it's on a human to actually decide on the picture. Unless you don't have hundreds of different risks a manual approach is likely the best. And then again if you really have so many, you would need to invest the money in *real* RM tools rather than using EA for it.