-
8/12/2019 Simple Notes on Risk Managent Andcmm in Software
Engg
1/4
Software configuration management
-
8/12/2019 Simple Notes on Risk Managent Andcmm in Software
Engg
2/4
Q Process managementAns.
i. Improving quality and productivityare fundamental goal of
project.ii. Process management, manages and improves processes, to
achieve this goal.
iii. To improve software process, an organization needs to ;
First understand the current statusof process Develop plan to
improve process
iv. It is not possible to improve software process completely
and at once. Bcaz, it takestime to internalize the process. Another
Question is the new method that is created by theprocess. Will it
be visible to process or not.
v. Therefore, improve (change) is done in small incrementand the
order of theimprovement activities of process must be
specified.
vi. The function of the current stateof the process is to decide
whether which activities toundertake for process improvement.
vii. Changes in small increments based on the current state of
the process have been capturedin the Capability Maturity Model(CMM)
framework.
viii. The CMM framework provides a general roadmapfor process
improvement.ix. CMM determines the process capability. CMM
describes the range of expected results
that can be achieved by following the process.x. The goal of
process improvement is to improve these process capabilities.
Q Capability Maturity Model (CMM) framework and its
levelsAns.
i to x :- Refer to Process management.
xi. The CMM suggests that there are five well-defined maturity
levelsfor a s/w process asfollows;
1. Initial (level 1),2. Repeatable,3. Defined,4. Managed, and5.
Optimizing (level 5).
xii. Processes go from their current levels to the next higher
level as they improved.xiii. Depiction for CMM framework ;
-
8/12/2019 Simple Notes on Risk Managent Andcmm in Software
Engg
3/4
xiv. Characteristics of each level1. I ni tial Process (Level 1)
;
It is an ad hoc process, which has no formalized method, for any
processactivities.
Success of software project depends on quality people.2.
Repeatable Process (Level 2) ;
Planning is done Disciplined execution of planning. Make a
realistic project commitment. Problems of cost and schedule are
tracked and resolved when they arise. Results obtained by this
process can be repeated if required.
(Result can be used @ the time of resolving the problem that
arise)
3. Defined Level (Level 3); Organization has standardized s/w
process, which is properly documented
and improves over time.
Training program Integrated software management4. Managed Level
(Level 4) ; Software quality management Quantitative process
management.(i.e. measurement of process capabilities and
deficiences)
5. Optimizing Level (Level 5) ; Continuous process improvement
by collecting data, analyzing data, to
identify areas that can be improved.
New technologies introduced to measures effort, so to improve
theperformance of the process.
Defect prevention
-
8/12/2019 Simple Notes on Risk Managent Andcmm in Software
Engg
4/4
Q3. Risk management ;Ans.
I. Risk management concept;a) Risk occurs due to common
unexpected event like a personnel takes leaves, S/W
requirement changes..etc.
b) Risk has an adverse effect on cost, quality or schedule.c)
Risk management is a best practice to minimize the impact of
risk.d) Risk management begins where project management ends.
II. Risk Assessment;a) Risk assesement identifies risk, analyze
it, prioritize it then resolve it.b) Risk assessment should be done
throughout the projectc) Steps is Risk Assessment;
1. Risk identification; Is a First step in risk assessment.
Identifies all risk in project. Method that can help risk
identification include lists of possible risks, surveys,
meetings and brainstorming, and plansetc Some common risk;
Personnel Shortfalls Unrealistic Schedules and Budgets Developing
the Wrong Software Functions Less capabilities of
personnals(Perfomance shortfall).etc
2. Decision driver analysis; Analyzing decisions by marketing,
politicsetc not by technical and management department
3. Assumption analysis; Optimistic assumptions (keep positive
thinking about project). These assumption can create risk
Therefore, assumption compared with past experience.
4. Decomposition; By decomposing large projects into small
modules, the risk
identification becomes comparatively easier.
