Usage Models Mapped to Programs

Abstract

Model-based programming can replace classical programming based on compilation and systematic development of models as well on explicit consideration of all model components without hiding intrinsic details and assumptions. A key element of model-based programming is the proper definition and management of model suites, by which multiple, interrelated models can be transformed from one another and their consistency is ensured after modifications. A usage model is based on the specification of user roles and types, together with an interaction space described in a form of a storyboard, showing which activities are supported, in which order, by which actors. A workflow model is an extended, well-formed declaration of how specific processes should be carried out. It can directly be translated to program code, using a proper workflow or process engine. A novel way of programming is being opened up by usage modeling, which is being investigated in this paper: Given a storyboard with supported usage scenarios, it is possible to derive a workflow model from it. We present our two translation methods using a working example, identifying guidelines as requirements for model refinement and normalization, rules for model translation, and propose considerations towards improved methods and model specifications.