Analysis of Modeling Techniques used for Translating Natural Language Specification into Formal Software Requirements

Sandhu, Geet

doi:10.5120/19792-1570

Cited by 2 publications

(2 citation statements)

References 10 publications

(20 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One of the preliminary stages is requirements elicitation from stakeholders. Unfortunately, elicited user requirements typically suffer from some imprecision challenging issues such as inaccuracy, inconsistency, incompleteness and ambiguity [1].…”

Section: Introductionmentioning

confidence: 99%

Implementation of a Formal Software Requirements Ambiguity Prevention Tool

Alomari¹,

Elazhary²

2018

ijacsa

View full text Add to dashboard Cite

Abstract-The success of the software engineering process depends heavily on clear unambiguous software requirements. Ambiguity refers to the possibility to understand a requirement in more than one way. Unfortunately, ambiguity is an inherent property of the natural languages used to write the software user requirements. This could cause a final faulty system implementation, which is too expensive to correct. The basic requirements ambiguity resolution approaches in the literature are ambiguity detection, ambiguity avoidance, and ambiguity prevention. Ambiguity prevention is the least tackled approach because it requires designing formal languages and templates, which are hard to implement. The main goal of this paper is to provide full implementation of an ambiguity prevention tool and then study its effectiveness using real requirements. Towards this goal, we developed a set of Finite State Machine (FSMs) implementing templates of various requirement types. We then used Python to implement the ambiguity prevention tool based on those FSMs. We also collected a benchmark of 2460 real requirements and selected a random set of forty real requirements to test the effectiveness of the developed tool. The experiment showed that the implemented ambiguity prevention tool can prevent critical requirements ambiguity issues such as missing information or domain ambiguity. Nevertheless, there is a tradeoff between ambiguity prevention and the effort needed to write the requirements using the imposed templates.

show abstract

Section: Introductionmentioning

confidence: 99%

Implementation of a Formal Software Requirements Ambiguity Prevention Tool

Alomari¹,

Elazhary²

2018

ijacsa

View full text Add to dashboard Cite

show abstract

“…nitial_Diagram_2.pdf The format of these early-stage requirements is typical of those found in real-world projects. In this phase, the job of the requirements engineer is to translate the view that the stakeholders have of their world, colored by their implicit domain knowledge, into a view that the developers can comprehend (Sandhu, 2015). These statements express intent without explaining how the piston or software is intended to implement the functionality.…”

Section: Gathering the Initial Pre-requirements Informationmentioning

confidence: 99%