Transition from Process- to Product-Level Perspective for Business Software

Abstract

Abstract. When there are insufficient inputs for a product-level approach to requirements elicitation, a process-level perspective is an alternative way for achieving the intended base requirements. We define a V+V process approach that supports the creation of the intended requirements, beginning in a process-level perspective and evolving to a product-level perspective trough successive models derivation with the purpose of creating context for the implementation teams. The requirements are expressed through models, namely logical architectural models and stereotyped sequence diagrams. Those models alongside with the entire approach are validated using the architecture validation method ARID.

Delivering User Stories for Implementing Logical Software Architectures by Multiple Scrum Teams

“…However, implementation teams may experience difficulties in understanding key information from requirements artifacts, including the architecture (namely, understanding the "who", "what" and the "why"). Even when the system requirements are (semi-)automatically derived from user requirements, like the V+V process [3], the gathered information typically it is not yet ready to be consumed and passed on to the implementation teams. Within the V+V process, the requirements are expressed through logical architectural models and stereotyped sequence diagrams in both a process-and a product-level perspective.…”

“…In the V+V process [3], technological requirements comply with the organization's business requirements. The first execution of the V-Model acts in the analysis phase and regards a process-level perspective.…”

“…The first execution of the V-Model is out of the scope of this paper. The second V-Model (at product-level), is composed by Mashed UCs model [3], A-and B-type sequence diagrams [3], and Use Case models (UCs) that are used to derive (and, validate) a product-level logical architecture (i.e., the software logical architecture). The execution of this V-Model is presented in Fig.…”

A Demonstration Case on Steps and Rules for the Transition from Process-Level to Software Logical Architectures in Enterprise Models

“…The transition is part of an approach that expresses the project goals and allows creating context to implement a software system. The entire approach is detailed in [3] as a V + V process, based on the composition of two V-shaped process models (inspired in the "Vee" process model [4]). This way, we formalize the transition steps between perspectives that are required in order to align the requirements the V+V process presented in [3].…”

“…The entire approach is detailed in [3] as a V + V process, based on the composition of two V-shaped process models (inspired in the "Vee" process model [4]). This way, we formalize the transition steps between perspectives that are required in order to align the requirements the V+V process presented in [3]. The requirements are expressed through logical architectural models and stereotyped sequence diagrams [5] in both a process-and a product-level perspective.…”