Our interest is embedded systems validation as part of the model-driven approach. To design a model, the modeller needs to obtain knowledge about the system and decide what is relevant to model and how. A part of the modelling activities is inherently informal - it cannot be formalised in such a way to constitute a basis for automated model design. This does not mean that modelling has to be
chaotic. We therefore propose an informal method that structures modelling activities. In this paper we will focus on one of the method ingredients - modelling guidelines. In the industrial case study we performed, we
captured modelling steps and elements in a form of a modelling handbook. The goal was to make modelling more efficient by preventing next modellers re-inventing
things, but also to preserve a modelling style recognized within company's context. We show in detail what these re-usable modelling elements are, and how identifying them can be generalised for designing modelling guidelines in
general. Finally, we compare our work with work of researchers that formalise problem analysis.
|Workshop||International Workshop on Applications and Advances of Problem-Orientation, IWAAPO|
|Period||8/05/10 → 8/05/10|
|Other||8 May 2010|