IJSTR >> Volume 8 - Issue 12, December 2019 Edition

[Full Text]

AUTHOR(S)

Rishi singh, Sowmay Vijayan, V. Ilango*, A. Abdul Rasheed

KEYWORDS

Agile models, Degree of Agility, Extreme Programming, Process model, Scrum, Traditional software models, Software Paradigm.

ABSTRACT

: Software Process Improvement is generally regarded a key to economic success by increasing the quality of software systems, accelerating time-to-market and decreasing development costs. The new software development paradigm is much different from the traditional approach. It is necessary to study and analyze the gap between classical and modern software development methods. The use of agile methods is becoming widespread in the system development industry. Agile methods have several benefits over traditional plan-based methods, in particular their ability to handle projects where requirements are dynamic Organization’s varying needs and environments results in context specific adjustments of agile methods. In the present digital transformation world, agility processes, practice and degree of agility need to be assessed. The assessment of agile work is often based on how well the organization complies with a commercial method. In the last few years, a number of agile software development methods have been developed but a detailed evaluation (which is essential) of these methods is not available. In this paper, we survey and compare traditional software development models and agile software models, described their advantages and disadvantages, and discuss the features they inherit. The aim is to identify how gaps between practice and priority can be measured. A detailed study has been conducted to measure the perceptual performance of five Scrum practices with consideration to the prioritization of seven agile aspects. The results shows that the studied agile aspects are considered essential in the organization and that practices in some cases underperform or over perform. This paper presents a detailed comparative analysis of two well-known agile methods, XP and Scrum, based on agility characterization. However, in this study, compliance of practices to strategic priorities is considered.

REFERENCES

[1] Murat güneştaş, “A study on component based software engineering”, a Master’s thesis in Computer Engineering, Atılım University, JANUARY 2005
[2] Ivica Crnkovic, Stig Larsson; Michel Chaudron, “Component-based Development Process and Component Lifecycle.” Online Available: http://www.mrtc.mdh.se/publi cations/0953.pdf
[3] Luiz Fernando Capretz Y, “A New Component-based software life cycle model”, Journal of Computer Science 1 (1): 76-82, 2005, ISSN 1549-3636, Science Publications, 2005
[4] K.Kaur, H Singh, “Candidate process models for component based software development”, Journal of Software Engineering 4 (1):16-29, Academic Journal Inc, India 2010.
[5] Sajid Riaz, “Moving Towards Component Based Software Engineering in Train Control Applications”, Final thesis, Linköpings universitet, sweden, 2012
[6] Ian Somerville, Software Engineering, Addison Wesley, 9th ed, 2010.
[7] Nabil Mohammed Ali Munassar, A.Govardhan, “A Comparison between Five Models of Software Engineering”, International Journal of Computer Science Issues, Vol.: 7, Issue: 5, Sep, 2010.
[8] Craig Layman and Victor Basili, “Iterative and Incremental Development: A Brief History”, IEEE Computer 2003.
[9] W. Royce, “Managing the Development of Large Software Systems”, presented at the Proceedings of IEEE WESCON, 1970.
[10] Rajesh Shah, ”A Comparative Study of two Software development Approach Traditional and object Oriented”, International Journal of Advanced Research in Computer Science and Software Engineering”, Vol -5 Issue-5, pp 1383-1387, ISSN-2277128X, 2011.
[11] Barry Boehm, "Spiral Development: Experience, Principles, and Refinements", edited by Wilfred J. Hansen, 2000.
[12] Jintao zeng, Jinzhong Li, Xiaohui Zeng, Wenlang Luo, “A Prototype System of Software Reliability Prediction and Estimation”, IITSI 2010.
[13] Craig Larman and Victor Basili, “Iterative and Incremental Development: A Brief History”, IEEE Computer, June 2003.
[14] C. Melissa McClendon, Larry Ragout, Gerri Akers, “The Analysis and Prototyping of Effective Graphical User Interfaces”, October 1996.
[15] Conboy K, “Agility From First Principles: Reconstructing the Concept of Agility in Information Systems Development”, Information Systems Research, 2009
[16] Dingsøyr T, Nerur S, Balijepally V, and Moe N.B, “A decade of agile methodologies: Towards explaining agile software development”, Journal of Systems and Software, vol. 85, no. 6, pp. 1213-1221, 2012
[17] Abrahamsson P, Conboy K, Wang X, “Lots done, more to do’: the current state of agile systems development research”, European Journal of Information Systems, 18, pp. 281–284, 2009
[18] Dingsøyr, T., Dybå, T., and Abrahamsson, P, “A preliminary roadmap for empirical research on agile software development”, In Agile, 2008. AGILE'08. Conference, pp. 83-94, IEEE, 2008
[19] Erande, A. S., & Verma, A. K, “Measuring agility of organizations–a comprehensive agility measurement tool (CAMT)”, International Journal of Applied Management and Technology, 6(3), 3, 2008
[20] Guion, R. M, “Performance measurement and theory”, Hills-dale, NJ: Erlbaum, pp 267-275, 1983
[21] Highsmith J, “Agile Software Development Ecosystems”, Addison-Wesley, Boston, 2002
[22] Neely A, “Business Performance Measurement: Theory and Practice”, Cambridge University Press, 2002
[23] Schwaber K, Sutherland J, “The Scrum guide – the definite guide to Scrum: the rules of the game:, Scrum.org, 2013
[24] Qumer A and Henderson-Sellers B, “Measuring agility and adoptability of agile methods: A 4-Dimensional Analytical Tool”, Procs. IADIS International Conference Applied Computing 2006, IADIS Press, 503-507.
[25] Williams L, Krebs W, Layman L, Anton A.I and Abrahamsson P, “Toward a framework for evaluating Extreme Programming”, Empirical Assessment in Software Engineering, Edinburgh, pp 11-20, 2004
[26] Kitchenham B.A and Jones L, “Evaluating software engineering methods and tool part 5: the influence of human factors”, ACM SIGSOFT Software Engineering Notes, 13-15, 1997
[27] Agile Manifesto, “Manifesto for Agile Software Development”, 2001
[28] Beck K, “Extreme Programming Explained”, Addison-Wesley Pearson Education, Boston, 2000
[29] ] Boehm B and Turner R, “Balancing agility and discipline: evaluating and integrating agile and plan-driven methods”, Proceedings of the 26th International Conference on Software EngineeringIEEE Computer Society, Washington, DC, USA, pp 718-719, 2004
[30] Kitchenham B.A and Jones L, “Evaluating software engineering methods and tool part 5: the influence of human factors”, ACM SIGSOFT Software Engineering Notes, pp 13-15, 1997
[31] Koch A.S, “Agile Software Development: Evaluating the Methods for Your Organization”, Artech House, Inc, London, 2005
[32] Palmer S.R and Felsing J.M, “A Practical Guide to Feature-Driven Development”, Prentice-Hall Inc, Upper Saddle River, 2002