Scribd
Upload
3K views7 pages

Risk Mitigation, Monitoring, and Management (RMMM) Plan: Module-6

The document discusses the Risk Mitigation, Monitoring, and Management (RMMM) plan which includes risk mitigation, monitoring, and management. It describes the objectives and steps for each component. Risk mitigation aims to avoid risks, monitoring tracks risks, and management addresses risks that occur. The document also discusses software quality, quality assurance versus quality control, formal technical reviews, software reliability, software configuration management, and version control systems.

Uploaded by

SHUBHAM SHAH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3K views7 pages

Risk Mitigation, Monitoring, and Management (RMMM) Plan: Module-6

The document discusses the Risk Mitigation, Monitoring, and Management (RMMM) plan which includes risk mitigation, monitoring, and management. It describes the objectives and steps for each component. Risk mitigation aims to avoid risks, monitoring tracks risks, and management addresses risks that occur. The document also discusses software quality, quality assurance versus quality control, formal technical reviews, software reliability, software configuration management, and version control systems.

Uploaded by

SHUBHAM SHAH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Module-6

Risk Mitigation, Monitoring, and


Management (RMMM) plan
A risk management technique is usually seen in the software Project plan.

This can be divided into Risk Mitigation, Monitoring, and Management Plan
(RMMM).

In this plan, all works are done as part of risk analysis.

As part of the overall project plan project manager generally uses this RMMM
plan.

Risk Mitigation :
It is an activity used to avoid problems (Risk Avoidance).
Steps for mitigating the risks as follows.

1. Finding out the risk.


2. Removing causes that are the reason for risk creation.
3. Controlling the corresponding documents from time to time.
4. Conducting timely reviews to speed up the work.

Risk Monitoring :
It is an activity used for project tracking.
It has the following primary objectives as follows.

1. To check if predicted risks occur or not.


2. To ensure proper application of risk aversion steps defined for risk.
3. To collect data for future risk analysis.
4. To allocate what problems are caused by which risks throughout the
project.

Risk Management and planning :


It assumes that the mitigation activity failed and the risk is a reality. This task is
done by Project manager when risk becomes reality and causes severe
problems. If the project manager effectively uses project mitigation to remove
risks successfully then it is easier to manage the risks. This shows that the
response that will be taken for each risk by a manager. The main objective of
the risk management plan is the risk register. This risk register describes and
focuses on the predicted threats to a software project.

Drawbacks of RMMM:
• It incurs additional project costs.
• It takes additional time.
• For larger projects, implementing an RMMM may itself turn out to be
another tedious project.
• RMMM does not guarantee a risk-free project, infact, risks may also
come up after the project is delivered.

Software Quality
Software quality product is defined in term of its fitness of purpose.

Example: Consider a functionally correct software product. That is, it performs all tasks as
specified in the SRS document. But, has an almost unusable user interface. Even though it may
be functionally right, we cannot consider it to be a quality product.

Portability: A software device is said to be portable, if it can be freely made to work in


various operating system environments, in multiple machines, with other software
products, etc.

Usability: A software product has better usability if various categories of users can easily
invoke the functions of the product.

Reusability: A software product has excellent reusability if different modules of the


product can quickly be reused to develop new products.

Correctness: A software product is correct if various requirements as specified in the SRS


document have been correctly implemented.

Maintainability: A software product is maintainable if bugs can be easily corrected as


and when they show up, new tasks can be easily added to the product, and the
functionalities of the product can be easily modified, etc.
Quality Assurance v/s Quality control
Quality Assurance Quality Control

Quality Assurance (QA) is the set of actions including Quality Control (QC) is described as the
facilitation, training, measurement, and analysis needed to processes and methods used to compare
provide adequate confidence that processes are product quality to requirements and
established and continuously improved to produce applicable standards, and the actions are
products or services that conform to specifications and are taken when a nonconformance is detected.
fit for use.

QA is an activity that establishes and calculates the QC is an activity that demonstrates whether
processes that produce the product. If there is no process, or not the product produced met standards.
there is no role for QA.

QA helps establish process QC relates to a particular product or service

QA sets up a measurement program to evaluate processes QC verified whether particular attributes exist,
or do not exist, in a explicit product or service.

QA identifies weakness in processes and improves them QC identifies defects for the primary goals of
correcting errors.

Quality Assurance is a managerial tool. Quality Control is a corrective tool.

Verification is an example of QA. Validation is an example of QC.

Formal Technical Review (FTR)


Formal Technical Review (FTR) is a software quality control activity performed
by software engineers.

Review reporting and record keeping :-

It answers three questions :-


1. What was reviewed ?
2. Who reviewed it ?
3. What were the findings and conclusions ?

Software Reliability
Software Reliability means Operational reliability. It is described as the ability of a
system or component to perform its required functions under static conditions for a
specific period.

The complexity of software is inversely associated with software reliability

Software reliability is also defined as the probability that a software system fulfills its
assigned task in a given environment for a predefined number of input cases, assuming
that the hardware and the input are free of error.

Software Configuration Management


The elements that comprise all information produced as a part of the software process
are collectively called a software configuration.

The objective is to maximize productivity by minimizing mistakes (errors).

Configuration Management (CM) is a technic of identifying, organizing, and controlling


modification to software being built by a programming team.

SCM is used in keeping a system in a consistent state by automatically producing derived


version upon modification of the same component.
SCM Process
It uses the tools which keep that the necessary change has been implemented adequately
to the appropriate component. The SCM process defines a number of tasks:

o Identification of objects in the software configuration


o Version Control
o Change Control
o Configuration Audit
o Status Reporting

Version Control
o Version Control combines procedures and tools to handle different version of
configuration objects that are generated during the software process.

o The "check-in" and "check-out" process implements two necessary elements of


change control-access control and synchronization control.
o Access Control governs which software engineers have the authority to access and
modify a particular configuration object.
o Synchronization Control helps to ensure that parallel changes, performed by two
different people, don't overwrite one another.

Change Control

Change Management in software development refers to the transition from an


existing state of the software product to another improved state of the product.

Change control is a systematic approach to managing all changes made to a product or


system

Version Control Systems


What is a “version control system”?
Version control systems are a category of software tools that helps in recording
changes made to files by keeping a track of modifications done to the code.
Use of Version Control System:

• A repository: It can be thought of as a database of changes. It


contains all the edits and historical versions (snapshots) of the project.

• Copy of Work (sometimes called as checkout): It is the personal


copy of all the files in a project. You can edit to this copy, without
affecting the work of others and you can finally commit your changes
to a repository when you are done making your changes.

Types of Version Control Systems:

• Local Version Control Systems


• Centralized Version Control Systems
• Distributed Version Control Systems

You might also like