The Prevalence and Impact of Persistent Ambiguity in Software Requirements Specification Documents
MetadataShow full item record
Despite a large amount of research in methods and tools for avoiding and detecting requirements ambiguity, recent studies have indicated that requirements ambiguity seems to be resolved through multiple inspections and discussions that characterize the requirements engineering process. However, this process may not catch ambiguity types that are likely to result in subconscious disambiguation. People are likely unaware of and incapable of recognizing these ambiguity types; therefore, these types are likely to remain after multiple inspections. This kind of ambiguity is defined as persistent ambiguity and may cause expensive damage. The potential impact of persistent ambiguity was investigated. Initially, a comprehensive ambiguity model based on linguistic ambiguity and its application to requirements engineering was developed. The model was subsequently analyzed to determine the ambiguity types likely to result in subconscious disambiguation and therefore likely to persist. Three requirements specifications were inspected for instances of persistent ambiguity as defined in the model. Each chief requirements engineer verified whether the persistent ambiguities likely to have the greatest impact on each project were indeed interpreted ambiguously, and if so, what the impact was. For the three requirements specifications inspected, there is an average of one persistent ambiguity for every 15.38 pages; project one has the highest average of one persistent ambiguity for every 3.33 pages, project three has an average of one persistent ambiguity for every 31.25 pages, and project two has the lowest average of one persistent ambiguity for every 56 pages. For the three projects, none of the persistent ambiguities reviewed by each chief requirements engineer caused expensive damage because all of the requirements engineers seemed to subconsciously disambiguate the ambiguities in the same way. For the three projects analyzed and the ambiguities reviewed by each chief requirements engineer, the least expensive approach would have been to forego initially identifying persistent ambiguity in these three projects. The first main conclusion is that persistent ambiguity remained undetected by the teams of requirements engineers. The second main conclusion is that the process used by these particular requirements engineering teams for these particular projects is enough to prevent damage. The third main conclusion is that the identification of persistent ambiguity in requirements specifications is potentially an effective and efficient strategy for minimizing damage caused by ambiguity precisely because of its focus on ambiguity that remained undetected due to lack of awareness. Further study is necessary to determine what factors are involved in persistent ambiguity and its prevalence, as well as its potential impacts.
Cite this version of the work
Cristina Ribeiro (2016). The Prevalence and Impact of Persistent Ambiguity in Software Requirements Specification Documents. UWSpace. http://hdl.handle.net/10012/11123
Showing items related by title, author, creator and subject.
Csonka-Peeren, Jacqueline (University of Waterloo, 2022-01-24)This PhD dissertation applies the science of decision making to management, specifically entrepreneurship. The purpose of this research is to better understand entrepreneurial behaviour under condition of Knightian ...
Jahnke, Heidi (University of Waterloo, 2011-05-19)Each painting in this exhibition is a transformed documentation of a specific experience culled from my daily, ordinary life. These encounters are not monumental; however their impact is significant because of their ...
Jin, Hyunjong (University of Waterloo, 2012-04-11)The classical mean-variance model, proposed by Harry Markowitz in 1952, has been one of the most powerful tools in the field of portfolio optimization. In this model, parameters are estimated by their sample counterparts. ...