Comparing Traditional and Agile Software Development Approaches: Case of Personal Extreme Programming
- DOI
- 10.2991/icst-18.2018.116How to use a DOI?
- Keywords
- agile, PXP, waterfall, job training application
- Abstract
Generally, there are two approaches to software development, traditional and agile. Traditional is heavy and well documented, agile is light and less documentation. Personal Extreme Programming (PXP) is one of the agile approaches that iterative, more flexible and responsive to changes. This research compared Waterfall as one of the traditional methods and PXP as agile in the requirement analysis, planning and implementation processes. The project that used to compares those approaches is job training monitoring application. PXP used a closed questionnaire with weighted questions to determined which one of user requirement has the highest priority. The planning phase determined the time estimation for completed each task of making the application. PXP provided more short developing time less than three months. Implementing phase in PXP is a unit testing, code generation, and code refactoring when a user story finished, there for a mistake or an error can be detecting earlier, unlike the waterfall that often tested the application at the end of project development. The result is the agile approach (PXP) gives more convenient and flexibility for developing the application.
- Copyright
- © 2018, the Authors. Published by Atlantis Press.
- Open Access
- This is an open access article distributed under the CC BY-NC license (http://creativecommons.org/licenses/by-nc/4.0/).
Cite this article
TY - CONF AU - Sri Andriati Asri AU - I Gusti Made Agung Sunaya AU - Putu Manik Prihatini AU - Widyadi Setiawan PY - 2018/12 DA - 2018/12 TI - Comparing Traditional and Agile Software Development Approaches: Case of Personal Extreme Programming BT - Proceedings of the International Conference on Science and Technology (ICST 2018) PB - Atlantis Press SP - 561 EP - 563 SN - 2589-4943 UR - https://doi.org/10.2991/icst-18.2018.116 DO - 10.2991/icst-18.2018.116 ID - Asri2018/12 ER -