On the use of software models during software execution

N. Bencomo

Research output: Chapter in Book/Published conference outputChapter

Abstract

Increasingly software systems are required to survive variations in their execution environment without or with only little human intervention. Such systems are called "eternal software systems". In contrast to the traditional view of development and execution as separate cycles, these modern software systems should not present such a separation. Research in MDE has been primarily concerned with the use of models during the first cycle or development (i.e. during the design, implementation, and deployment) and has shown excellent results. In this paper the author argues that an eternal software system must have a first-class representation of itself available to enable change. These runtime representations (or runtime models) will depend on the kind of dynamic changes that we want to make available during execution or on the kind of analysis we want the system to support. Hence, different models can be conceived. Self-representation inevitably implies the use of reflection. In this paper the author briefly summarizes research that supports the use of runtime models, and points out different issues and research questions.
Original languageEnglish
Title of host publicationProceedings of the 2009 31st International Conference on Software Engineering and ICSE Workshops
Pages62-67
Number of pages6
DOIs
Publication statusPublished - 2009
Event ICSE workshop on modeling in software engineering - Vancouver, Canada
Duration: 17 May 200918 May 2009

Workshop

Workshop ICSE workshop on modeling in software engineering
Abbreviated titleMISE '09
Country/TerritoryCanada
CityVancouver
Period17/05/0918/05/09

Bibliographical note

© 2009 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

Fingerprint

Dive into the research topics of 'On the use of software models during software execution'. Together they form a unique fingerprint.

Cite this