A Study of Agile-Based Approaches to Improve Software Quality
Agile Software development approaches and techniques are being considered as efficient, effective, and popular methods to the development of software. Agile software developments are useful for developing high-quality software that completes client requirements with zero defects, and in short delivery period. In agile software development methodology, quality is related to coding, which means quality, is managed through the use of approaches like refactoring, pair programming, test-driven development, behavior-driven development, acceptance test-driven development, and demand-driven development. The quality of software is measured using metrics like the number of defects during the development and improvement of the software. Usage of the above-mentioned methods or approaches reduces the possibilities of defects in developed software, and hence improves quality. This paper focuses on the study of agile-based quality methods or approaches for software development that ensures improved quality of software as well as reduced cost, and customer satisfaction.
[1] P. Abrahamsson, J. Warsta, M. T. Siponen and J. Ronkainen,” New Directions on Agile Methods: A Comparative Analysis”, 25th ICSE, 2003.
[2] A. Cockburn, “Agile Software Development”, 1st Edition, Addison-Wesley Professional, 2001
[3] J. Eckstein, “Agile Software Development in the Large: Diving Into the Deep”. New York: Dorset House, 2004.
[4] M.R. Barbacci, R. Ellison, A.J. Lattanze, J.A. Stafford, C.B. Weinstock and W.G. Wood, “Quality Attribute Workshops (QAWs)”, Technical Report, 3rd Edition, SEI, CMU, 2003.
[5] R. Wojcik, F. Bachmann, L. Bass, P. Clements, P. Merson, R. Nord and B. Wood, “Attribute-Driven Design (ADD)”, Technical Report, 2nd Edition, SEI, CMU, 2006.
[6] R. Nord, M. Barbacci, P. Clements, R. Kazman, L. OBrien and J. Tomayko, “Integrating the Architecture Tradeoff Analysis Method(ATAM) with the Cost Benefit Analysis Method (CBAM)”, Technical Report, 1st Edition, SEI, CMU, 2003.
[7] L. Bass, P. Clements, and R. Kazman, “Software Architecture in Practice”, 2nd Edition, Addison-Wesley, 2003.
[8] GalinD” Software quality: concepts and practice”. Wiley, NJ,2017
[9] Tian J “Software quality engineering testing, quality assurance, and quantifiable improvement”. Wiley, New Jersey,2005
[10] Kandt KR “Software engineering quality practices”. Auerbach Publications, Philadelphia,2006
[11] Dingsøyr T, Dyba ˚ T, Moe NB (Eds) (2010) “Agile software development: current research and future directions”. Springer, Berlin
[12] Sommerville I “Software engineering”, 10th edn. Pearson, India,2017
[13] R. Chillarege et al., “Orthogonal Defect Classification-A Concept for In-Process Measurements”, IEEE Trans. Softw. Eng., vol. 18,no.11,1992.http://doi.org/10.1109/32.1773 64
[14] “How Userful Is the Metaphor Component of Agile Methods”? A Preliminary Study,
[15] A. Cockburn and L. Williams, "The Costs and Benefits of Pair Programming," in Extreme Programming examined, G. Succi and M. Marchesi, Eds. Boston: Addison-Wesley, 2001, pp. xv, 569 p.
[16] M. Fowler, "Information about Refactoring," 2004.
[17] “Continuous Integration”, http://www.martinfowler.com/articles/continuousIntegratio n.html.
[18] Shrivastava and Jain, "Metrics for Test Case Design in Test Driven Development", International Journal of Computer Theory and Engineering, Vol.2, No.6, December, 2010, Pg: 1793-8201
[19] Emam K “Finding success in small software projects, agile project management executive report. Technical report”, Cutter Consortium, Arlington, Massachusetts, 2003.
[20] Latorre R “A successful application of a test-driven development strategy in the industrial environment”. EMPSoftwEng 19:753–773, 2014.
[21] Rodriguez P, Markkula J, Oivo M, TurulaK “Survey on agile and lean usage in Finnish software industry”. In: six international symposiums on empirical software engineering and measurement, 2012.
[22] Sanchez JC, Williams L, Maximilien EM “On the sustained use of a test-driven development practice at IBM”. In: AGILE conference, pp 5–14, 2007.
[23] N. Koudelia, “Acceptance test-driven development”. 2011.
[24] L. Koskela, “Test Driven: TDD and Acceptance TDD for Java Developers”, Edición: 1. Greenwich, CT: Manning Publications, 2007.
[25] W. Silva, N. M. Costa Valentim, and T. Conte, “Integrating the Usability into the Software Development Process,” in Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 3, Portugal, 2015, pp. 105–113.
[26] K. Curcio, R. Santana, S. Reinehr, and A. Malucelli, “Usability in agile software development: A tertiary study,” Computer Standards & Interfaces, Jan. 2019.
[27] M. Leotta et al., “An acceptance testing approach for Internet of Things systems,” IET Software, vol. 12, no. 5, pp. 430–436, 2018.
[28] R. Chillarege et al., “Orthogonal Defect Classification-A Concept for In-Process Measurements,” IEEE Trans. Softw. Eng., vol. 18,no.11,1992.http://doi.org/10.1109/32.1773 64
[29] N. Li, Z. Li, and X. Sun, “Classification of software defect detected by black-box testing: An empirical study,” Proc. - 2010 2nd WRI World Congr. Softw. Eng. WCSE 2010, vol. 2, pp. 234–240, 2010. http://doi.org/10.1109/WCSE.2010.28
[30] F. Zeng, A. Chen, and X. Tao, “Study on software reliability design criteria based on defect patterns,” Reliab. Maintainab. Safety, 2009. ICRMS 2009. 8th Int. Conf., pp. 723– 727,2009.http://doi.org/10.1109/ICRMS.2009. 5270095
[31] W. S. Humphrey, PSP(sm): “A Self Improvement Process for Software Engineers”, 1st ed. Addison-Wesley Professional, 2005.
[32] W. S. Humphrey, “The personal process in software engineering,” in Proceedings of the Third International Conference on the Software Process. Applying the Software Process, 1994, no. c, pp. 69–77. http://doi.org/10.1109/SPCON.1994.344422
[33] G. Rong, H. Zhang, M. Xie, and D. Shao, “Improving PSP education by pairing: An empirical study,” Proc. - Int. Conf. Softw. Eng., pp. 1245–1254, 2012.
[34] W. Nachiengmai and S. Ramingwong, “Implementing Personal Software Process in Undergraduate Course to Improve Model View-Controller Software Construction,” in Lecture Notes in Electrical Engineering, vol. 339, 2015, pp. 949–956. http://doi.org/ 10.1007/978-3-662-46578-3_113
[35] W. Nachiengmai, and S. Ramingwong, “Improving Reliability of Defects Logging in MVC-PSP,” in 2015 2nd International Conference on Information Science, and Security (ICISS), 2015, pp. 1–4. http://doi.org/ 10.1109/ICISSEC.2015.7371007.
[1] P. Abrahamsson, J. Warsta, M. T. Siponen and J. Ronkainen,” New Directions on Agile Methods: A Comparative Analysis”, 25th ICSE, 2003.
[2] A. Cockburn, “Agile Software Development”, 1st Edition, Addison-Wesley Professional, 2001
[3] J. Eckstein, “Agile Software Development in the Large: Diving Into the Deep”. New York: Dorset House, 2004.
[4] M.R. Barbacci, R. Ellison, A.J. Lattanze, J.A. Stafford, C.B. Weinstock and W.G. Wood, “Quality Attribute Workshops (QAWs)”, Technical Report, 3rd Edition, SEI, CMU, 2003.
[5] R. Wojcik, F. Bachmann, L. Bass, P. Clements, P. Merson, R. Nord and B. Wood, “Attribute-Driven Design (ADD)”, Technical Report, 2nd Edition, SEI, CMU, 2006.
[6] R. Nord, M. Barbacci, P. Clements, R. Kazman, L. OBrien and J. Tomayko, “Integrating the Architecture Tradeoff Analysis Method(ATAM) with the Cost Benefit Analysis Method (CBAM)”, Technical Report, 1st Edition, SEI, CMU, 2003.
[7] L. Bass, P. Clements, and R. Kazman, “Software Architecture in Practice”, 2nd Edition, Addison-Wesley, 2003.
[8] GalinD” Software quality: concepts and practice”. Wiley, NJ,2017
[9] Tian J “Software quality engineering testing, quality assurance, and quantifiable improvement”. Wiley, New Jersey,2005
[10] Kandt KR “Software engineering quality practices”. Auerbach Publications, Philadelphia,2006
[11] Dingsøyr T, Dyba ˚ T, Moe NB (Eds) (2010) “Agile software development: current research and future directions”. Springer, Berlin
[12] Sommerville I “Software engineering”, 10th edn. Pearson, India,2017
[13] R. Chillarege et al., “Orthogonal Defect Classification-A Concept for In-Process Measurements”, IEEE Trans. Softw. Eng., vol. 18,no.11,1992.http://doi.org/10.1109/32.1773 64
[14] “How Userful Is the Metaphor Component of Agile Methods”? A Preliminary Study,
[15] A. Cockburn and L. Williams, "The Costs and Benefits of Pair Programming," in Extreme Programming examined, G. Succi and M. Marchesi, Eds. Boston: Addison-Wesley, 2001, pp. xv, 569 p.
[16] M. Fowler, "Information about Refactoring," 2004.
[17] “Continuous Integration”, http://www.martinfowler.com/articles/continuousIntegratio n.html.
[18] Shrivastava and Jain, "Metrics for Test Case Design in Test Driven Development", International Journal of Computer Theory and Engineering, Vol.2, No.6, December, 2010, Pg: 1793-8201
[19] Emam K “Finding success in small software projects, agile project management executive report. Technical report”, Cutter Consortium, Arlington, Massachusetts, 2003.
[20] Latorre R “A successful application of a test-driven development strategy in the industrial environment”. EMPSoftwEng 19:753–773, 2014.
[21] Rodriguez P, Markkula J, Oivo M, TurulaK “Survey on agile and lean usage in Finnish software industry”. In: six international symposiums on empirical software engineering and measurement, 2012.
[22] Sanchez JC, Williams L, Maximilien EM “On the sustained use of a test-driven development practice at IBM”. In: AGILE conference, pp 5–14, 2007.
[23] N. Koudelia, “Acceptance test-driven development”. 2011.
[24] L. Koskela, “Test Driven: TDD and Acceptance TDD for Java Developers”, Edición: 1. Greenwich, CT: Manning Publications, 2007.
[25] W. Silva, N. M. Costa Valentim, and T. Conte, “Integrating the Usability into the Software Development Process,” in Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 3, Portugal, 2015, pp. 105–113.
[26] K. Curcio, R. Santana, S. Reinehr, and A. Malucelli, “Usability in agile software development: A tertiary study,” Computer Standards & Interfaces, Jan. 2019.
[27] M. Leotta et al., “An acceptance testing approach for Internet of Things systems,” IET Software, vol. 12, no. 5, pp. 430–436, 2018.
[28] R. Chillarege et al., “Orthogonal Defect Classification-A Concept for In-Process Measurements,” IEEE Trans. Softw. Eng., vol. 18,no.11,1992.http://doi.org/10.1109/32.1773 64
[29] N. Li, Z. Li, and X. Sun, “Classification of software defect detected by black-box testing: An empirical study,” Proc. - 2010 2nd WRI World Congr. Softw. Eng. WCSE 2010, vol. 2, pp. 234–240, 2010. http://doi.org/10.1109/WCSE.2010.28
[30] F. Zeng, A. Chen, and X. Tao, “Study on software reliability design criteria based on defect patterns,” Reliab. Maintainab. Safety, 2009. ICRMS 2009. 8th Int. Conf., pp. 723– 727,2009.http://doi.org/10.1109/ICRMS.2009. 5270095
[31] W. S. Humphrey, PSP(sm): “A Self Improvement Process for Software Engineers”, 1st ed. Addison-Wesley Professional, 2005.
[32] W. S. Humphrey, “The personal process in software engineering,” in Proceedings of the Third International Conference on the Software Process. Applying the Software Process, 1994, no. c, pp. 69–77. http://doi.org/10.1109/SPCON.1994.344422
[33] G. Rong, H. Zhang, M. Xie, and D. Shao, “Improving PSP education by pairing: An empirical study,” Proc. - Int. Conf. Softw. Eng., pp. 1245–1254, 2012.
[34] W. Nachiengmai and S. Ramingwong, “Implementing Personal Software Process in Undergraduate Course to Improve Model View-Controller Software Construction,” in Lecture Notes in Electrical Engineering, vol. 339, 2015, pp. 949–956. http://doi.org/ 10.1007/978-3-662-46578-3_113
[35] W. Nachiengmai, and S. Ramingwong, “Improving Reliability of Defects Logging in MVC-PSP,” in 2015 2nd International Conference on Information Science, and Security (ICISS), 2015, pp. 1–4. http://doi.org/ 10.1109/ICISSEC.2015.7371007.
@article{"International Journal of Information, Control and Computer Sciences:80812", author = "Gurmeet Kaur and Jyoti Pruthi", title = "A Study of Agile-Based Approaches to Improve Software Quality", abstract = "Agile Software development approaches and techniques are being considered as efficient, effective, and popular methods to the development of software. Agile software developments are useful for developing high-quality software that completes client requirements with zero defects, and in short delivery period. In agile software development methodology, quality is related to coding, which means quality, is managed through the use of approaches like refactoring, pair programming, test-driven development, behavior-driven development, acceptance test-driven development, and demand-driven development. The quality of software is measured using metrics like the number of defects during the development and improvement of the software. Usage of the above-mentioned methods or approaches reduces the possibilities of defects in developed software, and hence improves quality. This paper focuses on the study of agile-based quality methods or approaches for software development that ensures improved quality of software as well as reduced cost, and customer satisfaction.", keywords = "Agile software development, ASD, Acceptance test-driven development, ATDD, Behavior-driven development, BDD, Demand-driven development. DDD, Test-driven development, TDD.", volume = "16", number = "5", pages = "158-6", }
