MODEL REQUIREMENT TRACEABILITY UNTUK METODE PENGEMBANGAN PERANGKAT LUNAK FEATURE DRIVEN DEVELOPMENT (FDD)

Fildzah Shabrina, Widodo Widodo, Bambang Prasetya Adhi

Abstract


Abstract
A recent study conducted by the Standish Group in 2012 shows that in the preparation of requirements becomes one of the critical success factors of a software. Requirements traceability is the method used to explore inter-linkages or inter-relations requirement, so that when an error occurs in one or more functions on a software, or changes in the requirements, then it can easily be identified requirements which are problematic. Feature Driven Development (FDD) is one of the Agile method that does not have a fixed rule in the formation of inter-search requirement models and inter-feature. By using grounded theory in research, such as open coding, axial coding, and selective coding, and sorting. The research began with the determination of the review and identification of the problem, collect relevant data, perform data analysis, and the final document the results. Based on the test results, the modeling traceability requirements in the FDD method can assist in tracing linkages, inter-relations requirements as well as inter-feature during software development. And can be used as documentation of a software development work.
Keywords : requirement, traceability, relation, Feature Driven Development, and grounded theory.


Penelitian terbaru yang dilakukan oleh Standish Group pada tahun 2012 menunjukkan bahwa dalam penyusunan requirements menjadi salah faktor penentu keberhasilan sebuah perangkat lunak. Requirement traceability merupakan metode yang digunakan untuk menelusuri keterkaitan atau interkoneksi antar-requirement, sehingga ketika terjadi kesalahan dalam satu atau lebih fungsi pada sebuah perangkat lunak, atau terjadi perubahan requirement, maka dengan mudah dapat diidentifikasi requirement mana yang bermasalah. Metodologi pengembangan perangkat lunak Feature Driven Development (FDD) merupakan salah satu bagian dari metode Agile dimana pendekatan FDD dilakukan secara adaptif dalam pengembangan sistem. FDD merupakan Agile Method yang belum mempunyai aturan baku dalam pembuatan model penelusuran antar-requirement maupun antar-feature. Requirement pada FDD tidak secara eksplisit dapat digali, dicari, dan diatur. Namun dokumentasi requirement dibutuhkan pada proses pembentukan feature list. Oleh sebab itu dibutuhkan suatu dokumentasi model penelusuran antar requirements. Pembuatan model penelusuran requirement dengan menggunakan metode grounded theory yaitu diantaranya adalah open coding, axial coding, selective coding, dan sorting. Penelitian bermula dengan penentuan bidang kaji dan identifikasi masalah, mengumpulkan data-data terkait, melakukan analisis data, dan terakhir mendokumentasikan hasil. Berdasarkan hasil uji, pembuatan model penelusuran requirement pada metode FDD dapat memudahkan penelusuran jika terjadi kesalahan dalam testing hasil akhir program dan dapat dijadikan sebagai acuan pembuatan fungsi dalam pengembangan proyek selanjutnya.
Kata kunci : requirement, penelusuran, keterkaitan, Feature Driven Development, dan grounded theory.


Keywords


requirement; traceability; relation; Feature Driven Development; grounded theory.

Full Text:

PDF

References


Abrahamsson, P., Salo, O., & dkk. (2002). Agile Software Development Methods. Finlandia: VTT Publication.

Adolph, S., Hall, W., & Kruchten, P. (2011). Using Grounded Theory to Study The Experience of Software Development. Empirical Software Engineering, 16(4), 487-513.

Arimbawa, I. A. (2014). Feature Driven Development (FDD), Apakah Bisa Disebut Agile ? STMIK Lombok, 1-5.

Aurum, A., & Wohlin, C. (2005). Engineering and Managing Software Requirements. Requirements Engineering for Agile Methods, 18, 309-325.

Coad, P., & De Luca, J. (1999). Java Modeling in Color With UML. Upper Saddle River: NJ: Prentice Hall PTR.

Elizabeth, K. (2010). Requirement Engineering: Third Edition. London: Springer.

Ghazarian, A. (2008). Traceability Pattern: An Approach to Requirement-Component Traceability in Agile Software Development. The 8th WSEAS International Conference on APPLIED COMPUTER SCIENCE (hal. 236-241). Canada: University of Toronto.

Goyal, S. (2007/2008). Major Seminar on Feature Driven Development: Agile Techniques for Project Management and Software Engineering. Munich: Technical University Munich.

Hoda, R., Noble, J., & Marshall, S. (2011). Developing a Grounded Theory to Explain The Practices of Self-Organizing Agile Teams. Empirical Software Engineering, 17(6), 609-639.

Hull, E., Jackson, K., & Dick, J. (2011). Requirements Engineering: Third Edition. London: Springer.

IEEE Computer Society. (2004). SWEBOK: Guide to the Software Engineering Body of Knowledge. California: Angela Burgess.

IEEE STD 1220-1998. (1998). Standard for Application and Management of the Systems Engineering Process. New York: IEEE.

Jiang, L. (2005). A Framework for The Requirements Engineering Process Development. Alberta: University of Calgary.

Paetsch, F., Eberlein, A., & Maurer, F. (2003). Requirements Engineering and Agile Software Development. Proceedings of The 12th IEEE International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (hal. 1-5). IEEE Computer Society.

Palmer, S. R., & Felsing, J. (2001). A Practical Guide to Feature-Driven Development. Dipetik November 2015, dari www.step- 10.com

Palmer, S. R., & Felsing, J. M. (2002). A Practical Guide tp Feature-Driven Development. Upper Saddle River, NJ: Prentice-Hall.

Palo, M. (2003). Requirements Traceability. Department of Computer Science University of Helsinki.

Pinheiro, F., & Goguen, J. A. (1996). An Object- Oriented Tool for Tracing Requirements. IEEE Software, 13(2), 52-64.

Ramesh, B., & Jarke, M. (2001). Towards Reference Models for Requrements Traceability. IEEE Transactions on Software Engineering, 27(1), 58-93.

Sommerville, I., & Sawyer, P. (1997). Requirements Engineering: A Good Practice Guide. England: John Wiley & Sons.

Strauss, A., & Corbin, J. (2003). Dasar-Dasar Penelitian Kualitatif. (Terjemahan oleh M. Shodiq, & I. Muttaqien) Yogyakarta: PUSTAKA BELAJAR.

The Standish Group. (2012). Chaos Manifesto 2012: The Year of the Executive Sponsor. The Standish Group.

Young, R. R. (2004). The Requirements Engineering Handbook. London: Artech House.

Zave, P. (1997). Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, 29(4), 315-321.


Refbacks

  • There are currently no refbacks.