Identifying Nocuous Ambiguities in Natural Language Requirements

Chantree, Francis; Nuseibeh, Bashar; Roeck, Anne De; Willis, Alistair

doi:10.1109/re.2006.31

Cited by 121 publications

(106 citation statements)

References 16 publications

Supporting

Mentioning

103

Contrasting

Order By: Relevance

“…Definition: Ambiguous requirement are requirements of which two different experts may have different interpretation [Chantree et al(2006)Chantree, Nuseibeh, de Roeck, and Willis]. Scenario: Ambiguous requirements may result into different interpretation and implementation.…”

Section: Ambiguous Requirementsmentioning

confidence: 99%

Factors Impacting the Inputs of Traceability Recovery Approaches

Ali

Guéhéneuc

Antoniol

2011

Software and Systems Traceability

View full text Add to dashboard Cite

In requirement engineering, researchers have proposed various tractability recovery approaches. To the best of our knowledge, all traceability recovery approaches have low precision and recall. Our main claim in this chapter is that there exist factors that impact the traceability approaches' inputs, in particular source document, target document, and experts' opinion, that cause low precision and recall. In this chapter, we pursue four objectives: first, to identify and document factors that impact traceability recovery approaches' inputs; second, to identify metrics/tools to measure/improve the quality of the inputs with respect to the identified factors, third, to provide precautions to control these factors, and, fourth, to empirically prove and quantify the effect of one of these factors-expert's programming knowledge-on the traceability recovery approaches' inputs. To achieve the first two objectives, we perform an incremental literature review of traceability recovery approaches and identify and document three key inputs and the seven factors impacting these inputs, out of 12 identified factors. We analyse the reported results in literature for the identified factors to address our third objective. We conduct an empirical study to assess the impact of expert's programming knowledge, to address our fourth objective. We use the effort, number of correct answers, and time to measure the effect of expert's programming knowledge on traceability recovery. We conclude that, in the literature, seven factors impacting the inputs of traceability recovery approaches have been identified, documented, and reported along with related metrics/tools and precautions. We suggest that practitioners should be wary of these seven factors and researchers should focus on the five others to improve traceability recovery approaches.

show abstract

Section: Ambiguous Requirementsmentioning

confidence: 99%

Factors Impacting the Inputs of Traceability Recovery Approaches

Ali

Guéhéneuc

Antoniol

2011

Software and Systems Traceability

View full text Add to dashboard Cite

show abstract

“…Functional requirements are typically formulated as prescriptive statements to be satisfied by the system. While it is still a common practice to describe functional requirements using natural language, the potential for misinterpretation of such descriptions is considerable due to the inherent ambiguity of natural languages [Ber08,CNdRW06]. Formal languages with well-defined semantics provide a more rigorous and reliable means for specifying functional requirements in the context of system design.…”

Section: Functional Requirementsmentioning

confidence: 99%

Using Models at Runtime to Address Assurance for Self-Adaptive Systems

et al. 2014

View full text Add to dashboard Cite

Abstract.A self-adaptive software system modifies its behavior at runtime in response to changes within the system or in its execution environment. The fulfillment of the system requirements needs to be guaranteed even in the presence of adverse conditions and adaptations. Thus, a key challenge for self-adaptive software systems is assurance. Traditionally, confidence in the correctness of a system is gained through a variety of activities and processes performed at development time, such as design analysis and testing. In the presence of selfadaptation, however, some of the assurance tasks may need to be performed at runtime. This need calls for the development of techniques that enable continuous assurance throughout the software life cycle. Fundamental to the development of runtime assurance techniques is research into the use of models at runtime (M@RT). This chapter explores the state of the art for using M@RT to address the assurance of self-adaptive software systems. It defines what information can be captured by M@RT, specifically for the purpose of assurance, and puts this definition into the context of existing work. We then outline key research challenges for assurance at runtime and characterize assurance methods. The chapter concludes with an exploration of selected application areas where M@RT could provide significant benefits beyond existing assurance techniques for adaptive systems.

show abstract

“…• when various forms of ambiguity exist in requirements that could lead to different incompatible interpretations of same set of requirements by different stakeholder groups [8,9].…”

Section: Introductionmentioning

confidence: 99%

“…These include [3,12,13,14], which considered how to identify and handle IMR. The works in [8,15,16,17,18] focussed on dealing with tacit/implicit knowledge in requirements; while [9,19,20,21,22] dealt with handling ambiguity in requirements.…”

Section: Introductionmentioning

confidence: 99%

A survey on implicit requirements management practices in small and medium-sized enterprises

2017

View full text Add to dashboard Cite

Preliminary communicationEffective requirements management that embraces both explicit and implicit aspects is a prerequisite for successful software development. Although different researchers and practitioners have identified the importance of implicit requirements (IMR) for overall successful outcome of software development, there is a need to correlate these theoretical assumptions about implicit requirements with the state of the practice. This paper empirically investigates the perception and handling of implicit requirements in small and medium-sized software organisations. The survey was undertaken through a web-based questionnaire to which 56 participants from 23 countries responded. The study found that critical organisational factors such as number of years in business of an organisation, the years of experience of an organisation in requirements engineering, and size of software development team have positive correlation with the perception and handling of implicit requirements within an organisation. It also recommends that a comparative evaluation of the existing support tools for implicit requirements is necessary in order to validate the potential of these tools to solve existing challenges, and determine gaps that still exist. Keywords: empirical survey; implicit requirements; requirements engineering; requirements management; software organisations Anketa o načinu upravljanja bezuvjetnim zahtjevima u malim i srednje malim poduzećimaPrethodno priopćenje Učinkovito upravljanje zahtjevima koje uključuje i izričita i bezuvjetna motrišta pretpostavka je za uspješni razvoj softvera. Iako su razni istraživači i praktičari prepoznali važnost bezuvjetnih zahtjeva (implicit requirements -IMR) za opći uspjeh razvijenog softvera, potrebno je povezati te teorijske pretpostavke oko bezuvjetnih zahtjeva s postojećim stanjem. U radu se provodi empirijsko istraživanje o shvaćanju i provođenju bezuvjetnih zahtjeva u malim i srednje malim organizacijama koje se bave razvojem softvera. Provedena je anketa preko interneta na koju je stiglo 56 odgovora iz 23 zemlje. Analiza je pokazala da se kritički organizacijski čimbenici kao što su broj godina provedenih na poslu u nekoj organizaciji, godine iskustva organizacije u inženjeringu zahtjeva i veličina tima koji se bavi razvojem softvera pozitivno odražavaju na sagledavanje i pristup bezuvjetnim zahtjevima u okviru organizacije. Izražava se potreba za komparativnom procjenom postojećih alata podrške bezuvjetnim zahtjevima kako bi se potvrdio potencijal tih alata u rješavanju postojećih izazova i popunjavanju nedostataka koji još postoje. Ključne

show abstract

Identifying Nocuous Ambiguities in Natural Language Requirements

Cited by 121 publications

References 16 publications

Factors Impacting the Inputs of Traceability Recovery Approaches

Factors Impacting the Inputs of Traceability Recovery Approaches

Using Models at Runtime to Address Assurance for Self-Adaptive Systems

A survey on implicit requirements management practices in small and medium-sized enterprises

Contact Info

Product

Resources

About