PREEvision. Release Notes. Version 7.5 SP5 English

Transcription

1 PREEvision Release Notes Version 7.5 SP5 English

2 Imprint Vector Informatik GmbH Ingersheimer Straße Stuttgart, Germany Vector reserves the right to modify any information and/or data in this user documentation without notice. This documentation nor any of its parts may be reproduced in any form or by any means without the prior written consent of Vector. To the maximum extent permitted under law, all technical data, texts, graphics, images and their design are protected by copyright law, various international treaties and other applicable law. Any unauthorized use may violate copyright and other applicable laws or regulations. Copyright 2016, Vector Informatik GmbH. Printed in Germany. All rights reserved.

3 Contents Contents 1 PREEvision 7.5 SP Version numbers Installation and compatibility information New features Fixed issues Diagrams Tables Product goals Logical function Software Communication Hardware Geometry Functional safety Rules Metrics Reports Administration Migration License Known issues 18 2 PREEvision 7.5 SP Version numbers Installation and compatibility information Fixed issues Tables Software Communication Hardware Geometry Rules and reports Administration and migration Known issues 27 3 PREEvision 7.5 SP Version numbers Installation and compatibility information Fixed issues 31 Vector Informatik GmbH Version 7.5 SP5 3

4 Contents Tables Logical function Communication Product line approach Functional safety Rules and metrics Administration Known issues 35 4 PREEvision 7.5 SP Version numbers Installation and compatibility information Fixed issues Diagrams and tables System software Communication Hardware Geometry Product line management Rules, metrics and reports Roles and rights Known issues 43 5 PREEvision 7.5 SP Version numbers Installation and compatibility information Fixed issues Diagrams and tables Product goals Logical function Hardware Geometry Product line approach Functional safety Rules, metrics and reports Roles and rights Administration and migration Known issues 54 6 PREEvision Version numbers 56 Vector Informatik GmbH Version 7.5 SP5 4

5 Contents 6.2 Installation and compatibility information New features Feature highlights Requirements engineering software, system and communication design Communication design Wiring harness design Design of safety relevant systems Product line engineering Usability improvements Administration Fixed issues Diagrams and tables Product goals Logical function Software Communication Hardware Geometry Product line approach Functional safety Rules, metrics and reports Administration and license Known issues 99 Vector Informatik GmbH Version 7.5 SP5 5

6 PREEvision 7.5 SP5 1 PREEvision 7.5 SP5 This chapter contains the following information: 1.1 Version numbers Installation and compatibility information New features Fixed issues Diagrams 11 Tables 11 Product goals 11 Logical function Software 12 Communication 12 Hardware 13 Geometry 13 Functional safety 14 Rules 14 Metrics 14 Reports Administration 16 Migration 16 License Known issues 18 Vector Informatik GmbH Version 7.5 SP5 6

7 PREEvision 7.5 SP5 1.1 Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 7

8 PREEvision 7.5 SP5 1.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 7.5 in general, refer to PREEvision Installation and compatibility information. New Java version Update of 3-tier environments Java 1.8.0_74 is now provided with the PREEvision client installation. Existing application server runtimes should also be updated to Java version 1.8.0_74. In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. The following table shows compatible client, server application and database server script versions for specific PREEvision 7.5 versions: Client version Server application version Database server script version For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Further information > Installation and compatibility information Vector Informatik GmbH Version 7.5 SP5 8

9 PREEvision 7.5 SP5 1.3 New features KBL import and export using metrics The import or export of KBL files can now be started via metrics. Therefore, a KBL Import Block and a KBL Export Block are available. This allows the simple execution of a series of exports or imports and also the automation without user interaction. Synchronize lightweight enumeration attribute values across reuses The attribute values of lightweight custom attributes of data type Application Enumeration are now kept synchronous across reuses. An event-triggered metric ensures that the attribute values are identical for all reuses. Therefore, the metric "simulates" a typeof relation between the attribute value of the enumeration and the enumeration literal defined in the data type. The metric is only executed if the respective artifact is changed. If the attribute value is not identical for all reuses, the metric aligns the values and sets the value that was changed last as attribute value for all reuses. Caution: The Metric Executor EnumEntrySync is contained in the demo and initialization model under Administration Metrics Utilities EnumEntrySync Metric Package and must be initialized via Factory Reset or manually integrated. Vector Informatik GmbH Version 7.5 SP5 9

10 PREEvision 7.5 SP5 1.4 Fixed issues Fixed issues in PREEvision 7.5 SP5 Further information You will find the important fixed issues in the following tables. Please note that some issues are depending on specific configurations, views or models. > > Diagrams > Tables > Product goals > Logical function > > Software > Communication > Hardware > Geometry > Functional safety > Rules > Metrics > Reports > > Administration > Migration > License The column width of tables in the Property View is persisted for the client session The quick search shows 500 results by default. The description of the search is adapted in case of more than 500 results are provided Sorting Property View tables via the sort buttons in the table toolbar works again If types within the Library only allow read access, they can be set on instances which allow write access The Artifacts page is available again and displays included and excluded artifacts of a Set The E/E-Model Online Check view shows online check results again. Vector Informatik GmbH Version 7.5 SP5 10

11 PREEvision 7.5 SP Diagrams If a Perspective Configuration is displayed in a dynamic label within a diagram, the perspective can be opened via double click in the dynamic label Within diagrams, free text fields, which are inside of graphical objects (like rectangle etc.), are changeable again. Diagrams Diagrams Tables All column types within a table can be moved, including table prototype columns Custom attribute values of type Integer can now be show in hexadecimal notation in table editors When sorting a table editor which displays a tree, children are sorted Ordering of table prototype columns has been fixed. Tables Tables Tables Tables Product goals For the requirement list import (Import Requirements From an Excel File) it is no longer required to select a library package The context menu for Use Case artifacts can be opened quickly in tables and in the Model View During the requirement list import, empty lines in the Excel file are handled If the Excel file for the requirement list import contains special characters, these characters are removed and the file is now imported. The information about not importable special characters is posted to the Information View. Product goals Product goals Product goals Product goals Vector Informatik GmbH Version 7.5 SP5 11

12 PREEvision 7.5 SP Logical function The highlighting within Activity Chains is calculated correctly. Therefore, sense and actuation are updated after a diagram has been opened The highlighting within Activity Chains is calculated correctly. Therefore, sense and actuation are updated after a diagram has been opened Activity Chains can be extended in reused diagram over a connection. Logical function Logical function Logical function export: SIGNAL-TO-I-PDU- MAPPINGs and I-PDU-TO-FRAME-MAPPINGs are sorted by their start positions Commit after an import is now ensured Software On the Usage property page, the correct prototype owner is now displayed in the table for the Application SW Component Type and the Composition Type The Application Enumeration value can be set via drop-down list now. Software Software Communication The Information View is optimized to enhance the performance of the signal router During signal routing, Gateway Routing Entries are reused when their in and out transmissions are also reused During frame synthesis, no PDU Transmission is created if there already exists a valid PDU Transmission The DBC ECU extract considers the custom attributes. Communication Communication Communication Communication Vector Informatik GmbH Version 7.5 SP5 12

