Categorization of Software Release Risks and Its Abatement Strategy
Affiliation(s)
1 Amity Institute of Information Technology, Amity University, Noida (UP), India. 2 Birla Institute of Technology, Extension Centre, Noida, India. 3 Department of Computer Science, DAV College for Girls, Yamuna Nagar, India. 4 Department of Computer Science, Govt. College, Bherian (Pehowa), Haryana, India.
1 Amity Institute of Information Technology, Amity University, Noida (UP), India. 2 Birla Institute of Technology, Extension Centre, Noida, India. 3 Department of Computer Science, DAV College for Girls, Yamuna Nagar, India. 4 Department of Computer Science, Govt. College, Bherian (Pehowa), Haryana, India.
ABSTRACT
Growing competition in the software industry with the persistently changing needs and the usual problems associated with software release, which have made acceptance of a new software in market, are extremely important for the success. Volatility in the software developmental processes is generally difficult to handle. The change request at any arbitrary point of time leads to the inevitable change and rework request. The software release process which broadly includes all the process that starts after the completion of development till the final deployment. This complete phase is exposed to various risks which may hamper the final result. This paper presents threat associated with software release activities and their possible mitigation and exploring the role played by the change management in controlling or reducing those risks.For the effective survival in ever changing software industry needs, Software Release Management takes a holistic view of the change and configuration relationship and work on the improvement strategies for the effective release with zero defect potential.
Growing competition in the software industry with the persistently changing needs and the usual problems associated with software release, which have made acceptance of a new software in market, are extremely important for the success. Volatility in the software developmental processes is generally difficult to handle. The change request at any arbitrary point of time leads to the inevitable change and rework request. The software release process which broadly includes all the process that starts after the completion of development till the final deployment. This complete phase is exposed to various risks which may hamper the final result. This paper presents threat associated with software release activities and their possible mitigation and exploring the role played by the change management in controlling or reducing those risks.For the effective survival in ever changing software industry needs, Software Release Management takes a holistic view of the change and configuration relationship and work on the improvement strategies for the effective release with zero defect potential.
Cite this paper
Rana, A. , Singh, S. , Soni, R. and Jolly, A. (2014) Categorization of Software Release Risks and Its Abatement Strategy. Journal of Software Engineering and Applications, 7, 1039-1044. doi: 10.4236/jsea.2014.712091.
Rana, A. , Singh, S. , Soni, R. and Jolly, A. (2014) Categorization of Software Release Risks and Its Abatement Strategy. Journal of Software Engineering and Applications, 7, 1039-1044. doi: 10.4236/jsea.2014.712091.
References
[1] Penny, D.A. (2002) An Estimation-Based Management Framework for Enhance Maintenance in Commercial Software Product. Proceedings of the international Conference on Software Maintenance (ICSM 02), Washington DC, 2002, 122-130. [2] IBM Software Thought Leadership (2013) 7 Proven Practices to Strengthen Release Management. IBM Corporation, USA. [3] Greer, D. and Ruhe, G. (2004) Software Release Planning Software Release Planning: An Evolutionary and Iterative Approach. Information &software Technology, 46, 243-253. [4] Ruhe, G. and Sailu, M.O. (2005) Art and Science of Software Release Planning. IEEE Software, 22, 47-53. http://dx.doi.org/10.1109/MS.2005.164 [5] Sailu, M.O. and Ruhe, G. (2005) Supporting Release Planning Decision for Evolving Systems. Proceedings of 29th Annual NASA Software Engineering Workshop, Washington DC, 6-7 April 2005, 14-26. [6] Curtis, P. and Carey, M., Thought Leadership in ERM (2012) Risk Assessment in Practice. The Committee of Sponsoring Organizations of the Treadway Commission (COSO), USA. [7] Shahzad, B. and Al-Mudimigh, A.S. (2010) Risk Identification, Mitigation and Avoidance Model for Handling Software Risk. 2010 Second International Conference on Computational Intelligence, Communication Systems and Networks (CICSyN), Liverpool, 28-30 July 2010, 191-196, [8] Karlsson, J. and Ryan, K. (1997) A Cost-Value Approach for Prioritize Requirements. IEEE Software, 14, 67-74. http://dx.doi.org/10.1109/52.605933 [9] Carlshamre, P., Sandahl, K., Lindvall, M., Rengnell, B. and Noch Dag, J. (2001) An Industrial Survey of Requirements Interdependencies in Software Product Release Planning. 5th IEEE International Symposium on Requirements Engineering, Toronto, 27-31 August 2001, 84-91. [10] Jung, H.W. (1998) Optimizing Value and Cost in Requirements Analysis. IEEE Software, 15, 74-78. http://dx.doi.org/10.1109/52.687950 [11] Lindren, M., Nordstrom, C., Wall, A. and Land, R. (2008) Importance of Software Architecture during Release Planning. Seventh Working IEEE/IFIP Conference on Software Architecture, Vancouver, 18-21 February 2008, 253-256. [12] Wohlin, C. and Aurum, A. (2005) What Is Important When Deciding to Include a Software Requirement in a Project or Release? 2005 International Symposium on Empirical Software Engineering, Queensland, 17-18 November 2005, 10. [13] Li, Q., Yang, Y., Li, M.S., Wang, Q., Boehm, B.W. and Hu, C.Y. (2010) Improving Software Testing Process: Feature Prioritization to Make Winners of Success-Critical Stakeholders. Journal of Software: Evolution and Process, 24, 783-801. [14] Wall, A. (2008) Key Aspects of Software Release Planning in Industry. 19th Australian Conference on Software Engineering, Perth, 26-28 March 2008, 320-329. [15] Lu, Y.K. (2012) An Information Systems Design Product Theory for Integrated Requirements, Test and Defect Management Systems. 47th Hawaii International Conference on System Sciences, Maui, 4-7 January 2012, 5516-5525.
[1] Penny, D.A. (2002) An Estimation-Based Management Framework for Enhance Maintenance in Commercial Software Product. Proceedings of the international Conference on Software Maintenance (ICSM 02), Washington DC, 2002, 122-130. [2] IBM Software Thought Leadership (2013) 7 Proven Practices to Strengthen Release Management. IBM Corporation, USA. [3] Greer, D. and Ruhe, G. (2004) Software Release Planning Software Release Planning: An Evolutionary and Iterative Approach. Information &software Technology, 46, 243-253. [4] Ruhe, G. and Sailu, M.O. (2005) Art and Science of Software Release Planning. IEEE Software, 22, 47-53. http://dx.doi.org/10.1109/MS.2005.164 [5] Sailu, M.O. and Ruhe, G. (2005) Supporting Release Planning Decision for Evolving Systems. Proceedings of 29th Annual NASA Software Engineering Workshop, Washington DC, 6-7 April 2005, 14-26. [6] Curtis, P. and Carey, M., Thought Leadership in ERM (2012) Risk Assessment in Practice. The Committee of Sponsoring Organizations of the Treadway Commission (COSO), USA. [7] Shahzad, B. and Al-Mudimigh, A.S. (2010) Risk Identification, Mitigation and Avoidance Model for Handling Software Risk. 2010 Second International Conference on Computational Intelligence, Communication Systems and Networks (CICSyN), Liverpool, 28-30 July 2010, 191-196, [8] Karlsson, J. and Ryan, K. (1997) A Cost-Value Approach for Prioritize Requirements. IEEE Software, 14, 67-74. http://dx.doi.org/10.1109/52.605933 [9] Carlshamre, P., Sandahl, K., Lindvall, M., Rengnell, B. and Noch Dag, J. (2001) An Industrial Survey of Requirements Interdependencies in Software Product Release Planning. 5th IEEE International Symposium on Requirements Engineering, Toronto, 27-31 August 2001, 84-91. [10] Jung, H.W. (1998) Optimizing Value and Cost in Requirements Analysis. IEEE Software, 15, 74-78. http://dx.doi.org/10.1109/52.687950 [11] Lindren, M., Nordstrom, C., Wall, A. and Land, R. (2008) Importance of Software Architecture during Release Planning. Seventh Working IEEE/IFIP Conference on Software Architecture, Vancouver, 18-21 February 2008, 253-256. [12] Wohlin, C. and Aurum, A. (2005) What Is Important When Deciding to Include a Software Requirement in a Project or Release? 2005 International Symposium on Empirical Software Engineering, Queensland, 17-18 November 2005, 10. [13] Li, Q., Yang, Y., Li, M.S., Wang, Q., Boehm, B.W. and Hu, C.Y. (2010) Improving Software Testing Process: Feature Prioritization to Make Winners of Success-Critical Stakeholders. Journal of Software: Evolution and Process, 24, 783-801. [14] Wall, A. (2008) Key Aspects of Software Release Planning in Industry. 19th Australian Conference on Software Engineering, Perth, 26-28 March 2008, 320-329. [15] Lu, Y.K. (2012) An Information Systems Design Product Theory for Integrated Requirements, Test and Defect Management Systems. 47th Hawaii International Conference on System Sciences, Maui, 4-7 January 2012, 5516-5525.