Abstract
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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: International Journal on Advanced Science, Engineering and Information Technology
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.