13 PREEvision 7.5 SP For the signal router, the option Pass routing solution to information view for analysis no longer overrides the option Suppress standard output to log file and information view Results of the signal router are also displayed correctly if the results are long strings. Communication Communication Hardware A performance problem has been solved that occurred when performing a double click on Wiring Harness An error which caused the Error Log view to be shown during working within an Electric Circuit Diagram was corrected so that the Error Log view is not shown anymore The refactorings to replace the wire type and the refactoring to replace the synthesis constraint descriptor have been corrected and work again The refactoring to create missing Wiring Connectors has been enhanced and now considers a set workspace Offsheet connectors can be created even if a section is not changeable, because the connector is created in diagram connection and not in the section In diagrams of the hardware layer, the positioning of Name labels is now available Routing of cores that end in different components works correctly now. A problem with routing in different directions was corrected The refactoring of a Branch-Off into a Topology Point was corrected and works correctly again The ground spot optimization dialog now consistently supports selection and deselection of solutions using the check boxes. Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Geometry Executing a cut and paste action in the Geometry Diagram no longer leads to a client freeze. Geometry Vector Informatik GmbH Version 7.5 SP5 13

14 PREEvision 7.5 SP Functional safety When generating an FTA diagram via the "FTA Layouter" metric, all blocks have an identical block size. The block size is calculated and aligned after all blocks are drawn in the diagram When generating an FTA diagram via the "FTA Layouter" metric, condition assignments are displayed according to the defined block size Performance of generating an FTA diagram via the "FTA Layouter" has been improved. Functional safety Functional safety Functional safety Rules Online check of rule models has been enhanced to detect rules with corrupt links Two-step migration has been fixed for rule model from PREEvision 6.5 to 7.5. Rules Rules Metrics The auto-creation factory for diagrams creates now correct lines if connections are overlapping In the ANT script runmetric.xml that is used for automated metric execution, the reference to the MetricSuite.xml is removed. This reference could not be resolved and thus led to an error For loading a file-based model for automated metric execution, a port no longer has to be specified in the parameters.properties file. Metrics Metrics Metrics Reports Table rendering is finished before a report is fully generated. In that way, no hour glass is displayed in the generated report anymore. Reports Vector Informatik GmbH Version 7.5 SP5 14

15 PREEvision 7.5 SP Undo All Locks works after doing special diagram modifications A performance problem has been solved that occurred when updating the model from the server Performance has been improved for comparing two model versions of a selected subtree A deadlock has been fixed that occurred after performing the Undo All Locks action Model cache files are removed from the server after they have been fetched by the client (or automatically after one hour) A performance problem has been fixed that occurred when locking artifacts Deleting artifact no longer leads to a client freeze Requesting a lock after editing and saving a Source Code no longer leads to a client freeze A deadlock has been fixed that occurred after performing the Undo action When switching between scopes no model artifacts are shown grayed out, i.e. disabled To support long running commit transactions, the default value for middlewarecalltimeout has been increased. Instead of 30 seconds, it is now set to 120 seconds. The error message that is displayed if a commit fails because of a SocketTimeoutException was improved An update of the model can be executed even if the client is in scope definition mode An error occurred when connecting to the model. The error has been fixed; writing the model to the cache file has been improved The thread handling in the server has been improved. To avoid deadlocks, locking statements have a timeout The commit dialog disappears when the commit is finished To prevent inconsistencies, the set of changed artifacts is validated after every operation in the client. In case of invalid changes, the commit fails and a rollback is performed The demo model contains a complete Uniqueness Cache configuration now. Vector Informatik GmbH Version 7.5 SP5 15

16 PREEvision 7.5 SP The check-out life cycle trigger is also performed on automatic check-out The handling after a client crash has been improved and no longer leads to connection errors A commit error occurred after creating a reuse and branch of a Component Package and creating a Wiring Harness and Wiring Harness Diagram. The problem was solved A commit error occurred after changing a Wiring Harness Diagram. The problem was solved Administration Factory Reset has been reworked to reset physical files on hard disk correctly. Administration Migration Database restore has been enhanced to handle checked-in state of artifacts in backup history Database restore has been enhanced to handle checked-in state of artifacts in backup history. Migration Migration License Invalid licenses no longer produce a client crash Metrics that perform model changes cannot be executed with a viewer license. License License Printing is possible when using a viewer license. License Selecting artifacts in the model tree is possible even if using a viewer license Metrics which perform model changes cannot be executed with a viewer license When using a viewer license, the Excel export of tables is available When using a viewer license, diagrams can be exported via the diagram export. License License License License Vector Informatik GmbH Version 7.5 SP5 16

17 PREEvision 7.5 SP The "Insert Smart Card" request is only displayed if a HTTPs connection is used and certificate is required When using a viewer license, scopes can be defined. License License Vector Informatik GmbH Version 7.5 SP5 17

18 PREEvision 7.5 SP5 1.5 Known issues Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > which PREEvision version shall be used for valid backup and restore. Meta class cannot be created for meta class artifact picker For the configuration of a Meta Class Artifact Picker, it is not possible to create new Meta Class proxies on the Meta Class Artifact Picker. Workaround: Existing Meta Class proxies can be assigned to the Meta Class Artifact Picker via drag and drop to the Meta Classes property page. Vector Informatik GmbH Version 7.5 SP5 18

19 PREEvision 7.5 SP4 2 PREEvision 7.5 SP4 This chapter contains the following information: 2.1 Version numbers Installation and compatibility information Fixed issues Tables Software 24 Communication 24 Hardware 25 Geometry 25 Rules and reports Administration and migration Known issues 27 Vector Informatik GmbH Version 7.5 SP5 19

20 PREEvision 7.5 SP4 2.1 Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 20

21 PREEvision 7.5 SP4 2.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 7.5 in general, refer to PREEvision Installation and compatibility information. New Java version Update of 3-tier environments Java 1.8.0_74 is now provided with the PREEvision client installation. Existing application server runtimes should also be updated to Java version 1.8.0_74. In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. The following table shows compatible client, server application and database server script versions for specific PREEvision 7.5 versions: Client version Server application version Database server script version For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Further information > Installation and compatibility information Vector Informatik GmbH Version 7.5 SP5 21

22 PREEvision 7.5 SP4 2.3 Fixed issues Fixed issues in PREEvision 7.5 SP4 Further information You will find the important fixed issues in the following tables. Please note that some issues are depending on specific configurations, views or models. > > Tables > > Software > Communication > Hardware > Geometry > Rules and reports > > Administration and migration For performance optimization, the online check decoration of parents has been disabled. Only the concrete artifacts with findings are indicated by an online check decorator in the Model View. In the E/E-Model Online Check view, the findings of the selected artifact and its children are presented by default. A new button has been added to toggle between displaying findings with or without children The compare table works again for comparing complete models When saving the model on disconnect, an error message is no longer displayed If the Model View is extended via Model Queries, navigation on artifacts displayed by the Model Query is possible again by pressing <SPACE> Missing mapping property pages are available again for Requirement Packages. Note: The property page "Mappings" is only relevant for Requirements. Vector Informatik GmbH Version 7.5 SP5 22

23 PREEvision 7.5 SP Tables Table prototypes are no longer removed on opening the Add/Remove/Reorder Columns dialog Opening tables on any artifact is possible again. Creating tables is still only possible for artifacts which are set as TableOwner in the meta model When changing attribute values in the Property View, corresponding table cells within a table editor are directly updated A currently opened LibreOffice editor is refreshed if the associated formatted text is changed somewhere else, e.g. in the Property View. Tables Tables Tables Tables files causing import problems can be imported now as far as they are compatible with the schema An error has been fixed regarding the import During import and export, I- SIGNAL.initValue is now imported to / exported from the attribute Raw Initial Value of the Signal Problems with the variant-sensitive export have been fixed During export, Bus Connectors which are not referenced are not exported During import and export, the Protocol Name of CAN Clusters is imported and exported ISignal generation for fan-out scenarios directly works after changing the flag in the import/export configuration file without having to restart the client During import, record elements without value can be imported During export, the complete controller configuration including CAN parameters of a CAN FD Controller Configuration is exported. Vector Informatik GmbH Version 7.5 SP5 23

24 PREEvision 7.5 SP During export of a system extract, only Sender Receiver Interfaces which belong to the selected ECU are exported During export of an ECU extract, the value for "Invalid" is exported During export, the start position is correctly exported if byte order "Opaque" is set Software The Port Types property page of the Sender Receiver Interface shows the port types now Mode Access Points can now be created via the New context menu on the Runnable Entity Typed Per Instance Memory can now be created via the New context menu on Internal Behavior New property page pages for Per Instance Memory and Typed Per Instance Memory have been added. The Typed Per Instance Memory can be created via the New context menu on the Internal Behavior artifact and the created Typed Per Instance Memory artifact is displayed as a child of the virtual folder "Per-Instance Memories". Software Software Software Software Communication If a Signal Group is used in different Frames, during DBC export, for each Frame a Signal Group is exported. In that way, no Frames are merged because of the Signal Group During DBC import and export, the name of the ECU is adjusted. The export of attributes of Tx Message and Rx Signal works correctly The Frame Synthesis also considers CAN Frames for CAN FD buses. That can be changes with a new setting on the preferences page The DBC export wizard filters out the checked elements in the same way as the export. Performance is improved significantly During DBC export, unrelated Signal Groups are not exported. Communication Communication Communication Communication Communication Vector Informatik GmbH Version 7.5 SP5 24

25 PREEvision 7.5 SP During DBC export, Scale Linear Verbal Table Conversion is exported like Linear Verbal Table Conversion The actions Add Controller Configuration and Add Controller Requirements create a CAN FD Connector Configuration and a CAN Connector Configuration if the selected element is a CAN FD Connector Type. The Delete action on the selected CAN FD Connector Type removes the created CAN FD Connector Configuration and the CAN Connector Configuration. Two groups are added which separately display the CAN FD Controller Configurations and the CAN Controller Configurations During DBC export, enumeration entries of Attribute Definitions which are used by several Meta Classes are exported only once. Communication Communication Communication Hardware The KBL import and export has been enhanced and supports now the KBL attribute housingcode of connector housing. It is imported and exported to the attribute Coding of a Connector Type Merging Hardware Devices with the same Hardware Device Type works now. Hardware Hardware Geometry Diagrams can be opened even if they have set a small zooming size. Geometry Vector Informatik GmbH Version 7.5 SP5 25

26 PREEvision 7.5 SP Rules and reports During synchronization of rules, the internal rule cache is now handled correctly. Existing rules are no longer marked as to be deleted Consistency rule results are displayed even if the affected artifact has no name The Generate Report dialog handles long paths correctly now: The report is no longer created in the installation directory and the full path is persisted. Rules Rules Reports Replace with latest revision works even if a reuse exists which is out of scope Activating and deactivating scopes has been stabilized To avoid commit problems, the UUID is also checked before handling container instances and types Performance has been improved for deleting version artifacts with a large number of dependable-versioned child artifacts (like in very big diagrams) A lock is possible after several refreshes of a diagram which contains query labels that generate model changes Importing a Product Line no longer locks sibling Product Lines External relations are maintained when replacing artifacts, e.g. during a specific import Administration and migration During factory reset, branches within the factory reset source model are ignored Post migration considers cases where newly creates relations are not corrected after deleting artifacts. This prevented the delete operation. Administration Migration Vector Informatik GmbH Version 7.5 SP5 26

27 PREEvision 7.5 SP4 2.4 Known issues Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > which PREEvision version shall be used for valid backup and restore. Meta class cannot be created for meta class artifact picker For the configuration of a Meta Class Artifact Picker, it is not possible to create new Meta Class proxies on the Meta Class Artifact Picker. Workaround: Existing Meta Class proxies can be assigned to the Meta Class Artifact Picker via drag and drop to the Meta Classes property page. Vector Informatik GmbH Version 7.5 SP5 27

28 PREEvision 7.5 SP3 3 PREEvision 7.5 SP3 This chapter contains the following information: 3.1 Version numbers Installation and compatibility information Fixed issues Tables 31 Logical function Communication 32 Product line approach 33 Functional safety 33 Rules and metrics Administration Known issues 35 Vector Informatik GmbH Version 7.5 SP5 28

29 PREEvision 7.5 SP3 3.1 Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 29

30 PREEvision 7.5 SP3 3.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 7.5 in general, refer to PREEvision Installation and compatibility information. New Java version Update of 3-tier environments Java 1.8.0_74 is now provided with the PREEvision client installation. Existing application server runtimes should also be updated to Java version 1.8.0_74. In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. The following table shows compatible client, server application and database server script versions for specific PREEvision 7.5 versions: Client version Server application version Database server script version For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Further information > Installation and compatibility information Vector Informatik GmbH Version 7.5 SP5 30

31 PREEvision 7.5 SP3 3.3 Fixed issues Fixed issues in PREEvision 7.5 SP3 Further information You will find the important fixed issues in the following tables. Please note that some issues are depending on specific configurations, views or models. > > Tables > Logical function > > Communication > Product line approach > Functional safety > Rules and metrics > > Administration Default values of custom attributes are now correctly set and reset The Constant Specification property page has been removed, the new Usage property page has been added for the Constant Specification Custom EEA import works correctly now on multi-user environments Tables Filtering metric-based table columns works correctly now Table actions such as creating an artifact in a Data Providing Table Column are possible even if the associated table artifacts are not locked. Necessary locks are requested via auto-lock Opening and closing the LibreOffice editor from a table no longer leads to an empty formatted text Tables are now correctly refreshed after performing a Dereference action in the table. Tables Tables Tables Tables Vector Informatik GmbH Version 7.5 SP5 31

32 PREEvision 7.5 SP Logical function Executing the Pull Up refactoring on a Building Block no longer creates duplicated ports and correctly connects assemblies Line routings are correctly maintained after executing the Creating Building Block refactoring. Logical function Logical function Roundtrip of NvBlockNeeds has been improved import of a folder with several files works correctly For the import the transformation of Y-Axis and X-Axis has been corrected Communication The Interfaces property page available for Sender Port Types and Receiver Port Types has been corrected. The property page is only displayed once and the assigned interface with its content is displayed DBC files can be parsed even if there is no LF at the end of the file and even if Strings contain signs for escaping like \ If the option Create new gateways automatically if necessary is activated during signal routing, new gateways are created only if no gateway exists or an existing gateway has a condition PDU Assignments are merged during DBC import if they address the same Signal IPDUs and Frames An Nm Node can now be assigned to an ECU Interface via drag and drop to the Network Management property page. Communication Communication Communication Communication Communication Vector Informatik GmbH Version 7.5 SP5 32

33 PREEvision 7.5 SP Product line approach Assets and sub Assets are added to the active scope when replacing with revision. Additionally all core and boundary artifacts are added to the active scope as well Closing the PREEvision client is possible after working within the variant management Creating a Product Line with substructure creates those artefacts which are supported by the selected license. Product line approach Product line approach Product line approach Functional safety Safe States can now be associated with Safety Goals via drag and drop in the hazard analysis editor After calculating Minimal Cut Sets, the top event of the fault tree analysis will be represented in the Property View now. Functional safety Functional safety Rules and metrics Model queries now respect the execution order defined in Rule Dependency Diagrams A type mismatch error which occurred during rule generation has been resolved Rules can be generated now if the source Object has been changed When calculating signal router results via metric, the results use less memory now. In this way, the application no longer slows down after running the metric multiple times Overlapping connections in diagrams can now be configured when using the auto-creation framework for creating diagrams via metrics. Rules Rules Rules Metrics Metrics Vector Informatik GmbH Version 7.5 SP5 33

