ABSTRACT
This chapter introduces the DREAMS metamodel and a model-driven development process ranging from variability exploration to configuration synthesis. It shows how Model-Driven Engineering supports to map mixed-critical applications onto the DREAMS platform. For the consideration of timing requirements throughout the development process, generic methodology pattern can be mapped to the V-Model based on the safety-related development process of DREAMS. The DREAMS Safety Compliance Model is associated to the Logical Component Architecture Model and the Platform Architecture Model. When a safety related subsystem is reused in a specific DREAMS system, it must be ensured that usage constraints specified by the subsystem in its safety manual are fulfilled by the system. The DREAMS safety case generation process takes advantage of a development process that relies on the composition of modules to design the products, so that the final products reuse safety assurance artifacts either at subsystem or component levels.
