## 4 Linking the Two Approaches
### Application to the Multicopter Example
The state flow initially starts with the state _\"resting on ground\"_ of the component \"Chassis Frame\" and illustrates the possible processes that may lead to another state of the component. For instance, a combination of the processes P1, P2 and P13 can lead to another state, i.e., the state may change _\"in flight, distributing forces\"_, which is also a state of the component \"Chassis Frame\". A detailed look at these processes and their interconnections can be fostered by means of the process flow view (Figure 15, adapted from [50]). In the process flow view in Figure 15, the processes, which are also described in the state view (Figure 14), are linked with oriented connections. Through this, the interplay of the processes becomes transparent. Certain decision points may also be included in this process flow view. It is important to note that each process in the technical system is  
Figure 16: Actor view of the IFM model (X indicates active actors and O indicates passive actors). Figure 15: Process flow view of the IF model (simplified). realized by means of actors (see Section 3.1); the connection of the actors to the respective processes can be described in the actor view (Figure 16). In the actor view shown in Figure 16, a differentiation between active actors that are indicated by an \"X\" (e.g., the actor \"Battery\" in the process _\"distribute energy according to need\"_) and passive actors that are indicated by an \"O\" (e.g., the actor \"Battery\" in the process \"_start system_\") is possible. This differentiation supports the identification of actors that are especially active. One may notice that the actors are already concrete system elements, indicating the transition to the more concrete levels of the successive architecture development over the functional and logical architecture to the physical architecture (see Section 1). In the representation in Figure 16, the developed connection between the IFM Framework and the engineering framework based on GBDLs becomes particularly visible. The actor view represents a concise system model that achieves a direct connection of the function-oriented processes with the actors, which are, amongst others, the objects/components in the engineering framework and their later instantiation. The model described in the actor view can serve as a basis for the further product development steps of the technical system under consideration. Employing the different views of the IF model, which were illustrated presciently, the GBDL generates a design graph in an automatic manner. The design graph of the function model of the multicopter is shown in Figure 17 (adapted from [PERSON] et al. [50]). Based on the UML model of the technical system, several analyses may be performed automatically, such as reasoning tests (Section 5). The starting point is the central data model, which represents information in the form of a design graph. From this high-level model, several interfaces may allow the generation of generic models that are usually domain-specific, e.g., geometry models in CAD data formats or simulation models in typical CAE data formats. Figure 10 indicates some of the generic models that were generated in the earlier phases of the product development of the multicopter. Therefore, the IF model combined with GBDLs leads to an engineering framework that allows the generation of the abstract logical structure of a technical system. This kind of structure enables the automated creation of multi-domain models. In the described framework based on GBDLs, these multi-domain models also contain detailed geometrical information. These multi-domain models allow the analysis and exploration of a large product variety, i.e., a large number of possible, sensible and feasible product configurations; a large product portfolio can be analyzed and evaluated. Domain-specific models, which were created from the design graph using interfaces (Figure 10), can be employed for verifying the functions that were demanded in the requirements.