Bilgi Sistemi Yazılım Geliştirme Yaşam Döngüsü Safhalarından Gereksinim Belirleme ve Sistem Tasarımında Kalite Odaklılık: Üç Proje İncelemesi

Yıl 2022, Cilt: 15 Sayı: 1, 55 - 64, 31.01.2022

Doğan Yıldız

https://doi.org/10.17671/gazibtd.871411

Cited By: 1

Öz

Yazılım geliştirme yaşam döngüsü safhalarından gereksinim belirleme ve tasarım safhasının önemi, sistem geliştirmenin ilk başında olması ve bu safhada yapılacak olan bir hatanın maliyeti ilerleyen safhalarda veya işin bitiminde fark edilmesi durumunda çok pahalıya mal olmasındandır. Yazılım geliştirmenin bu safhasındaki tüm faaliyet ve teknikleri aktaran iş analizi bilgi birikimi (Business Analysis Body of Knowledge- BABOK)) dokümanındaki teknikler ve yöntemlerden faydalanılarak çalışma şekillendirilmiştir. Bu çalışmanın amacı, bu safhada yapılan çalışmaların ve ortaya çıkan ürünlerin kalite gereklerine uyumunun nasıl sağlanabileceğini göstermektir. Bunun için bu çalışmada yöntem olarak farklı standart ve çalışmalar incelenmiş ve bu çalışma kapsamında incelenen projeler için özel kalite gereksinimleri konularak değerlendirme yapılmıştır. Kalite gereksinimleri projeden projeye değişebileceği için özellikle standart veya daha önce ortaya konulan kalite gereksinimleri doğrudan alınmamıştır. Çalışma sonucunda, üç farklı projede, kalite kriterlerine ne derece uyulup uyulmadığı analiz edilmiş ve ortaya konulan kalite gereksinimlerinden özellikle açıklık gereksinimini her üç projenin de ihlal ettiği görülmüştür.

Anahtar Kelimeler

Gereksinim Belirleme, Sistem Tasarımı, Yazılım Geliştirme Yaşam Döngüsü, Gereksinim Kalite Kriterleri

Quality Focused in Determining the Requirements and System Design from the Information System Software Development Life Cycle Phases: Review of Three Projects

Öz

The importance of the requirement determination and design phase, which is one of the software development life cycle phases, is that it is at the beginning of the system development and the cost of an error to be made in this phase is very expensive if it is noticed in the later stages or at the end of the work. The study was shaped by utilizing the techniques and methods in the Business Analysis Body of Knowledge (BABOK) document, which conveys all the activities and techniques at this stage of software development. The purpose of this study is to show how the work done at this stage and the resulting products can comply with the quality requirements. For this, different standards and studies have been examined as a method in this study and an evaluation has been made by setting special quality requirements for the projects examined within the scope of this study. Since the quality requirements may vary from project to project, especially the standard or previously stated quality requirements were not taken directly. As a result of the study, it was analyzed to what extent the quality criteria were complied with in three different projects and it was observed that all three projects violated the quality requirements, especially the clarity requirement.

Anahtar Kelimeler

Requirement Determination, System Design, Software Development Life Cycle, Requirement Quality Criteria

Kaynakça

