CHAPTER 3

BSIT-4108-
07A








CHAPTER 3

3.1 Risk Mitigation, Monitoring, and Management Plan

3.1.1 Introduction
This section gives an overview of the Risk Mitigation,
Monitoring and Management Plan for the Student Information
Systems General Ledger with Accounts Payable and Receivable in
Tertiary level.
Mitigation, as the word itself is a process of developing
options and actions to enhance opportunities and reduce
seriousness, severity, threats to protect objectives, and monitoring
to assess whether risk occur or not, ensuring the steps are being
properly applied for future risk analysis. In risk management, the
proponents plan is to jot down actions to be taken in the event that
mitigation steps have failed and the risk has become the actual
problem.

3.1.1.1 Scope and Intent of RMMM Activities
The proponents plan is to create an error free
system which is very difficult to attain. To be safe, the
proponents created a risk management plan to
counter all the possible hindrances that may affect the
operation, the development or the completion of this
study.

3.1.1.2 Risk Management Organizational Role
The proponents have the responsibility of
managing risk in the development of the software. All
of the identified risk at the early phase of the system
development may be avoided.

3.1.2 Functional Data Description
This section describes the risks that can possibly encounter
during the production of this study.
3.1.2.1 Risk Table

3.1.2.1.1 Description of Risk M

Financial Risk
This risk is concern about the financial
stability of a company or firm. It is the risk
where to determine if an organization will be
adequate enough to meet the financial
obligations of the proposed system.

Schedule/Availability Risk


Development Risk
This risk refers to the client who are not
able to provide the resources that the proposed
system may need to build an efficient
information system.

Downloadable Files
This risk refers to those unsecured files
or software that can be downloaded in an
open-source. This software can harm the
proposed system and also can cause errors.

Technology Risk
This risk is concern about the rapid
changes in the technology. It is where to
determine whether the resources to be used in
developing the proposed system are functional
or soon to be obsolete.

Human Related Risk
This risk refers to the people involved in
the proposed system. They can be a big factor
that can affect the system.

3.1.2.1.2 Probability and Impact for Risk M
The following is the sorted version of the
above table by probability and impact:

3.1.3 Risk Mitigation, Monitoring and Management
3.1.3.1 Risk Mitigation for Risk M
3.1.3.1.1 P
3.1.3.2 Risk Monitoring for Risk M
3.1.3.3 Risk Management for Risk M
3.1.4 Special Conditions
3.2 Software Configuration Management Plan
3.2.1 Introduction
3.2.1.1 Scope and Intent of SCM Activities
3.2.1.2 SCM Organizational Role
3.2.2 Software Configuration Management Tasks
3.2.2.1 Identification
3.2.2.1.1 Description
3.2.2.1.2 Work Products and Documentation
3.2.2.2 Configuration Control
3.2.2.2.1 Description
3.2.2.3 Version Control
3.2.2.3.1 Description
3.2.2.3.2 Increasing Version Number
3.2.2.3.3 Work Products and Documentation
3.2.2.4 Configuration Status Accounting (CSA)
3.2.2.4.1 Description
3.2.2.4.2 Work Products and Documentation
3.2.3 Software Quality Assurance Overview
3.2.3.1 Scope and Intent of SQA Activities
3.2.3.2 Reviews and Audits
3.2.3.2.1 Generic Review Guidelines
3.2.3.2.2 Formal Technical Reviews
3.2.3.2.3 SQA Audits
3.2.3.3 Problem Reporting and Corrective Action/Follow-up
3.2.3.3.1 Reporting Mechanisms
3.2.3.3.2 Responsibilities
3.2.3.3.3 Data Collection and Valuation
3.3 Software Quality Assurance Plan
3.3.1 Introduction
3.3.1.1 Scope and Intent of SQA Activities
3.3.1.2 SQA Organizational Role
3.3.2 SQA Tasks
3.3.2.1 Task Overview
3.3.2.2 Standard, Practices and Conventions (SPC)
3.3.2.3 SQA Resources
3.3.3 Reviews and audits
3.3.3.1 Generic Review Guidelines
3.3.3.2 Formal Technical Reviews
3.3.3.3 SQA Audits
3.3.4 Problem Reporting and Corrective Action/Follow-up
3.3.4.1 Reporting Mechanisms
3.3.4.2 Responsibilities
3.3.4.3 Data Collection and Valuation
3.3.4.4 Statistical SQA
3.3.5 Software Process Improvement Activities
3.3.5.1 Goal and Object of SPI
3.3.5.2 SPI Tasks and Responsibilities
3.3.6 SQA Tools, Techniques, Methods
3.4 System Specification
3.5 Software Requirements Specification
3.6 Software Design Specification
3.7 Test Specification