12/13/2022 0 Comments Taskboard architecture![]() However, only the most detailed linking variant causes readers to process related information simultaneously. None of the investigated linking variants impedes reading a use case and requirements. Only links embedded in the fields of a use case description significantly increase the readers' efforts to interrelate both artifacts. ![]() In all cases, reading the single artifacts one after the other is the most frequently occurring behavior. All investigated linking variants cause comparable visual effort. The results of the baseline experiment, its repetition, and their joint analysis are consistent. We conducted the study twice each with 15 subjects as a baseline experiment and as a repetition. We designed an eye tracking study about reading a use case and 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. Linking variants are intended to cause a specific reading behavior in which a reader interrelates a use case and its associated requirements. Regardless of the linking, a reader must process the related information simultaneously to understand them. 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.Ī wide variety of use case templates supports different variants to link a use case with its associated requirements. 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. Nevertheless, the different variants result in divergent reading behaviors. In all cases, the use case was read first and then the requirements. Our findings indicate that all investigated variants cause comparable visual effort and share the most frequent sequential reading pattern. 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. Besides considering both artifacts for themselves, a reader needs to interrelate them to achieve a high understanding of the overall content. The main purpose of all linking variants is to highlight the interrelationships between use cases and requirements. There are different variants to link a use case with its associated requirements due to a wide variety of use case templates. Their common notations are use cases and requirements which are related to each other. The descriptions of interactions and system functions are two of the most important artifact types in requirements specifications. ![]() ![]() In case of customization, a task board's structure should be adjusted since this is the only beneficial kind of customization, that additionally complies more precisely with the concept of fast and easy project overview. They may be better served by focusing on the original task board design and by applying only carefully selected adjustments. According to our findings, agile teams should rethink their current task board design. The original task board design is more beneficial than individual colored codings and changed card sizes. Our findings yield that only the customized task board design with modified structures reduces the required time. In an eye tracking study with 30 participants, we compared an original task board design with three customized ones to investigate which design shortened the required time to identify a particular story card. ![]() Hence, task board customization is in conflict with the agile practice of fast and easy overview for everyone. The increased effort impedes the work of both the team and team externals. Although the customizations are intended to improve the task board's usability and effectiveness, they may also complicate its comprehension and use. They modify the structure of boards, define colored codings for different purposes, and introduce different card sizes. Teams often customize their task boards according to the team members' needs. It provides a good overview of the project status. The task board is an essential artifact in many agile development approaches. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |