https://drive.google.com/drive/folders/1f0ckKlrmbPcm1rI1B6yeDz9kDN9AG5s2?usp=sharing

UNIT - 5

Topics:

Metrics for Process and Products: Software measurement, metrics for software quality. Risk management: Reactive Vs proactive risk strategies, software risks, risk identification, risk projection, risk refinement, RMMM, RMMM plan.

Software Measurement

Software Measurement: A measurement is a manifestation of the size, quantity, amount, or dimension of a particular attribute of a product or process. Software measurement is a titrate impute of a characteristic of a software product or the software process. Classification of Software Measurement

There are 2 types of software measurement:

1. Direct Measurement: In direct measurement, the product, process, or thing is measured directly using a standard scale.
2. Indirect Measurement: In indirect measurement, the quantity or quality to be measured is measured using related parameters i.e. by use of reference.

Reactive vs Proactive risk strategies

Reactive Risk Strategies:

1. Definition: Reactive strategies involve responding to risks after they have occurred or become apparent.
2. Characteristics:
   • Damage Control: Focuses on minimizing the impact of risks that have already materialized.
   • Event-driven: Actions are triggered by the occurrence of specific risks or incidents.
   • Short-term focus: Primarily deals with immediate consequences rather than preventing future occurrences.

Proactive Risk Strategies:

1. Definition: Proactive strategies involve anticipating and preparing for risks before they manifest.