On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews - Results from a Controlled Experiment

To ensure fulfilling stakeholder wishes, it is crucial to validate the documented requirements. This is often complicated by the fact that the wishes and intentions of different stakeholders are somewhat contradictory, which manifests itself in inconsistent requirements. To aid requirements engineers in identifying and resolving inconsistent requirements, we investigated the usefulness for manual reviews of two different model-based representation formats for inconsistent requirements; one that represent the inconsistent requirements in separate diagrams and one that represents them integrated into one diagram using annotations. The results from a controlled experiment show that the use of such integrated review diagrams can significantly increase efficiency of manual reviews, without sacrificing effectiveness.

• Publication year

  2017

• Venue

  International Conference on Conceptual Modeling

• Publication date

  2017-07-10

• Fields of study

  Computer Science

• Identifiers
  DOI 10.1007/978-3-319-69904-2_35arXiv 1707.02907
• External record

  Open on Semantic Scholar

• Source metadata

  Semantic Scholar

• No claims are published for this paper.

• No concepts are published for this paper.

• Common Threats and Mitigation Strategies in Requirements Engineering Experiments with Student Participants

  2016cited by this paper
• The impact of students' skills and experiences on empirical results: a controlled experiment with undergraduate and graduate students

  2015cited by this paper
• Views on Internal and External Validity in Empirical Software Engineering

  2015cited by this paper
• Detecting and Correcting Outdated Requirements in Function-Centered Engineering of Embedded Systems

  2015cited by this paper
• Are Students Representatives of Professionals in Software Engineering Experiments?

  2015cited by this paper
• Validating the functional design of embedded systems against stakeholder intentions

  2014cited by this paper
• Function-centered engineering of embedded systems: Evaluating industry needs and possible solutions

  2014cited by this paper
• Experimentation in Software Engineering

  2012cited by this paper
• A systematic review of the use of requirements engineering techniques in model-driven development

  2010cited by this paper
• Synthesis of Partial Behavior Models from Properties and Scenarios

  2009cited by this paper
• Using students as subjects - an empirical evaluation

  2008cited by this paper
• Reporting Experiments in Software Engineering

  2008cited by this paper
• Model-driven Development of Complex Software: A Research Roadmap

  2007cited by this paper
• A Formal Model for Integrating Multiple Views

  2007cited by this paper
• Model-Driven Engineering

  2006cited by this paper
• PBR vs. checklist: a replication in the n-fold inspection context

  2006cited by this paper
• Perspective-Based Reading: A Replicated Experiment Focused on Individual Reviewer Effectiveness

  2006cited by this paper
• Interaction-based behavior modeling of embedded software using UML 2.0

  2006cited by this paper
• Merging Scenarios

  2005cited by this paper
• Model-Based Development: Combining Engineering Approaches and Formal Techniques

  2004influential reference
• Assessing defect detection performance of interacting teams in object-oriented design inspection

  2004cited by this paper
• Using Students as Experiment Subjects – An Analysis on Graduate and Freshmen Student Data

  2003cited by this paper
• Evaluation of a perspective based review method applied in an industrial setting

  2003influential reference
• High quality statecharts through tailored, perspective-based inspections

  2003cited by this paper
• Specifying and executing behavioral requirements: the play-in/play-out approach

  2003cited by this paper
• Infinite-state high-level MSCs: Model-checking and realizability

  2002cited by this paper
• An Internally Replicated Quasi-Experimental Comparison of Checklist and Perspective-Based Reading of Code Documents

  2001cited by this paper
• How perspective-based reading can improve requirements inspections

  2000cited by this paper
• Hints for Reviewing Empirical Work in Software Engineering

  2000cited by this paper
• Using Students as Subjects—A Comparative Study of Students and Professionals in Lead-Time Impact Assessment

  2000cited by this paper
• Decomposition of Message Sequence Charts

  2000cited by this paper
• Detecting defects in object-oriented designs: using reading techniques to increase software quality

  1999cited by this paper
• Testing Object-Oriented Systems: Models, Patterns, and Tools

  1999cited by this paper
• LSCs: Breathing Life into Message Sequence Charts

  1999cited by this paper
• Detecting defects in object-oriented designs

  1999cited by this paper
• Formal Methods for Open Object-Based Distributed Systems

  1999cited by this paper
• Comparing Detection Methods For Software Requirements Inspections: A Replication Using Professional Subjects

  1998cited by this paper
• Further Experiences with Scenarios and Checklists

  1998cited by this paper
• The empirical investigation of Perspective-Based Reading

  1995cited by this paper
• Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment

  1995cited by this paper
• Viewpoint Oriented Software Development: Mehtods and Viewpoints in Requirements Engineering

  1989cited by this paper
• The magical number seven plus or minus two: some limits on our capacity for processing information.

  1956cited by this paper

• Perceived Potential of Humanoid Robots

  2025cites this paper
• Review Time as Predictor for the Quality of Model Inspections

  2024cites this paper
• Investigating Factors Influencing Students’ Assessment of Conceptual Models

  2023cites this paper
• Aggregating N-fold Requirements Inspection Results

  2023cites this paper
• Model-Based Engineering of Collaborative Embedded Systems: Extensions of the SPES Methodology

  2021cites this paper
• Reliability of self-rated experience and confidence as predictors for students’ performance in software engineering

  2021cites this paper
• Model inspections in the engineering of collaborative cyber‐physical systems with instance‐level review diagrams

  2021cites this paper
• FUNCTIONAL APPLICATION OF THE INTERNAL CONTROL SYSTEM IN AUTONOMOUS INSTITUTIONS

  2020cites this paper
• Do Instance-level Review Diagrams Support Validation Processes of Cyber-Physical System Specifications : Results from a Controlled Experiment

  2020cites this paper
• On the Benefits of using Dedicated Models in Validation Processes for Behavioral Specifications

  2019cites this paper
• Improving manual reviews in function-centered engineering of embedded systems using a dedicated review model

  2019cites this paper
• Experimentation in Conceptual Modeling Research: A Systematic Review

  2019cites this paper
• A Comparative Analysis of ITU-MSC-Based Requirements Specification Approaches Used in the Automotive Industry

  2018cites this paper