34 PREEvision 7.5 SP If the client was closed abnormally the local delta model could become invalid and local changes could no longer be committed. The issue has been fixed Edited Reports and Report Modules can be committed without error message Displaying the commit history for an artifact allocates significantly less TEMP tablespace. The underlying SQL statement has been optimized Administration An exclusive full lock of the whole model is no longer required to perform a factory reset External relations are correctly maintained during factory reset Several issues have been fixed with regard to the factory reset on 3-tier environments Isolating artifacts for the custom factory reset now works correctly with the provided migration tools (metrics) Custom factory reset files created with Vector metrics do not contain revision and branch information anymore. Administration Administration Administration Administration Administration Vector Informatik GmbH Version 7.5 SP5 34

35 PREEvision 7.5 SP3 3.4 Known issues Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > which PREEvision version shall be used for valid backup and restore. Meta class cannot be created for meta class artifact picker For the configuration of a Meta Class Artifact Picker, it is not possible to create new Meta Class proxies on the Meta Class Artifact Picker. Workaround: Existing Meta Class proxies can be assigned to the Meta Class Artifact Picker via drag and drop to the Meta Classes property page. Vector Informatik GmbH Version 7.5 SP5 35

36 PREEvision 7.5 SP2 4 PREEvision 7.5 SP2 This chapter contains the following information: 4.1 Version numbers Installation and compatibility information Fixed issues Diagrams and tables System software 40 Communication 40 Hardware 40 Geometry 41 Product line management 41 Rules, metrics and reports Roles and rights Known issues 43 Vector Informatik GmbH Version 7.5 SP5 36

37 PREEvision 7.5 SP2 4.1 Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 37

38 PREEvision 7.5 SP2 4.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 7.5 in general, refer to PREEvision Installation and compatibility information. New Java version Update of 3-tier environments Java 1.8.0_74 is now provided with the PREEvision client installation. Existing application server runtimes should also be updated to Java version 1.8.0_74. In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. The following table shows compatible client, server application and database server script versions for specific PREEvision 7.5 versions: Client version Server application version Database server script version For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Further information > Installation and compatibility information Vector Informatik GmbH Version 7.5 SP5 38

39 PREEvision 7.5 SP2 4.3 Fixed issues Fixed issues in PREEvision 7.5 SP2 Further information You will find the important fixed issues in the following tables. Please note that some issues are depending on specific configurations, views or models. > > Diagrams and tables > > System software > Communication > Hardware > Geometry > Product line management > Rules, metrics and reports > > Roles and rights The performance of the model compare function has been improved Default value handling of custom attributes works correctly now on the list-based page of the Property View (displaying and resetting to default value is possible now) Subversion errors during commit of files have been resolved Diagrams and tables The automatic creation of diagrams mechanism has been extended by two new methods for defining the diagram name during creation of diagrams Tables are properly refreshed now when adding or deleting artifacts to or from tables Hexadecimal values can now be edited in tables if enabled via object configuration. Diagrams Tables Tables Vector Informatik GmbH Version 7.5 SP5 39

40 PREEvision 7.5 SP ApplicationArrayTypes are correctly exported in now Constant Specifications are correctly exported in now System software For internal behavior, Service Dependencies are now created within a virtual folder. Data Type Sets and Mode Declaration Sets are grouped together within a virtual folder called Included Sets. System software Communication Only CAN Frames with CAN FD Frame Support=true are correctly handled by the Frame-PDU Synthesis now, if the Bus Type is a CAN FD Type A read only validator for the attribute CAN FD Frame Support has been implemented. The corresponding attribute on the CAN Frame can be set now, independent of the CAN Frame Transmission The refactoring enabling the merge of PDUs applies to all PDU types now. Communication Communication Communication Hardware The wiring harness router now also creates the necessary mappings for Wiring Connectors to the respective Inline Connectors The refactoring for a type change of a connector works now, even if more than two connectors participate in the bus system The wiring harness router is now also able to split off cable cores if the Connector Locations are part of different Installation Locations (split off only for the last part after the last Branch- Off). Hardware Hardware Hardware Vector Informatik GmbH Version 7.5 SP5 40

41 PREEvision 7.5 SP Geometry When creating a new Geometry Diagram from 3D coordinates it can be decided whether Installation Spaces shall also be created or not. Geometry Product line management Creating Assets properly is possible now. Product line management Rules, metrics and reports Assigning a Calculation Block to source code is possible again after import Hits of indirect referenced java-based Rules are now correctly updated in the Rule Model Online Check view Closing rule model is possible now, while lock is missing in.eea model The initialization of query rule models works correctly now. Rules, metrics and reports Rules, metrics and reports Rules, metrics and reports Rules, metrics and reports All necessary artifacts are locked automatically again when working with Wiring diagrams Auto lock strategy considers delete operations correctly Bug reports with any legal file name can be committed now Commit of files works correctly now Auto-lock for synchronized custom attributes works correctly now During an update with latest revision, the incorrect error message is not shown any more, if the latest revision is not checked in. Vector Informatik GmbH Version 7.5 SP5 41

42 PREEvision 7.5 SP Roles and rights Recursions within role inheritance are now identified and prevented. Roles and rights Vector Informatik GmbH Version 7.5 SP5 42

43 PREEvision 7.5 SP2 4.4 Known issues Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > which PREEvision version shall be used for valid backup and restore. Meta class cannot be created for meta class artifact picker For the configuration of a Meta Class Artifact Picker, it is not possible to create new Meta Class proxies on the Meta Class Artifact Picker. Workaround: Existing Meta Class proxies can be assigned to the Meta Class Artifact Picker via drag and drop to the Meta Classes property page. Vector Informatik GmbH Version 7.5 SP5 43

44 PREEvision 7.5 SP1 5 PREEvision 7.5 SP1 This chapter contains the following information: 5.1 Version numbers Installation and compatibility information Fixed issues Diagrams and tables 48 Product goals 48 Logical function Hardware 51 Geometry 51 Product line approach 51 Functional safety 52 Rules, metrics and reports Roles and rights 53 Administration and migration Known issues 54 Vector Informatik GmbH Version 7.5 SP5 44

45 PREEvision 7.5 SP1 5.1 Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 45

46 PREEvision 7.5 SP1 5.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 7.5 in general, refer to PREEvision Installation and compatibility information. Update of 3-tier environments In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. The following table shows compatible client, server application and database server script versions for specific PREEvision 7.5 versions: Client version Server application version Database server script version For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Further information > Installation and compatibility information Vector Informatik GmbH Version 7.5 SP5 46

47 PREEvision 7.5 SP1 5.3 Fixed issues Fixed issues in PREEvision 7.5 SP1 Further information You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. > > Diagrams and tables > Product goals > Logical function > > Hardware > Geometry > Product line approach > Functional safety > Rules, metrics and reports > > Roles and rights > Administration and migration Within the comparison perspective, Property View filters can be saved for the left and right side Property View Due to the new custom attributes concept, text values of additional requirement attributes can be displayed within the comparison perspective Performance of the model merge has been restored to performance within previous PREEvision versions Formatted text attributes will be correctly displayed in the comparison perspective Comparing formatted texts works again The documentation for the automatic metric execution has been extended and describes all necessary configuration files now Performance of selecting and deselecting a large number of artifacts has been improved Performance of model queries and Model View has been improved. Vector Informatik GmbH Version 7.5 SP5 47

