Enabling the Reuse of Software Development Assets Through a Taxonomy for User Stories

Abstract

Context-Agile Software Development (ASD) and Reuse-Driven Software Engineering (RDSE) are wellaccepted strategies to improve the efficiency of software processes. A challenge to integrate both approaches is that ASD relies mostly on tacit knowledge, hampering the reuse of software development assets. An opportunity to enable RDSE for ASD is by improving the traceability between user stories (USs), the most used notation to register product requirements in ASD. Having enough link semantics between USs could enable defining similarity between them and, consequently, promote RDSE for ASD. However, this is an open challenge. Objective-To propose a taxonomy for adding link semantics between USs, focusing on easing the task of identifying similar ones. Such links, with support of traceability tools, enable the reuse of USs and their related assets. Method: We constructed a taxonomy for types of US focusing on Web Information Systems. The taxonomy is used to classify the US, given two facets: module and operation. Such information is used to infer the similarity between USs using link rules. We developed the taxonomy based on an empirical analysis of five product backlogs, containing a total of 118 USs. Afterward, we validated the taxonomy in terms of its potential to enable the reuse of US-related assets. First, we executed an offline validation by applying it to classify 530 USs from 26 already ended projects. Finally, we applied the taxonomy in a case study with two ongoing projects (59 USs). Results: The proposed taxonomy for USs is composed of two sub-facets, namely, module and operation, which have, respectively, three and 18 terms. In terms of coverage, for the offline study and case study, we classified 90.17% of the USs with the proposed taxonomy. For the case study, we classified all the USs analyzed. Conclusion: We concluded that it is possible to use our approach to compare USs and, consequently, retrieve their related assets. Our results regarding its practical utility have shown that users considered the taxonomy a useful approach to ease the process of assessing the similarity between user stories.

Ambiguity in user stories: A systematic literature review

“…Studies focusing on detecting ambiguity generally applied means of automatic interpretation of natural language requirements (e.g., [24,28,37,[39][40][41]) or the transformation of natural language requirements into models (e. g., [36,[42][43][44][45][46][47]). Studies that aimed to reduce ambiguity in natural language requirements proposed grammatical restrictions (e.g., [26,[48][49][50]), the standardization of sentence structures (e.g., [32,51,52]), and models or ontologies supporting requirements formulation (e.g., [53][54][55][56][57]).…”

“…Ambiguity can also lead to a user story being incomplete regarding the description of a feature that a user expects from a system. Several studies have mentioned neglected requirements [52,56], while team member turnover has been identified as a cause [26,78]. Insufficiency as a semantic ambiguity problem has been demonstrated by reviewing a user story in the context of previously written user stories [26,56,78].…”

“…Several studies have mentioned neglected requirements [52,56], while team member turnover has been identified as a cause [26,78]. Insufficiency as a semantic ambiguity problem has been demonstrated by reviewing a user story in the context of previously written user stories [26,56,78]. In [78], high turnover impacted the inability of development teams to relate clients' emails with specific user stories.…”

“…Despite empirical support for these benefits (e.g., [18,19,25,26]), several studies showed that user stories are prone to ambiguity [24,[26][27][28]. Based on these studies, we describe ambiguity as problems regarding the articulation of requirements as user stories, which cause doubtful, imprecise, and multiple interpretations of these requirements.…”

Simulated Software Testing Process and Its Optimization Considering Heterogeneous Debuggers and Release Time

“…Since the computer era, software has been playing an essentially important role in many complex, sophisticated and safety-critical systems of a variety of significant and multifaceted areas, such as air traffic analysis and control, nuclear reactor testing and management, military and defense services, etc. [1][2][3][4][5][6][7]. The failure of software may lead to significant losses.…”