Home      Log In      Contacts      FAQs      INSTICC Portal


A panel is basically a one and a half hour to 2 hours session in which four to six speakers - distinguished members of the scientific and/or enterprise community, briefly present different perspectives/opinions on key issues with the goal of stimulating a lively, controversial, and provocative discussion. Panelists are expected to actively debate one another and engage the audience to help broaden understanding of the technologies and issues. Two types of panels are to be considered: Research Panels, oriented to the academic community and focused on the discussion of research topics; and Industrial Panels, oriented to promote knowledge exchanges between academia and industry.

Panel proposals are accepted until:

January 10, 2019

If you wish to propose a new Panel please kindly fill out and submit this Expression of Interest form.

Plenary Panel Session

Plenary Panel Session

Date: Monday 22nd, 2018
Time: 09:15 -10:30
Immediately After Opening Session

The Different Roles Models Can Play in Software Development and Their Pros and Cons

Chair and Moderator:
Bran Selic,Malina Software Corp., Canada

Franck Barbier, University of Pau, France
David Harel, The Weizmann Institute of Science, Israel
Bernhard Rumpe, RWTH Aachen University, Germany

We are bombarded with buzzwords such as “model-driven development”, “model-driven architecture”, “model-based engineering” etc., to the point where one might think that the models themselves (rather than corresponding actual systems) are the sought-for end result. Because they are not well defined, these terms are open to much misinterpretation and confusion (e.g., why “model-driven architecture” when there is no architecture in that standardization initiative?). For example, to many in the software community "model-driven development" reduces to automatic code generation from UML or similar “modeling” language), something which, by the way, naturally arouses hostility among those who feel that their ability to write program code is key to their employability. However, as in any engineering discipline, models have the potential to serve numerous useful functions in the process of design and development.

In this panel, we will attempt to identify all the varied purposes that models can and do serve in the software lifecycle as well as the advantages that such usages can bring. However, to play the devil’s advocate, based on the dictum that rarely is something gained without something being lost, we also want to understand the theoretical and practical drawbacks (if any) associated with the use of models in software. Moreover, we also want to examine the practical impediments that stand in the way of full exploitation of models in the software domain and what can be done to mitigate them. If this stuff is so good, why isn’t everyone doing it?