Rmmm plan in software engineering

R.S. Pressman & Associates, Inc. Home About Us Products Process Models SE Resources Commentary Contact us Breaking News! A new blog ... visit A new edition ... the 6th edition of A first novel ... Roger Pressman's first novel is a technothriller -- A new training curriculum! RSP&A has partnered with QAI to develop a comprehensive Internet-based A redesigned Web site ... we've done a major redesign and added many new features Adaptable Process Model Document Templates: RMMM Plan IMPORTANT NOTICE: The complete RISK MITIGATION, MONITORING, AND MANAGEMENT (RMMM) PLAN The RMMM Plan maybe developed in the form of a document. Alternatively, an organization may create a set of Risk Information Sheets (RIS) [often in electronic form] that contain all pertinent information outlined below. IMPORTANT note: Like most software engineering documents, the RMMM Plan evolves over time. 1.0 Introduction This section provides an overview of the RMMM Plan. 1.1 Scope and intent of RMMM activities A description of the overall RMMM focus including objectives, organizational responsibilities. 1.2 Risk management organizational role Description of who has responsibility for risk management. 2.0 Project risks This section describes all known project risks. 2.1 Risk table A presentation of all risks, probabilities and impact. 2.1.1 Description of risk m Risk m is described along with relevant subconditions. Section2.1.1 is repeated for each of m risks. 2.1.2 Probability and impact for risk m Probabil...

1. Risk Identification: Risk identification involves brainstorming activities. it also involves the preparation of a risk list. Brainstorming is a group discussion technique where all the stakeholders meet together. this technique produces new ideas and promotes creative thinking. Preparation of risk list involves identification of risks that are occurring continuously in previous software projects. 2. Risk Analysis and Prioritization: It is a process that consists of the following steps: • Identifying the problems causing risk in projects • Identifying the probability of occurrence of problem • Identifying the impact of problem • Assigning values to step 2 and step 3 in the range of 1 to 10 • Calculate the risk exposure factor which is the product of values of step 2 and step 3 • Prepare a table consisting of all the values and order risk on the basis of risk exposure factor For example, TABLE (Required) Risk No Problem Probability of occurrence of problem Impact of problem Risk exposure Priority R1 Issue of incorrect password 2 2 4 10 R2 Testing reveals a lot of defects 1 9 9 7 R3 Design is not robust 2 7 14 5 3. Risk Avoidance and Mitigation: The purpose of this technique is to altogether eliminate the occurrence of risks. so the method to avoid risks is to reduce the scope of projects by removing non-essential requirements. 4. Risk Monitoring: In this technique, the risk is monitored continuously by reevaluating the risks, the impact of risk, and the probability of occ...

Identification, Projection, RMMM Stakeholders (SH) are people or organizations (legal entities such as companies, standards bodies) which have a valid interest in the system. They may be affected by it either directly or indirectly. A major new emphasis in the 1990s was a focus on the identification of stakeholders. It is increasingly recognized that stakeholders are not limited to the organization employing the analyst. Other stakeholders will include: · anyone who operates the system (normal and maintenance operators) · anyone who benefits from the system (functional, political, financial and social beneficiaries) · anyone involved in purchasing or procuring the system. In a mass-market product organization, product management, marketing and sometimes sales act as surrogate consumers (mass-market customers) to guide development of the product · organizations which regulate aspects of the system (financial, safety, and other regulators) · people or organizations opposed to the system (negative stakeholders; see also Misuse case) · organizations responsible for systems which interface with the system under design · those organizations who integrate horizontally with the organization for whom the analyst is designing the system Projection Risk Projection (aka Risk Estimation) Attempts to rate each risk in two ways · · The probability that the risk is real · · The consequences of the problems associated with the risk, should it occur. Project planner, along with other manage...