Abstract

based design. This paper presents a development process based on modelling, simulation, and code synthesis. The DCharts formalism, a Statecharts variant with extensions, is used to model a small application to demonstrate our approach: a traffic light. The development of this system highlights the use of various formalisms with appropriate supporting tools: AToM 3, A Tool for Multi-formalism and Meta-Modelling, is used as a multi-formalism visual modelling environment; SVM is the simulation engine used to experiment with prototype models; SCC is the code synthesizer that generates reusable source code in a variety of target languages. Transformation onto the Communicating Sequential Processes (CSP) formalism allows for model checking using the Failures Divergences Refinement Checker (FDR2) model checker. We demonstrate how using multiple formalisms as well as model transformations during the design process can drastically improve productivity, reliability and reusability. 1. MODELLING, ANALYSIS AND SIMU-LATION BASED DESIGN Compared to traditional software programming, modelling and simulation based (software) design has many advantages. By modelling the structure and behaviour of the system at an appropriate level of abstraction in the most appropriate formalism(s), accidental complexity will be minimized, and the designer can focus on essential issues instead of being bogged down with implementation details at early stages in the development process. 1.1. The process Our modelling and simulation based design process is illustrated in Figure 1. The system designer starts from a set of requirements, which constrain the design space. In the example given here, the requirements are not modelled explicitly

Citations