Requirements quality control: a unifying framework

Katasonov, Artem; Sakkinen, Markku

doi:10.1007/s00766-005-0018-1

Cited by 33 publications

(19 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In ID, scenarios are proposed to be used in several phases of the design, from early requirement elicitation to design validation. Actually, as recently stressed by Katasonov et al [9], a major problem in requirement quality control is the achievement of a satisfactory level of understanding on the requirements by stakeholders especially when they lack technical expertise and do not share the same (formal and abstract) language of analysts and engineers. Due to the assumption that validating requirements is more an issue of efficiently communicating and iteratively negotiating knowledge than a linear process of checking a given corpus of data, in our study we designed visual scenarios as communication tools to allow technical and non-technical partners to symmetrically contribute to requirements validation and refinement.…”

Section: Personas and Visual Scenariosmentioning

confidence: 98%

Ahab’s Leg: Exploring the Issues of Communicating Semi-formal Requirements to the Final Users

Leonardi

Sabatucci

Susi

et al. 2010

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

Abstract. In this paper, we present our experience in using narrative scenarios as a tool to communicate and validate semi-formal requirements with the stakeholders in a large software project. The process of translating the semi-formal language of Tropos into the narrative form of scenarios is introduced and some unintended implications of this process are discussed. In particular, we define the notion of Ahab's leg to describe the necessity to introduce new constraints or features in a description when moving to a different representational language. Starting from the lessons learned with this specific case study, we derive some general implications concerning the issue of requirement translation for validation tasks and we propose some methodological guidelines to address the Ahab's leg dilemma.

show abstract

Section: Personas and Visual Scenariosmentioning

confidence: 98%

Ahab’s Leg: Exploring the Issues of Communicating Semi-formal Requirements to the Final Users

Leonardi

Sabatucci

Susi

et al. 2010

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

show abstract

“…Subjects were asked how they were feeling about a given sentence, and had to select one answer among Strongly Disagree, Disagree, Neither Agree nor Disagree, Agree or Strongly Agree. The set of variables that we used in our survey is reported in Table II. The quality of documentation REC was studied using some of the quality criteria defined in the quality requirement framework suggested in [22]. Although the sentences shared by stakeholders during elicitation were not proper requirements, we consider the previous criteria can still be considered as ways to evaluate quality of information.…”

Section: Exploratory Study -Empirical Designmentioning

confidence: 99%

How Stakeholders' Commitment May Affect the Success of Requirements Elicitation

Burnay¹,

Jureta²,

Faulkner³

2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Requirements elicitation consists in collecting information about the requirements and the environment of a systemto-be. It usually involves business analysts who are eliciting information, and stakeholders who are providing information. This paper investigates how the commitment of stakeholders to a RE project influences the results of elicitation. We suggest a way to measure the commitment of stakeholders during RE, and propose the so-called "commitment matrix", which shows what analysts can expect from stakeholders who are more, as opposed to those who are less committed. The matrix builds on a survey of 87 stakeholders. Our results suggest that commitment somehow affects the information provided by stakeholders, and that it is therefore a relevant criterion to account for when selecting stakeholders to be involved in elicitation.

show abstract

“…Ott [39] investigated the typical defect type distributions in current natural language requirement specifications. Katasonov et al [23] developed a unifying framework for requirement quality control. Instead of detecting requirement-related defects, our approach is to predict bugs, which can be caused by defects introduced throughout the software lifecycle.…”

Section: Early Bug Predictionmentioning

confidence: 99%

“…However, these approaches can only be applied in later phases of the software lifecycle [49,53]. Prior work also concentrated on requirement inspection techniques to detect requirement-related errors [23,46]. However, these techniques can only be used to detect errors originating in the requirements phase.…”

Section: Introductionmentioning

confidence: 99%

Analyzing and predicting software integration bugs using network analysis on requirements dependency network

Wang

2014

Requirements Eng

View full text Add to dashboard Cite

Complexity, cohesion and coupling have been recognized as prominent indicators of software quality. One characterization of software complexity is the existence of dependency relationships. Moreover, the degree of dependency reflects the cohesion and coupling between software elements. Dependencies in the design and implementation phase have been proven to be important predictors of software bugs. We empirically investigated how requirements dependencies correlate with and predict software integration bugs, which can provide early estimates regarding software quality and thus facilitate decision making early in the software lifecycle. We conducted network analysis on the requirements dependency networks of three commercial software projects. Significant correlation is observed between most of our network measures and the number of bugs. Furthermore, many network measures demonstrate significantly greater values for higher severity (or a higher fixing workload). Afterward, we built bug prediction models using these network measures and found that bugs can be predicted with high accuracy and sensitivity, even in cross-project and crosscompany contexts. We further identified the dependency type that contributes most to bug correlation, as well as the network measures that contribute more to bug prediction. These observations show that the requirements dependency network can be used as an early indicator and predictor of software integration bugs.

show abstract

Requirements quality control: a unifying framework

Cited by 33 publications

References 31 publications

Ahab’s Leg: Exploring the Issues of Communicating Semi-formal Requirements to the Final Users

Ahab’s Leg: Exploring the Issues of Communicating Semi-formal Requirements to the Final Users

How Stakeholders' Commitment May Affect the Success of Requirements Elicitation

Analyzing and predicting software integration bugs using network analysis on requirements dependency network

Contact Info

Product

Resources

About