Abstract

A wide variety of use case templates supports different variants to link a use case with its associated requirements. Regardless of the linking, a reader must process the related information simultaneously to understand them.Linking variants are intended to cause a specific reading behavior in which a reader interrelates a use case and its associated requirements. Due to the effort to create and maintain links, we investigated the impact of different linking variants on the reading behavior in terms of visual effort and the intended way of interrelating both artifacts.We designed an eye tracking study about reading a use case and requirements. We conducted the study twice each with 15 subjects as a baseline experiment and as a repetition. The results of the baseline experiment, its repetition, and their joint analysis are consistent. All investigated linking variants cause comparable visual effort. In all cases, reading the single artifacts one after the other is the most frequently occurring behavior. Only links embedded in the fields of a use case description significantly increase the readers’ efforts to interrelate both artifacts. None of the investigated linking variants impedes reading a use case and requirements. However, only the most detailed linking variant causes readers to process related information simultaneously.

Highlights

  • Linking Use CasesRequirements specifications contain several artifact types such as descriptions of interactions or system functions

  • Despite the benefit of objective measures, we had to determine the scan­paths manually over both artifacts due to a technical constraint of the used eye tracking system

  • We coun­ teracted this threat to validity by including in the manually created scan­paths only the areas of interest (AOIs) visits that were captured by the eye tracking system

Read more

Summary

Introduction

Requirements specifications contain several artifact types such as descriptions of interactions or system functions. Common notations to represent in­ teractions and functionalities are fully dressed use cases and natural language requirements (Fricker et al, 2015). Anda et al (2001) compared the use of differ­ ent guidelines for writing use cases, including use case tem­ plates. Use cases are widely accepted and acknowledged for specify­ ing interactions and functionalities (Tiwari and Gupta, 2015). Tiwari and Gupta (2015) conducted a systematic literature re­ view to examine the evolution of the use cases, i.a., regarding their representation. We present a brief summary of the evolution of these use case templates and their linking vari­ ants for associated requirements

Methods
Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.