Interrelating Use Cases and Associated Requirements by Links: An Eye Tracking Study on the Impact of Different Linking Variants on the Reading Behavior

[Context:] The descriptions of interactions and system functions are two of the most important artifact types in requirements specifications. Their common notations are use cases and requirements which are related to each other. There are different variants to link a use case with its associated requirements due to a wide variety of use case templates. The main purpose of all linking variants is to highlight the interrelationships between use cases and requirements. Besides considering both artifacts for themselves, a reader needs to interrelate them to achieve a high understanding of the overall content. [Objective / Method:] Due to the effort to create and maintain links, we investigated the impact of different linking variants on the reading behavior in an eye tracking study with 15 subjects. [Results:] Our findings indicate that all investigated variants cause comparable visual effort and share the most frequent sequential reading pattern. In all cases, the use case was read first and then the requirements. Nevertheless, the different variants result in divergent reading behaviors. Especially, links embedded in the table of a use case description significantly increase the number of attention switches from the use case to the requirements. [Conclusion:] These attention switches represent the reading behavior of interrelating the use case and the associated requirements which only occurred in case of the most detailed linking variant.

[1]  Geri Schneider,et al.  Applying use cases (2nd ed.): a practical guide , 2001 .

[2]  Jacob Cohen Statistical Power Analysis for the Behavioral Sciences , 1969, The SAGE Encyclopedia of Research Design.

[3]  Dawn J. Lawrie,et al.  The impact of identifier style on effort and comprehension , 2012, Empirical Software Engineering.

[4]  Sebastian Eder,et al.  Understanding changes in use cases: A case study , 2015, 2015 IEEE 23rd International Requirements Engineering Conference (RE).

[5]  Marjo Kauppinen,et al.  Bridging the Gap between User Needs and User Requirements , 2001 .

[6]  Barbara Paech,et al.  Task-Driven Requirements in Object-Oriented Development , 2004 .

[7]  Adam A. Porter,et al.  Comparing Detection Methods For Software Requirements Inspections: A Replication Using Professional Subjects , 1998, Empirical Software Engineering.

[8]  Neil Maiden,et al.  Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle , 2004 .

[9]  Yann-Gaël Guéhéneuc,et al.  A systematic literature review on the usage of eye-tracking in software engineering , 2015, Inf. Softw. Technol..

[10]  Andreas Busjahn,et al.  Analysis of code reading to gain more insight in program comprehension , 2011, Koli Calling.

[11]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[12]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[13]  Per Runeson,et al.  Usage-based readingan experiment to guide reviewers with use cases , 2001, Inf. Softw. Technol..

[14]  J. Fleiss Measuring nominal scale agreement among many raters. , 1971 .

[15]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[16]  James Miller,et al.  Further Experiences with Scenarios and Checklists , 1998, Empirical Software Engineering.

[17]  Johannes Gehrke,et al.  Sequential PAttern mining using a bitmap representation , 2002, KDD.

[18]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[19]  Yann-Gaël Guéhéneuc,et al.  Women and men — Different but equal: On the impact of identifier style on source code reading , 2012, 2012 20th IEEE International Conference on Program Comprehension (ICPC).

[20]  Karl E. Wiegers Automating Requirements Management 1 , 1999 .

[21]  Jonathan I. Maletic,et al.  An eye tracking study on the effects of layout in understanding the role of design patterns , 2010, 2010 IEEE International Conference on Software Maintenance.

[22]  James Robertson,et al.  Mastering the Requirements Process: Getting Requirements Right , 2012 .

[23]  Alistair Cockburn,et al.  Patterns for Effective Use Cases , 2002 .

[24]  Luisa Mich,et al.  Market research for requirements analysis using linguistic tools , 2004, Requirements Engineering.

[25]  René Riedl,et al.  Fundamentals of NeuroIS , 2016, Studies in Neuroscience, Psychology and Behavioral Economics.

[26]  Pablo Romero,et al.  Visual Attention and Representation Switching During Java Program Debugging: A Study Using the Restricted Focus Viewer , 2002, Diagrams.

