Shape the Future of Model-Based Systems Engineering with PREEvision

Stakeholder requirements form the starting point. They describe the product benefits for the stakeholders in natural language. A simple editor allows us to use texts, images, and use case diagrams.

We then translate these stakeholder needs into technically refined system requirements. Defined by models or text, these actionable specifications guide the design, the implementation, and the testing.

During requirements engineering, we develop test specifications covering all requirements. We then link the test items to the requirements to establish horizontal traceability.

Finally, we link the system requirements to the stakeholder requirements using simple traceability editors to define vertical traceability. In later stages, we link design and implementation artifacts to the requirements, ensuring compliance with standards like ASPICE and ISO 26262.

We start by defining the required functions, sub-functions, and their interactions. Modern products are systems of systems. Model activity diagrams to describe the behavior of a system in an isolated perspective. Set up a functional viewpoint that maps out all system requirements.

From the functional viewpoint, we define how the system fulfills our functions, remaining independent from the physical implementation. The logical viewpoint integrates the different systems of a complex product, such as sensors or actuators shared by different systems. Using block diagrams, we define a logical architecture that includes logical components like sense, function, and actuation blocks, as well as data flows.

For traceability, link the development artifacts created for the system design to both requirements and test specifications.

We define software components with their connections and interfaces. For the modeling of these static aspects of software architecture, PREEvision provides software architecture diagrams and class diagrams.

Besides defining the architecture, PREEvision allows you to model the detailed software design. Class diagrams describe the inner structure of software components. For system behavior, utilize state machines, sequence diagrams, and activity diagrams.

In diagrams, we set up a network topology of the complete E/E system or the relevant part of the system in scope. The network diagram supports the definition of the different E/E components, including their interfaces, power supply, and communication topology.

For the detailed hardware design, specify the power, fusing, and grounding concepts. Model the details of the wiring harness design. For the internal architecture of sensors, actuators, ECUs, and High-Performance Computers (HPCs), PREEvision provides component diagrams

Link both software and hardware to requirements and to the logical architecture for vertical traceability. Linking software to hardware finally determines which data is exchanged over the hardware network.