## 2 State of the Art
### Safety and Security Engineering in MBSE  
The scientific literature deals with the integration of safety and security engineering into the MBSE environment from three perspectives: application examples, frameworks as well as approaches, and the implementation of individual safety/security-relevant frameworks (e.g., FMEA). The focus of this literature review is on analyzing methods, approaches, and frameworks. In the context of functional safety, [PERSON] et al. [18] describe the aSET approach, a high-level metamodel implemented in SysML from the concept phase to the HW/SW engineering phase. A profile implemented in UML for functional safety requirements based on ISO 26262:2018 [9] was developed by [PERSON] et al. [19] for use in automated driver assistance systems. The implementation of parts of safety in MBSE as an interface between the document-based component model and the Matlab model for validation was described by [PERSON] et al. [20]. Safety-MBSE integration has been taken up by the Object Management Group (OMG) with the aim of supplementing it with safety applications from the perspective of the SysML environment. The OMG's safety specification for SysML consists of a metamodel that supplements SysML with the necessary stereotypes and enables FTA, FMEA frameworks, and the implementation of HARA [21; 22].  
Metamodel-based approaches to integrating standards-based processes with MBSE solutions are also available in cybersecurity. Based on a template and SysML stereotypes, [PERSON] et al. [23] have shown how a cybersecurity concept can be modeled in SysML. The cybersecurity process from requirements to solutions has been adapted by [PERSON] et al. [24] as a process model for MBSE, focusing on the identification of security requirements in the early stages of development in the context of aerospace. [PERSON] et al. [25] describe the translation of cybersecurity threats into SysML with the security-aware systems engineering approach whereby the aim is the early integration of the threats into the SysML model of the product. The HEAVENS approach describes the security process from the TARA to the definition of the security requirements. The HEAVENS approach was implemented together with the processes of ISO 26262:2018 by [PERSON] et al. [26] using the IBM Rhapsody framework in SysML, which enables the implementation of the safety and security analysis from the ITEM definition to the technical safety concept. Stakeholder information was transferred to the MBSE context by [PERSON] et al. [27] and used as the basis for the hazard analysis of safety-relevant cybersecurity hazards. The relevance of integrating MBSE and safety/security is also shown by the fact that the manufacturer of one of the most prominently used tools for MBSE, Dassault Systems, released packages that contain the modeling elements for certain parts of the base standards [28; 29].  
The analysis of the scientific literature shows that the implementation of the base standards in an MBSE context is widespread. The safety and security processes, conforming to the base standards, were carried out by [PERSON] et al. [26]. The general focus of the scientific work in the subject area analyzed is on the implementation of the base standards or frameworks, such as TARA, as metamodels or templates for carrying out safety and security activities. Outside the focus of the publications is the integration of safety and security management into the method, the possible tailoring approaches depending on the use cases of the method, the detailed modeling of the individual activities from the perspective of method and information flow, and the modeling of the application environment of the method as a prerequisite for conformity with the base standards.