Question

Q: Complete the following "Reason column" for your software engineering risk analysis project.

Please Note that there is a sample for filling the reason column please see it.

Risk	Probability	Effects	Reason
Organizational financial problems force reductions in the project budget (7).	Low	Catastrophic
It is impossible to recruit staff with the skills required for the project (3).	High	Catastrophic
Key staff are ill at critical times in the project (4).	Moderate	Serious
Faults in reusable software components have to be repaired before these components are reused. (2).	Moderate	Serious
Changes to requirements that require major design rework are proposed (10).	Moderate	Serious
The organization is restructured so that different management are responsible for the project (6).	High	Serious
The database used in the system cannot process as many transactions per second as expected (1).	Moderate	Serious
The time required to develop the software is underestimated (12).	High	Serious
Software tools cannot be integrated (9).	High	Tolerable
Customers fail to understand the impact of requirements changes (11).	Moderate	Tolerable
Required training for staff is not available (5).	Moderate	Tolerable
The rate of defect repair is underestimated (13).	Moderate	Tolerable
The size of the software is underestimated (14).	High	Tolerable
Code generated by code generation tools is inefficient (8).	Moderate	Insignificant

A sample for Completing the reason column :-

Risk	Probability	Effects	Reason
Development of the wrong user interface which will result in redesign and implementation from scratch.(1)	High	Catastrophic	Probability of such risk is high due to the presence of more than one service and different requirements. It causes a catastrophic effect because it basically doesn’t meet the assigned requirements.
Depending on a technology that is still being developed. (2)	Low	Serious	The occurrence of this risk due to the presence of only one technology but it doesn’t usually happen and it causes a serious issue in the time and cost of the project.
Too much conflicts among team members developing the software will result in poor communication and therefore poor designing, incomplete work and late delivery of the product.(3)	Moderate	Catastrophic	Too much disagreement in any team designing has a chance of 50% occurring due to each member having a different point of view. If such risk occurs, it is going to cause a huge mess and an imbalance. Therefore, the project will not be delivered correctly and on time.
Replacement of team members or change in tasks among between the team members. (4)	High	Serious	Sometimes a member or more in a team can fail to complete his task and therefore pass it to another team member or probably switch tasks due to improper division of work. Also, team members might leave and therefore replaced by others which will cause conflicts related with time and organization.
Failing to integrate the software tools. (5)	High	Tolerable	In most cases, incorporating software tools along with the project is a concern. However, it is not that much of a concern because it can be easily fixed by training or by seeking the help of a specialist.
Introduction of new requirements according to the customer’s desire.(6)	Very High	Serious	Customers have unlimited requirements and expectations. This is why the risk of introducing new requirements is really high. In addition, it will cause re-developing or re-designing some software functions of the system and this is costly and time-consuming.
Software productivity rate is overestimated.(7)	High	Tolerable	Software productivity is often assumed to be quick by most developers. Nevertheless, they get surprised that it is not. However, it does not cause that much of a great impact on the development.
The size of the software and integration effort is underestimated. (8)	High	Serious	Misinterpretation of the amount of effort to build the software is always an issue. Developers don’t realise this issue until they start actually developing the functions of the system which is approximately halfway through the development process. They also don’t realise how bad it can get when time starts running out and the project is not even past halfway the assigned time for the project.