OTIENO JAMES OLIECH

SCT213-C002-0052/2021

BSC DATA SCIENCE AND ANALYTICS

ICS 2302 SOFTWARE ENGINEERING

CAT 2

1. The process of requirement engineering.

i. Feasibility study; this is an approach done to assess whether the software to be
developed would be beneficial in terms of profit and productive and a subject to
adaptability.
ii. Requirement elicitation and analysis; this is the process where all necessary
information about the software to be developed is collected with the help of the
customer and analyzed to remove or identify any error.
iii. Software requirement specification; this is a document created by the software
analyst after collecting requirement details written in ordinary language and
presented to the customer.
iv. Software requirement validation; the requirements are checked if they are valid,
legal and can be practically implemented.
v. Software management; this refers to the process of implementing changes in
either the requirements or technology during the software development process.
2. how to solve risk quantification problems between the customer and the
contractor

Communication between the developer and customer should encourage constant

feedback about the development of the project through regular meetings. Overall,
collaboration between the customer and the contractor should be the ultimate way
to resolve a matter of dispute. Members from both the customer and contractor
side should meet discuss historical events, modeling and simulation to arrive at
the appropriate answer. Ensure the terms and condition on the contract are
legitimate and the risks likely to occur are covered under this contract.

3. List and explain two types of risk

i. Technical risk; this refers to a type of risk that occur when only part of the
development team are familiar with the technology being used.
ii. Business risk; this refers to a type of risk that would occur if the developers
create a software that is of no use hence attracts little or no demand hence no
profit can be generated from the project.
4. steps of risk management process
 i. Risk Identification; the developers should be in a position to
anticipate and predict risk that may occur in the future; here they try
to categorize the type of risk that could occur.
ii. Risk analysis; this is where all the type of risks identified are
analyzed and the severity of the risks identified.
iii. Risk prioritization; each risk is ranked according to its likelihood of
happening and its overall effect on the software project.
iv. Risk Planning; each of the mentioned risks is considered and ways
to maintain these risks are developed.
v. Risk monitoring; this refers to the process of keeping close tabs on
these risk and maintaining awareness considering the likelihood of
their occurrence.