Automated Reuse of Model Transformations through Typing Requirements Models

Juan De Lara; Esther Guerra; Davide Di Ruscio; Juri Di Rocco; Jesús S´nchez Cuadrado; Ludovico Iovino; Alfonso Pierantonio

doi:10.1145/3340108

An Ontology-Based and Model-Driven Approach for Designing IT Service Management Systems

International Journal of Service Science Management Engineering and Technology ◽

10.4018/jssmet.2011040104 ◽

2011 ◽

Vol 2 (2) ◽

pp. 65-81 ◽

Cited By ~ 4

Author(s):

María-Cruz Valiente ◽

Cristina Vicente-Chicote ◽

Daniel Rodríguez

Keyword(s):

Domain Knowledge ◽

Service Management ◽

Management Systems ◽

Model Transformations ◽

Software Systems ◽

Incident Management ◽

Model Driven ◽

Technology Service ◽

High Level ◽

Requirements Models

Currently, few projects applying a Model-Driven Engineering (MDE) approach start from high-level requirements models defined exclusively in terms of domain knowledge and business logic. Ontology Engineering (OE) aims to formalize and make explicit the knowledge related to a particular domain. In this vein, this paper presents a modeling approach, formalized in ontological terms, for defining high-level requirements models of software systems that provide support for the implementation of Information Technology Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.

Download Full-text

Reusing Model Transformations Through Typing Requirements Models

Fundamental Approaches to Software Engineering - Lecture Notes in Computer Science ◽

10.1007/978-3-662-54494-5_15 ◽

2017 ◽

pp. 264-282 ◽

Cited By ~ 9

Author(s):

Juan de Lara ◽

Juri Di Rocco ◽

Davide Di Ruscio ◽

Esther Guerra ◽

Ludovico Iovino ◽

...

Keyword(s):

Model Transformations ◽

Requirements Models

Download Full-text

An Ontology-Based and Model-Driven Approach for Designing IT Service Management Systems

Best Practices and New Perspectives in Service Science and Management ◽

10.4018/978-1-4666-3894-5.ch008 ◽

2013 ◽

pp. 142-159

Author(s):

María-Cruz Valiente ◽

Cristina Vicente-Chicote ◽

Daniel Rodríguez

Keyword(s):

Domain Knowledge ◽

Service Management ◽

Management Systems ◽

Model Transformations ◽

Software Systems ◽

Incident Management ◽

Model Driven ◽

Technology Service ◽

High Level ◽

Requirements Models

Currently, few projects applying a Model-Driven Engineering (MDE) approach start from high-level requirements models defined exclusively in terms of domain knowledge and business logic. Ontology Engineering (OE) aims to formalize and make explicit the knowledge related to a particular domain. In this vein, this paper presents a modeling approach, formalized in ontological terms, for defining high-level requirements models of software systems that provide support for the implementation of Information Technology Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.

Download Full-text

Model-Driven Requirements Specification for Software Product Lines

Model-Driven Domain Analysis and Software Development ◽

10.4018/978-1-61692-874-2.ch017 ◽

2011 ◽

pp. 369-386

Author(s):

Mauricio Alférez ◽

Ana Moreira ◽

Vasco Amaral ◽

João Araújo

Keyword(s):

Software Product Lines ◽

Product Line ◽

Requirements Specification ◽

Model Transformations ◽

Case Scenario ◽

Product Lines ◽

Model Driven ◽

Variability Modeling ◽

Software Product ◽

Requirements Models

Model-driven methods for requirements specification in Software Product Lines (SPLs) support the construction of different models to provide a better understanding of each SPL feature and intended use scenarios. However, the different models must be composed to show the requirements of the target applications and, therefore, help to understand how features will be integrated in a new product of a software product line. Although well-established standards for creating metamodels and model transformations exist, there is currently no established foundation that allows practitioners to distinguish between the different modeling and composition approaches for requirements models. This chapter provides an overview of different approaches for specifying requirements models and composing models for specific products of an SPL. In particular, it emphasizes one of the most recurring specification techniques: model-driven and use case scenario-based specification. This technique, in combination with feature models and the Variability Modeling Language for Requirements (VML4RE), integrates our approach for model-driven requirements specification for SPLs.

Download Full-text