48 PREEvision 7.5 SP Diagrams and tables Results of model query rules are displayed in dynamic labels again Drag and drop actions are shown in the correct column now even if columns are hidden Data within a table will not be changed if selecting a value within a drop-down list is cancelled, e.g. by pressing <ESC> or by clicking into another table cell For selecting custom attribute columns in the Add/Remove/Reorder Columns dialog of table editors, the Type Definition Package must be associated to the Query Package which contains the table definition A MetricCellInformation object can now be delegated to metrics if requested via Model Context. Diagrams Tables Tables Tables Tables Product goals Drag and drop of modified and affected artifacts is possible in the Property View now During RIF import, the file name of the RIF import file is used as name for new Definition Sub Sets and new Definition Sets. Product goals Product goals Logical function Logical assembly connectors presented in system diagrams are listed in the Open with context menu Assembly connectors can be deleted from a diagram independently from each other. Logical function Logical function Vector Informatik GmbH Version 7.5 SP5 48

49 PREEvision 7.5 SP Performance of exporting an ECU extract has been improved During export, the attribute SHORT- LABEL of a NUMERICAL-VALUE- SPECIFICATION is only exported when it has a value During export, the Attribute CATEGORY of the APPLICATON-ARRAY- DATA-TYPE is correctly exported now For the import and export, handling of "not set" has been added for the attributes SW-IMPL-POLICY, SW-INTERPOLATION- METHOD, SW-REFRESH-TIMING of the APPLICATION-PRIMITIVE-DATA-TYPE Attributes of the Base Type are correct after roundtrip with import and export The export of Computation Method limit constraints has been corrected The attribute Invalid Value of Signals is exported to The value of the Data Filter Type of a Receiver Communication Specification is exported to In the export wizard, the new option No datatype restriction has been introduced to disable the data types restrictions The initial value of a shared Parameter is exported to The Implementation Policy of the Data Element is imported from During import, the Sender of LIN Tp Connections is imported PDU Frame Assignments of Xcp PDU, User defined PDU and Nm PDU are exported to LENGTH of USER-DEFINED-PDU and XCP- PDU are imported from The import metric custom block provides the created Product Line on the result port A NullPointer Exception which occurred within the metric-based model merge has been fixed. Vector Informatik GmbH Version 7.5 SP5 49

50 PREEvision 7.5 SP Custom attributes with type Opaque Reference are exported to as SDX- RFs The export of DATA-TYPE-MAPs has been corrected During export, date constraints are exported to an package. In PREEvision this is indicated by a Virtual Package with a Model Context named "DATA- CONSTR" During export, the value "-1" is handled for SW-ALIGNMENT Ports with Trigger Interfaces will be imported and exported in During export, the value "-1" is handled for REFRESH-TIMING SW-CALIBRATION-ACCESS (Calibration Access) and SW-IMPL-POLICY (Implementation Policy) are imported and exported in The Application Data Type of the Operation Argument will be imported from Calibration Access of the Mode Declaration Group Prototype is imported from During export, data constraints get the suffix "DC_" DATA-TYPE-MAPPING-REFS of the Composition Type are imported from Port API Options are completely imported from Ports with Nv Data Interface are imported from CONNECTION-TYPE of OBD-RATIO- SERVICE-NEEDS is imported from CALC-RAM-BLOCK-CRC of the NV-BLOCK- NEEDS is imported from Configuration of SWC description export has been extended to export initial values COMPU-CONST of computation methods with CATEGORY=TEXTTABLE are now correctly imported and exported in During export of a SWC description, Application Literals which are set as initial value for Communication Specifications are exported. Vector Informatik GmbH Version 7.5 SP5 50

51 PREEvision 7.5 SP Base data types of Implementation Data Pointers has been added to the SWC description export configuration SWC description configuration has been extended to export possible errors Hardware AWG values no longer have a decimal format and are correctly transferred to full numbers when changing the systems Within the Wiring Harness Diagram the pop-up bar for the cable was corrected and contains the shielding and the conductor now If the option for merging inline connectors with more than two pins with the same name is already activated no additional hint is given in the Information View The refactoring of connections into power outputs has been corrected and works now as expected. Hardware Hardware Hardware Hardware Geometry Moving Geometry Diagrams has been corrected and is performed quickly now The performance of creating new Geometry Diagrams with content based on existing data has been improved. Geometry Geometry Product line approach Numbering of Customer Features is displayed in the VM Template View again Highlighting is available in the VM Template View. Product line approach Product line approach Vector Informatik GmbH Version 7.5 SP5 51

52 PREEvision 7.5 SP Functional safety The requirement decomposition metric on a safety goal provides initial names for the functional safety requirements A new drag and drop operation for the FMEA Cause has been introduced in the Model View. The action facilitates creating a link to an existing FMEA Effect under the same FMEA Failure Mode Drag and drop from Safety Goal to Hazardous Event and vice versa is possible now. Drag and drop from Hazardous Event to Malfunction and vice versa is possible now. Functional safety Functional safety Functional safety Rules, metrics and reports Performance of generating and synchronizing rules has been improved Performance of selecting rule packages has been improved for the rule model import An error has been fixed which caused a client freeze when modeling rules The attributes xindex and yindex will now be displayed correctly for the Sort Filter Block The CurrentCalc class is now available in metrics again For rendering diagrams during report generation, the diagram height is calculated according to the first page of the report Embedded images in formatted texts are now correctly integrated in reports For rendering diagrams during report generation, the option Scale down if diagram is too big now considers preferences settings like Resize diagram height Editing include placeholders in a report template now correctly updates the contexts in the placeholder dialog In the Generate Report dialog, the file extension displayed in the file Name text field and the File Type selected in the drop-down list are synchronized. Rules Rules Rules Metrics Metrics Reports Reports Reports Reports Reports Vector Informatik GmbH Version 7.5 SP5 52

53 PREEvision 7.5 SP Fixed paste of files from history in cases where the ID of artifacts should be adopted during the paste operation (e.g. Requirements, Requirement Packages, Customer Features) A commit error caused by an error in the handling of formatted texts has been fixed. Handling of formatted texts has been corrected for the case that an artifact changes its class and the new class does not have the former formatted text attribute After executing the Undo All Locks operation it is possible again to change to another project Collected actions in the delta are now synchronous with the model in case new artifacts are created after an undo and getting deleted artifacts again by the following delete operation Show Reuse action is now available in offline mode An SVN error which prevented a commit has been fixed Roles and rights Recursions within role inheritance are now identified and prevented. Roles and rights Administration and migration Bug reports with any legal file name can be committed Initializing with custom factory settings does now handle reuses and assets correctly Initializing via Factory Reset correctly initializes Excel files Trace Assignment Relations between Assets are now correctly handled during automatic data migration. Administration Administration Administration Migration Vector Informatik GmbH Version 7.5 SP5 53

54 PREEvision 7.5 SP1 5.4 Known issues Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > which PREEvision version shall be used for valid backup and restore. Meta class cannot be created for meta class artifact picker Default value handling does not work correctly ( ) For the configuration of a Meta Class Artifact Picker, it is not possible to create new Meta Class proxies on the Meta Class Artifact Picker. Workaround: Existing Meta Class proxies can be assigned to the Meta Class Artifact Picker via drag and drop to the Meta Classes property page. Default value handling for custom attributes does not work correctly on the list-based page of the Property View (display and reset to default value not possible). Workaround: Use the table-based property page for displaying and resetting default values of custom attributes. Vector Informatik GmbH Version 7.5 SP5 54

