A Review Study: Automated Risk IdentificationTool For Software Development Process
Omni Thakur*, Janpreet Singh
Department of Computer Science Engineering, Lovely Professional University (Punjab)
Article Publishing History
Article Received on :
Article Accepted on :
Article Published : 05 Jul 2014
Article Metrics
ABSTRACT:
Risk Identification tools are usually established for avoiding or minimizing problems, likely to occur during software development. It can be stated as the task of analysing and managing the impact of every important risk occurred in the project. In the context of Risk Identification tool practices, we developed a scoping study, aiming at analysing the current scenario of Risk Identification practices in software development process. We analysed different studies published by the most important venues published up to the year 2013. Based on the analysed data set, we sketched a set of useful techniques and tools for applying Risk Identification in software projects. The analysis indicates that most of the studies subjectively describe ways to evaluate risks, instead of providing readers with details on how Risk Identification is to be performed. Such findings points out to the need of further research in the field of Risk Management, especially for the identification of risks in software development process for better results.
KEYWORDS:
Risk Management; Risk Identification; Risk Index; Risk Analysis; Risk Assessment
Copy the following to cite this article:
Thakur O, Singh J. A Review Study: Automated Risk Identification Tool For Software Development Process. Orient. J. Comp. Sci. and Technol;7(1)
|
Copy the following to cite this URL:
Thakur O, Singh J. A Review Study: Automated Risk Identification Tool For Software Development Process. Orient. J. Comp. Sci. and Technol;7(1). Available from: http://computerscijournal.org/?p=766
|
INTRODUCTION
The risk management is all about managing the risks which occur. Many concepts of software risk management are there but the most important from them are risk index (can be categorised as high level risk, medium level risk and low level risk), risk assessment (it involves the accurate understanding of the current system and it’s all other features like security), risk analysis (used to identify the risk elements of a project with high probability).[5](Luanna Lopes Lobato, 2012) As the technology is increasing very fast, the developed applications are having
The complex user interface and these developed applications run on the various systems simultaneous like applications which support client server architecture. Due to the complexity and the nature of the developed application these are able to run on the various operating systems. To overcome these types of problems we want to evaluate the performance and other factor of the application and this can be done by defining some set of rules. These types of problems include the concept, strategies and practices of software engineering. With the help of including these concepts we can evaluate the performance and other relevant factors of the application. Before proceeding further we have to take in consideration some of the major failures that will lead to software failure before delivering the application to the customer. Those major failures
- It can be poor user input.
- Stockholder Conflicts can be there.
- Vague requirements.
- It can be poor cost and schedule requirements.
- Can be due to wrong analysis of the requirements.
- Can be due to communication breakdown.
- Can be due to architectural breakdown.
1.1 RISK MANANGEMENT PROCESS
There are several models available for risk management. The model recommended in this section was developed by the Software Engineering Institute (SEI).
Identify
Before risks can be managed its must be identified before adversely affecting the project.
Analyse
Analysis is the conversion of risk data into risk decision-making information. It includes reviewing, prioritizing and selecting the most critical risks to address. The Software Risk Evaluation (SRE) Team analyses each identified risk in terms of its consequence on cost, schedule, performance and product quality.
Plan
Planning turns risk information into decisions and actions for both the present and future. Planning involves developing actions to address individual risks, prioritizing risk actions and creating a Risk Management Plan. The key to risk action planning is to consider the future consequences of a decision made today.
Track
Tracking consists of monitoring the status of risks and the actions taken against risks to mitigate them.
Control
Risk control relies on project management processes to control risk action plans, correct for variations from plans, respond to triggering events, and improve risk.
The risk management process consists of ten steps as described in the diagram. Use of the activities associated with these steps constitutes an acceptable risk management approach and could be incorporated into a Risk Management Plan. The size, visibility, or consequences of the project drives the complexity of the process. The steps can be
- Identify Risks
- Analyse Risk
- Prioritize Risk
- Identify Risk Aversion Methods
- Identify Risk Mitigation Methods
- Identify Risk Recovery Methods
- Define Risk Metrics
- Implement Mitigation Actions
- Track Risk
- Implement Contingency action
Risk identification team determines Risks which are categorizes according to the Risk Levels by mapping each risks onto a Risk Matrix. The risk levels are defined as:
- Tolerable Risk: risk is identified as having little or no effect or consequence on project objectives.
- Low Risk: risk is identified as having minor effects on project objectives.
- Medium Risk: risk is identified as one that could possibly affect project objectives, cost or schedule.
- High Risk: risk is identified as having a high probability of occurrence and the consequences would affect project objectives.
- Intolerable Risk: risk is identified as having a high probability of occurrence and the consequences would have significant impact on cost, schedule and performance.
1.2 RISK CLASSIFICATION
Risk classification is considered as the proper way to analyse risks and group similar types of risk in different categories or classes. Software risks can be internal risk or external risk.
Risk in software requirements
-No proper requirements gathering.
-No proper documentation.
-The definition of the requirement is very poor.
-On the spot change of requirements.
Risk in software cost
-Poor estimation of the projects cost.
-Poor working of the hardware.
-No proper testing techniques used.
-No proper monitoring.
-Due to the Complexity of architecture.
-Also due to the large size of architecture.
Software scheduling Risk
-Due to the change in requirements and their extension.
-Inadequate knowledge about tools and techniques.
-Due to the lack of manager experience.
-Due to the lack of knowledge and the skills.
-Due to the lack of good estimation in projects.
Software quality Risk
-Due to the extension of requirements change.
-Absence of design documentation.
-Due to the inadequate documentation.
-Due to the absence of project standard.
-No proper estimation of budget.
-Poor definition of requirements.
-Due to insufficient knowledge skills.
II. REVIEW OF LITERATURE
(Arefeen, 2011) In [1] many software risks have been discussed. The management of the software risk has provided a disciplined environment for decision making to assess continuously the wrong things which are happening and determining the risks which are occurring and the actions which can be taken to deal with these kinds of risks. The objective of managing the risk is to identify problems which had occurred before so that the activities which can help to handle the risk can be planned and invoked as needed. The planning of the risk management addresses the risk management strategies, the processes, methods, the techniques and tools which are to be used to support the process of risk management.
(Basri, 2011) In [2]the author has discussed about the assessment of the risk in software projects development. Risk has been explained as the probability of the loss suffered which shows the impact on the project. This can be stated as a worst quality of the software solutions and results. The essential risk factors affect the software projects which lead to the unsuccessfulness of the software projects. Risk can be reduced and managed in accordance with tight planning and assessment. To formulate different types of risk the risk management is equally divide into two categories i.e. risk controlling and risk assessment. Firstly the risk control can be divided into three sub parts i.e. planning of risk management, risk monitoring and risk resolution. Secondly the assessment of the risk is also dividing into three sub parts i.e. analysing the risk, identifying the risk and prioritizing the risk.
(Shiva Mansoorzadeh, 2011) In [6]the discussion of the author is all about the scheduling of the projects reliability. In this paper the optimization of scheduling will be viewed from the perspective of the reliability. There are many issues related to the scheduling of the project but the two main issues related are a) duration of the project b) uncertainty about the project duration. In the software development process the critical path keeps on changing with the progress of each project. In this reliable project scheduling approach which has taken in consideration the integration of risk management and critical chain schedule analysis both. In the method which is proposed has analysed the risk of the potential projects and the strategies of their responses which are developed by the failure mode of fuzzy and the effective analysis.
(Yogini Bazar, March 2012) In [7] the author in this paper has discussed about the models of the risk assessment at this time software engineering, there is static and dynamic environment of the software development which leads to several faults and errors which are to be handled and taken care of. Managing a risk means a solution that helps to understand the software team and manage the uncertainties. It is important to measure the level of uncertainty and the degree of loss associated with each risk when the risks are analysed. Everyone involved in the software development projects participate in risk analysis and management. Due to poor risk management and poor estimation of budget many software development projects miss their goals of delivering a acceptable software product. The author in this paper has discussed the software models of risk assessment and their comparison according to various risk elements.
(Dr. M. M. Sharma, 2013) In [3] this paper it is briefly discussed about the tools which help to remove risk that are presented in software engineering. Managing risk is the figurative process in which the risk factors are identified systematically, are being assessed and are being mitigated. In a project management the toughest part is to find out the risk in the software project. As it is believed that no IT Project can ever be remain free of errors or risk. In this paper, author proposed a framework of automated risk removal model. This model helps to identifies, classifies and generates solution to solve the problems. These problems caused by software risks. This is a phase wise process of risk removal. This is a phase wise process of risk removal. First, risk sources and risks are identified, after that they are classified, and then solution patches are generated and applied on encountered problem.
(Julio Menezes Jr., APRIL 2013) [4] Project management is very necessary while developing a project. For developing a project, the project manager faces the many difficulties related to project failure, risk assessment and so on. Project management is related to one of the discipline of management of risk whose usage is becoming necessary as in the increase of the size and growing in the complexity of software. The software development environments has a great importance for knowing the usage of processes, tools that are being used in the risk management and the techniques used. The resources are shared if the different projects are executed simultaneously one after another. In this paper the indicators which are specific to the software project environment are defined which helps in supporting the risk assessment activities, risk analysis and identification of risk.
CONCLUSION
Now a days, present risk identification tools do not clearly address where the risk is coming from and how the problems caused by the risks and what can be taken to the solution. Available techniques do not provide automated software risk removal.
Automated risk identification tool is novel method which gives different phases of risk identification. In present work lots of methods are used for risk identification. They starts from first phase of identification of software risks and its sources and after then they are identified and analysed before going into next phase. Once the risks are identified then it can be easily classified that it’s as probability of low level risk, probability of medium low risk, probability of medium level risk , probability of medium high level risk, and probability of high level risk.
PROPOSED WORK
The proposed work can be done on the basis of experience of software development experts. We can develop a tool which can help the new software developers to overcome different risks during software development. The proposed tool will help them to tell them that if they choose this way then they may face this type of risk. For example if developer is adding number of very complex algorithms in software then they can create risk for low performance due to high complexity. Now our purposed tool contains all factors that can cause for risk creation and from this tool developer can easily check that what kind of risks he can face during development means this tool will gives the estimation of risk occurrence.
REFERENCES
- Arefeen, A. A. (2011). “Sotware Risk management: Importance and Practices.” IJCIT, pp. 49-54.
- Basri. (2011). “A study on Risk Assessment for Small and Medium Software.” International Journal on New Computer Architectures and Their Applications(IJNCAA), pp. 325-335.
- Dr. M. M. Sharma, A. K. (2013). ”Pioneering an Automated Risk Removal Tools in Software Engineering”. IEEE (pp. 104-107). Ajmer,India: International Conference on Information Systems and Computer Networks.
- Julio Menezes Jr., C. G. (APRIL 2013). “Defining Indicators for Risk Assessment in Software Development Projects.” CLEI ELECTRONIC JOURNAL, pp. 1-24.
- Luanna Lopes Lobato, I. d. (2012). “Risk Management in Software Engineering: A scopy Study.” IET (pp. 243-252). Brazil: IET.
CrossRef
- Shiva Mansoorzadeh, S. M. (2011). “Reliable Project Scheduling with Combination of Risk Management and Critical Chain Schedule.” IEEE (pp. 442-447). Malaysia: IEEE Student Conference on Research and Development.
CrossRef
- Yogini Bazar, S. G. (March 2012). “Comparitive study of Risk Assessment Models corresponding to Risk Elements.” IEEE (pp. 61-66). Central University of Rajasthan,India,University of Jammu,India: International Conference On Advances in Engineering, Science And Management(ICAESM-2012).
This work is licensed under a Creative Commons Attribution 4.0 International License.
PDF Downloads:
1071
Open
Access -
