2017Unpublished venueRequires access

A framework for detecting ambiguity in software requirement specification

Ali Olow Jimale, Wan Mohd Nazmee Wan Zainon

Open publisher page 34 citations

Abstract

The accomplishment of any software system success depends on how well it meets the requirements of the stakeholders. These requirements are elicited from the customers. Software requirements are unambiguous if and only if it has one meaning. The elicited requirements are documented in software requirements specification document and these requirements are written in natural languages. Natural languages are basically ambiguous which makes the requirements documented in software requirements specification document unclear. This unclear requirement causes that software developers develop software which is different from the expected software based on the customer needs. The objective of this paper is to propose a framework that are able to detect ambiguity in software requirements specification document automatically using parts of speech tagging technique. To validate the outcome of the proposed work, open source software requirements specification documents will be used and generated result of the proposed work will be evaluated and validated by making comparison between the proposed prototype results and human generated results to decide how the proposed prototype can solved the ambiguity problem.

About this research paper

What this paper is about

The accomplishment of any software system success depends on how well it meets the requirements of the stakeholders. These requirements are elicited from the customers. Software requirements are unambiguous if and only if it has one meaning. The elicited requirements are documented in software requirements specification document and these requirements are written in natural languages. Natural languages are basically ambiguous which makes the requirements documented in software requirements specification document unclear. This unclear requirement causes that software developers develop software which is different from the expected software based on the customer needs. The objective of this paper is to propose a framework that are able to detect ambiguity in software requirements specification document automatically using parts of speech tagging technique. To validate the outcome of the proposed work, open source software requirements specification documents will be used and generated result of the proposed work will be evaluated and validated by making comparison between the proposed prototype results and human generated results to decide how the proposed prototype can solved the ambiguity problem.

Why it matters

OpenAlex reports 34 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The accomplishment of any software system success depends on how well it meets the requirements of the stakeholders. These requirements are elicited from the customers. Software requirements are unambiguous if and only if it has one meaning. The elicited requirements are documented in software requirements specification document and these requirements are written in natural languages. Natural languages are basically ambiguous which makes the requirements documented in software requirements specification document unclear. This unclear requirement causes that software developers develop software which is different from the expected software based on the customer needs. The objective of this paper is to propose a framework that are able to detect ambiguity in software requirements specification document automatically using parts of speech tagging technique. To validate the outcome of the proposed work, open source software requirements specification documents will be used and generated result of the proposed work will be evaluated and validated by making comparison between the proposed prototype results and human generated results to decide how the proposed prototype can solved the ambiguity problem.

Key concepts: Software requirements specification, Computer science, Software requirements, Requirement, Software engineering, Requirement prioritization, Ambiguity, Requirements analysis

Related papers

Back to paper searchBrowse research topicsOriginal source
A framework for detecting ambiguity in software requirement specification — Research Paper | ScholarLens