RAUMM: A Model for Requirement Ambiguity and Uncertainty Management in Software Requirement Specification
DOI:
https://doi.org/10.61841/0d2s0q24Keywords:
Software Engineering,, Software Requirement Specification, Requirement ambiguity,, Lexical ambiguity,, Syntax ambiguity, Syntactic ambiguity,, Referential ambiguity,, Adaptive Neuro Fuzzy System.Abstract
The Requirement specification document serves as a contract between the developer and the various stakeholders of the system under development. For better quality control, every requirement needs to be verified before being based line. According to the report of Systems Sciences Institute at IBM, it cost 6 times more when fixing a bug in implementation phase than fixing the same bug during the design phase. Furthermore, it costs 15 times more to fix bugs in testing phase if left during the design phase. This paper attempts to propose a model Requirement Ambiguity and Uncertainty Management Model (RAUMM) to deal with requirement ambiguity and uncertainty at early stage of software development. A tool has been developed to detect four types of ambiguities i.e. lexical, syntax, syntactic and referential ambiguity in requirements specification document. A compilation of potential ambiguous words is done from the taxonomy present in Ambiguity Handbook. This proposed tool will help the analysts to detect potential ambiguities. Several requirements writing rules have been taken from literature. Ambiguity Assessment has been performed by implementation of Adaptive Fuzzy Neural Network and ambiguities detected by tool have been taken as input. Relationship between Uncertainty and ambiguity has been analyzed finally.
Downloads
Published
Issue
Section
License
This work is licensed under a Creative Commons Attribution 4.0 International License.
You are free to:
- Share — copy and redistribute the material in any medium or format for any purpose, even commercially.
- Adapt — remix, transform, and build upon the material for any purpose, even commercially.
- The licensor cannot revoke these freedoms as long as you follow the license terms.
Under the following terms:
- Attribution — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
- No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Notices:
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation .
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
