A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document

Beg, Rizwan; Abbas, Qamar; Joshi, Alok

doi:10.1109/icetet.2008.160

Cited by 9 publications

(8 citation statements)

References 4 publications

(3 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The work of [7] can be another example of POS tagging technique for ambiguity detection. In this method, it detects only the lexical ambiguity and matches the words of one line in NLSRS by the part of speech tagger.…”

Section: Related Workmentioning

confidence: 99%

Algorithm for Automatic Detection of Ambiguities from Software Requirements

2019

IJITEE

View full text Add to dashboard Cite

Software Systems are built by the Software engineers and must ensure that software requirement document (SRS) should be specific. Natural Language is the main representation of Software requirement specification document, because it is the most flexible and easiest way for clients or customers to express their software requirements [2]. However being stated in natural language, software requirement specification document may lead to ambiguities [28]. The main goal of presented work to automatically detection of the different types of ambiguities like Lexical, Syntactic, Syntax and Pragmatic. Then an algorithm is proposed to early detection the different types of ambiguities from software requirement document. Part of Speech (POS) technique and regular expression is used to detect each type of ambiguities. An algorithm presented in this paper have two main goals (1) Automatic detection of different types of ambiguities. (2) Count the total number of each types of ambiguities found and evaluate the percentage of ambiguous and non- ambiguous statements detected from software requirement document. The suggested algorithm can absolutely support the analyst in identifying different kinds of ambiguities in Software requirements specification (SRS) document.

show abstract

Section: Related Workmentioning

confidence: 99%

Algorithm for Automatic Detection of Ambiguities from Software Requirements

2019

IJITEE

View full text Add to dashboard Cite

show abstract

“…In requirements engineering (RE), ambiguity is defined as “ having multiple interpretations despite the readers knowledge of the RE context ”[ 3 ]. Literature is evident that ambiguity in requirements is a more intractable problem than the other problems in requirements like misunderstood and incomplete requirements [ 4 ] because requirements are specified in natural language (NL) [ 5 , 6 ]. One way to avoid ambiguity is specification of requirements in formal languages.…”

Section: Introductionmentioning

confidence: 99%

Reducing Requirements Ambiguity via Gamification: Comparison with Traditional Techniques

Dar

Imtiaz

Lali

2022

Computational Intelligence and Neuroscience

View full text Add to dashboard Cite

Requirements elicitation is one of the most significant activities of requirements engineering (RE) process. Poorly specified requirements can lead to a failed project. Various elicitation techniques are used to elicit requirements from the users and other stakeholders, each having its own pros and cons. Lack of user engagement, less user involvement, textual nature of the requirements, time taking process are some of the major problems that make it difficult to perform elicitation via traditional techniques. Moreover, these problems further create other challenges such as ambiguity, inconsistency, and incompleteness in requirements. Currently, researchers have focused on reducing ambiguity in requirements with the help of different techniques such as natural language processing techniques, requirement templates, and formal methods; however, these techniques work on reducing ambiguity during specification or from specified requirements. One of the “young’ and exciting way of engaging users in requirements elicitation of a system is “Gamification’, which helps in user engagement into the system. We intend to discover how gamification helps in reducing ambiguity by engaging stakeholders in an interactive manner. In this review study, we have reviewed traditional techniques used to detect and reduce requirements ambiguity. On the contrary, we have also presented the significance of gamification in requirements elicitation and the popular but effective game elements used in similar systems. Furthermore, this study highlights the significance of using gamification in requirements elicitation, which is beneficial to software development team as well as the users involved in the system.

show abstract

“…Using semi-formal notations is one of well-known ways for requirements analysis and definitions [5], [6]. Such kinds of notations enable us to explicitly specify the semantic structure in each requirement.…”

Section: Introductionmentioning

confidence: 99%

Quality Requirements Analysis Using Requirements Frames

Kaiya

Ohnishi

2011

2011 11th International Conference on Quality Software

View full text Add to dashboard Cite

Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to define quality requirements more completely and correctly.

show abstract

A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document

Cited by 9 publications

References 4 publications

Algorithm for Automatic Detection of Ambiguities from Software Requirements

Algorithm for Automatic Detection of Ambiguities from Software Requirements

Reducing Requirements Ambiguity via Gamification: Comparison with Traditional Techniques

Quality Requirements Analysis Using Requirements Frames

Contact Info

Product

Resources

About