Subjects
Applied Mathematics for Electrical Engineering - 3130908
Complex Variables and Partial Differential Equations - 3130005
Engineering Graphics and Design - 3110013
Basic Electronics - 3110016
Mathematics-II - 3110015
Basic Civil Engineering - 3110004
Physics Group - II - 3110018
Basic Electrical Engineering - 3110005
Basic Mechanical Engineering - 3110006
Programming for Problem Solving - 3110003
Physics Group - I - 3110011
Mathematics-I - 3110014
English - 3110002
Environmental Science - 3110007
Software Engineering - 2160701
Data Structure - 2130702
Database Management Systems - 2130703
Operating System - 2140702
Advanced Java - 2160707
Compiler Design - 2170701
Data Mining And Business Intelligence - 2170715
Information And Network Security - 2170709
Mobile Computing And Wireless Communication - 2170710
Theory Of Computation - 2160704
Semester
Semester - 1
Semester - 2
Semester - 3
Semester - 4
Semester - 5
Semester - 6
Semester - 7
Semester - 8
Software Engineering
(2160701)
SE-2160701
Summer-2017
Question-3b-OR
BE | Semester-
6
Summer-2017
|
04/27/2017
Q3) (b)
4 Marks
Explain RMMM.
RMMM Plan
The RMMM PLAN documents all work performed as part of risk analysis and used by the project manager as part of the overall project plan
Some software teams do not develop a formal RMMM document, rather each risk is documented individually using a Risk information sheet (RIS)
In most cases, RIS is maintained using a database system.
So Creation and information entry, priority ordering, searches and other analysis may be accomplished easily.
The format of RIS is describe in diagram
RMMM - Mitigation, Monitoring, and Management
An effective strategy for dealing with risk must consider three issues
Risk mitigation
is a problem avoidance activity
Risk monitoring
is a project tracking activity
Risk management
includes contingency plans that risk will occur
Risk Mitigation
Risk mitigation (avoidance) is the primary strategy and is achieved through a plan
For Ex., Risk of high staff turnover
To mitigate this risk, you would develop a strategy for reducing turnover.
The possible steps to be taken are:
Meet with current staff to determine causes for turnover (e.g., poor working conditions, low pay, and competitive job market)
Mitigate those causes that are under your control before the project starts
Once the project commences, assume turnover will occur and develop techniques to ensure continuity when people leave
Organize project teams so that information about each development activity is widely dispersed
Define work product standards and establish mechanisms to be sure that all models and documents are developed in a timely manner
Conduct peer reviews of all work (so that more than one person is “up to speed”).
Assign a backup staff member for every critical technologist
Risk Monitoring
The project manager monitors factors that may provide an indication of whether the risk is becoming more or less likely.
In the case of high staff turnover, the general attitude of team members based on project pressures, the degree to which the team has jelled, inter-personal relationships among team members, potential problems with compensation and benefits, and the availability of jobs within the company and outside it are all monitored.
In addition to monitoring these factors, a project manager should monitor the effectiveness of risk mitigation steps.
The project manager should monitor work products carefully to ensure that each can stand on its own and that each imparts information that would be necessary if a newcomer were forced to join the software team somewhere in the middle of the project.
Risk Management
Risk management and contingency planning assumes that mitigation efforts have failed and that the risk has become a reality.
If the mitigation strategy has been followed, backup is available, information is documented, and knowledge has been dispersed across the team.
In addition, you can temporarily refocus resources (and readjust the project schedule) to those functions that are fully staffed, enabling newcomers who must be added to the team to “get up to speed.” Those individuals who are leaving are asked to stop all work and spend their last weeks in “knowledge transfer mode.”
Questions
Go to Question Paper
Q1
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
Q2
(a)
(b)
(c)
(c)
(OR)
Q3
(a)
(b)
(c)
Q3
(a)
(OR)
(b)
(OR)
(c)
(OR)
Q4
(a)
(b)
(c)
Q4
(a)
(OR)
(b)
(OR)
(c)
(OR)
Q5
(a)
(b)
(c)
Q5
(a)
(OR)
(b)
(OR)
(c)
(OR)