software engineering -test 1-(part 4)
RISK MITIGATION TYPES
Risk avoidance
Risk acceptance
Risk transfer
Risk Reduction
Risk avoidance
This is best suited in situations where the costs of mitigating risks are more
than the benefits. Opting to stop construction die to potential storm.
Risk acceptance
Accept the risk, let it happen. Example, Amazon delivery (no guarantee that
the item will be delivered to the right address).
Risk transfer
The process of allocating a portion of risk to a third party. Example, an insurance
policy.
Risk Reduction
Risk reduction involves taking steps to minimize the likelihood or impact of
potential risks. This can include implementing safety measures, conducting regular inspections, or
investing in backup systems.
COCOMO ESTIMATION MODELS (Cont.)
1) It picks an estimation for a project based on the Project mode.
2) Estimate the size of the project, in thousand lines of code (KLOC).
3) Review fifteen factors, known as cost-drivers, and estimate the amount of impact each factor will
have on the project.
4) Determine the effort for the software project by inserting the estimated values into the effort
formula for the chosen mode.
PROJECT
FUNCTION POINT ANALYSIS
The Functional Point Analysis (FPA) is a one of the most popularly used software estimation
technique to measure the functional size of the software work.
The Functional Point (FP) is the measurement of functional size of the software application.
• Each component is assigned a weight, based on three possible descriptions of the project:
1. Simple
2. Average
3. Complex
Number of External Inputs(EI)
Data entry by users & Data or file feeds by
external applications
Number of External Output (EO)
Output screens and reports
Number of external inquiries (EQ)
Prompts and interrupts.
Number of internal files (ILF)
Databases and directories (Data storage)
Number of external interfaces (EIF)
Shared databases and shared routines.