5th Bellairs Modelling Workshop The 5th Modelling Workshop at the Bellairs Research Institute of McGill will take place from Friday February 8th 2013 to Friday February 15th 2013. This year’s workshop theme is concern-driven modelling and concern-driven software development. A concern encapsulates a set of models at potentially different phases of software development that pertain to some point of interest of a developer or stakeholder. A concern has a root phase, i.e., it starts to be relevant at a certain point during software development. For example, some concerns appear at the requirements phase, e.g. security, since they are of relevance to external stakeholders. Other concerns, for instance database integration, appear during the architecture or design phase. For the root phase and all subsequent phases, models are built that express the properties of the concern that are relevant during that phase using the most appropriate formalism. Concern models should also include all relevant variations/choices that are available to developers, if any, together with guidance on how to choose among those variations when moving from one phase to the next. Finally, a concern should also define the model transformations that link the models established for the concern at different levels of abstraction. We therefore want to attract participants that are in some way interested in concern-driven software development. This includes participants that: Work with specific model-driven engineering approaches Want to understand the properties of modelling notations and approaches, and how they relate to each other Work with software product lines Apply separation of concern principles to develop well-modularized software artifacts (models / code) Are experts for specific concerns (e.g. security, reliability, performance, ...) We are planning to invite a group of ~25 researchers (composed of senior and junior faculty, postdocs and students) whose expertise covers the areas mentioned above. Within the 5 days of the workshop, we will investigate how compositional view-based modelling techniques and approaches can be combined to support identification, separation and composition of concerns throughout the software development process. The concrete models used as a basis for our discussions are models of the bCMS case study, a case study specifically designed for the activities that will take place in this workshop. Planned Workshop Activities The workshop schedule is not set in stone yet, i.e. the activities that are going to take place depend on the expectations and motivation of the participants. The following are the specific activities that are so far planned for the workshop: 1. First time attendees of the workshop are expected to read the bCMS case study requirements document before the workshop, and they (or members of their research team) prepare some models (or even code) for the bCMS using their technique or approach. Early in the week of the workshop, the participants will present the models, and the technique / approach will be discussed, and evaluated against comparison criteria that were developed during last year’s Bellairs workshop and refined based on the CMA workshops (Comparing Modelling Approaches) at MODELS 2012. 2. Discussion and analysis of bCMS models. Teams will work on comparing the models of the bCMS (and therefore also the modeling approaches used by the participants represented at the workshop), focussing in particular on identifying the mechanisms to separate concerns. 3. Teams will attempt to integrate development approaches by developing a set of end-to-end models for the bCMS. This exercise will help us develop a deeper understanding of how different view-based modeling techniques can be integrated to address development concerns across the lifecycle, as well as how concern relationships evolve throughout the development phases. 4. Discussion of the comparison criteria themselves. We would like to get feedback on the criteria in order to improve them for future comparisons. 5. Evaluation of the Repository for Model-Driven Development, short ReMoDD, with a particular focus on ReMoDDs group work facilities. The models developed at the workshop will be entered into ReMoDD by attendees, as well as documents that need to be shared among attendees to support the discussions and collaborative work. There will be a session in which we discuss how ReMoDD can be improved to support group collaborations. Use the navigation menu above to get more information on Bellairs and on the current list of participants. You can also look at the 2012, 2011, 2010 and 2009 editions of the Bellairs AOM workshop. Last modified: November 23, 2015, Jörg Kienzle

5th Bellairs Modelling Workshop

The 5th Modelling Workshop at the Bellairs Research Institute of McGill will take place from Friday February 8th 2013 to Friday February 15th 2013. This year’s workshop theme is concern-driven modelling and concern-driven software development.

A concern encapsulates a set of models at potentially different phases of software development that pertain to some point of interest of a developer or stakeholder. A concern has a root phase, i.e., it starts to be relevant at a certain point during software development. For example, some concerns appear at the requirements phase, e.g. security, since they are of relevance to external stakeholders. Other concerns, for instance database integration, appear during the architecture or design phase. For the root phase and all subsequent phases, models are built that express the properties of the concern that are relevant during that phase using the most appropriate formalism. Concern models should also include all relevant variations/choices that are available to developers, if any, together with guidance on how to choose among those variations when moving from one phase to the next. Finally, a concern should also define the model transformations that link the models established for the concern at different levels of abstraction.

We therefore want to attract participants that are in some way interested in concern-driven software development. This includes participants that:

•Work with specific model-driven engineering approaches
•Want to understand the properties of modelling notations and approaches, and how they relate to each other
•Work with software product lines
•Apply separation of concern principles to develop well-modularized software artifacts (models / code)
•Are experts for specific concerns (e.g. security, reliability, performance, ...)

We are planning to invite a group of ~25 researchers (composed of senior and junior faculty, postdocs and students) whose expertise covers the areas mentioned above. Within the 5 days of the workshop, we will investigate how compositional view-based modelling techniques and approaches can be combined to support identification, separation and composition of concerns throughout the software development process. The concrete models used as a basis for our discussions are models of the bCMS case study, a case study specifically designed for the activities that will take place in this workshop.

Planned Workshop Activities

The workshop schedule is not set in stone yet, i.e. the activities that are going to take place depend on the expectations and motivation of the participants. The following are the specific activities that are so far planned for the workshop:

1. First time attendees of the workshop are expected to read the bCMS case study requirements document before the workshop, and they (or members of their research team) prepare some models (or even code) for the bCMS using their technique or approach. Early in the week of the workshop, the participants will present the models, and the technique / approach will be discussed, and evaluated against comparison criteria that were developed during last year’s Bellairs workshop and refined based on the CMA workshops (Comparing Modelling Approaches) at MODELS 2012.

2. Discussion and analysis of bCMS models. Teams will work on comparing the models of the bCMS (and therefore also the modeling approaches used by the participants represented at the workshop), focussing in particular on identifying the mechanisms to separate concerns.

3. Teams will attempt to integrate development approaches by developing a set of end-to-end models for the bCMS. This exercise will help us develop a deeper understanding of how different view-based modeling techniques can be integrated to address development concerns across the lifecycle, as well as how concern relationships evolve throughout the development phases.

4. Discussion of the comparison criteria themselves. We would like to get feedback on the criteria in order to improve them for future comparisons.

5. Evaluation of the Repository for Model-Driven Development, short ReMoDD, with a particular focus on ReMoDDs group work facilities. The models developed at the workshop will be entered into ReMoDD by attendees, as well as documents that need to be shared among attendees to support the discussions and collaborative work. There will be a session in which we discuss how ReMoDD can be improved to support group collaborations.

Use the navigation menu above to get more information on Bellairs and on the current list of participants. You can also look at the 2012, 2011, 2010 and 2009 editions of the Bellairs AOM workshop.

Last modified: November 23, 2015, Jörg Kienzle