Integrate MBSE in established engineering processes for holistic lifecycle management

If model-based development is introduced for the development of complex cyber-physical systems, this is to be understood as a supplement to the tools and process steps already in use. It should be a matter of course to consider the existing tools and processes and to integrate model artifacts into the entire development process in an automated way - from requirements to code to ensure holistic application lifecycle management.
Typically, there are different tools and processes for different disciplines, all of which are relevant to the development process. Unfortunately, the models created are usually just collections of diagrams that are neither reviewed nor used in the ongoing process.
The presentation will focus on how information shall be transferred from an ALM tool to a modelling tool in order to derive the system architecture specification and vice versa. The following 3 requirements are discussed, where different approaches exist offering different advantages and disadvantages:
a) Traceability should be consistent for all development artifacts.
b) Requirements baselines should always correspond to the correct model versions.
c) Integrations like OSLC, Add-in, etc. should fit into existing agile processes.