An Ontology Framework for Generating Requirements Specification
Requirements engineering is the initial process of software development that critically determines the overall software process quality. However, this process is error-prone. This is generally related to the factors of communication, knowledge, and documentation. With the lack of business knowledge, it is complicated for (technical) engineers to define customer needs. Also, modeling and documenting requirements need much time and effort to ensure that the requirements are valid, and nothing is missed. The current approach of the requirements modeling process mostly focuses on the Unified Modeling Notation (UML) use case, that not provide enough information for a stakeholder to define system requirements. The generated SRS is still lack of detail development guideline that increase risk of development error. The purpose of this research is to guide for the elicitation process to avoid missing and mismatch requirements, and to make the modeling and documentation process more effective and efficient. We propose an ontology framework for generating requirements specification. This framework, namely the Rule-Based Ontology Framework (ROF) consists of two main processes: First, requirements elicitation. This step provides a guideline for the stakeholder to define system requirements based on the problem of the current system and business process enhancement. Based on this final requirement list, the requirements ontology is generated. Second, the auto-generation of the requirements specification document. The document consists of semi-formal modeling and natural language. In this research, we use Business Process Modeling Notation (BPMN) is a modeling language. For natural language documents, we use IEEE for the SRS template.
P. Spoletini, “Requirements Elicitation : A Look at the Future through the Lenses of the Past,” IEEE 25th Int. Requir. Eng. Conf., 2017.
B. Borlini, A. Luiz, D. C. Leal, R. De Almeida, and G. Guizzardi, “Ontological Foundations for Software Requirements with a Focus on Requirements at Runtime,” Appl. Ontol., vol. 13, pp. 1–3, 2018.
R. Chitchyan, C. Becker, and B. Penzenstadler, “Sustainability Design in Requirements Engineering : State of Practice,” Proc. 38th Int. Conf. Softw. Eng. Companion, pp. 533–542, 2016.
M. A. Ramdhani, D. Sa, A. S. Amin, and H. Aulawi, “Requirements Elicitation in Software Engineering,” Int. J. Eng. Technol., vol. 7, pp. 772–775, 2018.
R. N. Rehman T., Naeem M., “Analysis of Requirement Engineering Processes , Tools / Techniques and Methodologies,” I.J. Inf. Technol. Comput. Sci., vol. 3, pp. 40–48, 2013.
O. Isam, A. Mrayat, N. Norwawi, and N. Basir, “Requirements Elicitation Techniques : Comparative Study,” Int. J. Recent Dev. Eng. Technol., vol. 1, pp. 1–10, 2013.
S. Khan, A. B. Dulloo, and M. Verma, “Systematic Review of Requirement Elicitation Techniques,” Int. J. Inf. Comput. Technol., vol. 4, pp. 133–138, 2014.
S. Sharma, “Requirements Elicitation: Issues and Challenges,” Comput. Sustain. Glob. Dev. (INDIACom), 2014 Int. Conf., pp. 151–155, 2014.
F. Adikara, B. Hendradjaya, and B. Sitohang, “Organization Goal-Oriented Requirements Elicitation Process to Enhance Information System,” Int. J. Electr. Comput. Eng., vol. 6, no. 6, p. 12802, 2016.
J. Melegati, A. Goldman, and S. Paulo, “Requirements Engineering in Software Startups : a Grounded Theory approach,” IEEE Int. Technol. Manag. Conf., pp. 57–65, 2016.
P. Jakkaew, “Requirements Elicitation to Develop Mobile Application for Elderly,” 2017 Int. Conf. Digit. Arts, Media Technol., no. March, pp. 464–467, 2019.
Q. Xu, R. J. Jiao, X. Yang, M. Helander, H. M. Khalid, and A. Opperud, “An analytical Kano model for customer need analysis,” Des. Stud., vol. 30, pp. 87–110, 2009.
K. Pohl, Requirements Engineering: Fundamentals, Principles, and Techniques, vol. 1. 2010.
E. Pereira, A. Rettberg, and S. Soares, “Model-based requirements specification of real-time systems with UML, SysML and MARTE,” Softw. Syst. Model., vol. 17, pp. 343–361, 2018.
R. S. K.Deyb, Alaaeddine Yousfi, Christine Bauer, “uBPMN: A BPMN extension for modeling ubiquitous business processes,” Inf. Softw. Technol., vol. 24, pp. 55–68, 2016.
M. Geiger, S. Harrer, J. Lenhard, and G. Wirtz, “BPMN 2.0: The state of support and implementation Matthias,” 2016.
H. Kaiya, “Using Domain Ontology as Domain Knowledge for Requirements Elicitation,” Requir. Eng. 14th IEEE Int. Conf., vol. 14, pp. 189–198, 2006.
M. El Ghosh, H. Naja, H. Abdulrab, and M. Khalil, “Ontology Learning Process as a Bottom-up Strategy for Building Domain- specific Ontology from Legal Texts Ontology Learning Process as a Bottom-up Strategy for Building Domain-specific Ontology from Legal Texts,” J. Intell. Manuf., vol. 27, pp. 263–282, 2016.
T. H. Nguyen, J. Grundy, and M. Almorsy, “GUITAR: An ontology-based automated requirements analysis tool,” 2014 IEEE 22nd Int. Requir. Eng. Conf. RE 2014 - Proc., vol. 22, pp. 315–316, 2014.
R. a. Elliott, Sr. and E. B. Allen, “A Methodology for Creating an IEEE Standard 830-1998 Software Requirements Specification Document,” J. Comput. Sci. Coll., vol. 29, pp. 123–131, 2013.
I. W. Taifa and D. A. Desai, “Student-Defined Quality By Kano Model : A Case Study of Engineering Students in India,” Int. J. Qual. Res., vol. 10, no. 3, pp. 569–582, 2016.
M. Straka and J. Strakov, “Tokenizing , POS Tagging , Lemmatizing and Parsing UD 2 . 0 with UDPipe,” Proc. CoNLL 2017 Shar. Task Multiling. Parsing from Raw Text to Univers. Depend., vol. 2, pp. 88–99, 2017.
M. De Laat and M. Daneva, “Empirical Validation of a Software Requirements Specification Checklist,” CEUR Workshop Proc., vol. 2075, 2018.
- There are currently no refbacks.
Published by INSIGHT - Indonesian Society for Knowledge and Human Development