Derleme

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

Cilt: 20 Sayı: 2 28 Ocak 2020
PDF İndir
TR EN

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

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.

Keywords

Requirements engineering,Traditional software development methods,Agile software development methods,Agile and traditional comparison

Kaynakça

  1. Babok v3: A guide to business analysis body of knowledge. (2015). Toronto: IIBA.
  2. 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
  3. 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
  4. BOURQUE, P., & FAIRLEY, R. E. (2014). SWEBOK: Guide to the software engineering body of knowledge. Los Alamitos, CA: IEEE Computer Society.
  5. BOYER, J., & MILI, H. (2014). Agile Business Rule Development Process, Architecture, and JRules Examples. Berlin: Springer Berlin.
  6. BROOKS. (1987). No Silver Bullet Essence and Accidents of Software Engineering. Computer, 20(4), 10-19.
  7. DECARLO, D. (2004). EXtreme project management: Using leadership, principles, and tools to deliver value in the face of volatility. San Francisco, CA: Jossey-Bass.
  8. ELSHANDIDY, H. & MAZEN, S., Agile and Traditional Requirements Engineering: A Survey, International Journal of Scientific & Engineering Research, 4 (9), 2013
  9. GRIFFITHS, M. (2015). PMI-ACP exam prep: Rapid learning to pass the PMI Agile Certified Practitioner (PMI-ACP) exam. Minnetonka, MN: RMC Publications.
  10. 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

Kaynak Göster

IEEE
[1]K. Çamoğlu ve R. Kandemir, “COMPARISON OF REQUIREMENTS ENGINEERING KNOWLEDGE AREAS IN TERMS OF TRADITIONAL AND AGILE SOFTWARE METHODS”, TUJES, c. 20, sy 2, ss. 79–91, Oca. 2020, [çevrimiçi]. Erişim adresi: https://izlik.org/JA89FM83PF