Explicit Alignment of Requirements and Architecture in Agile Development

Abstract

Context & Motivation]Requirements and architectural components are designed concurrently, with the former guiding the latter, and the latter restricting the former. [Question/problem] Effective communication between requirements engineers and software architects is often experienced as problematic. [Principal ideas/results] We present the Requirements Engineering for Software Architecture (RE4SA) model with the intention to support the communication within the development team. In RE4SA, requirements are expressed as epic stories and user stories, which are linked to modules and features, respectively, as their architectural counterparts. Additionally, we provide metrics to measure the alignment between these concepts, and we also discuss how to use the model and the usefulness of the metrics by applying both to case studies. [Contribution] The RE4SA model employs widely adopted notations and allows for explicitly relating a system's requirements and architectural components, while the metrics make it possible to measure the alignment between requirements and architecture.

Seamless transformation from use case to sequence diagrams

“…Jyothi & Rao (2011) proposed various tracing strategies for extreme programming ( Lindstrom & Jeffries, 2004 ) and scrum methodologies ( Permana, 2015 ), some of which involve requirements. Agile methodologies place great importance on the model development process, while traceability and alignment are critical for developing more productive system models ( Molenaar et al, 2020 ). Additionally, seamless alignment concepts are relevant for model transformation within the agile development process ( Jyothi & Rao, 2011 ; Marlowe & Kirova, 2008 ).…”

“…Furthermore, Yue, Briand & Labiche (2010) focuses on developing traceability connections between the system requirements and the created diagrams. Traceability is important in software development because it helps engineers comprehend the connections between different software system artifacts ( Molenaar et al, 2020 ). A technique suggested in Khan & Mahmood (2016) to facilitate and streamline the transition from need to artifact design.…”

Enhancing and Consolidating Requirements Specification in Teaching System Design by Aligning Concepts From Heterogeneous Diagrams

“…Some of the tracing practices proposed involve requirements. Models development plays a critical role in agile methodologies, whereas traceability and alignment are important in improving the way of developing the system model effectively [17]. Effective alignment is relevant for model transformation within agile development methodologies [12], [18].…”

“…[27] focuses on creating traceability links from system requirements to the generated diagrams. Traceability is essential in software development since it helps engineers understand the relationships between different artifacts for the software system [17]. The study proposed [28] proposes a technique to facilitate the seamless transition from requirements to artifact design.…”