• Damla Topalli Department of Computer Engineering, Atilim University, Ankara
  • Gonca Gökçe Menekse Dalveren Department of Software Engineering, Atilim University, Ankara
  • Seda Camalan Department of Information Systems Engineering, Atilim University, Ankara


A variety of development methodologies are available in the current context of software development. In software development process, it is difficult to compare methods and decide on the most appropriate method to be used. In this case study, firstly a literature review is conducted on two topics; software development methodologies and software quality assurance methods. Then, we contacted two major companies in Turkey, in order to compare their software development methodologies used for the projects, quality assurance methods and measures. Accordingly, qualitative data is collected using a questionnaire, and a semi-structure interview is conducted and the results are analyzed descriptively. The main aim of this study is to understand the differences about software development methodologies and quality assurance methods of the companies. The results of the study are expected to give insights in order to guide the developers and managers in making choices for software development process in companies.


[1] P. Diebold and M. Dahlem, “Agile practices in practice: a mapping study,” In Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering, ACM, 2014, pp. 30.
[2] J. Higgins and S. Green, “Cochrane Handbook for Systematic Reviews of Interventions 4.2.6”, The Cochrane Collaboration, 2006.
[3] F. Ferrucci, M. Harman, and F. Sarro, “Search-based software project management,” In Software Project Management in a Changing World Springer Berlin Heidelberg, 2014, pp. 373-399.
[4] S. Balaji, and M. S. Murugaiyan, “Waterfall vs. V-Model vs. Agile: A comparative study on SDLC,” International Journal of Information Technology and Business Management, 2012, 2(1), pp. 26-30.
[5] N. M. A. Munassar, and A. Govardhan, “A comparison between five models of software engineering”, IJCSI, 2010, 5, pp. 95-101.
[6] I. Inayat, S. S. Salim, S. Marczak, M. Daneva, and S. Shamshirband, “A systematic literature review on agile requirements engineering practices and challenges”, Computers in human behavior, 2015, 51, pp. 915-929.
[7] T. Chow, and D. B. Cao, “A survey study of critical success factors in agile software projects,” Journal of Systems and Software, 2008, 81(6), 961-971.
[8] A. Cockburn, “Agile Software Development (second edition)”, 2006.
[9] P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta, “Agile software development methods: Review and analysis,” Technical Research Centre of Finland, Tech. Rep. ESPOO 2002, VTT Publication 478, 2002.
[10] X. Ge, R. F. Paige, and J. A. McDermid, “An iterative approach for development of safety-critical software and safety arguments,” In Agile Conference (AGILE), IEEE, 2010, pp. 35-43.
[11] B. W. Boehm, "A spiral model of software development and enhancement.", Computer 21.5, 1988, pp. 61-72.
[12] M. A. Awad, "A comparison between agile and traditional software development methodologies," University of Western Australia, 2005.
[13] R. S. Pressman, “Software engineering: a practitioner's approach,” Palgrave Macmillan. E. J. Braude, and M. E. Bernstein. "Software engineering: modern approaches." Waveland Press, 2016.
[14] Jacobson, Ivar, et al. The unified software development process. Vol. 1. Reading: Addison-wesley, 1999.
[15] A. I. Khan, J. Q. Rizwan, and A. K. Usman, "A comprehensive study of commonly practiced heavy and light weight software methodologies.", 2011.
[16] W. Tracz, "Extreme Programming (XP)." Encyclopedia of Software Engineering, 2002.
[17] M. Fowler, and J. Highsmith. "The agile manifesto." Software Development 9.8 ,2001, pp. 28-35.
[18] S. C. Dimri, “An Innovative Model of Software Quality Assurance for Component-Based Software Systems,” 2015.
[19] E. K. El-Rayyes, and I. M. Abu-Zaid, “New Model to Achieve Software Quality Assurance (SQA) in Web Application,” International Journal of Science and Technology, 2012, 2(7).
[20] NASA Software Quality Assurance Center Software Assurance Guidebook_NASA-GB_A201, 1989.
[21] C. Yoo, J. Yoon, B. Lee, C. Lee, J. Lee, S. Hyun and C.Wu , “An Integrated Model of ISO 9001:2000 and CMMI for ISO Registered Organizations,” IEEE Computer Society, Proceedings of the 11th Asia-Pacific Software Engineering Conference (APSEC 04), 2004.
[22] Carnegie Mellon University Software Engineering Institute, CMMI overview Pittsburgh, USA, 2005.
[23] S. Bhasin, “Quality assurance in agile: a study towards achieving excellence,” In 2012 Agile India, IEEE, 2012, pp. 64-67.
[24] S. Ambler, Agile Adoption Survey, 2008. Retrieved from:
[25] E. Çetin, and P. O. Durdu, “Türkiye'de Çevik Yazılım Geliştirme Üzerine Bir İnceleme,” In UYMS, 2014.
How to Cite
TOPALLI, Damla; MENEKSE DALVEREN, Gonca Gökçe; CAMALAN, Seda. COMPARISON OF SOFTWARE DEVELOPMENT METHODOLOGIES: AN INDUSTRIAL CASE STUDY IN TURKEY. International Journal of Scientific Research in Information Systems and Engineering (IJSRISE), [S.l.], v. 3, n. 2, p. 11-19, sep. 2017. ISSN 2380-5579. Available at: <>. Date accessed: 21 nov. 2017.

Most read articles by the same author(s)

Obs.: This plugin requires at least one statistics/report plugin to be enabled. If your statistics plugins provide more than one metric then please also select a main metric on the admin's site settings page and/or on the journal manager's settings pages.