scispace - formally typeset
Open AccessJournal Article

Model Driven Engineering

Stuart Kent
- 01 Jan 2002 - 
- pp 286-298
TLDR
A framework for model driven engineering is set out, which proposes an organisation of the modelling 'space' and how to locate models in that space, and identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions.
Abstract
The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

read more

Content maybe subject to copyright    Report

Citations
More filters
Proceedings ArticleDOI

A view of 20th and 21st century software engineering

TL;DR: This paper tries to identify at least some of the major past software experiences that were well worth repeating, and some that were not, and makes some first steps towards distinguishing relatively timeless software engineering principles that are risky not to repeat, and conditions of change under which aging practices will become increasingly risky to repeat.
Journal ArticleDOI

A critical review of Knowledge-Based Engineering: An identification of research challenges

TL;DR: Key findings include the necessity for improved methodological support and adherence, the need for a quantitative framework to assess the viability and success of KBE development and implementation projects, and the opportunity to move towards mass customization approaches through distributed deployment of K BE in the extended enterprise.

[서평]「Applying UML and Patterns - An Introduction to Object-Oriented Analysis and Design」

정인기
TL;DR: The money is found for applying uml and patterns an introduction to object oriented analysis and design an approach to object Oriented Analysis and design that can be your partner.
Book

Contracts for System Design

TL;DR: This paper intends to provide treatment where contracts are precisely defined and characterized so that they can be used in design methodologies such as the ones mentioned above with no ambiguity, and provides an important link between interfaces and contracts to show similarities and correspondences.
Journal ArticleDOI

A survey on context‐aware web service systems

TL;DR: It is hard to find a truly context‐aware web service‐based system that is interoperable and secure, and operates on multi‐organizational environments.
References
More filters
Proceedings ArticleDOI

N degrees of separation: multi-dimensional separation of concerns

TL;DR: A new paradigm for modeling and implementing software artifacts is described, one that permits separation of overlapping concerns along multiple dimensions of composition and decomposition, which addresses numerous problems throughout the software lifecycle.
Book

Objects, Components, and Frameworks With Uml: The Catalysis Approach

TL;DR: This chapter discusses Model Frameworks as Templates, a model framework for component-based development, and its applications in architecture, management, and user experience.
Proceedings ArticleDOI

Subject-oriented programming: a critique of pure objects

TL;DR: This paper explores this shift to a style of objectoriented technology that emphasizes the subjective views: Subject-Oriented Programming.
Journal ArticleDOI

A framework for expressing the relationships between multiple views in requirements specification

TL;DR: This work deploys multiple ViewPoints that hold partial requirements specifications, described and developed using different representation schemes and development strategies, and proposes a general model for ViewPoint interaction and integration.
Related Papers (5)