Gøran K. Olsen

Scenarios of traceability in model to text transformations

The challenges of managing change in model-driven development are addressed by traceability mechanisms for model to text transformations. A traceability model, tailored for representing trace information between models and generated code, provides the basis for visualisation and analysis of the relationships between models and code. Usage scenarios for traceability are discussed and illustrated by our traceability implementation.

The Future of Train Signaling

Producing the source code for a railway interlocking system based on the description of a station has traditionally been a multistage manual process. We show how this process can be automated and made less error-prone by introducing model-driven development (MDD). This paper addresses the experience of developing a Domain Specific Language (DSL) to describe railway stations, Train Control Language (TCL), and tools to support this language. In the railroad domain where there are extreme safety requirements, it is essential to show that consistency and completeness can be assured. We address how the model is used to generate several different representations for different purposes. We look at advantages and challenges with our approach, and we discuss improvements to existing technologies to support our case better.

Developing a software product line for train control: a case study of CVL

This paper presents a case study of creating a software product line for the train signaling domain. The Train Control Language (TCL) is a DSL which automates the production of source code for computers controlling train stations. By applying the Common Variability Language (CVL), which is a separate and generic language to define variability on base models, we form a software product line of stations. We discuss the process and experience of using CVL to automate the production of three real train stations. A brief discussion about the verification needed for the generated products is also included.

Comparison of Three Model Transformation Languages

In this paper we compare three model transformation languages: 1) Concrete syntax-based graph transformation (CGT) which is our emerging model transformation language, 2) Attributed Graph Grammar (AGG) representing traditional graph transformation, and 3) Atlas Transformation Language (ATL) representing model transformation. Our case study is a fairly complicated refactoring of UML activity models. The case study shows that CGT rules are more concise and requires considerably less effort from the modeler, than with AGG and ATL. With AGG and ATL, the transformation modeler needs access to and knowledge of the metamodel and the representation in the abstract syntax. In CGT rules on the other hand, the transformation modeler can concentrate on the familiar concrete syntax of the source and target languages.

Rigorous identification and encoding of trace-links in model-driven engineering

Model-driven engineering (MDE) involves the construction and manipulation of many models of different kinds in an engineering process. In principle, models can be used in the product engineering lifecycle in an end-to-end manner for representing requirements, designs and implementations, and assisting in deployment and maintenance. The manipulations applied to models may be manual, but they can also be automated—for example, using model transformations, code generation, and validation. To enhance automated analysis, consistency and coherence of models used in an MDE process, it is useful to identify, establish and maintain trace-links between models. However, the breadth and scope of trace-links that can be used in MDE is substantial, and managing trace-link information can be very complex. In this paper, we contribute to managing the complexity of traceability information in MDE in two ways: firstly, we demonstrate how to identify the different kinds of trace-links that may appear in an end-to-end MDE process; secondly, we describe a rigorous approach to defining semantically rich trace-links between models, where the models themselves may be constructed using diverse modelling languages. The definition of rich trace-links allows us to use tools to maintain and analyse traceability relationships.

Train Control Language – Teaching Computers Interlocking

This paper describes how computer specialists are rarely trained in the world of tracks and trains, while signaling experts are rarely computer specialists. This paper is about bridging the gap between trains and computers with a specially designed language that enables the signaling experts to create consistent train interlocking systems. The language is supported by tailored tools created with open source technology on the development platform Eclipse. From the formal definition of the language in the form of a metamodel, a graphical editor is generated. The systems created with that graphic editor are then transformed for several purposes that are internally consistent. The editor makes sure that the systems conform to the language, and the language makes sure that the systems conform to the way interlockings are designed. The transformations then produce interlocking tables and even actual code automatically from the graphically created model.

Guest editorial to the theme issue on traceability in model-driven engineering

This issue of Software and Systems Modeling, and part of the issue that follows, are dedicated to the theme of traceability in model-driven engineering (MDE). Traceability is a fundamental concern in MDE processes, where models are related via application of different model management operations, such as model-to-model transformations, modelto-text transformations, model merging, model comparison, and many others. MDE emphasises on the application of automated model management operations, and substantial traceability information can be produced as a side-effect of applying these operations. In addition, in realistic MDE processes, traceability information can be produced by hand, through engineers manually relate MDE artefacts, or relate MDE artefacts with other artefacts (such as requirements documents). Overall, there are many challenges to traceability in MDE, ranging from managing large traceability models, to synchronizing models, and to keep traceability information consistentwhenmodels are beingmodified automatically and manually. This theme issue presents state-ofthe-art research on these and other challenges. Since 2005, the ECMDA-FA/ECMFA Workshop on Traceability has presented the leading research on traceability in MDE. After the 2008 workshop in Berlin, authors of accepted papers from the previous four workshops were invited to submit their latest results (perhaps derived from their workshop papers) to this theme issue. At the same time, an open call was issued, soliciting submissions from the