Verifying goal-oriented specifications used in model-driven development processes

Abstract

Goal-oriented requirements engineering promotes the use of goals to elicit, elaborate, structure, specify, analyze, negotiate, document, and modify requirements. Thus, goal-oriented specifications are essential for capturing the objectives that the system to be developed should achieve. However, the application of goaloriented specifications into model-driven development (MDD) processes is still handcrafted, not aligned in the automated flow from models to code. In other words, the experience of analysts and designers is necessary to\ud manually transform the input goal-oriented models into system models for code generation (models compilation). Some authors have proposed guidelines to facilitate and partially automate this translation, but there is a lack of techniques to assess the adequacy of goal-oriented models as starting point of MDD processes. In this paper, we present and evaluate a verification approach that guarantees the automatic, correct, and complete transformation of goal-oriented models into design models used by specific MDD solutions. In particular, this approach has been put into practice by adopting a well-known goal-oriented modeling approach, the i* framework, and an industrial MDD solution called Integranova.Peer ReviewedPostprint (author's final draft

An empirical study on the use of i* by non-technical stakeholders: the case of strategic dependency diagrams

“…Although this will produce several hand-drawn CMs with odd notations, e.g., the ones presented in Figure 4, this will help them to focus in more relevant issues, such as the identification of intentional elements. It is important to remark as supporting argument that these models are not supposed to be used afterwards (e.g., as starting point in a model-driven process, in which case some properties would be required [23]). It is also important to keep in mind, as mentioned in the introduction, that the final aim is not to train non-technical stakeholders in the use of specialized tools, but to empower them to more proactively participate in early phases of requirements modelling activities.…”

Estado de las investigaciones sobre la optimización en el proceso de producción de software

“…López, Giovanni Gianichetti, Beatriz Marin, Eberhard Abele y Alain Abran con sus trabajos: The OOmethod approach for information systems modeling: from object-oriented conceptual modeling to automated programming (Pastor, Gómez et al 2001) y Verifying goal-oriented specifications used in model-driven development processes (Giachetti, Marín et al 2017). Estos contribuyen en varios trabajos en conjunto, que siguen con la línea del tema de investigación.…”

Theme section on model-driven requirements engineering

“…For instance, a model can be used to generate other models by means of automatic model transformations, thus ensuring consistency and speeding up repetitive tasks of system's development [7]. Using model management languages, models can be inspected and analyzed to ensure different non-functional requirements [8][9][10][11], such as security and/or gender equality. In other cases, models are used for simulation purposes or to govern the execution of a system at runtime [12].…”