|
Methodology
|
Advantages
|
Disadvantages
|
|
BOEHM
|
- Realistic
simplistic
- Cover
all of phases of software development
|
- Doesn’t
handle generic risk implicitly
|
|
RISKIT
|
- Flexibility
- originally developed for software development projects, but it can be
applied in many other areas, such as business planning, marketing and
in technology related fields.
|
- The
method doesn’t bridge the gap between risk estimation and risk metrics;
this means it is very difficult to predict the potential risk reliably.
- The
method doesn’t offer a way to combine and harmonize the different
stakeholder perspectives on the risk results.
|
|
SEI-SRE
|
- The
main strength of SEI-SRE is that it is not purely theoretical; any
clients have used it successfully.
- Another
important factor is that SRE was developed by the Software Engineering
Institute, and can therefore be used in any IT projects.
|
- In
this method everything is defined as a template including the way the
interviews are to be conducted. There is no space where human
intelligence can be applied
- Because
the method is based on human experience, the results of the analysis
may be inconclusive when assessed by the SRE team.
|
|
SERUM
|
- Particularly
applicable to the planning of software, and software version releases
- SERUM
is a method of risk management that looks at the business aspect of
system change and also the technical aspect. It even takes in to
consideration the evolution part of the software. SERUM enables
software to be released in versions.
- Handles
Implicit and Explicit risks.
- SERUM
is based on two well-defined methods mainly SSM and Evolutionary
delivery. This is the main advantage of this method, not all of the
risks have to be dealt with explicitly, like in other traditional
methods.
- Considers
the Risk in current System as well as proposed system.
- A
lot of risk assessment methods do not take into account the risks
involved in the current system, they just analyze the risk in the
proposed system. Risk models should be able to take care of those risks
that have been already there in the current system. It would be of no
use, if the proposed system has the same amount of risk exposure in the
same area as the current system.
- Self-Learning
- After
every release is issued, the user comments are passed onto the
developer. The developer then takes this into consideration and
implements changes in the next release. This is a feature of SERUM that
takes into consideration the importance of meeting the user
requirements implicitly
|
- SERUM
doesn’t take into account feedback of similar projects, even if they
are in the same organization. There are possibilities that everything
could be documented again unnecessarily.
- SERUM, suggests that after every software
release the user input should be taken and changes must be applied to
the future release. It is however difficult to have a cost/benefit
analysis for all the stages even before the development has begun.
- SERUM
tries to cover as many of the risks as possible. This at times may not
be manageable. The best way to overcome this would be to cover only the
risks with high-risk exposure. This can cause low productivity, as the
developers would be working on similar risks over and over again.
|
|
SERIM
|
- Within
the SERIM model there is simple use made of basic statistics (mainly
through assignment of subjective probabilities and use of means and
weighted means). Therefore sets of formulas are used
to assess the risks in the complex software
development environment
- The
author claims that SERIM can be used to monitor risks at any point in
the development cycle. SERIM assessments
can be performed against a regular schedule for each project, or as
seems appropriate to the individual project manager.
|
- The
intention with SERIM is that the perspectives are used by the
project/risk manager to focus on problem areas, and create action plans
to improve the project’s chance of success. However, SERIM does not
provide guidance and advice on how to create and implement these action
plans.
- The
major drawback of the SERIM method is the lack of explicit guidelines
on how to use the information and how to identify the risks that may be
lurking in the project.
|