Abstract
An inconsistent and ambiguous Software Requirement Specification (SRS) document results in an erroneous/failed software project. Hence, it is a serious challenge to handle and process complex and ambiguous requirements. Most of the literature work focuses on detection and resolution of ambiguity in software requirements. Also, there is no standardized way to write unambiguous and consistent requirements. The goal of this research was to generate an ambiguity-less SRS document. This paper presents a new approach to write ambiguity-less requirements. Furthermore, we design a framework for Natural Language (NL) to Controlled Natural Language (CNL) (such as Semantic Business Vocabulary and Rules (SBVR)) transition and develop a prototype. The prototype also generates Resource Description Framework (RDF) representation. The SBVR has a shared meaning concept that minimizes ambiguity, and RDF representation is supported by query language such as SPARQL Protocol and RDF Query Language (SPARQL). The proposed approach can help software engineers to translate NL requirements into a format that is understandable by all stakeholders and also is machine processable. The results of our prototype are encouraging, exhibiting the efficient performance of our developed prototype in terms of usability and correctness.
Highlights
Requirements engineering (RE) has been dealing with similar issues since the beginning in software engineering
Requirement elicitation and requirement analysis phases are significant to ensure complete, consistent, and unambiguous requirement specifications. e end product of the RE phase is the Software Requirement Specification (SRS) document. e SRS document becomes the base of the later stages [1] of the software development process. e initial phases of the software development process have more impact on the software quality as compared to later phases [2]. e SRS document maintains user end story in descriptive form using Natural Language (NL) [1], because NL is the most convenient way to communicate while gathering requirements in business process development as well as in software development
A sample of extracted Noun concepts, Verb concepts, Fact types, and generated Semantic Business Vocabulary and Rules (SBVR) rules are presented in Table 12. e sampling requirement set T is a subset of the requirements set T1
Summary
Requirements engineering (RE) has been dealing with similar issues since the beginning in software engineering. RE is a common phase in business process development as well as software development for user requirement specification. The four stages of RE in the software development process include requirement elicitation, analysis, requirement validation, and specification. Requirement elicitation and requirement analysis phases are significant to ensure complete, consistent, and unambiguous requirement specifications. E end product of the RE phase is the SRS document. E SRS document becomes the base of the later stages [1] of the software development process. E SRS document maintains user end story in descriptive form using NL [1], because NL is the most convenient way to communicate while gathering requirements in business process development as well as in software development. Almost 79% of requirement specification documents are found in “Real Natural Language” [3]. Along with the key features, NL is inherently ambiguous [5] and has extensively been recognized as a challenge [6]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