55 PREEvision PREEvision 7.5 This chapter contains the following information: 6.1 Version numbers Installation and compatibility information New features 59 Feature highlights 59 Requirements engineering 64 software, system and communication design 66 Communication design 69 Wiring harness design 70 Design of safety relevant systems 75 Product line engineering Usability improvements 78 Administration Fixed issues Diagrams and tables 88 Product goals 89 Logical function 89 Software Communication 91 Hardware 91 Geometry 93 Product line approach 94 Functional safety 94 Rules, metrics and reports Administration and license Known issues 99 Vector Informatik GmbH Version 7.5 SP5 55

56 PREEvision Version numbers Version numbers Application Version number PREEvision client PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Manual Version number PREEvision manual PREEvision operating manual PREEvision system requirements Vector Informatik GmbH Version 7.5 SP5 56

57 PREEvision Installation and compatibility information Reference: For detailed information about the installation, update and migration of PREEvision, refer to the Operating Manual. System requirements Middleware license server login The following client system requirements have been changed: > Windows 8 is now supported. > Windows 10 is now supported. > Windows XP is no longer supported. > Tomcat 6 is no longer supported. For login to the middleware license server, a PREEvision user account with administration rights is now required. For login to the middleware license server, the PREEvision user account and password must be specified. The login of the stand-alone license server remains unchanged. Backup/restore and migration The following migration paths from PREEvision 7.0 to PREEvision 7.5 are supported with the mentioned restrictions: 2-tier to 2-tier migration from PREEvision 7.0 to 7.5 > without history (migration of latest model version only) 2-tier to 3-tier migration from PREEvision 7.0 to 7.5: > without history (migration of latest model version only) > must be carried out in two steps: 1. Technology change from 2-tier to 3-tier must be performed first (on PREEvision 7.0) 2. Afterwards, data migration from PREEvision 7.0 to 7.5 can be performed. 3-tier to 3-tier migration from PREEvision 7.0 to 7.5: > with or without history possible > improved performance of history migration Backup of 2-tier models from PREEvision 7.5 and restore to PREEvision 7.5 is only supported without history (last model version only). For backup/restore including history use a database dump instead. Vector Informatik GmbH Version 7.5 SP5 57

58 PREEvision 7.5 Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > the appropriate migration procedure if you are planning to switch the system from 2-tier to 3-tier > which PREEvision version shall be used for valid backup and restore. Compatibility 2-tier environments: The following table shows compatible client and database server script versions for specific PREEvision versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5/7.0 (2.0.13) 5.0.x read-only read-only read-only Database server version 6.5/7.0/7.5 (2.0.14) 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible not compatible compatible compatible from not compatible not compatible compatible 3-tier environments: In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same PREEvision version. Using a new client version on a previous server version or a previous client version on a new server version is not supported and may lead to data inconsistencies or data loss. Client version Server application version Database server script version Licenses and license server PREEvision workspace and PREEvision.ini Operating system: character set For PREEvision 7.5, new licenses are required. Existing workspaces from earlier PREEvision versions cannot be reused for PREEvision 7.5. Overwriting the PREEvision.ini is not allowed as well. Please do use an operating system with a full character set of your language. For example, in order to support Japanese in PREEvision, the Japanese operating system has to be installed. An English operating system with Japanese character set might not support all characters. As a consequence, this may result in displaying wrong characters in PREEvision. Vector Informatik GmbH Version 7.5 SP5 58

59 PREEvision New features Further information > Feature highlights > Requirements engineering > software, system and communication design > Communication design > Wiring harness design > Design of safety relevant systems > Product line engineering > > Usability improvements > Administration Complete support of Software Component Template Feature highlights PREEvision now fully supports the Software Component Template. Missing event types and artifacts to model internal behavior of software components have been added. Further new features are: > Import and export for > Customizable export of extracts beyond ECU and system extract, e.g. for bus or communication based extracts > Extended consistency checks for compliant modeling CAN Design according to SAE J1939 PREEvision supports the network protocol SAE J1939 for commercial vehicles including ISOBUS for forestry or agricultural tractors and implements. J1939 allows easy integration of tractors with engines, transmissions and implements. ISOBUS supports a unified and easy control of the additional equipment from the cockpit of the tractor. PREEvision is now ready to model and manage the increasing communication complexity of commercial vehicles: Vector Informatik GmbH Version 7.5 SP5 59

60 PREEvision 7.5 > Import and export of J1939 designs via DBC and > Extended multiplexing for CAN > Modeling of controller applications > compliant software and hardware network design > Dedicated editors Custom attributes PREEvision offers a new concept for customizable attributes. The former concept of different attributes for different layers with e.g. requirement attributes, diagnostic attributes or attributes for tests and tickets is replaced by this new concept, which is applicable in every layer. If there is an attribute missing for a special purpose, just one attribute for this demand can be created. The appearance and presentation of the new attributes in the property editor can be defined in an easy way. With this concept it is also possible to implement Special Data Groups (SDGs) including support of import and export. Vector Informatik GmbH Version 7.5 SP5 60

61 PREEvision 7.5 Additionally, custom attributes are supported for the DBC and KBL import and export. Change marker When working in the team it is crucial to be aware of any changes that were made by other team members or outside partners. The new change marker concept allows the easy and reliable identification of any changes made during development. No matter if an attribute, a value, a relation or even a hidden artifact has been changed. The change marker is a delta icon that is shown in the Model View, Property View and in tables. The change marker can easily be removed, either manually by the user or automatically via life cycle change or check-in. A change history is available for detailed information of the changes and offers a possibility to compare formatted texts. The benefits of the change marker at a glance: > Reliable tracking of all the changes made in the model > Fast and reliable identification of all the changes made in the model > Easier cooperation between OEM and supplier > Easy removing of change markers Scratchpad and merge The scratchpad is a safe working environment stored in the PREEvision database to find new solutions, because all the work done in the scratchpad is not immediately integrated into the bigger model context. In the scratchpad new artifacts can be designed and existing artifacts can be redesigned as copy or branch. The benefits of the scratchpad at a glance: > Fast and easy drag and drop to start sketching out ideas > Safe working environment to find new solutions > Easy merging of artifacts created in the scratchpad back to the model Vector Informatik GmbH Version 7.5 SP5 61

62 PREEvision 7.5 After finishing the design in the scratchpad the artifacts can be integrated into the bigger model context with the new merge functions. The new merge operation considers identities, attributes, relations and child artifacts and support six different merge strategies. Partial model support The partial model support of PREEvision provides a tailored view showing only dedicated parts of the entire PREEvision database model to the user. The model parts of interest are defined in the Scope Definition Perspective and only these model parts are delivered to the client of the user. This concept reduces resource needs of the client PC and hides unnecessary model complexity from the user. Vector Informatik GmbH Version 7.5 SP5 62

63 PREEvision 7.5 If partial model support is activated, the scope definition is a mandatory step after initial login to the client. When loading the E/E model for the first time or if no scope has been defined, the Scope Definition Perspective will be displayed. Within this perspective, the Model View only displays the package structure of the E/E model. To define and activate a scope, the following steps are necessary: 1. Select the packages to be included in the scope. 2. Drag them to the Project and Scope View and drop them on the project. A scope is created containing the selected packages and the Administration. 3. Select the scope, open the context menu and select Activate Scope. The scope is activated. When reconnecting to the project the scope will be automatically loaded. Vector Informatik GmbH Version 7.5 SP5 63

