Trivial model for mitigation of risks in software development life cycle

Software development is the art of developing the software in an appropriate manner by using the software development life cycle, regardless of the fact that which model is used for the development. The development is a dynamic activity and requires a lot of rational thinking during the analysis, design, coding, testing and maintenance phases of software development. As the development of software is becoming more systematic and tool-driven, and due to the over emphasized use of the technology the orientation of risks are increasing but the attention to risk management has been observed to be helpless to improve with the same pace to tackle the dynamically increasing software risks. In the last decade, precisely, having felt the importance of software risk management, increasing emphasis has been given in this domain. Therefore the academic and industrial community is worried to consider that how the risks can be handled to minimize the losses and to increase the profits and maintain reputation in the market This paper focuses on the aspect of suggesting the techniques to handle or manage the software risks. Taking into consideration the eighteen most prominent risk factors that affect the software quality and software process, the handling or avoidance strategy has been proposed. This paper suggests addressing the risk factors to be treated not only by the technology but by using intuition as well. Key words:

[1]  Hassan Rashidi,et al.  Classification and Analysis of Risks in Software Engineering , 2009 .

[2]  Linda Westfall.  SOFTWARE IS A RISKY BUSINESS , 2009 .

[3]  Robert N. Charette,et al.  Software Engineering Risk Analysis and Management , 1989 .

[4]  Alan R. Dennis,et al.  Selecting the appropriate application development methodology , 1985, DATB.

[5]  Thomas E. Bell,et al.  Software requirements: Are they really a problem? , 1976, ICSE '76.

[6]  Keith C. C. Chan,et al.  Test Driven Development and Software Process Improvement in China , 2004, XP.

[7]  Peter Naur,et al.  Intuition in Software Development , 1985, TAPSOFT, Vol.2.

[8]  Yacov Y. Haimes,et al.  Software Risk Management , 1996 .

[9]  B. Baskeles,et al.  Software effort estimation using machine learning methods , 2007, 2007 22nd international symposium on computer and information sciences.

[10]  Tammie D. Hertel,et al.  Team size and technology fit: participation, Awareness,and rapport in distributed teams , 2005, IEEE Transactions on Professional Communication.

[11]  Sachidanandam Sakthivel,et al.  A decision model to choose between software maintenance and software redevelopment , 1994, J. Softw. Maintenance Res. Pract..

[12]  Bradley J. Alge,et al.  When does the medium matter? Knowledge-building experiences and opportunities in decision-making teams , 2003 .

[13]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[14]  Lars Mathiassen,et al.  Managing Risks in Distributed Software Projects: An Integrative Framework , 2009, IEEE Transactions on Engineering Management.

[15]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[16]  Joseph JáJá,et al.  Mitigating risk of data loss in preservation environments , 2005, 22nd IEEE / 13th NASA Goddard Conference on Mass Storage Systems and Technologies (MSST'05).

[17]  Barry W. Boehm,et al.  Software Risk Management , 1989, ESEC.

[18]  Paul Arnold,et al.  Experience Using Cleanroom Software Engineering , 1996, IEEE Softw..