PREEvision
| PREEvision | |
|---|---|
| Basic data
|
|
| developer | Vector computer science |
| Current version | 9.0 (September 2018) |
| operating system | Windows 7,8, 10 |
| category | Development tool |
| German speaking | Yes |
| vector.com/preevision | |
PREEvision is a model-based development software for electrical / electronic systems . With the help of this application, models of electrical and electronic systems can be designed. PREEvision thus supports the development process through the method of model-based system development ( MBSE ). The different facets of the model-based system design are also reflected in the individual development levels. Starting with requirements and use cases , functions and their logical structure are now modeled. These artifacts are then converted into hardware and software . Everything is possible up to the definition of cable sets, electrical connectors as well as data streams and signals.
history
The development of PREEvision started as an industry- funded research project at the FZI Research Center for Computer Science at the University of Karlsruhe at the end of 2003. The development partner was Daimler AG . After completing the study on the so-called E / E concept tool, the development partner Daimler AG was looking for a company that could take over product development. As a classic research spin-off from two researchers from the University of Karlsruhe and the FZI, aquintos GmbH took over product development from April 2005 and released the product version Release 1.0 under the brand name PREEvision for the first time in January 2007. In the year it was launched, aquintos won the Embedded Award (2007) in the tool category.
In September 2009 Vector Informatik took a minority stake in aquintos. In May 2010, aquintos GmbH was then completely taken over by Vector Informatik GmbH. Since then the product has been developed and sold by Vector.
| Publication date | version | Basic features |
|---|---|---|
| September 2018 | PREEvision
9.0 |
|
| August 2016 | PREEvision 8.0 |
|
| March 2016 | PREEvision 7.5 |
|
| August 2014 | PREEvision 7.0 | |
| August 2013 | PREEvision 6.5 |
|
| December 2012 | PREEvision 6.0 |
|
| May 2012 | PREEvision 5.5 |
|
| December 2011 | PREEvision 5.0 |
|
| July 2010 | PREEvision 3.0 | Introduction of the logical architecture level, differential analysis of models, LIN LDF and CAN DBC exporter, merging of the data model with the Vector development environment eASEE. |
| January 2007 | PREEvision 1.0 | First product version with modeling support for function lists, software architecture, network topologies and on-board network.
Database support for MySQL databases. The development environment is based on Eclipse Rich-Client Platform / Java. Architectural rating metrics were developed in a Python dialect. |
application
example
There are many examples of such electrical and electronic systems (E / E). Basically, it includes all systems that have electrical components. For example, the on-board electronics of a motor vehicle can be understood as an E / E system. Use cases can be described starting with the requirements for the electronic components. For example, a requirement could be that it must be possible to listen to the radio in the vehicle. Use cases such as switching the radio on / off, changing channels are use cases.
The logical sequence of listening to the radio now consists of receiving a radio station via an antenna and transmitting the electrical signal to a tuner. In addition to the antenna input, this requires a specification as to which frequency can be heard. The music signal obtained in this way may already be digitally passed on to an amplifier, which in turn outputs it to a loudspeaker according to a specified volume level.
The above The logical sequence must now be converted into concrete electrical and electronic components and their functions. E.g. a digital tuner, which in turn could consist of the DSP, main memory, an antenna input and an Ethernet input. A bus system such as MOST or Ethernet is used to transmit the digital music data to the amplifier. Let us assume that the tuner also receives the frequency via the Ethernet bus and the amplifier also reads the volume via it.
Of course, it is also not possible without software modules. In other words, software modules and their interfaces that can write the music data to the bus or read in a volume are described on the software layer.
The communication is modeled in the signal layer. Here you can specify the resolutions and cycle rates with which the information is to be transmitted.
In the lower modeling levels, the Ethernet bus system can now be described using concrete (four individual) wires. In addition, it is possible to model which separation points are required where in which form and where exactly the cable routes run (including length evaluation). The position of the tuner and amplifier are also modeled in this way.
Through the consistent linking of the individual elements and artifacts of the levels, it can be determined exactly for which use cases the specific wire in the cable is used: i.e. listening to music, changing the volume, etc.
In practice
Specifically, PREEvision is used today, for example, in the electronics development departments in motor vehicles, often in cooperation with specialized tools.
Today all German automobile manufacturers and many of the international suppliers work with the application.
Collaborative work
Usually, complex electrical / electronic systems are developed in large teams - possibly spread over various departments and locations. Consistent modeling of the systems in a collaborative database means that the relationships between the individual assemblies are always visible and transparently traceable. This supports a systematic approach.
For this purpose, PREEvision can be operated on a server basis. The central server takes over the administration of the models, users and their rights. In an intermediate server layer, the model parts are buffered according to user needs. This takes the administrative load off the central server. The model is then processed in a rich client on the end user's computer. The client is based on the Eclipse framework.
Layer architecture
- Requirement level (green)
- Customer features: Functions that the product should have in front of the customer
- Use Cases: Use cases and usage scenarios for which the system is intended
- Requirements: Requirements that exist for the product
- Logical level (yellow)
- Effect chains: technology-free / implementation-free description of the structure and functionality that customer functions should have
- Software level (blue)
- Service-oriented architecture: Services and interfaces that software can access
- Software modules: software modules and their interaction
- Implementation: bound software packages in modules / files etc.
- Library: reuse of interfaces and types
- Hardware level (purple)
- Electronic components: such as control units and their internal structure
- Bus systems such as CAN , LIN or Flexray to supply the components with data, operating voltage, ground, etc.
- Circuits: physical mapping of buses on lines (e.g. CAN on 2-wire line, twisted)
- Geometry plane (orange)
- Cabling routes: Laying routes in a 2D or 3D model, mapping of connectors, crimps, etc.
- Installation locations of components: Location of the control units and buses in a model
- Communication level (turquoise, vertical)
- Individual signals, signal groups and PDUs
- Timing and latencies in transmission
- Formation of virtual LANs
- Network management and transmission protocols
- Variant management (beige)
- All artifacts can be grouped into variants and product lines
- Several derivatives can be described with one modeling
automation
Use of rules
PREEvision supports the formulation of rules using graphic diagrams. These rules are used in the model for the following tasks:
- Automatic checks of model consistency or naming scheme.
- Generating variants with the help of propagation rules.
- Search and provision of model artifacts using search rules.
Use of script-like program modules
Many tasks in a model, such as imports and exports of special formats, evaluations of connections, calculation of memory usage, etc., can be created subsequently by the user via a plug-in interface (called metrics). Various functions are available for this purpose that can be used by the user to implement their own functions. If these resources are not sufficient, user-specific Java source code can be implemented in special modules. For this purpose, a complete API is made available in the Java environment with which the model can be stepped through, changed and expanded. For example, special questions can be answered, or special company-internal formats can be created or imported.
Individual evidence
- ^ Martin Hillenbrand, Matthias Heinz, Klaus D. Müller-Glaser: Rapid Specification of Hardware-in-the-Loop Test Systems in the Automotive Domain Based on the Electric / Electronic Architecture Description of Vehicles . In: Proceedings of 2010 21st IEEE International Symposium on Rapid System Prototyping . June 1, 2010, p. 1-6 , doi : 10.1109 / RSP.2010.5656344 .
- ^ Rixin Zhang, Ajay Krishnan: Using Delta Model for Collaborative Work of Industrial Large-Scaled E / E Architecture Models . In: Jon Whittle, Tony Clark, Thomas Kühne (Eds.): Model Driven Engineering Languages and Systems (= Lecture Notes in Computer Science . 14th International Conference, MODELS 2011 Wellington, New Zealand, October 16-21, 2011 Proceedings, No. 6981 ). Springer, Berlin, Heidelberg, October 16, 2011, p. 714-728 , doi : 10.1007 / 978-3-642-24485-8_52 .
- ↑ Daum, Silke (ITIV): KIT - Institute for Information Processing Technology Spin-offs . July 6, 2016, accessed on March 21, 2017 (German).
- ↑ Heinz, Matthias: Model-based development and configuration of the time-controlled FlexRay bus system . KIT Scientific Publishing, 2012, ISBN 978-3-86644-816-2 , 2.8.2, pp. 306 .
- ^ Bernard Bäker: Modern Electronics in Motor Vehicles IV . tape 4 . expert verlag, 2009, ISBN 978-3-8169-2928-4 , 2.1 integrated, graphically noted approach for evaluating electrical / electronic architectures in vehicles, p. 223 .