Abstract

Model-based System Engineering (MBSE) is a methodology that uses models throughout the engineering to replace the paper-based approach of communication among stakeholders. Multi-Paradigm Modelling (MPM) is at the core of this engineering approach as for each phase in the engineering process the most appropriate models at the most appropriate levels of abstraction is used. A design process includes a set of activities in which the design decisions or evaluations of the (sub-) system properties are done. Furthermore, the design artifacts are transformed by the design activities.We can define transformations as the manipulation of a model with a specific purpose. MPM approaches do not have a standard way of representing processes. A process model for MPM should focus on the languages, model instances and transformations between these models at different levels of abstraction. In this chapter, we propose the Formalism Transformation Graph and Process Model (FTG+PM) as a standard representation of MPM processes. The described process can be simulated for analysis and orchestration, as a set of (automatic) transformations.

Highlights

  • To tackle the increasing complexity of today’s systems, engineers already practice a Model-Based Systems Engineering (MBSE) methodology [95]

  • Multi-Paradigm Modelling (MPM) approaches do not have a standard way of representing processes

  • A process model for MPM should focus on the languages, model instances and transformations between these models at different levels of abstraction

Read more

Summary

Introduction

Design, verification, and validation activities of a system beginning in the conceptual design phase and continuing throughout development and later life cycle phases [153] While these models often operate at different abstraction levels, model transformations are applied to manipulate models between different appropriate representations. They can be regarded as model transformations where information in a set of input models is consumed to produce a set of output models This series of design activities should result in an operational system that meets the predefined set of requirements, MPM approaches do not have a standard way of representing the process.

Model-based Systems Engineering
Development Lifecycle Models
Waterfall Model
V Model
Spiral Model
Agile Model
Modelling the Design Process
Rationale
What to model?
Reasoning about maturity
The tool perspective
FTG+PM: Formalism Transformation Graph and Process Model
Reasoning about appropriateness of formalisms and heterogeneous modelling
Orchestrating Processes
Summary
Literature and Further Reading
9.10 Self-Assessment
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call