Journals / Trakya Üniversitesi Mühendislik Bilimleri Dergisi / 2019 / Cilt: 20 - Sayı: 2

COMPARISON OF REQUIREMENTS ENGINEERING KNOWLEDGE AREAS IN TERMS OF TRADITIONAL AND AGILE SOFTWARE METHODS

GEREKSİNİM MÜHENDİSLİĞİ BİLGİ ALANLARININ GELENEKSEL VE ÇEVİK YAZILIM YÖNTEMLERİ AÇISINDAN KARIŞLAŞTIRILMASI

Pages
79–91
Publication Date
2020-01-28
DOI
—
🏛️Bibliographic metadata and full text access for this article are provided via DergiPark.
DergiPark Record ↗
✨

AI Summary & Key Takeaways

AI Insight
⚡ TL;DR(Too Long; Didn't Read)

In this study, the necessary engineering applications in traditional and agile methodology approaches are evaluated to assist in the selection of methodology.

📌 3 Key Takeaways

🎯
Objective & Hypothesis:One of the important points to be considered when implementing a software project is the successful management of the requirements.
📊
Key Findings & Data:Knowing the positive and negative aspects, advantages and disadvantages of the existing methodologies helps for selecting the appropriate methodology and choosing the appropriate approach to the situation and the project in this direction will increase the probability of success of the project.
💡
Conclusion & Impact:In this study, the necessary engineering applications in traditional and agile methodology approaches are evaluated to assist in the selection of methodology.
🔬Design:Research Article
📍Scope:Comprehensive Sample
⚙️Variables:Gereksinim mühendisliği · Geleneksel yazılım geliştirme yöntemleri · Çevik yazılım geliştirme yöntemleri

Abstract

One of the important points to be considered when implementing a software project is the successful management of the requirements. The success of the software depends on the accuracy and completeness of the requirements. Knowing the positive and negative aspects, advantages and disadvantages of the existing methodologies helps for selecting the appropriate methodology and choosing the appropriate approach to the situation and the project in this direction will increase the probability of success of the project. Although there is a lot of research in the literature about the traditional and agile approaches which are the main trends of software development approaches, the publications made in specific for requirements engineering process are limited. In this study, the necessary engineering applications in traditional and agile methodology approaches are evaluated to assist in the selection of methodology.

Özet

Bir yazılım projesi uygularken dikkat edilmesi gereken önemli noktalardan biri gereksinimlerin başarılı bir şekilde yönetimidir. Yazılımın başarısı, gereksinimlerin doğruluğuna ve eksiksizliğine bağlıdır. Mevcut metodolojilerin olumlu ve olumsuz yönlerini, avantajlarını ve dezavantajlarını bilmek gerçekleştirilecek projeler için en uygun metodolojinin seçilmesine yardımcı olacaktır. Proje için kaynaklara, bağlama ve diğer unsurlara göre en uygun yaklaşımı seçmek de proje başarımını artırır.

🔖

Cite This Article

ÇAMOĞLU, K., KANDEMİR, R. (2020). COMPARISON OF REQUIREMENTS ENGINEERING KNOWLEDGE AREAS IN TERMS OF TRADITIONAL AND AGILE SOFTWARE METHODS. Trakya Üniversitesi Mühendislik Bilimleri Dergisi, Cilt: 20 - Sayı: 2, 79–91. https://ajindex.com/articles/807386

📄 Full Text PDF Viewer

📄

PDF görüntüleyici hazırlanıyor...

References (9)

  1. Babok v3: A guide to business analysis body of knowledge. (2015). Toronto: IIBA. BATOOL, A., MOTLA, Y.H., HAMID, B., ASGHAR, S., RIAZ, M.N., MUKHTAR, M., AHMED, Comparative study of traditional requirements engineering and Agile requirements engineering., 15th (ICACT), 1006-1014, 2013
  2. BOSE S., KURHEKAR M., GHOSHAL I. (2014, October) Agile Methodology in Requirements Engineering, Retrieved from: http://www.infosys.com/research/publica-tions/agilerequirements-engineering.pdf
  3. BOURQUE, P., & FAIRLEY, R. E. (2014). SWEBOK: Guide to the software engineering body of knowledge. Los Alamitos, CA: IEEE Computer Society. BOYER, J., & MILI, H. (2014). Agile Business Rule Development Process, Architecture, and JRules Examples. Berlin: Springer Berlin. BROOKS. (1987). No Silver Bullet Essence and Accidents of Software Engineering. Computer, 20(4), 10-19.
  4. DECARLO, D. (2004). EXtreme project management: Using leadership, principles, and tools to deliver value in the face of volatility. San Francisco, CA: Jossey-Bass. ELSHANDIDY, H. & MAZEN, S., Agile and Traditional Requirements Engineering: A Survey, International Journal of Scientific & Engineering Research, 4 (9), 2013
  5. GRIFFITHS, M. (2015). PMI-ACP exam prep: Rapid learning to pass the PMI Agile Certified Practitioner (PMI-ACP) exam. Minnetonka, MN: RMC Publications. HASTLE, S., WOJEWODA S. (2015, October 4). Standish Group 2015 Chaos Report - Q&A with Jennifer Lynch. InfoQ. Retrieved from https://www.infoq.com/articles/standish-chaos-2015 IEEE recommended practice for software requirements specifications. (1998). New York: IEEE.Industry implementation of International Standard ISO / 1995: (ISO/IEC 12207) standard for information technology: Software life cycle processes. (1998). New York: Institute of Electrical and Electronics Engineers. LAWRENCE, B., WIEGERS, K., and EBERT, C. "The top risk of requirements engineering," in IEEE Software, vol. 18, no. 6, pp. 62-63, Nov.-Dec. 2001.
  6. LUCIA A., QUSEF A., Requirements Engineering in Agile Software Development, Journal Of Emergıng Technologıes In Web Intellıgence, 2, (3), Ağustos 2010.Manifesto for Agile Software Development, Agile Manifesto (2001). Retrieved from https://agilemanifesto.org/
  7. MORE N., SAPRE B.S., CHAWAN P.M., An Insight into the Importance of Requirements Engineering, IJIC,,1 (2), 2011.
  8. NORTON D., Agile Estimation and Planning Is Moving From a Dictatorship to a Democracy, Gartner, 2008.
  9. PALMQUIST M.S., LAPHAM M.A., MILLER S., CHICK T, OZKAYA I., Parallel W