Risk Driven Testing , Managing Risks and Quality Assurance : An Introspection and Benchmarking Implementation

Abstract

Extensive literature has been surveyed related to risk, risk management, risk oriented testing, software quality assurance, computing environment for risk oriented testing. Various kind of studies i.e. Modeling, Theoretical, review, simulation, case study, action research, experimental, empirical and exemplary have been explored to find out the answers for the research questions. The research is qualitative and descriptive in nature. II. RISK MANAGEMENT In this section, we have analyzed perspectives on project risks and risk management. A. Risk Risk characterization is done by two main factors i.e. Probability of occurrence and Severity of potential failure [4]. Probability of Occurrence is output of backward risks and consequence is output of forward risks [5].Risk is a futuristic harm that can arise from present actions taken. It comprises of uncertainty or lack of information [6] that can probably lead to loss [7]. Modifiers associated with risk are Risk proxy, Risk profile and Risk exposure [8]. Risk is one amongst the critical aspects in project management [9] and technological projects [10].Increase in the intensity of risk management strategies in the past years is because of socio economic pressures imposed by economics, politics and public awareness as software engineering without risk planning is riskier than ever [11]. C. Risk Drivers Following are the required drivers for risk in a software project [12]: Software Availability: ability to deliver services whenever required. Security: Accidental attacks are prevented. Reliability: As per specification delivering the software services. Safety: Operating software by protecting it from dangerous states. Resilience: Recovering from unexpected faults timely. D. Risk Factors Risks factors are used for quantifying the Risk [12]. The risk factors may include Risk Exposure, Risk Proxy or risk profile. Where Risk Exposure: =Risk Impact* Risk Likelihood E. Risk in Software Testing If risks are identified and assessed in the software testing life cycle phases i.e. planning of test cases, test selection, test prioritization, test designing, test coding and execution then software quality gets enhanced to a higher degree. Risks assessment is required to be done with effective planning so that project losses are minimized to a greater extent. For balancing the effort employed in the system and for avoidance of disasters risk probability and impact are predicted as accurate as possible. F. Project Risk Management Risk management is conglomeration of following four stages: Identification of all risk factors, Analysis and assessment of various risk factors, To draw out plan for managing risks, Monitoring the risk plan and assessment strategies for continuous quality improvement. G. Stages of Risk Management Following are various stages of risk management: Risk Identification: This is approached by collecting all information about resources i.e. project plan and risk plan once roles and responsibilities are assigned completely. Approaches for Risk Identification: Following are the approaches by which risks can be identified in a software project: Brainstorming, Checklist analysis, Cross functional teams, Root cause identification, Documentation reviews, Diagramming techniques, Delphi technique, Interviewing, Surveys, Force field analysis. Risk Assessment: Risk assessment means how we are going to estimate impact and consequence of risk on project life cycle and taking care of overall accuracy in perceiving the likelihood of risk. Approaches for Risk Assessment: Probabilistic approach, Decision tree and decision focus, Questionnaires, Risk metrics, Vulnerability metrics, Likelihood and loss expectancy, Impact and consequence, Risk exposure. Risk Planning: Risk is planned either by avoiding or by making a contingency plan for minimizing the risk. Approaches for Risk Planning: Conducting market research, Risk pre-warning indexing, Changing technology, detailed study, Profit rate and Volatility rate, using consultants. Risk Monitoring: Based on resource requirements risks such strategies aim to either reduce or transfer the risk exposure effect on software project. This type of strategies focus on how project risks are avoided or mitigated and further helps in project continuous quality improvement. Approaches for Risk Monitoring: Industrial survey, Rough Set theory.