|
|
| (198 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| | <div style="line-height:2.0em;"> | | <div style="line-height:2.0em;"> |
| - | <div align="center" style="font-size: 200%;">Workshop on Modeling in Software Engineering @ ICSE 2013 [http://2013.icse-conferences.org/ ]</div> | + | <div align="center" style="font-size: 200%;">10th Workshop on Modelling in Software Engineering (MiSE’2018)</div> |
| - | <div align="center" style="font-size: 200%;">(MiSE 2013)</div>
| + | <div align="center" style="font-size: 200%">hosted by [https://www.icse2018.org/ ICSE 2018]</div> |
| - | <div align="center" style="font-size: 200%;">San Francisco, CA</div> | + | <div align="center" style="font-size: 200%;">Gothenberg, Sweden, May 2018 </div> |
| - | <div align="center" style="font-size: 200%;">May 18th - 19th, 2013 </div> | + | |
| | | | |
| - | == Workshop Overview ==
| |
| | | | |
| - | The purpose of this 2-day workshop is to study and advance the effective use of models in the engineering of software systems. In particular, we are interested in the exchange of experiences and innovative technical ideas related to modeling. Engineers have used models to manage complexity for centuries, and there is a growing body of work on the use of models to manage inherent problem and solution complexity in software development. The use of software models will become more prevalent as methodologies and tools that manipulate them at various levels of abstraction become available. A secondary goal of the workshop is to further promote cross-fertilization between the modeling communities (e.g., MODELS) and software-engineering communities.
| + | == Theme and Goals == |
| | | | |
| - | We take a broad view of what models are and how they are used, including
| + | The purpose of this 2-day workshop is to promote the ''use of models in the engineering of software systems''. In particular, we are interested in the ''exchange of innovative technical ideas and experiences'' related to modeling. Engineers have used models to effectively manage complexity for centuries, and there is a growing body of work on the use of models to manage inherent problem and solution complexity in software development. The use of software models will become more prevalent as methodologies and tools that manipulate models at various levels of abstraction become available. |
| | | | |
| - | * <B>Exploration</B>: Models are used to explore and learn about the problem to be solved, where the “problem” can be, for example, requirements identification, system specification, system or component design, complex protocol or algorithm design.
| + | Workshop activities will focus on analyzing successful applications of software-modeling techniques to gain insights into challenging modeling problems, including: (1) identifying, describing, and using appropriate abstractions, (2) supporting incremental, iterative development through the use of appropriate model composition, transformation and other model manipulation operators, and (3) automated analysis of possibly large, possibly incomplete models to determine the presence or absence of desired and undesired properties. |
| - | * <B>Communication</B>: Communication models are used to document software decisions (e.g., requirements, designs, and deployment decisions). Support for downstream activities: We use software models to answer questions or check properties (e.g., correctness, fitness for use) of the modeled artifact, to generate other artifacts, or to configure existing systems.
| + | |
| - | * <B>Support for downstream activities</B>: We use software models to answer questions or check properties (e.g., correctness, fitness for use) of the modeled artifact, to generate other artifacts, or to configure existing systems.
| + | |
| - | * <B>Configurability and adaptation</B>: We use models at runtime to configure the system, to adapt it to changed needs of the users. A model of the environment also allows a system to capture its knowledge about the environment it controls or communicates with.
| + | |
| | | | |
| - | Workshop activities will focus on analyzing successful and unsuccessful applications of software modeling techniques to gain insights into challenging modeling problems, including: (1) identifying, describing, and using appropriate abstractions, (2) supporting incremental, iterative development through the use of appropriate model composition, transformation and other model manipulation operators, and (3) automated analysis of possibly large and possibly incomplete models to determine the presence or absence of desired and undesired properties.
| + | === Topics === |
| | | | |
| - | ==Topics of interest include==
| + | Topics of interest include: |
| | + | * Modeling notations and tools |
| | + | * Metamodeling |
| | + | * Abstractions and modeling methodologies |
| | + | * Model-based analysis and synthesis |
| | + | * Model transformation and composition |
| | + | * Model evaluation |
| | + | * Model management |
| | + | * Extracting models from software artifacts |
| | + | * Models for learning machines |
| | + | * Models of big and smart data |
| | + | * Use of models for downstream activities |
| | + | * Modeling the system environment |
| | + | * Modeling cyber-physical systems |
| | + | * Models at runtime (e.g., for software adaptation) |
| | + | * Models for ''what-if?'' analysis and prognostics |
| | + | * Empirical studies |
| | + | * Domain-specific modeling |
| | + | * management using models |
| | + | * Model reuse |
| | + | * Further uses of modeling |
| | | | |
| - | * Modeling notations and tools
| + | == Program == |
| - | * Metamodeling
| + | |
| - | * Abstractions and modeling methodologies
| + | |
| - | * Model-based analysis and synthesis
| + | |
| - | * Model transformation and composition
| + | |
| - | * Model evaluation
| + | |
| - | * Model management
| + | |
| - | * Extracting models from software artifacts (e.g., program understanding)
| + | |
| - | * Use of models for downstream activities (e.g., generating test cases, using models at runtime)
| + | |
| - | * Modeling the systems environment
| + | |
| - | * Models at runtime (e.g. for software adaptation)
| + | |
| - | * Empirical studies
| + | |
| - | * Domain-specific modeling
| + | |
| - | * Variability management using models
| + | |
| - | * Model reuse
| + | |
| - | * Other uses of modeling
| + | |
| | | | |
| | + | tba |
| | | | |
| | + | == Organizing Committee (for 2018) == |
| | | | |
| - | | + | * Richard Paige, University of York (UK) |
| - | | + | * Jennifer Horkoff, Chalmers and the University of Gothenberg (Sweden) |
| - | == Workshop Program ==
| + | * Sahar Kokaly, McMaster University (Canada) |
| - | | + | * Jocelyn Simmonds, University of Chile (Chile) |
| - | Below is the advance program. Details about keynotes and the panel are coming soon!!
| + | |
| - | | + | |
| - | <b> Saturday May 18 </b>
| + | |
| - | | + | |
| - | <b> 8:30 Session #1: Introduction and Keynote </b><br>
| + | |
| - | Session Chair: Joanne Atlee
| + | |
| - | | + | |
| - | * <b> Why We Model: Using MBD Effectively in Critical Domains</b><br> Michael Whalen, University of Minnesota, USA <br><br> <i>Model-Based Development (MBD) is a paradigm in which software and systems development are focused on high-level executable models of the system to be fielded. These models allow a wide range of exploration and analysis including high-fidelity simulation, test-case generation, and even proofs to be performed at low cost early in development cycles. MBD is seeing widespread adoption in a variety of domains, especially in critical systems such as aerospace and medical devices. In this talk, I describe how to use model-based development effectively in the development of critical software, using examples from the aerospace domain. I focus on V&V of models, as this is an important cost driver for critical systems, and discuss benefits of using automated verification techniques for both unit testing to "unit proving". I also describe several possible pitfalls that can occur when adopting model-based development at scale and steps to take to avoid them.</i> | + | |
| - | | + | |
| - | <br>
| + | |
| - | <b> 10:30 Session #2: Model Representation</b><br>
| + | |
| - | Session Chair: Jeff Gray
| + | |
| - | *<b> Issues in Representing Domain-Specific Concerns in Model-Driven Engineering </b><br> Lionel Montrieux, Yijun Yu, Michel Wermelinger and Zhenjiang Hu | + | |
| - | *<b> MAV-Vis: a Notation for Model Uncertainty </b><br> Michalis Famelis and Stephanie Santosa
| + | |
| - | *<b> Modes, Features, and State-Based Modeling for Clarity and Flexibility </b><br> Anitha Murugesan, Sanjai Rayadurgam and Mats Heimdahl
| + | |
| - | | + | |
| - | <br>
| + | |
| - | <b> 1:30 Session #3: Applications of Modeling </b> <br>
| + | |
| - | Session Chair: Robert Baillargeon <br>
| + | |
| - | | + | |
| - | *<b> Model Based Control for Multi-Cloud Applications </b><br> Marco Miglierina, Giovanni Paolo Gibilisco, Danilo Ardagna and Elisabetta Di Nitto
| + | |
| - | *<b> Design Module: A Modularity Vision Beyond Code (Not Only Program Code But Also a Design Model Is a Module) </b><br> Naoyasu Ubayashi and Yasutaka Kamei
| + | |
| - | *<b> Highlighting the Challenges of Model-Based Engineering for Spaceflight Software Systems </b><br> Robert Pettit and Navneet Mezcciani
| + | |
| - | | + | |
| - | <br>
| + | |
| - | <b> 3:30 Session #4: Poster Session </b>
| + | |
| - | | + | |
| - | | + | |
| - | <b> Sunday May 19 </b>
| + | |
| - | | + | |
| - | <b> 8:30 Session #5: Keynote </b><br>
| + | |
| - | Session Chair: Richard Paige
| + | |
| - | * Lionel Briand, University of Luxembourg, Luxembourg
| + | |
| - | | + | |
| - | <br>
| + | |
| - | <b> 10:30 Session #6: Model Analysis and Development Support </b><br>
| + | |
| - | Session Chair: Marsha Chechik
| + | |
| - | *<b> Light-weight Analysis of Software Design Models at the Whiteboard</b><br> Alfredo Motta, Nicolas Mangano and André van der Hoek
| + | |
| - | *<b> Complementing Model-Driven Development for the Detection of Software Architecture Erosion </b><br> Sebastian Herold and Andreas Rausch
| + | |
| - | *<b> Enhancing Version Control with Domain-Specific Semantics </b><br> Matthieu Foucault, Sébastien Barbier and David Lugato
| + | |
| - | | + | |
| - | <br><b> 1:30 Session #7: Runtime models </b><br>
| + | |
| - | Session Chair: Bernhard Rumpe
| + | |
| - | *<b> A UML Profile for Dynamic Execution Persistence with Monitoring Purposes </b><br> Eladio Domínguez Murillo, Beatriz Pérez and María A. Zapata
| + | |
| - | *<b> Requirements Models for Design- and Runtime: a Position Paper </b><br> Alexander Borgida, Fabiano Dalpiaz, Jennifer Horkoff and John Mylopoulos
| + | |
| - | | + | |
| - | <b> 2:30 Session #7b: Short Papers </b><br>
| + | |
| - | Session Chair: Bernhard Rumpe
| + | |
| - | *<b> Model Oriented Programming: Bridging the Code-Model Divide </b> <br> Omar Badreddin and Timothy C. Lethbridge
| + | |
| - | *<b> A Model-Based Approach to Language Integration </b><br> Federico Tomassetti, Antonio Vetro', Marco Torchiano, Markus Voelter and Bernd Kolb
| + | |
| - | *<b> Prioritizing Software Anomalies with Software Metrics and Architecture Blueprints: A Controlled Experiment </b><br> Everton Guimaraes, Alessandro Garcia, Eduardo Figueiredo and Yuanfang Cai
| + | |
| - | | + | |
| - | <br>
| + | |
| - | <b> 3:30 Session #8: Panel (TBA) </b><br>
| + | |
| - | Session Chair: Robert France
| + | |
| - | | + | |
| - | == Important Dates ==
| + | |
| - | | + | |
| - | {| border=1
| + | |
| - | |March 7, 2013 || Camera-ready papers due
| + | |
| - | |-
| + | |
| - | |May 18th - 19th, 2013 || Workshop takes place @ ICSE
| + | |
| - | |}
| + | |
| - | | + | |
| - | == Workshop Format ==
| + | |
| - | | + | |
| - | The workshop will be highly interactive and focused on the sharing of ideas and on progressing towards a shared vision of research goals. Included in the program will be paper presentations, open discussions, at least one panel discussion, posters, and a keynote talk. Paper presentations will be grouped into sessions of three 20-minute presentations, with 30 minutes of discussion at the end of each session. Our goal is not to create a mini-conference and all attendees will also have an opportunity to discuss topics emerging from the collective presentations.
| + | |
| - | | + | |
| - | == Submission Guidelines ==
| + | |
| - |
| + | |
| - | Prospective participants are invited to submit a 4-6 page position or technical paper. Workshop papers must follow the ICSE 2013 Format and Submission Guideline. All submissions will be reviewed by members of the program committee and the organizing committee for quality and relevance. Accepted papers will become part of the workshop proceedings and will be entered into the ACM and IEEE Digital Libraries.
| + | |
| - | | + | |
| - | EasyChair will be used to manage the submission review process. The submission site is here: http://www.easychair.org/conferences/?conf=mise2013
| + | |
| - | | + | |
| - | == Organizing Committee ==
| + | |
| - | | + | |
| - | * Joanne M. Atlee (primary contact), University of Waterloo, Ontario, Canada
| + | |
| - | * Robert Baillargeon, Sodius, East Amherst, NY, USA | + | |
| - | * Marsha Chechik, University of Toronto, ON, Canada
| + | |
| - | * Robert France, Colorado State University, USA | + | |
| - | * Jeff Gray, University of Alabama, USA
| + | |
| - | * Richard Paige, University of York, UK
| + | |
| - | * Bernhard Rumpe, RWTH Aachen University, Germany
| + | |
| | | | |
| | == Program Committee == | | == Program Committee == |
| | | | |
| - | * Lionel Briand, University of Luxembourg, Luxembourg
| + | tba |
| - | * Manfred Broy, Technical University of Munich, Germany
| + | |
| - | * Krzysztof Czarnecki, University of Waterloo, Canada
| + | |
| - | * Juergen Dingel, Queen's University, Canada
| + | |
| - | * Geri Georg, Colorado State University, USA
| + | |
| - | * Mats Heimdahl, University of Minnesota, USA
| + | |
| - | * Michael Jackson, The Open University, UK
| + | |
| - | * Jean-Marc Jezequel, INRIA & Univ. Rennes 1, France
| + | |
| - | * Dimitris Kolovos, University of York, UK
| + | |
| - | * Jeff Kramer, Imperial College London, UK
| + | |
| - | * Ana Moreira, Universidade Nova Lisboa, Portugal
| + | |
| - | * Alfonso Pierantonio, University of L’Aquila, Italy
| + | |
| - | * Awais Rashid, Lancaster University, UK
| + | |
| - | * Andrey Sadovykh, Softeam, France
| + | |
| - | * Sebastian Uchitel, Universidad de Buenos Aires, Argentina
| + | |
| - | * Steffen Zschaler, Kings College, UK
| + | |
| | | | |
| - | === Older Mise Workshops === | + | == Further MiSE Information == |
| | | | |
| - | * [[older MISE instances]] | + | * MISE [[Main Page]] |
| | + | * MISE [[Steering Committee]] |
| | + | * The call for papers is available for download at tba |