[27]  Jörg Dörr,et al.  What do software architects expect from requirements specifications? results of initial explorative studies , 2012, 2012 First IEEE International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks).

[28]  Pablo Romero,et al.  Visual attention and representation switching during Java program debugging: A study using the Restricted Focus Viewer. Diagrammatic representation and inference , 2002 .

[29]  Derek Coleman A Use Case Template: Draft for Discussion , 1998 .

[30]  J. R. Landis,et al.  The measurement of observer agreement for categorical data. , 1977, Biometrics.

[31]  Giuseppe Visaggio,et al.  A Replicated Experiment to Assess Requirements Inspection Techniques , 2004, Empirical Software Engineering.

[32]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[33]  N. Hari Narayanan,et al.  Visual attention patterns during program debugging with an IDE , 2012, ETRA '12.

[34]  Jonathan I. Maletic,et al.  Assessing the Comprehension of UML Class Diagrams via Eye Tracking , 2007, 15th IEEE International Conference on Program Comprehension (ICPC '07).

[35]  Adam A. Porter,et al.  Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment , 1995, IEEE Trans. Software Eng..

[36]  João Araújo,et al.  What is the Impact of Bad Layout in the Understandability of Social Goal Models? , 2016, 2016 IEEE 24th International Requirements Engineering Conference (RE).

[37]  Ola Blomkvist,et al.  An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections , 1998, Empirical Software Engineering.

[38]  Pablo Romero,et al.  Java Debugging strategies in multi-representational environments , 2003, PPIG.

[39]  Yue Lu,et al.  Towards feature-oriented requirements validation for automotive systems , 2014, 2014 IEEE 22nd International Requirements Engineering Conference (RE).

[40]  Samuel Fricker,et al.  Requirements Engineering: Best Practice , 2015 .

[41]  I. Alexander,et al.  Scenarios, stories, and use cases: the modern basis for system development , 2004 .

[42]  Stefan Biffl,et al.  Using reading techniques to focus inspection performance , 2001, Proceedings 27th EUROMICRO Conference. 2001: A Net Odyssey.

[43]  Magne Jørgensen,et al.  Quality and Understandability of Use Case Models , 2001, ECOOP.

[44]  Forrest Shull Software Reading Techniques , 2002 .

[45]  Michael E. Fagan Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[46]  Akito Monden,et al.  Analyzing individual performance of source code review using reviewers' eye movement , 2006, ETRA.

[47]  Ari Jaaksi,et al.  Our Cases with Use Cases , 1998, J. Object Oriented Program..

[48]  Yann-Gaël Guéhéneuc,et al.  An empirical study on the efficiency of different design pattern representations in UML class diagrams , 2010, Empirical Software Engineering.

[49]  Claes Wohlin,et al.  An Experimental Comparison of Usage-Based and Checklist-Based Reading , 2003, IEEE Trans. Software Eng..

[50]  Yann-Gaël Guéhéneuc,et al.  An empirical study on the efficiency of graphical vs. textual representations in requirements comprehension , 2013, 2013 21st International Conference on Program Comprehension (ICPC).

[51]  Forrest Shull,et al.  Detecting defects in object-oriented designs: using reading techniques to increase software quality , 1999, OOPSLA '99.

[52]  Kurt Schneider,et al.  How Do We Read Specifications? Experiences from an Eye Tracking Study , 2016, REFSQ.

[53]  Yann-Gaël Guéhéneuc,et al.  An empirical study on requirements traceability using eye-tracking , 2012, 2012 28th IEEE International Conference on Software Maintenance (ICSM).

[54]  João Araújo,et al.  Identifying Aspectual Use Cases Using a Viewpoint-Oriented Requirements Method , 2003 .

[55]  Markku Tukiainen,et al.  An eye-tracking methodology for characterizing program comprehension processes , 2006, ETRA.

[56]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

[57]  Forrest Shull,et al.  The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.

[58]  Jörg Dörr,et al.  What you need is what you get!: The vision of view-based requirements specifications , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).