• Aucun résultat trouvé

A Classification of Collaborative Model-Driven Software Engineering Approaches: Opportunities and Challenges

N/A
N/A
Protected

Academic year: 2022

Partager "A Classification of Collaborative Model-Driven Software Engineering Approaches: Opportunities and Challenges"

Copied!
1
0
0

Texte intégral

(1)

A Classification of Collaborative Model-Driven Software Engineering Approaches: Opportunities and Challenges

Davide Di Ruscio and Mirco Franzago

Department of Information Engineering, Computer Science and Mathematics (DISIM) University of L’Aquila, Italy

{

davide.diruscio

|

mirco.franzago

}

@univaq.it

ABSTRACT

Collaborative software engineering (CoSE) deals with meth- ods, processes and tools for enhancing collaboration, com- munication, and co-ordination (3C) among team members [3]. CoSE can be employed to conceive different kinds of artifacts during the development and evolution of software systems. For instance, when focusing on software design, multiple stakeholders with different expertise and responsi- bility collaborate on the system design.

Model-Driven Software Engineering (MDSE) provides suit- able techniques and tools for specifying, manipulating, and analyzing modeling artifacts including metamodels, models, and transformations [1]. A collaborative MDSE approach can be defined as a method or technique allowing multiple stakeholders to work on a set of shared modeling artifacts, and to be aware of each others’ work. Even though Collabo- rative MDSE is gaining a growing interest in both academia and practice, a holistic view on what Collaborative MDSE is, its components, the related opportunities and challenges is still missing.

Figure 1: Collaborative MDSE dimensions In this talk, we outline the main insights of the system- atic mapping study [4] we have done to identify and classify approaches, methods, and techniques that support collab- orative MDSE (for the complete protocol of the mapping, see [2]). We present three complementary dimensions that we have identified during the study as the peculiar aspects building up a collaborative MDSE (Figure 1): amodel man- agement infrastructure for managing the life cycle of the models, a set ofcollaboration means for allowing involved stakeholders to work on the modelling artifacts collabora- tively, and a set of communication means for allowing in- volved stakeholders to be aware of the activities of the other stakeholders. The identification of limitations and chal- lenges of currently available collaborative MDE approaches is also given by discussing the implications for future inves- tigation.

Biographies of the authors

Davide Di Ruscio is Assistant Professor at the Depart- ment of Information Engineering and Computer Science and Mathematics of the University of L’Aquila. His main re- search interests are related to several aspects of Model Driven Engineering (MDE) including domain specific modelling lan- guages, model transformation, model differencing, model evolution, and coupled evolution. He has published more than 80 papers in various journals, conferences and work- shops on such topics. He has been in the PC and involved in the organization of several workshops and conferences, and reviewer of many journals like IEEE Transactions on Software Engineering, Science of Computer Programming, Software and Systems Modeling, and Journal of Systems and Software.

Mirco Franzago is a PhD student in Information and Communication Technologies (Software Engineering and In- telligent Systems curriculum) at the Department of Infor- mation Engineering, Computer Science and Mathematics (DISIM) - University of L’Aquila, Italy. His research fo- cuses on collaborative software engineering, model-driven engineering and mobile enabled systems, especially on how MDE techniques can be exploited to support stakeholders’

collaboration during the design and development of complex and mobile-enabled software systems. He is program com- mittee member and reviewer for international conferences and workshops in his fields of interest.

References

[1] M. Brambilla, J. Cabot, and M. Wimmer. Model-driven software engineering in practice. Synthesis Lectures on Software Engineering, pages 1–182, 2012.

[2] M. Franzago, D. Di Ruscio, I. Malavolta, and H. Muccini.

Protocol for a Systematic Mapping Study on Collabora- tive Model-Driven Software Engineering. Technical Re- port TR-001-2016, DISIM - University of L’Aquila, 2016.

URL http://tinyurl.com/glv7bg5, accessed September 2016.

[3] I. Mistr´ık, J. Grundy, A. Van der Hoek, and J. White- head. Collaborative software engineering: Challenges and prospects. In Collaborative Software Engineering, pages 389–403. Springer, 2010.

[4] K. Petersen, S. Vakkalanka, and L. Kuzniarz. Guide- lines for conducting systematic mapping studies in soft- ware engineering: An update.Information and Software Technology, pages 1–18, 2015.

Références

Documents relatifs

The pre-property of languages used in the educational process is the visibility of the graphical representation of architecture, open documentation, support in var- ious

This paper presents the research design for a Scholarship of Learning and Teaching project that aims to explore how the collaborative learning strategies can impact student

The Russian scientific specialty closest to the foreign Software specialty on which PhD theses are defended is specialty 05.13.11 – Mathematical Support and Software of

Heterogeneous Models, Domain-Specific Languages, Compo- sition of Languages, Task migratability, Industry 4.0, Business- Process Modeling.. ACM

I believe that model and component based engineering will play a key role in the engineering methodologies of tomorrow and will discuss how to deal with existing (known)

At the first stage of this study a written survey was conducted of a group of PhD students of eleven universities currently involved in the doctoral programs in Software

Unlike most experience reports, we have dealt with two small software companies: Sinergia with around 100 employees, with which we carried out a modern- ization project, and

To make UML4SPM process models executable, the semantics of the metamodel is implemented in terms of operations and instructions using Kermeta.. This implementation is then woven