64 PREEvision 7.5 Use case diagram Requirements engineering Use case diagrams provide a user-centric perspective on a system by showing the intended functionality and the benefits of the system from the perspective of the users. They visualize the relations and dependencies between users and use cases. Use case diagrams are behavior diagrams and follow the Unified Modeling Language 2.0 (UML 2.0) specification. Available elements are: > Use cases > Use case systems > Actors > Include and extend relations > Extension points > Generalizations Additionally, a fulfillment association between Requirements, Customer Features and Use Cases is available. All general diagram features are also supported by use case diagrams. Use case diagrams can be created under any artifact in the Product Goals layer. RIF 1.2 import Support Excel import for customer features RIF 1.2 files can now be imported as Requirements, Customer Features or test artifacts. The RIF format (RIF 1.1a or RIF 1.2) is automatically recognized during the import without user interaction. The RIF configuration files have been extended. It is now possible to define settings for the Property View for the imported requirement attributes including: > the position, where the attributes page is shown in the categories list. > definition to show attributes as a list page and/or as a table. > definition of attribute grouping. The Product Goals import via Excel now also supports Customer Features. Vector Informatik GmbH Version 7.5 SP5 64

65 PREEvision 7.5 Configurable reports Comprehensive and flexible control of the reporting content is now possible. This allows creating single-source report templates which can be tailored to different audiences and depths during report generation. The report template defines: > the content and structure of the report > mandatory report sections > optional report sections which can be flexibly included/excluded in/from the report > additional parameters, e.g. the start and end date for generating charts For report generation, the sections/content to be included in the report can be selected and available parameters can be defined. The settings for report generation can be saved to a configuration file for later use. Vector Informatik GmbH Version 7.5 SP5 65

66 PREEvision import and export versions perspectives software, system and communication design import and export is now supported import and export is no longer supported. The predefined perspectives for have been simplified and the number has been reduced. packages packages are now supported for the roundtrip with other tools. Therefore, within the Library, a Virtual Package Root containing a Virtual Package structure can be created. By using the new Virtual Package structure it is possible to determine the package structure and content to be exported. On import, the package structure is imported in a Virtual Package structure with the same structure. New artifacts may be assigned to specific virtual packages. special data groups (SDG) special data groups are fully supported now including definition, editing, import and export. Vector Informatik GmbH Version 7.5 SP5 66

67 PREEvision 7.5 Configurable customized export The customized export can be preconfigured now. By using model queries, customer-specific extracts can be generated. Example: Export a "Cluster Extract" containing only communication content to protect the IP of the software. Support of system signal and system signal group Customer-specific propagation rules are executed during the customized export. The result is a customer-specific extract. For supporting communication fan-out scenarios it is possible to design SYSTEM-SIGNALs (System Signal) and I-SIGNALs (Signal) as well as SYSTEM-SIGNAL- GROUPs (System Signal Group) and I-SIGNAL-GROUPs (Signal Group). One System Signal has different I-Signals for the same bus for different receivers: One System Signal has different I-Signals for different buses: Vector Informatik GmbH Version 7.5 SP5 67

68 PREEvision 7.5 Vector Informatik GmbH Version 7.5 SP5 68

69 PREEvision Additional constraints for the signal router Communication design New constraints can be defined for the signal router. CAN: Support of frame with different frame ID on same bus Frame IDs for CAN bus systems can be flexibly configured considering the following use cases: > The same frame has different frame IDs on different bus systems. > The same frame has different frame IDs for different senders on the same bus system. CAN FD: Mode 2 and container IPDU concept Via 4.2.1, CAN FD Mode 2 (extended payload) is fully supported. With the introduction of the container IPDU, dynamic payload mapping, e.g. for CAN - CAN FD gateways, is now possible. Default values for meta model attributes Global default values for meta model attributes can be defined in the Administration. When creating a new artifact the default value is set and a default marker indicates that the current value is a default value and has not been changed by the user. Inconsistencies between default values of custom attributes, which are synchronized with PREEvision meta model attributes, can be avoided. Vector Informatik GmbH Version 7.5 SP5 69

70 PREEvision 7.5 Abstraction concept Wiring harness design In the ECU network and wiring harness design different user groups work on different abstraction levels together. These groups work in separated product lines, but need a possibility to link their artifacts. This is possible with the new abstraction relation. The abstraction relation is available for specific artifacts and is a "type-of" relation: > The abstract artifact is the "type". > The concrete artifacts are the "instances". The abstraction relation can be set on the Abstraction property page. Material data Materials are introduced in the library. Materials can be grouped into different categories (hierarchically). Each material can be described with its characteristics. Vector Informatik GmbH Version 7.5 SP5 70

71 PREEvision 7.5 Materials can be assigned to: > components > hardware parts > hardware types The classification of the materials at the instance is supported: Extensions for wiring harness router The routing behavior for cables has been changed: > The complete cable is no longer routed within the geometry. > Now, each core of a cable is routed within the geometry. Behavior of the routing of cable cores: > All cores are routed separately and parallel through the same segments. > Exception at the beginning and the end of a cable: Cable cores are allowed to be routed in different segments, but only after/before the last branch-off. Vector Informatik GmbH Version 7.5 SP5 71

72 PREEvision 7.5 KBL installation instructions The existing KBL import and export was extended to support KBL installation_instructions. No mapping to standard PREEvision attributes is possible as instruction types can be freely defined: > Import to and export from the newly introduced custom attributes. > For each instruction type an attribute definition is created in PREEvision. > Predefined attribute definitions in PREEvision can be used and will be recognized. Installation instruction values are stored at the artifact where the parent information (in KBL) is stored: Example: Connector occurrence with installation_instruction in KBL leads to Wiring Connector with attribute value for the defined instruction type. Hardware modules in diagram palette Hardware Module Types can be displayed in the palette of the Electric Circuit Diagram (extra section). Vector Informatik GmbH Version 7.5 SP5 72

73 PREEvision 7.5 Adding a new Hardware Module with the selected type to the diagram from the palette is possible. The icon, which is set on the type, is displayed in the palette and is used in the diagram. New refactoring The new refactoring Type change to EEComponent is available and supports the type change from a Wiring Harness Inline Connector to an EE-Component. Wiring harness and schematic diagram improvements The following diagram improvements are available: > Select all via <CTRL>+<A> > Move > Select and move in one action > Change routing option (e.g. from oblique to rectangular) > Placing and moving of components in Wiring Harness and Connector Template Diagram > Populate: no more loops and merging of overlapping edges > Permanently displaying fan area Vector Informatik GmbH Version 7.5 SP5 73

74 PREEvision 7.5 Vector Informatik GmbH Version 7.5 SP5 74

75 PREEvision Safety analysis: Fault tree analysis Design of safety relevant systems The following extensions have been made with regard to fault tree modeling: > Support of AND, OR, NOT and XOR gates > Improved visualization of gate symbols > House events with probability 0 or 1 > Reuse of Malfunctions with alias names > Support of variants of fault trees For the qualitative FTA, the following improvements have been introduced for performant calculation of minimal cut sets: > Cut off order can be defined > Quantitative importance is calculated > Results are structured in packages according to cut set order > Advanced highlighting for malfunctions included in minimal cut sets The following improvements have been introduced for the quantitative FTA: > Exponents of failure rate can be added easily Vector Informatik GmbH Version 7.5 SP5 75

