Software engineering: risk features in requirement engineering

The term risk is defined as the potential future harm that may arise due to some present actions. Risk management in software engineering is related to the various future harms that could be possible on the software due to some minor or non-noticeable mistakes in software development project or process. There are quite different types of risk analysis that can be used. Basically, risk analysis identifies the high risk elements of a project in software engineering. Also, it provides ways of detailing the impact of risk mitigation strategies. Risk analysis has also been found to be most important in the software design phase to evaluate criticality of the system. The main purpose of risk analysis understands the risks in better ways and to verify and correct the attributes. A successful risk analysis includes important elements like problem definition, problem formulation, data collection. Some of the requirement risks are Poor definition of requirements, Inadequate of requirements, Lack of testing, poor definition of requirements etc. The likelihood of the events which tends to the goal can be evaluated from the evidence of Satisfaction and denial of the goal and it can be achieved through Tropos goal model. Original Tropos model is modified to meet the risk assessment requirements in requirements engineering. The event considers as a risk which based on the likelihood values. The relations are defined between multiple goals and events, which identify the necessity of a particular goal. In order to analyze the risk in achieving some particular goals, a set of candidate solutions are generated. Based on the risk affinitive value, the candidate solutions can be evaluated. There are three risk parameters to compute the risk affinitive value, which are (1) low (2) medium (3) high. The risk parameters and cost analysis clearly evaluate the affinity of that event to a particular set of goals.