The Importance of Risk Control

Executive Summary

In the design of this report I wish to find an understanding of how the areas of risk, quality and testing can be emphasized in software projects. When the research of the areas is complete I will then attempt to portray how these areas will impact on the system that the group I am part of are expected to design for Games4U. This will be done by examining the risks that will be involved in the group creating the system, identifying the quality that is required in creating the system and the testing that will be needed to insure the system is implemented correctly.

Introduction

The following report will give you the complete understanding of the elements of risk, quality and testing when designing a system. This was achieved through the analysis of academic books and journals while conducting research on the subjects lined out above. The three elements will also be revealed as to how they are implemented inside the system the group I am in for Games4U. The first area of risk will be shown by explaining the potential risk and examining the likely hood of that risk, how it will affect the system and how it could be avoided. Testing will be identified in three areas, Structural (white-box), Behavioural (black-box) and Live (Alpha/Beta). Through the research completed on these three areas the explanation of how these three testing methods can help Games4U system will be conducted and portrayed. Quality will then be researched and it will be implementing with respect for the users wishes and the feedback that they give regarding a certain area in which they test.

Risk

Risk in software projects can play a major role in the outcome of a system. Roberta M. Roth et al. (2013) describes the areas that can affect a system, with regard to risk as “weak personal, scope creep, poor design and overly optimistic estimates.” A project team should create a risk assessment or a document that locates the potential risks. Therefore as part of the team that designed Games4U it was necessary to create one.

Risk 1:

This is the first time the team has created a system within a website; Java will be used along with HTML code that has never been combined together while creating a system by this group.

Likelihood of risk:

High probability of risk

Potential Impact on project:

This risk is likely to lead to some error with the output system. It will also increase the time it takes to complete the system.

Ways to avoid this risk:

This potential risk could be avoided if the members of the group undergo a learning session in the

...