• Internet: Yazılım, https://tr.wikipedia.org/wiki/Yaz%C4%B1l%C4%B1m, 25.07.2021.
• Business Analysis Body of Knowledge (BABoK), A Guide to Business Analysis Body of Knowledge, International Institute of Business, 2015.
• IEEE Recommended Practice for Software Requirements Specifications, IEEE Computer Society Sponsored by the Software Engineering Standards Committee, 1998.
• Internet: B. Aktaş, Kalite Yaklaşımları ve Yazılım Kalitesi, https://medium.com/@aktasburak/kaliteyakla%C5%9F%C4%B1mlar%C4%B1-ve-yaz%C4%B1l%C4%B1m-kalitesi-23d395754bc1, 03.04.2020.
• Internet: M. Kirikova, J. A.Bubenko, Enterprise Modelling: Improving the Quality of Requirements Specifications. IRIS 17, https://pdfs.semanticscholar.org/9657/5d5fcb0bba481eb399758040274186e555ac.pdf, 03.04.2020.
• J. J. Carr, “Requirements Engineering and Management: The Key to Designing Quality Complex Systems”, The TQM Magazine, 12(6), 400-407, 2000.
• M. Azuma, “Applying ISO/IEC 9126-1 Quality Model to Quality Requirements Engineering on Critical Software”, 12th IEEE International Requirements Engineering Conference (RE '04), 3-10, Kyoto, Japan, 06 Eylül 2004.
• G. Sabaliauskaite, A. Loconsole, E. Engstrom, M. Unterkalmsteiner, B. Regnell, P. Runeson, R. Feldt, “Challenges in Aligning Requirements Engineering and Verification in a Large-Scale Industrial Context.” Requirements Engineering: Foundation for Software Quality, 16th InternationalWorking Conference, REFSQ 2010, 128-142, Essen, Germany, 2010.
• T. Arao, E. Goto, T. Nagata, “Business Process Oriented Requirements Engineering Process” Proceedings of the 2005 13th IEEE International Conference on Requirements Engineering (RE’05), IEEE Computer Society, August 2005.
• A. David, X. Franch, “How Do Software Architects Consider Non-Functional Requirements: A Survey”, Requirements Engineering: Foundation for Software Quality, 16th International Working Conference, REFSQ 2010, 276-278, Essen, Germany, 2010.
• A. Davis, S. Overmyer, K. Jordan, J. Caruso, F. Dandashi, A. Dinh, M. Theofanos, “Identifying and Measuring Quality in a Software Requirements Specification”, Proceedings First International Software Metrics Symposium, 141-152, 1993.
• A. Nordin, N. H. Zaidi, N. A. Mazlan, “Measuring Software Requirements Specification Quality”, Journal of Telecommunication, Electronic and Computer Engineering, 9(3-5), 123-128, 2017.
• R. S. Carson, Implementing Structured Requirements to Improve Requirements Quality, The Boeing Company, 2015.
• A Chakraborty, M..K. Baowaly, A. Arefin, A. N. Bahar, “The Role of Requirement Engineering in Software Development Life Cycle”, Journal of Emerging Trends in Computing and Information Sciences, 3(5), 723-729, 2012.
• F. Fabbrini, M. Fusani, S. Gnesi, G. Lami, “Quality Evaluation of Software Requirement Specifications”, Proceedings of the Software and Internet Quality Week 2000 Conference, 1-18, 2000.
• Internet: A. Herrmann, B. Paech, Quality Misuse Semantic Scholar, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.100.6249&rep=rep1&type=pdf, 06.04.2020.
• K. Esaki, “System Quality Requirement and Evaluation, Importance of Application of the ISO/IEC25000 series”, Global Perspectives on Engineering Management, 2(2), 52-59, 2013.
• C. Denger, B. Paech, “An Integrated Quality Assurance Approach for Use Case Based Requirements”, Lecture Notes in Informatics, 59-74, 2004.
• W. M. Wilson, “Writing Effective Qequireents Specifications” CrossTalk: The Journal of Defense Software Engineering, 16-19, 1999.
• Internet: N. Boulila, Guidelines for Good Requirements Writing with Examples, Researchgate. https://www.researchgate.net/publication/284173600, 10.04.2020.
• Internet: K. Şen, İyi Gereksinim Yazma Teknikleri, http://www.emo.org.tr/ekler/41bea7a76881d2c_ek.pdf, 06.04.2020.
• H. L. Yang, J. H. Tang, “A Three‐Stage Model of Requirements Elicitation for Web‐Based Information Systems” Industrial Management & Data Systems, 103(6), 398-409, 2003.
• L. Cao, B. Ramesh, “Agile Requirements Engineering Practices: An Empirical Study”, IEEE Software, 60-67, 2008.
• System and Software Engineering – Life Cycle processes – Requirements engineering, ISO/IEC/IEEE 29148, 2011.
• Z. Racheva, M. Daneva, L. Buglione, “Supporting the Dynamic Reprioritization of Requirements in Agile Development of Software Products”, Proceedings of the Second International Workshop on Software Product Management, 49-58, 2008.
• T. Bebensee, I. Van De Weerd, S. Brinkkemper, “Binary Priority List for Prioritizing Software Requirements”, Requirements Engineering: Foundation for Software Quality, 16th InternationalWorking Conference, REFSQ 2010, 67-78, Essen, Germany, 2010.
• I. Sommerville, Software Engineering, Tenth Edition, Global Edition. Pearson, 2016.
• Agile Extension to the Business Analysis Body of Knowledge (BABOK), IIBA, Agile Alliance, 2017.
• Systems Engineering Handbook, Appendix C: How to Write a Good Requirement, NASA, 2020.
• Software Engineering - Product quality (ISO/IEC 9126), 2001.
• Systems and Software Engineering – Systems and Software Quality Requirements and Evaluation (SQuaRE) – System and Software Quality Models (ISO/IEC 25010: 2011), 2011.
• Chaos Raporu, The Standish Group, 2015.
• Chaos Raporu, The Standish Group, 2018.
• M. Huo, J. Verner, L. Zhu, M. A. Babar, “Software Quality and Agile Methods”, Proceedings of the 28th Annual International Computer Software and Applications Conference (COMPSAC’04), 2004.
• P. Heck, A. Zaidman, A Quality Fraework for Agile Requireents: A Practitioner’s Perspective, 2014.