Software Requirements Analysis Fifth chapter

Software Requirements Analysis Fifth chapter

First, we should make clear what is the basis of software risk management, including inaccurate estimates, the accurate estimation of the veto, the status of the project is unclear, capital turnover, technical risks, lack of knowledge and so we need to carefully conduct risk management for each project

First, identify the elements of risk management, so-called risk management is the use of certain tools and procedures to limit project risk to an acceptable scope, risk management including risk assessment is a review project engineering and identify its potential risk areas, risk avoidance, risk avoidance is a way to deal with risk is to try not to do risky things, But more often than not, risk control is required to develop a risk management plan is a program that deals with significant risks, including methods for mitigating risks, contingency plans, responsible persons, and deadlines.

It is not enough to recognize the risks that the project is facing. It should be documented and managed properly so that stakeholders understand the risk situation and status throughout the project development process. When writing a risk statement, it is best to adopt the condition-the form of the result. That is, first describe the conditions you care about, followed by potentially harmful results (if the risk becomes a fact). A template can record the likelihood of a risk becoming a fact and its negative impact on the project, as well as the overall risk value (likelihood x impact). We can define the activities to be taken to control risk by developing a risk reduction plan some of these strategies are to minimize the likelihood of risk occurring, while others reduce the impact of the risk. We also note that a risk list is not equal to a risk management plan, but a large project requires a separate risk management plan and other project management activities, you need to establish periodic monitoring measures. Maintain a high level of attention to the risk of 10 or more hazards and track the effectiveness of risk mitigation measures.

Software Requirements Analysis Fifth chapter