76 PREEvision 7.5 > Calculation and diagram configuration considers unit of failure rate lambda > Improved visualization of failure rates and calculated probabilities in fault tree Safety requirements Other technology New artifact classes for safety requirements are supported: > Hardware Safety Requirements > Software Safety Requirements A new artifact class Other Technology has been introduced: > According to ISO26262 for description of technology different from E/E technologies (e.g. mechanical or hydraulic technology) > Supported in Component, Network, Electric Circuit and Wiring Harness Diagram Vector Informatik GmbH Version 7.5 SP5 76

77 PREEvision Reuse unit renamed to asset Product line engineering Reuse Unit has been renamed to Asset. All artifact classes, views and attributes have been renamed accordingly. Reuse of product lines Reuse of Product Lines is now possible if no checked-out Assets are contained in the Product Line. When trying to reuse a Product Line which contains checked-out Assets, an error will be displayed and the checked-out Assets will be displayed in the Information View. Improved roles and rights concept Concurrent model operations The roles and rights concept has been improved: > Only visible artifacts are transferred from the application server to the client. > Invisible artifacts are no longer transferred to the client. has been improved with regard to concurrent model operations: > The waiting time of client users for dedicated server actions has been reduced. > Model update operations of different users are running concurrently on the application server. > Commit operations of different users are running sequentially. > Parallel read operations during a write operation are possible. Vector Informatik GmbH Version 7.5 SP5 77

78 PREEvision Usability improvements Property view The following improvements have been introduced for the Property View: > In the Property View, recently visited pages are now highlighted by a light green background color. > The table sort mode has been removed. If table entries are sortable, the up/down buttons are always displayed in the table toolbar. > Drag and drop to the Property View has been improved. During the drop action only allowed target pages are displayed. > It is possible to define a grid layout for the Property View. In this way, properties can be displayed next to each other. > The quick search is now available in the Property View to search for attribute names and values. The quick search field can be displayed in the Property View via the button in the action bar or via the shortcut <CTRL>+<F>. Vector Informatik GmbH Version 7.5 SP5 78

79 PREEvision 7.5 Tables The following improvements have been introduced for table editors: > Columns can be grouped via table context menu Group Columns. Several groups can be defined. Groups can be configured in the Add/Remove/Reorder Columns dialog. > Predefined column filters are persisted. All filter options are displayed. In this way, a simple change of the filter options is now possible. > Table filters can be defined directly in the table editor via table context menu Filter. Tables: Copy and paste behavior The copy and paste behavior of multi-selections in tables has been improved: > Discontiguous values can be pasted without empty cells. > Only contiguous values from different columns can be copied. > A preference is available to define if empty values overwrite existing values. > The paste action is only performed for the visible area. The tree is not automatically expanded. > The paste action is automatically aborted, when a read-only cell is reached. Vector Informatik GmbH Version 7.5 SP5 79

80 PREEvision 7.5 > The paste action is available for a selected cell range: > Case 1: If the target quantity is smaller than copied values: paste only into target range. > Case 2: If the target quantity is bigger than copied values: paste with repetition. Tables: Chart wizard Creation of charts for tables is now supported via wizard. The underlying ODT template is created automatically. Several charts and ODTs can be defined. For configuring the chart, predefined filters and aggregation functions are available. Copy and special paste In addition to the universal paste behavior, a customized behavior is needed, for example, to paste the structure of a copied Requirement Package and reuse all leaf artifacts. Therefore, a custom paste action can be defined for a meta class via a new metric executor (Metric Executor Paste). This allows to define which relations are to be copied (default: all external relations are copied) and whether the new Relation Editor should be opened or not. The Relation Editor can also be manually opened by the user via context menu Open with Relation Editor to view and detach relations. If a metric for a special paste action has been configured, it can be selected in the context menu, the drag and drop menu or via the Special Paste dialog (shortcut <CTRL> +<SHIFT>+<V>). The Special Paste dialog offers all paste actions for the selected meta class. Vector Informatik GmbH Version 7.5 SP5 80

81 PREEvision 7.5 The standard paste action is still available and unchanged. Automatic grouping folders Artifacts can be automatically grouped in folders. The grouping algorithm can be configured in the object configuration (Grouping Folder). Unique attribute values Server-side consistency checks Uniqueness checks and unique ID generation has been introduced. Uniqueness checks can be implemented to check whether an attribute value, entered by the user, is unique, e.g. the name of an ECU shall be unique. Furthermore, it is possible to generate short unique IDs that are compliant to a customer-defined pattern. For example, human readable IDs for Tickets or Requirements can be defined. Uniqueness is ensured for the current model including the history of the current model. Attribute values which are not unique cannot be committed and have to be changed for being able to perform a commit. Uniqueness checks and ID generation are configured within the model and can be applied to customer-defined meta classes and attributes. Server-side consistency checks have been introduced to: > improve performance, > enable uniqueness checks and > ensure consistency checks are executed on the complete model, even if only a partial model is loaded in the client. Vector Informatik GmbH Version 7.5 SP5 81

82 PREEvision 7.5 Online checks are executed on client side during runtime and on server side before a commit operation. Findings reported by the online check are highlighted in the Model View and displayed in the E/E Online Check view. Online check results are also associated to the corresponding artifacts and are displayed on the Online Checks property page of the artifact. Automatically creating and arranging diagrams The highlighting of online check findings in the Model View has been adapted as follows: > Artifacts with a finding are indicated by a colored decorator according to the severity. > Artifacts without a finding, but containing a child artifact with a finding are indicated by a grey decorator. Online checks are automatically initialized on the server. For existing E/E models, the action Administration Execute Online Checks on whole model has to be executed once by an administrator in order to create the finding associations. It is possible to ignore online check findings for a specific artifact or meta class. In this case, the finding association is still set but the finding is no longer displayed in the Model View and the E/E Online Check view. PREEvision now provides a possibility to automatically create, arrange and refactor diagrams. With the help of metrics, diagrams can be automatically created and arranged according to a predefined layout. In this way, for example, it is possible to quickly create a new diagram for a large number of newly imported artifacts or to rearrange an existing diagram. Vector Informatik GmbH Version 7.5 SP5 82

83 PREEvision 7.5 Artifact picker Diagram handling Extensions for editors The Assistance View has been renamed to Artifact Picker. The following improvements have been made for the Artifact Picker: > A navigation bar (breadcrumbs) is displayed within the Artifact Picker to show the parent hierarchy of a selected artifact. > The type-ahead filter now also works for trees. > From the Property View, the Artifact Picker can also be opened for drop-down lists. The following improvements have been introduced for the general diagram handling: > Artifact Pickers can now be configured for diagrams. The definition of the Artifact Picker is attached to the Diagram Configuration. Direct drag and drop from the Artifact Picker to the diagram is supported. > Reusing an artifact in the current workspace and inserting it into a diagram can now be performed in one step via <SHIFT> and drag and drop. > Formatting of number is now possible in the label configuration. For example, it can be configured to display no decimal digit for the segment length in a Geometry Diagram. By default, no decimal digit is displayed if the value does not have one. The decimal digits can be configured in the label configuration, e.g. to display two decimal digits: {0,number,#.00}; to display the value as defined in the attribute field: {0}. > The populate behavior has been aligned. <F8> opens the Populate dialog on all diagrams now. The selected populate options are stored for each diagram type. A new editor reference type Default To Command-ID Reference has been introduced which allows to register further (third party) editors for an artifact class. Registered editors are available in the Open with context menu. Optionally, it is possible to configure the editor to be opened via double click on the registered artifact class. Vector Informatik GmbH Version 7.5 SP5 83