Release Notes. PREEvision. Version 6.5 SP14 English

Transcription

1 Release Notes PREEvision Version 6.5 SP14 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 2015, Vector Informatik GmbH. Printed in Germany. All rights reserved.

3 Contents Contents 1 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 15 2 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 25 3 PREEvision 6.5 SP Version numbers Installation and compatibility information New features Fixed issues Common Diagrams and tables AUTOSAR System software architecture Hardware architecture Product line management Metrics and reports Collaboration Administration Authority Backup Known issues 41 4 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 49 5 PREEvision 6.5 SP Version numbers Installation and compatibility information 53 Vector Informatik GmbH Version 6.5 SP14-3 -

4 Contents 5.3 Fixed issues Common Diagrams and tables Product Goals Logical Function AUTOSAR System Software Communication Hardware Product Line Management Reports Collaboration Administration Known issues 62 6 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 70 7 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 76 8 PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues 83 9 PREEvision 6.5 SP Version numbers Installation and compatibility information Changes Fixed issues Common Diagrams and tables Product Goals Logical Function AUTOSAR System Software Hardware Version 6.5 SP14 Vector Informatik GmbH

5 Contents Geometry Communication Product Line Management Metrics and reports Collaboration Administration, authority, license, installation and migration Known issues PREEvision 6.5 SP Version numbers Installation and compatibility information Fixed issues Known issues PREEvision 6.5 SP Version numbers Installation and compatibility information New features Fixed issues Common Tables Logical Function System Software Hardware Geometry Communication Product Line Management Rules, metrics and reports Collaboration Administration, authority and migration Known issues PREEvision 6.5 SP Version numbers Installation and compatibility information New features Fixed issues Common Diagrams and tables Product Goals Logical Function System Software Hardware Geometry Communication Product line management Change management Metrics and reports 132 Vector Informatik GmbH Version 6.5 SP14-5 -

6 Contents Collaboration Administration, installation and migration Known issues PREEvision 6.5 SP Version numbers Installation and compatibility information New features Fixed issues Common Diagrams and tables Product Goals Logical Function System Software Hardware Geometry Communication Product Line Management Rules, metrics and reports Collaboration Administration, authority, license, installation and migration Known issues PREEvision Version numbers Installation and compatibility information New features Fixed issues Common Diagrams and tables Product Goals Logical Function System Software and AUTOSAR Hardware Communication Product Line Management Rules, metrics and reports Collaboration Administration, license, installation and migration Known issues Version 6.5 SP14 Vector Informatik GmbH

7 PREEvision 6.5 SP14 1 PREEvision 6.5 SP14 This chapter contains the following information: 1.1 Version numbers Installation and compatibility information Fixed issues Known issues 15 Vector Informatik GmbH Version 6.5 SP14-7 -

8 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

9 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Update licenses on middleware license server (3-tier only) Backup/restore and migration With PREEvision 6.0 SP13, a new version of the middleware license server is included in the PREEvision server application. When using the middleware license server, licenses have to be uploaded again with the following procedure: 1. Stop the application server (e.g. during the update of the PREEvision server application). 2. Switch to the license-db folder (e.g. under Tomcat in Tomcat/work/ Catalina/localhost\vCollab or in the specified license path in the Java settings). 3. Delete the *.lic files. 4. Start the application server. 5. Upload the licenses via the client again to the server. The license to user assigments (namedusersforlicenses configuration file) should still be valid. The following migration paths from PREEvision 6.5 to PREEvision 7.0 are supported with the mentioned restrictions: Vector Informatik GmbH Version 6.5 SP14-9 -

10 PREEvision 6.5 SP14 2-tier to 2-tier migration from PREEvision 6.5 to 7.0 > without history (migration of latest model version only) > with standard performance 2-tier to 3-tier migration from PREEvision 6.5 to 7.0: > without history (migration of latest model version only) > with standard performance > must be carried out in two steps: 1. Technology change from 2-tier to 3-tier must be performed first (on PREEvision 6.5) 2. Afterwards, data migration from PREEvision 6.5 to 7.0 can be performed. 3-tier to 3-tier migration from PREEvision 6.5 to 7.0: > with or without history possible > improved performance of history migration Backup of 2-tier models from PREEvision 6.5 and restore to PREEvision 6.5 is only supported without history (last model version only). For backup/restore including history use a database dump instead. 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 architecture from 2-tier to 3-tier > which PREEvision version shall be used for valid backup and restore. 3-tier migration from PREEvision 6.5 to PREEvision 6.5 and PREEvision 7.0 Migration to PREEvision tier database server version For the following 3-tier migration scenarios the specific parameter DenableDeltaMofForBackup must be set in the PREEvision.ini file for creating a micro delta backup. > PREEvision 6.5 to PREEvision 6.5 > DenableDeltaMofForBackup=false or > The parameter need not be set at all > PREEvision 6.5 to PREEvision 7.0 > DenableDeltaMofForBackup=true PREEvision 6.5 SP14 should be used for migrating to PREEvision 7.0. With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version ). Existing 2-tier database servers must be updated to version The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible Version 6.5 SP14 Vector Informatik GmbH

11 PREEvision 6.5 SP14 Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. Backup and restore from 2-tier to 2-tier and from 2-tier to 3-tier is only supported for the last model version (without history). For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. 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 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 6.5 versions: Vector Informatik GmbH Version 6.5 SP

12 PREEvision 6.5 SP14 Client version Server application version Database server script version (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Version 6.5 SP14 Vector Informatik GmbH

13 PREEvision 6.5 SP14 Reference: For detailed information, refer to the Operating Manual. Further information > Fixed issues Vector Informatik GmbH Version 6.5 SP

14 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP14 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models Exceptions after lock or commit actions in diagrams have been corrected It is now possible to create a reuse of an artifact which has been replaced from history before The handling of exceptions, which may result from network errors, has been improved Using the provided SQL script, erroneous data can be repaired An action in context of handling Requirements has been changed to support automatic locking Error handling has been improved to prevent incomplete data to get into the database after an error occurred (e.g. due to a network outage). Additionally, there is an SQL file available to repair the incomplete deleted artifacts Sporadic failures on dongle evaluation have been fixed. Diagram Product line management Collaboration Collaboration Collaboration Collaboration License Version 6.5 SP14 Vector Informatik GmbH

15 PREEvision 6.5 SP Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Delete action not available ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. Vector Informatik GmbH Version 6.5 SP

16 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

17 PREEvision 6.5 SP13 2 PREEvision 6.5 SP13 This chapter contains the following information: 2.1 Version numbers Installation and compatibility information Fixed issues Known issues 25 Vector Informatik GmbH Version 6.5 SP

18 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

19 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Update licenses on middleware license server (3-tier only) Backup/restore and migration With PREEvision 6.0 SP13, a new version of the middleware license server is included in the PREEvision server application. When using the middleware license server, licenses have to be uploaded again with the following procedure: 1. Stop the application server (e.g. during the update of the PREEvision server application). 2. Switch to the license-db folder (e.g. under Tomcat in Tomcat/work/ Catalina/localhost\vCollab or in the specified license path in the Java settings). 3. Delete the *.lic files. 4. Start the application server. 5. Upload the licenses via the client again to the server. The license to user assigments (namedusersforlicenses configuration file) should still be valid. The following migration paths from PREEvision 6.5 to PREEvision 7.0 are supported with the mentioned restrictions: Vector Informatik GmbH Version 6.5 SP

20 PREEvision 6.5 SP13 2-tier to 2-tier migration from PREEvision 6.5 to 7.0 > without history (migration of latest model version only) > with standard performance 2-tier to 3-tier migration from PREEvision 6.5 to 7.0: > without history (migration of latest model version only) > with standard performance > must be carried out in two steps: 1. Technology change from 2-tier to 3-tier must be performed first (on PREEvision 6.5) 2. Afterwards, data migration from PREEvision 6.5 to 7.0 can be performed. 3-tier to 3-tier migration from PREEvision 6.5 to 7.0: > with or without history possible > improved performance of history migration Backup of 2-tier models from PREEvision 6.5 and restore to PREEvision 6.5 is only supported without history (last model version only). For backup/restore including history use a database dump instead. 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 architecture from 2-tier to 3-tier > which PREEvision version shall be used for valid backup and restore. 3-tier migration from PREEvision 6.5 to PREEvision 6.5 and PREEvision 7.0 Migration to PREEvision tier database server version For the following 3-tier migration scenarios the specific parameter DenableDeltaMofForBackup must be set in the PREEvision.ini file for creating a micro delta backup. > PREEvision 6.5 to PREEvision 6.5 > DenableDeltaMofForBackup=false or > The parameter need not be set at all > PREEvision 6.5 to PREEvision 7.0 > DenableDeltaMofForBackup=true PREEvision 6.5 SP13 should be used for migrating to PREEvision 7.0. With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version ). Existing 2-tier database servers must be updated to version The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible Version 6.5 SP14 Vector Informatik GmbH

21 PREEvision 6.5 SP13 Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. Backup and restore from 2-tier to 2-tier and from 2-tier to 3-tier is only supported for the last model version (without history). For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. 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 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 6.5 versions: Vector Informatik GmbH Version 6.5 SP

22 PREEvision 6.5 SP13 Client version Server application version Database server script version (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Version 6.5 SP14 Vector Informatik GmbH

23 PREEvision 6.5 SP13 Reference: For detailed information, refer to the Operating Manual. Vector Informatik GmbH Version 6.5 SP

24 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP13 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models It is now possible to save perspectives in case of active Property Editor filter definition mode The field "Value" in the Property View does not disappear anymore when changing the Application Data Type of an EE attribute. Common Common Model export is working properly again. Common Saving a model will not lead into a dead lock anymore Shortcut menu of ECU now shows correct entries in diagram when scope is activated Save and export are possible again for file projects Logical Function ports in Interface Assignment Diagrams are now placed as expected (required ports on the left side, provided ports on the right side) DBC import: The standard value for the preconfigured DBC-File-CharSet has changed from "default" to "guess" Problems with the populate function on Single wires have been resolved, so that they can be executed on Wires again Special characters are now displayed correctly in metric editor The error message in case of lock conflicts has been adapted to provide more detailed information. In addition, special entries in the Information View are available now for artifacts not locked Fixed calculation to release outdated licenses to avoid a false release of a borrowed license. Common Common Common Logical function architecture Communication Hardware architecture Metrics Collaboration Administration Version 6.5 SP14 Vector Informatik GmbH

25 PREEvision 6.5 SP Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Delete action not available ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. Vector Informatik GmbH Version 6.5 SP

26 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

27 PREEvision 6.5 SP12 3 PREEvision 6.5 SP12 This chapter contains the following information: 3.1 Version numbers Installation and compatibility information New features Fixed issues 37 Common 37 Diagrams and tables 37 AUTOSAR 38 System software architecture 38 Hardware architecture 38 Product line management 38 Metrics and reports 39 Collaboration 39 Administration 40 Authority 40 Backup Known issues 41 Vector Informatik GmbH Version 6.5 SP

28 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

29 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. 3-tier migration from PREEvision 6.5 to PREEvision 6.5 and PREEvision 7.0 Migration to PREEvision 7.0 For the following 3-tier migration scenarios the specific parameter DenableDeltaMofForBackup must be set in the PREEvision.ini file for creating a micro delta backup. > PREEvision 6.5 to PREEvision 6.5 > DenableDeltaMofForBackup=false or > The parameter need not be set at all > PREEvision 6.5 to PREEvision 7.0 > DenableDeltaMofForBackup=true PREEvision 6.5 SP12 should be used for migrating to PREEvision 7.0. Migration to PREEvision Caution: When using PREEvision or older releases of PREEvision, Vector identified the risk of unintended delete actions and successive loss of modeling data under certain prerequisites. The risk only exists when working with the PREEvision 2-tier Collaboration Platform and when PREEvision clients with different licenses (e.g. PREEvision Architect and PREEvision Electric Designer) are accessing the same project. The risk also exists when a roles and rights concept is defined in the PREEvision authority model and used. The issue has been corrected in PREEvision (see issue in chapter Fixed issues). Vector strongly recommends to all customers to migrate to PREEvision when the above mentioned circumstances are given and to contact the Vector support if necessary. 2-tier database server version With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version ). Existing 2-tier database servers must be updated to version The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible Vector Informatik GmbH Version 6.5 SP

30 PREEvision 6.5 SP12 Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. 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 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 6.5 versions: Client version Server application version Database server script version Version 6.5 SP14 Vector Informatik GmbH

31 PREEvision 6.5 SP12 Client version Server application version Database server script version (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. Vector Informatik GmbH Version 6.5 SP

32 PREEvision 6.5 SP New features Anonymization of database models for 2-tier and 3-tier environments With PREEvision 6.5 SP12 it is possible to anonymize database projects for 2-tier as well as 3-tier environments. By means of this feature sensitive productive data can be anonymized and provided to Vector for a better analysis and reproducibility of model dependent defects. Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new feature of anonymizing database models. Anonymization of 2- tier database model copies With PREEvision 6.5 SP12 it is possible to create anonymized copies of database projects for 2-tier environments. During the anonymize process, a copy of the selected database model will be created in the database and anonymized. Rich texts and files will not be copied. Since the model copy requires additional tablespace, sufficient tablespace and undo tablespace must be available in the database. During the copy operation the database model is in administrative mode. During this time no access to the model is possible for other users. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize Model or via the corresponding icon in the toolbar. For the model to be copied and anonymized a new name can be specified or the predefined model name be kept Version 6.5 SP14 Vector Informatik GmbH

33 PREEvision 6.5 SP12 Depending on the model size the operation may take a longer period of time. During this time no other user has access to the model to be copied and anonymized. Anonymization of 3- tier database models With PREEvision 6.5 SP12 it is possible to create anonymized database projects for 3-tier environments. Caution: Take into account that a 3-tier database project anonymization must never be carried out on a productive system. Instead a test system is strictly recommended. Preconditions for anonymization of database projects > Productive system and test system: > Besides the productive system an equivalent test system must be available, i.e. identical infrastructure concerning software versions of Oracle database server, SVN and application server. > Oracle database administrator required: > An experienced Oracle database administrator is required on customer side to carry out a database export of the productive system and import into the test system. > Files: > A copy of the SVN repository data from productive to test system is not required. > Files will not be considered by the anonymization process. Preliminary steps before anonymization Vector Informatik GmbH Version 6.5 SP

34 PREEvision 6.5 SP12 To prepare the anonymization process, first create a copy of the productive system 1. Stop the application server of the test system. This step can be carried out by a PREEvision administrator. 2. Carry out a data dump export of the productive system and import it into the test system. This step should be carried out by an experienced Oracle database administrator. 3. Start the test system. Anonymization of database projects on the test system The anonymization of database projects is carried out on the test system Version 6.5 SP14 Vector Informatik GmbH

35 PREEvision 6.5 SP12 1. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize selected Model(s) or via the corresponding icon in the toolbar. Note: Take into account that if the authority model is selected for anonymization it will no longer be possible to log on to other models after anonymization to check the result of the anonymization. 2. Once starting the anonymization, take into account that the anonymization cannot be undone. A corresponding warning is displayed. Vector Informatik GmbH Version 6.5 SP

36 PREEvision 6.5 SP12 3. Confirm the warning by entering your password and the anonymization will be started. After anonymization the resulting anonymized project(s) can be directly checked on the test system client. Before checking the anonymized project(s), however, the client cache needs to be cleared. Note: As a recommendation you may check the result of the anonymized project(s) in the Model Query Rules perspective, for example. Other configured model perspectives do not function properly after anonymization since the configuration files required for these perspectives are not considered by the anonymization process. 4. As a last step, carry out a data dump export of the test system. This step should be carried out by an experienced Oracle database administrator again Version 6.5 SP14 Vector Informatik GmbH

37 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP12 You will find the important fixed issues in the following tables. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > AUTOSAR > System software architecture > Hardware architecture > Product line management > Metrics and reports > Collaboration > Administration > Authority > Backup Common The correct parent/interface information of Ports is now shown in the Property View of Assembly Software Connectors A mechanism for a reset of a corrupt Property model has been implemented. All property pages are available again Structured generic attributes (generic attributes below generic attributes) will now be displayed in the Model View After changing a column width of tables in the Property View the defined width is persisted for the current client session. Common Common Common Common Diagrams and tables Text boxes inserted from the Documentation diagram palette into a diagram can be moved and resized in all directions again The sorting of the main columns in table editors now works properly. Diagrams Tables Vector Informatik GmbH Version 6.5 SP

38 PREEvision 6.5 SP AUTOSAR AUTOSAR import: The update of Software Component Types works even if the.arxml file only contains Composition Types AUTOSAR import: The large memory usage for the Update SW Component Type operation was reduced. The problem was fixed AUTOSAR import: For not supported AUTOSAR versions during import a corresponding message will be written to the Information View. If possible, the file will be imported anyway. AUTOSAR AUTOSAR AUTOSAR System software architecture When connecting ports in a Software System Diagram, the assigned Interface Assignments will be kept, now. System software architecture Hardware architecture It is now possible to create single wires between ports in a Wiring System Diagram without a master if there is no active workspace set. A workspace dialog will now be opened which prompts for a suitable package. Hardware architecture Product line management For selection of an variant the performance has been improved (by using the table editor framework). Product line management Version 6.5 SP14 Vector Informatik GmbH

39 PREEvision 6.5 SP Metrics and reports Metrics are compiled after JAR file exchange and clearing caches to prevent compile errors. Metrics Collaboration Shared and exclusive locks of foreign users are propagated for checked-in reuses, now The missing/lost attribute values have been recreated. It is possible again to commit a new check-out together with a new reuse of checked out artifacts The autosave mechanism has been improved. The autosave first writes into the temp directory, then the content of this temp directory is moved to the final autosave directory. The read and write accesses on the relevant directory during autosave are synchronized. This way it is prevented that two autosaves executed in parallel are working on the same data. Even if an exception occurs during autosave because the user is changing the model, the delta is not copied into the final directory. Collaboration Collaboration Collaboration Commit with shared lock is possible, now. Collaboration Lock operation on server corrected. If a lock is requested for an invisible artifact, the lock is granted and not silently ignored Lock operations work correctly now. Commit is also possible , , The server caches the authority restrictions now, not only by role but by role and feature IDs Life cycle and ownership icons are now drawn correctly and without errors even if their size is in one dimension too large for the possible 16x16 pixel area. Collaboration Collaboration Collaboration Collaboration Vector Informatik GmbH Version 6.5 SP

40 PREEvision 6.5 SP Administration In case of short network interrupts, the release of a borrowed license on the middleware license server was stabilized Rollback model version now uses the correct methods to reinitialize the middle tier after the rollback. Administration Administration Authority When a user tries to delete an artifact which has type of and reuse unit relations, the read access of relation ends is checked and the delete action denied. Authority Backup Missing local reuse sequence numbers are created at backup procedure. Backup Version 6.5 SP14 Vector Informatik GmbH

41 PREEvision 6.5 SP Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Delete action not available ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. Vector Informatik GmbH Version 6.5 SP

42 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

43 PREEvision 6.5 SP11 4 PREEvision 6.5 SP11 This chapter contains the following information: 4.1 Version numbers Installation and compatibility information Fixed issues Known issues 49 Vector Informatik GmbH Version 6.5 SP

44 PREEvision 6.5 SP Version numbers Version numbers Application PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Version number Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

45 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Migration to PREEvision Caution: When using PREEvision or older releases of PREEvision, Vector identified the risk of unintended delete actions and successive loss of modeling data under certain prerequisites. The risk only exists when working with the PREEvision 2-tier Collaboration Platform and when PREEvision clients with different licenses (e.g. PREEvision Architect and PREEvision Electric Designer) are accessing the same project. The risk also exists when a roles and rights concept is defined in the PREEvision authority model and used. The issue has been corrected in PREEvision (see issue in chapter Fixed issues). Vector strongly recommends to all customers to migrate to PREEvision when the above mentioned circumstances are given and to contact the Vector support if necessary. Migration to PREEvision tier database server version PREEvision 6.5 SP11 should be used for migrating to PREEvision 7.0. With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version ). Existing 2-tier database servers must be updated to version The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C during client installation During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. Vector Informatik GmbH Version 6.5 SP

46 PREEvision 6.5 SP11 Database access rights Restore parameters Migration to a 3-tier environment The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. 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 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 6.5 versions: Client version Server application version Database server script version (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) Version 6.5 SP14 Vector Informatik GmbH

47 PREEvision 6.5 SP11 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. Vector Informatik GmbH Version 6.5 SP

48 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP11 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models The model import does not abort when new UUIDs are generated The NullPointerException which occurred when opening the property page Mappings for ECUs does not occur any more It is now possible to open the LibreOffice editor for rich texts of attributes of checked in artifacts. The LibreOffice editor can be opened via <Ctrl+O>. Additionally, a corresponding button to open the editor is also available in the attribute cells of table based editors A lock is possible, if another user has locked several sub packages, which are reused in the main package A commit after tree lock of a parent of a not visible artifact does not delete the artifact any more The error that caused the loss of formatting in generated reports under certain circumstances has been fixed The actual problem occurred in the backup and restore of The problem was fixed with the following backup and restore scenario: Backup tier. Restore with tier works properly. The subsequent backup tier also works properly. Common Common Common Collaboration Collaboration Reports Backup Version 6.5 SP14 Vector Informatik GmbH

49 PREEvision 6.5 SP Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Delete action not available ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. Vector Informatik GmbH Version 6.5 SP

50 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

51 PREEvision 6.5 SP9 5 PREEvision 6.5 SP9 This chapter contains the following information: 5.1 Version numbers Installation and compatibility information Fixed issues 56 Common 56 Diagrams and tables 57 Product Goals 58 Logical Function 58 AUTOSAR 58 System Software 59 Communication 59 Hardware 60 Product Line Management 60 Reports 60 Collaboration 61 Administration Known issues 62 Vector Informatik GmbH Version 6.5 SP

52 PREEvision 6.5 SP9 5.1 Version numbers Version numbers Application PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Version number Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

53 PREEvision 6.5 SP9 5.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Migration to PREEvision 7.0 New 2-tier database server version PREEvision 6.5 SP9 should be used for migrating to PREEvision 7.0. With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version ). Existing 2-tier database servers must be updated to version The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible not compatible compatible compatible from not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Vector Informatik GmbH Version 6.5 SP

54 PREEvision 6.5 SP9 Reference: For detailed information about the migration, refer to the Operating Manual. 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 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 6.5 versions: Client version Server application version Database server script version (update is optional; installation script for Linux fixed) (update is optional; installation script for Linux fixed) 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. Execution of LibreOffice managed by PREEvision To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged Version 6.5 SP14 Vector Informatik GmbH

55 PREEvision 6.5 SP9 Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. Vector Informatik GmbH Version 6.5 SP

56 PREEvision 6.5 SP9 5.3 Fixed issues Fixed issues in PREEvision 6.5 SP9 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. > Common > Diagrams and tables > Product Goals > Logical Function > AUTOSAR > System Software > Communication > Hardware > Product Line Management > Reports > Collaboration > Administration Common , , Use case form pages keep their size after setting attribute values. Use case form pages keep the current selection within drop-down lists after the page is refreshed (e.g. after executing an action) Formatted texts are saved when closing the model even if the placeholder preview is currently active When switching between navigation and property views in use case perspectives, views are no longer shown twice Use case form pages keep the current content of combo boxes after a lock After switching the perspective, navigation views of use case form pages are shown correctly Changing the description of a hidden label no longer resets the object and label configuration Deactivating the placeholder preview for formatted texts no longer causes a LibreOffice crash. Common Common Common Common Common Common Common Common Version 6.5 SP14 Vector Informatik GmbH

57 PREEvision 6.5 SP On the Context Artifacts property page of a Model Context, the assigned artifacts are displayed in the Context Artifacts table even if they do not have an own Name attribute The table view for mappings can be now opened from the Property View without error Within the Select Workspace dialog, packages are sorted as in the Model View If the LibreOffice editor is opened for a formatted text of a table cell, changes are stored in the correct artifact now Within formatted texts it is now possible to set the style "Strikethrough" and to save graphics (shortcut menu Save Graphic...). Common Common Common Common Common Diagrams and tables Artifacts can be moved to a desired position in 5x5 grid diagrams Waypoints within sections of diagrams move correctly when the section is being enlarged or moved Moving sections within diagrams works correctly now without affecting the layout of connections Labels on conditions are now displayed in all diagrams Tables are automatically refreshed after creating artifacts Sorting a table column no longer creates empty cells in other table columns If multiple cells of a table are edited at once none-editable artifacts remain unchanged , Copy and paste of (multiple) attribute values from Excel to tables works as expected Tables always show the same content regardless of whether they are opened via Open With or created via New. Diagrams Diagrams Diagrams Diagrams Tables Tables Tables Tables Tables Vector Informatik GmbH Version 6.5 SP

58 PREEvision 6.5 SP Product Goals Requirements are now sorted correctly by their ID if a file package has been created in the same sub folder , Moving Requirements or Requirement Packages before or after checked-in Requirements or Requirement Packages works correctly now Requirements are sorted correctly after copy and paste in the Model View. Product Goals Product Goals Product Goals Logical Function On the General property page of Logical Domains, it is now possible to navigate to the associated Logical Domain Type Fans are now available in the Logical System Diagram. Logical Function Logical Function AUTOSAR The AUTOSAR import works with *.eea files as well During AUTOSAR import, merging errors caused by AUTOSAR- CanTpConnectionChannel are resolved During AUTOSAR import, ECUs are no longer merged if in the AUTOSAR import file a CanTpConnectionChannel references several CommunicationConnectors which belong to different ECUs During AUTOSAR import (3.x and 4.x), only Micro Processors are created without a Process Unit. AUTOSAR AUTOSAR AUTOSAR AUTOSAR Version 6.5 SP14 Vector Informatik GmbH

59 PREEvision 6.5 SP System Software In the SWC System Editor, Data Elements are shown on assembly nets The Integrate into new Composition refactoring of the System Software has been corrected. If there is one provided port in the refactored assembly, then the port of the created Composition will be also a provided port In the Software Instance Diagram, the Pull up refactoring has been corrected. A delegation port is changed to a Receiver Port, if there is only one Sender Port and this port is pulled up Fixed Assembly SW Connector over Delegation Port / Port Prototype after moving an Atomic SW Component into a Composition or from a Composition to a higher hierarchy level In the Software Instance System Diagram, editing an assembly bus is possible again via the Edit bus dialog. System Software System Software System Software System Software System Software Communication The numerical format for exporting custom communication attributes to DBC has been corrected The signal router corrects wrong sending/ receiving relations on the ECU Interface, if they are wrong or no longer existing In the frame synthesis dialog, Communication packages located in Product Line Package hierarchies can be selected The commit performance after a DBC import with merge has been improved During DBC export, attribute values of Signals, Messages, etc. of type double are written as long expression without exponential short term The Create Gateway option of the DBC import works if there are LA Mappings on Signal Transmissions. These mappings are ignored. Communication Communication Communication Communication Communication Communication The Signal Router Metric Block works again. Communication Vector Informatik GmbH Version 6.5 SP

60 PREEvision 6.5 SP Hardware In the Electric Circuit Diagram, the function Show path to energy source works and shows the current path from the selected hardware component to the current source The KBL export no longer produces an empty file, an error in the transformation has been fixed The "Splice Optimizer" metric has been corrected and now returns results if the pin hit count ("MaxHitCount") is set to When creating a Schematic Connection via the wizard in the network layer, "<default>" can be selected to apply default naming conventions Committing the model (2-tier) is possible, after refactoring of Single Wire to Conductor under a new Cable artifact. Hardware Hardware Hardware Hardware Hardware Product Line Management 32614, Bus and assembly nets are greyed out if variant highlighting identifies one artifact in the bus system or the assembly net which is not contained in the active variant Variant highlighting also works for delegation ports on logical bus systems. Product Line Management Product Line Management Reports Static columns are no longer resized when generating reports with dynamic tables Generating reports on a historic model version works correctly now Style placeholders are correctly applied in reports now Paragraph styles are correctly applied to entire description if a conditional placeholder is set. Reports Reports Reports Reports Version 6.5 SP14 Vector Informatik GmbH

61 PREEvision 6.5 SP Performance of report generation has been improved Placeholders are checked before rendering a report. Associated log entries in the Information View have been improved to show more precisely which placeholder is wrong. A warning dialog is shown before opening a report if errors have been found. Reports Reports Collaboration The master database synchronization can now be executed without error messages and correctly synchronizes the object label configuration Creating a reuse of a container and, in the same commit, a local reuse of a child of this container, works correctly now. A subsequent check-out of the child no longer causes a commit error The mechanism to ensure data consistency for non-versioned artifacts during database restore is applied to revisions and valid reuses as well The middle-tier server now can handle corrupt legacy data during database restore where reuses are out of synchronization. Collaboration Collaboration Collaboration Collaboration Administration Initialization with the default setup (administration only) after a KBL export or import takes 2 minutes Initialize Project with File... is possible with a migrated model from PREEvision 5.5. Administration Administration Vector Informatik GmbH Version 6.5 SP

62 PREEvision 6.5 SP9 5.4 Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Delete action not available ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client Version 6.5 SP14 Vector Informatik GmbH

63 PREEvision 6.5 SP9 Vector Informatik GmbH Version 6.5 SP

64 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

65 PREEvision 6.5 SP8 6 PREEvision 6.5 SP8 This chapter contains the following information: 6.1 Version numbers Installation and compatibility information Fixed issues Known issues 70 Vector Informatik GmbH Version 6.5 SP

66 PREEvision 6.5 SP8 6.1 Version numbers Version numbers Application PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Version number Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

67 PREEvision 6.5 SP8 6.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Migration to PREEvision 7.0 Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment PREEvision 6.5 SP8 should be used for migrating to PREEvision 7.0. During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP8 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 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 6.5 versions: Client version Server application version Database server script version Vector Informatik GmbH Version 6.5 SP

68 PREEvision 6.5 SP8 Client version Server application version Database server script version (update is optional; installation script for Linux fixed) 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

69 PREEvision 6.5 SP8 6.3 Fixed issues Fixed issues in PREEvision 6.5 SP8 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models Formatted texts are no longer rewritten when creating a reuse, since they already exist on the source artifact. Thus, a commit error has been fixed which occurred when creating reused Requirements via a metric , , Refactorings with delete operations as well as diagram changes no longer cause multiple root artifacts in the internal delta model. Thus, the subsequent commit error has been fixed The Linux installation script for the database has been corrected and references the script create_pv.sql now Formatted texts with an invalid file ID are now correctly handled during 3-tier backup creation Dependently-versioned artifacts can now be correctly migrated. Collaboration Collaboration Installation Administration Migration Vector Informatik GmbH Version 6.5 SP

70 PREEvision 6.5 SP8 6.4 Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space Version 6.5 SP14 Vector Informatik GmbH

71 PREEvision 6.5 SP7 7 PREEvision 6.5 SP7 This chapter contains the following information: 7.1 Version numbers Installation and compatibility information Fixed issues Known issues 76 Vector Informatik GmbH Version 6.5 SP

72 PREEvision 6.5 SP7 7.1 Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

73 PREEvision 6.5 SP7 7.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Migration to PREEvision 7.0 Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment PREEvision 6.5 SP7 is required for migrating to PREEvision 7.0. During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP7 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 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 6.5 versions: Client version Server application version Database server script version Vector Informatik GmbH Version 6.5 SP

74 PREEvision 6.5 SP7 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

75 PREEvision 6.5 SP7 7.3 Fixed issues Fixed issues in PREEvision 6.5 SP7 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Significant issues have been fixed regarding backup/restore and migration During the AUTOSAR import, Base Type references of Implementation Values are correctly imported Temporarily created artifacts, which have already been deleted before executing the commit, are now handled correctly. Backup, Restore and Migration AUTOSAR Collaboration Vector Informatik GmbH Version 6.5 SP

76 PREEvision 6.5 SP7 7.4 Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space Version 6.5 SP14 Vector Informatik GmbH

77 PREEvision 6.5 SP6 8 PREEvision 6.5 SP6 This chapter contains the following information: 8.1 Version numbers Installation and compatibility information Fixed issues Known issues 83 Vector Informatik GmbH Version 6.5 SP

78 PREEvision 6.5 SP6 8.1 Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

79 PREEvision 6.5 SP6 8.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Installation of Visual C during client installation Database access rights Restore parameters Migration to a 3-tier environment During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP6 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 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 6.5 versions: Client version Server application version Database server script version Vector Informatik GmbH Version 6.5 SP

80 PREEvision 6.5 SP6 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

81 PREEvision 6.5 SP6 8.3 Fixed issues Fixed issues in PREEvision 6.5 SP6 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models Re-import of requirements via the RIF import is possible if the following topics are considered: If there are no changes in the attribute definitions and data types, they are allowed to be checked-in. The requirements must be checked-out. In the import wizard the existing (checked-in) attribute definition package and data type package has to be selected The AUTOSAR export of complex data types works again During AUTOSAR export, the relation between I-SIGNAL and I-SIGNAL-GROUP is correctly exported During AUTOSAR 3 import, base types are correctly imported Sorting of enumeration entries works correctly for the DBC round trip During DBC export, hyphens are exported and no longer replaced with underscores (even if this is not DBC compliant) Updating Composition Types to a newer revision no longer causes an "OutOfBounds" exception On the middleware license server, the location of the license-db folder can be configured now. Therefore, the variable - PREEvisionLS.dir has to be set, e.g. - DPREEvisionLS.dir=D:/AppServer/ tomcat/licensedb A new action has been added within the Model Management view of the Administration perspective to download the server log file from the application server During migration of former Hex Types to Application Integer Types The attributes Representation and Extended Representation Format are now correctly set Formatted texts are no longer lost during backup and restore An SVN error is no longer reported during restore. Product Goals AUTOSAR AUTOSAR AUTOSAR Communication Communication Collaboration Administration Administration Migration Migration Migration Vector Informatik GmbH Version 6.5 SP

82 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

83 PREEvision 6.5 SP6 8.4 Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Vector Informatik GmbH Version 6.5 SP

84 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

85 PREEvision 6.5 SP5 9 PREEvision 6.5 SP5 This chapter contains the following information: 9.1 Version numbers Installation and compatibility information Changes Fixed issues 90 Common 90 Diagrams and tables 90 Product Goals 91 Logical Function 91 AUTOSAR 92 System Software 93 Hardware 94 Geometry 94 Communication 95 Product Line Management 96 Metrics and reports 97 Collaboration 97 Administration, authority, license, installation and migration Known issues 99 Vector Informatik GmbH Version 6.5 SP

86 PREEvision 6.5 SP5 9.1 Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries PREEvision license server PREEvision database server (2-tier) PREEvision database server (3-tier) PREEvision application server (3-tier) Documentation Document Version number PREEvision manual PREEvision operating manual PREEvision system requirements Version 6.5 SP14 Vector Informatik GmbH

87 PREEvision 6.5 SP5 9.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Database access rights Restore parameters Migration to a 3-tier environment The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP5 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 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 6.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 Vector Informatik GmbH Version 6.5 SP

88 PREEvision 6.5 SP5 Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

89 PREEvision 6.5 SP5 9.3 Changes LibreOffice documents incompatible to Microsoft Word In PREEvision an integrated LibreOffice editor is used for editing formatted texts and generating reports. If a document which was created in LibreOffice is opened in Microsoft Word, its presentation may be incorrectly changed or it might not be possible to open the document. This applies to ODT documents as well as to documents stored in DOC format via LibreOffice. To avoid possible incompatibilities, ODT files created with PREEvision shall only be opened or edited with LibreOffice. Additionally, PREEvision no longer supports to create Word documents (DOC). Therefore, the following changes have been implemented: > The menu item Save As... has been removed from the main menu of the LibreOffice editor. > The *.doc format can no longer be selected during report generation. > The file extension "doc" can no longer be set as "savetype" for the Report Executor metric block. Note: The documentation for generating reports as well as for the Report Executor block are currently outdated in the PREEvision manual and do not contain the restrictions mentioned above. Vector Informatik GmbH Version 6.5 SP

90 PREEvision 6.5 SP5 9.4 Fixed issues Fixed issues in PREEvision 6.5 SP5 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. > Common > Diagrams and tables > Product Goals > Logical Function > AUTOSAR > System Software > Hardware > Geometry > Communication > Product Line Management > Metrics and reports > Collaboration > Administration, authority, license, installation and migration > Changes Common OLE objects are now correctly embedded in formatted texts (e.g. description fields) By double clicking on an artifact the default editor is reliably opened now Generic attributes with special naming conventions are displayed correctly in the tables of the Property View Disabling query folders in the Model View no longer affects non-query folders. Common Common Common Common Diagrams and tables It is now possible to repeatedly change the object configuration of multiple selected artifacts in a diagram When changing the object configuration of multiple selected artifacts in a diagram, the background image of the first selected block will be correctly applied to all blocks. Diagrams Diagrams Version 6.5 SP14 Vector Informatik GmbH

91 PREEvision 6.5 SP Sorting model query based table columns works again The alignment of table cells is exported to Excel. Tables Tables Product Goals Requirement Attribute Definitions located in an Administration package within the Product Line can now be selected as target package for the RIF import. Product Goals Logical Function Within Logical System Diagrams, way points are set correctly when using Show Path on Required Ports Within Logical System Diagrams, ports are now moved correctly after splitting Logical Functions Within Logical Diagrams, delegation ports are no longer deleted when they are placed inside a section area Mappings to empty Activity Chains are now displayed in the mapping table of the Property View For populating provided/required ports in the Logical System Diagram, the following option has been introduced in the preferences: Populate only counterpart ports on show contained ports". If enabled, only counterpart provided/ required ports will be populated For connecting ports in the Logical System Diagram, the following option has been introduced in the preferences: Create new Assembly Net when connecting ports instead of extending existing Assembly Net. If enabled, new assemblies are created when connecting ports. If disabled, existing assemblies will be extended. Logical Function Logical Function Logical Function Logical Function Logical Function Logical Function Vector Informatik GmbH Version 6.5 SP

92 PREEvision 6.5 SP Moving a port of a logical function instance in the Model View no longer updates all containing diagrams and no longer changes the relation to the assembly Within the Logical System Diagram, the correct number of assembly connectors is created now when connecting logical functions within Building Blocks. Logical Function Logical Function AUTOSAR AUTOSAR export: Communication elements are also exported if they are in a global communication library AUTOSAR export and import: Timing information (e.g. time period of cyclic timing) are consistently handled AUTOSAR import: Implementation Data Types without a category are displayed in the Information View During the AUTOSAR export of a System Description or an ECU Extract, Mode Declaration Groups are now correctly exported During the AUTOSAR export of an ECU Extract hierarchical delegation port structures are now correctly handled AUTOSAR export: FIBEX-ELEMENTs are created for ISignalGroups The attribute SYMBOL of RUNNABLE- ENTITY is correctly imported and exported in AUTOSAR format During the AUTOSAR export of a System Extract hierarchical delegation port structures are now correctly handled AUTOSAR export: Complex data types are correctly exported now During the AUTOSAR export of a System Description, access from a RunnableEntity to an InterRunnableVariable is now realized with the correct role AUTOSAR export: IPDUs are correctly converted. AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR Version 6.5 SP14 Vector Informatik GmbH

93 PREEvision 6.5 SP AUTOSAR export: All Bus Systems are exported AUTOSAR import: PPort- and RPort- Mappings are imported Differences between the AUTOSAR export in PREEvision 6.5 and PREEvision 6.0 have been aligned During the AUTOSAR export of an ECU Extract it is now checked whether PDU Transmissions are assigned to a Frame Transmission AUTOSAR export: Duplicate references of I- PDU-Ports are no longer created AUTOSAR import: Name and value of Application Errors are correctly imported AUTOSAR export: Application Errors are correctly exported AUTOSAR export: Unnecessary references to PDU ports are no longer created AUTOSAR import: Sender and receiver gateway routing entries are now imported with the correct direction AUTOSAR 4.0 export: Type references for inter runnable variables are exported. AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR AUTOSAR System Software The Convert Block refactoring features a name-based port preselection now and ports can be deleted Problems on updating software instances with a selected revision have been fixed A type update is possible after reuse and check-out of a Composition Type , Ports of Composition Types are placed correctly after creating them in the Interface Assignment Diagram Whether the Connect Ports refactoring is available for Compositions can be used can be defined in the preferences under Refactorings Software Port Connector Connect ports of compositions. System Software System Software System Software System Software System Software Vector Informatik GmbH Version 6.5 SP

94 PREEvision 6.5 SP The Create Composition refactoring available in the Software Diagram no longer causes a reuse error When deleting a software component, the local prototype of this component will be deleted as well. Reuses of this prototype will no longer be deleted The refactoring Integrate into new composition works correctly now. System Software System Software System Software Hardware Connectors can again be resized within a grid of 20x New connectors created in a diagram (via the palette or Model View) are placed on the grid again , Components and inline connectors can be resized to left or top again without moving the connectors, pins and connections. A combination of top-left, bottom-left or top-right is not supported, which means that the child components will be moved Object configuration via types works correctly now During wiring harness routing and signal routing automatic locking is now used. Hardware Hardware Hardware Hardware Hardware Geometry Setting the object configuration on Topology Segments is possible in all cases again It is possible again to open Geometry Diagrams which were created using existing 3D coordinates. An error in the label handling has been fixed The refactoring to merge Topology Segments has been corrected and is working again. Geometry Geometry Geometry Version 6.5 SP14 Vector Informatik GmbH

95 PREEvision 6.5 SP Communication The software architecture synthesis for the DBC and LDF import creates a Microprocessor instead a Process Unit now , During the DBC import CANClusters are created. Additionally, the cluster merge action has been added to the import wizard During the FIBEX import, software sender ports are only created for the actually sent signals in signal-based mode During the FIBEX import, ports and software components are associated to the created mappings For the FIBEX, DBC and LDF import with merge option, the System Software can now be additionally selected as target package During the DBC export, the attribute GenMsgSendType will always be exported, independent of the Send Mode value The calculation of the Initial Value of a Signal creates a constant of the proper type During the DBC export, the length of names is no longer restricted/cut to 32 characters During the DBC export, float and double values are now correctly exported During the DBC import, CAN Signal Transmissions are created if the bus type is unknown or not set Deleting Frame Transmission in the CAN Bus Editor works correctly now using the automatic locking mechanism For LIN-ECU Interfaces, the error response can now be set on the property page Protocol Parameters The execution time for applying signal routing results has been significantly reduced. The progress bar is updated and after each processing of 500 results a message is written to the log file. Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Vector Informatik GmbH Version 6.5 SP

96 PREEvision 6.5 SP The DBC Import is now able to handle different character sets. Therefore, the option DbcFileCharSet was added to the DBC import/export properties. If a file cannot be read correctly with the default character set the character set can be set by the user. If the character set is not known there is the option to let the import guess the right character set. The following values are possible for DbcFileCharSet: > default: use the default setting of the operating system > guess: try to guess the character set by file analysis > <charset>: the name of the character set that is to be used to import/export the file (for possible values see en.wikipedia.org/wiki/ Category:Character_sets) On the General property page of Signal PDU Groups, the link to the Partial Network Cluster is displayed now Property pages have been added to define nested Signal Groups and Signal IPDU Groups. Communication Communication Communication Product Line Management , Performance improvements have been implemented for updating a Reuse Unit to the latest version Commit works after updating Reuse Units which results in new artifacts being added to a diagram If a Set is activated in the VM Set View and the options for automatically adding created or modified artifacts is enabled, mappings and logical connections are now automatically added to the Set. Product Line Management Product Line Management Product Line Management Version 6.5 SP14 Vector Informatik GmbH

97 PREEvision 6.5 SP When creating an Alternative by copying an existing Alternative in the Template View, State Values are now copied to the new Alternative , After a refresh, table settings of the Template View will be maintained (columns, filter, sort order). Product Line Management Product Line Management Metrics and reports In the Metric Diagram it is possible again to delete ports of a Loop Block Placeholders can be correctly placed between text within the same line Exporting Microsoft Word documents is no longer supported by the report generator, see Changes Issue regarding rich text handling in report generation has been solved A Metric Table Context referenced in a Report can be correctly overwritten with a Model Context / Primary Data Context. Metrics Reports Reports Reports Reports Collaboration , Automatic locks are now obtained for creating and editing the object configuration An error has been fixed that prevented a commit or an undo lock in combination with a shared lock , Undo all Locks no longer causes an error during the auto save. Collaboration Collaboration Collaboration Vector Informatik GmbH Version 6.5 SP

98 PREEvision 6.5 SP Administration, authority, license, installation and migration A commit error has been fixed which occurred after migration of the administration part of the model and initializing with the default setup Initializing a database/server project with a file works again The operation Administration Remove locally cached formatted texts is now disabled after closing a project It is now possible to initialize a 2-tier authority model with a file-based model which was exported from 3-tier environment Stakeholder Packages can now be created in the Library. Within these packages it is possible to create stakeholders (Clients and Supplier) The performance has been improved for starting the client with a borrowed license The database script for creating the required tablespaces (preevision_tablespaces.sql) has been adapted and can also be executed under Linux now The web application archive for the PREEvision middletier can now be created under Linux/Unix using the BuildWebApp.sh script The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server Large Japanese texts are handled correctly by the model cache In case that a file was replaced with another version from the history, the wrong file content was restored during backup/restore. The problem has been fixed, all files in the history are correctly restored A backup/restore error has been fixed concerning missing files. Administration Administration Administration Authority License License Installation Installation Installation Migration Migration Migration Version 6.5 SP14 Vector Informatik GmbH

99 PREEvision 6.5 SP5 9.5 Known issues Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Vector Informatik GmbH Version 6.5 SP

100 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

101 PREEvision 6.5 SP4 10 PREEvision 6.5 SP4 This chapter contains the following information: 10.1 Version numbers Installation and compatibility information Fixed issues Known issues 107 Vector Informatik GmbH Version 6.5 SP

102 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries 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 Version 6.5 SP14 Vector Informatik GmbH

103 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Restore parameters Migration to a 3-tier environment The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP4 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 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 6.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. Vector Informatik GmbH Version 6.5 SP

104 PREEvision 6.5 SP4 Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

105 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP4 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models Selecting a port instance on the Software Instance Diagram selects the correct port instance of the projected port prototype in the Model View On the Weight property page of a Wire Type, the properties for the weight of insulation per meter can be set again On the Receiver and Sender property pages of a Signal, the port prototypes are now displayed On the General property page of SW Component instances and types, the Instance ID and SW Component Type ID are now displayed During the DBC import with merge option, a Duplicate Exception could occur. The problem has been fixed During the AUTOSAR export, the byte order of Signal-IPDU-Mappings is converted to a byte order supported by AUTOSAR During the DBC import, the attribute lengthtype of imported Base Types is set to "FIXED" During the LDF import, the attribute lengthtype of imported Base Types is set to "FIXED" The AUTOSAR import creates a LIN Communication container for LinPhysicalChannel. The created structure is equal to the structure created by the LDF import During the AUTOSAR import, the DISPLAY- NAME of UNITs is imported During the AUTOSAR export, two underscores (" ") are no longer generated within SHORT-NAMEs During the AUTOSAR import, Port Prototypes are correctly merged by name (if UUIDs are missing). System Software Hardware Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Vector Informatik GmbH Version 6.5 SP

106 PREEvision 6.5 SP During the AUTOSAR export, the PackingByteOrder is correctly set, so that the System Description can be opened in the AUTOSAR Network Explorer During the AUTOSAR export, the Unit of the Computation Method is exported During the AUTSAR import, LIN Connector Types and associated attributes are created. Communication Communication Communication Version 6.5 SP14 Vector Informatik GmbH

107 PREEvision 6.5 SP Known issues Double click does not open the standard editor Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, double clicking on an artifact may not open the defined standard editor. For example, instead of a table, diagram or report template, the form editor is always opened. Workaround: Keep <CTRL> pressed and double click again. Afterwards, double click again. <CTRL> and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. Vector Informatik GmbH Version 6.5 SP

108 PREEvision 6.5 SP4 The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space Version 6.5 SP14 Vector Informatik GmbH

109 PREEvision 6.5 SP3 11 PREEvision 6.5 SP3 This chapter contains the following information: 11.1 Version numbers Installation and compatibility information New features Fixed issues 114 Common 114 Tables 115 Logical Function 115 System Software 115 Hardware 115 Geometry 116 Communication 116 Product Line Management 117 Rules, metrics and reports 117 Collaboration 118 Administration, authority and migration Known issues 120 Vector Informatik GmbH Version 6.5 SP

110 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries 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 Version 6.5 SP14 Vector Informatik GmbH

111 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Restore parameters Migration to a 3-tier environment The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. For a migration from PREEvision 5.5/6.0 to a PREEvision tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP3 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 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 6.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. Vector Informatik GmbH Version 6.5 SP

112 PREEvision 6.5 SP3 Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

113 PREEvision 6.5 SP New features Refactorings of the System Software LIN and AUTOSAR The following refactoring of the System Software has been adapted according to the type-prototype-instance concept which has been introduced with PREEvision 6.5 and is available again: > Split Application SW Component Importing and exporting LIN busses via AUTOSAR is fully available now. Related tickets have been fixed. Vector Informatik GmbH Version 6.5 SP

114 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP3 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. > Common > Tables > Logical Function > System Software > Hardware > Geometry > Communication > Product Line Management > Rules, metrics and reports > Collaboration > Administration, authority and migration Common Partly exported eea models can be opened in the client again An eea model containing duplicate XMIIDs can be opened again Labels can be set to invisible in the object and label configuration again The text color displayed in the Model View can be configured by the tag <grey> in the object and label configuration again The attribute External Link can now be edited in the Property View. It is now also possible to paste a URL Anchors are now supported within the Model Queries which enhance the comparison tree The Property View no longer freezes but is correctly refreshed according to the current selection After initializing a model with the default perspectives, all perspectives are correctly loaded and displayed in the start cockpit. Diagrams can be opened from the Model View. Common Common Common Common Common Common Common Common Version 6.5 SP14 Vector Informatik GmbH

115 PREEvision 6.5 SP Tables , Cell content in table editors is now displayed correctly after hiding and moving columns Existing attribute values are now correctly displayed in table editors. Tables Tables Logical Function Selected packages of the refactoring Split Logical Block are now persisted when clicking [Finish] on the dialog Selecting all blocks in a Logical Diagram by mouse and moving them in the diagram works correctly now. Logical Function Logical Function System Software Existing connections are maintained when moving components across compositions (including different hierarchies). System Software Hardware 24947, The current calculation has been corrected to enable variant sensitivity. HW Devices not included in the selected variant are now ignored when calculating dependencies for current calculation Pins and Connectors are placed within the grid again during creation and moving Rotated labels within Hardware Diagrams are correctly placed on their selected docked position again Initializing the model with the default setup no longer causes errors within Electric Circuit Diagrams. Hardware Hardware Hardware Hardware Vector Informatik GmbH Version 6.5 SP

116 PREEvision 6.5 SP Geometry Errors during opening a Geometry Diagram have been corrected, so that opening Geometry Diagrams is possible in all cases again Geometry Communication During the DBC import, initial values of a Signal are now imported as Integer or Double Literals depending on the signal type Within the message overview table, the column "Transmitter" has been renamed to "Sender" , Computation Methods that are referenced from a Signal are exported in AUTOSAR into the NETWORK-REPRESENTATION The performance of the AUTOSAR import has been improved A merging import of DBC/LDF without creating the software layer, creates and modifies gateways now The property page Sending/Receiving Components has been adapted and displays the correct components now During the DBC import, the attribute GenSigStartValue is imported and synchronized with the constant Raw Initial Value in PREEvision. Communication Communication Communication Communication Communication Communication Communication AUTOSAR files can now be imported. Communication Short names for PHYSICAL-CHANNELS have been corrected for the AUTOSAR export (space is replaced with underscore) Import of AUTOSAR 4 files works correctly now During the AUTOSAR 4.x export of a System Description, ECUs without mapped software components (typically gateways) which are connected to a bus system are also exported During the AUTOSAR import, Base Types and Computation Methods are assigned to Signals. Communication Communication Communication Communication Version 6.5 SP14 Vector Informatik GmbH

117 PREEvision 6.5 SP In the AUTOSAR export, the Base Type of a Signal is exported as BaseType of I-SIGNAL. In the AUTOSAR export, the Base Type of a Signal is exported as BaseType of SystemSignal During the AUTOSAR import, units of Computation Methods are correctly referenced , The Software can be updated with the AUTOSAR import including a merge even if the AUTOSAR file does not contain UUIDs. The default implementation will use the artifact names for matching. If the AUTOSAR file contains no UUIDs, a warning will be displayed During the DBC import, types for initial value constants of signals are now calculated from the type of the GenSigStartValue communication attribute definition. If this definition is missing, the type is calculated from the type of the signal During the AUTOSAR export, data filters for PDUs are exported into the TRANSMISSION- MODE-CONDITION. Communication Communication Communication Communication Communication Product Line Management The progress of compiling guards was optimized. Rules are generated during initial propagation only. Product Line Management Rules, metrics and reports The consistency rule "NotMappedInstance" has been corrected in the demo model The online checks for editing rules no longer cause a client freeze When generating lots of diagrams within a metric, LibreOffice should be reinitialized. Therefore, the "reinitializelibreoffice" port has been added to the Diagram Render Block and should be set to "true" using a Parameter Block. Rules Rules Metrics Vector Informatik GmbH Version 6.5 SP

118 PREEvision 6.5 SP Chart blocks are now automatically available in the Metric Diagram palette. The - DenableChartInReport initialization flag no longer has to be set Displaying context artifacts within Metric Context Blocks has been corrected in terms of variant sensitivity When generating a report via the Report Executor Block, the table of contents will now be generated before exporting to PDF or ODT For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice which caused a program crash after starting the report generator Report Modules which are included in text with "Heading" format will be integrated in the same line without line feed. Metrics Metrics Reports Reports Reports Collaboration , Exceptions during the autosave task are no longer presented to the user. Furthermore, these exceptions do no longer block a commit. This allows the user to commit changes even if the autosave was not executed properly Dereferencing values of an enumeration from within a table now also acquires the required shared locks correctly The search has been corrected to work properly in the 3-tier environment again A wrong lock behavior which locked file artifacts in some cases directly after a commit has been corrected Reused elements could not be checked-out in some cases. Check-out is now possible again after replacing an artifact with another revision The check for predecessor revisions has been adapted when loading the Version History to enable handling of histories with missing revisions. History and replacing versions know also works in this case. Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Version 6.5 SP14 Vector Informatik GmbH

119 PREEvision 6.5 SP Administration, authority and migration Initialize model with default setup has been fixed regarding perspectives. Perspectives can be updated by deleting the perspectives in the model and then using the Initialize current model with default setup operation Initializing a project with a model containing artifacts without revision is now possible The Log4J file path in the standard server configuration has been changed to catalina.base to work properly with all Tomcat instances If "visible" object permissions have been assigned to an artifact, check-out and checkin of its child artifacts is no longer possible The arrangement of lines within Logical Diagrams is now correctly migrated from PREEvision 6.0 to The commit checks executed during a restore with migration have been changed to permit the commit of missing reuses in restore mode Initial values are now imported as Integer or Double Literals depending on the signal type Extended logging can be enabled/disabled via the initialization parameter - Dprofile.debug (true=enabled / false=disabled) Incomplete sort orders created during a restore are now recognized and handled properly Initializing a migrated model with the default setup works correctly now. Administration Administration Administration Authority Migration Migration Migration Migration Migration Migration Vector Informatik GmbH Version 6.5 SP

120 PREEvision 6.5 SP Known issues Double click does not open the standard editor Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Backup requires increased hard disk space ( ) Sporadically, double clicking on an artifact may not open the defined standard editor. For example, instead of a table, diagram or report template, the form editor is always opened. Workaround: Keep <CTRL> pressed and double click again. Afterwards, double click again. <CTRL> and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. Creating a project backup of a multi-user project requires significantly increased hard disk space. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space Version 6.5 SP14 Vector Informatik GmbH

121 PREEvision 6.5 SP3 The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Vector Informatik GmbH Version 6.5 SP

122 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

123 PREEvision 6.5 SP2 12 PREEvision 6.5 SP2 This chapter contains the following information: 12.1 Version numbers Installation and compatibility information New features Fixed issues 127 Common 127 Diagrams and tables 128 Product Goals 128 Logical Function 128 System Software 129 Hardware 129 Geometry 130 Communication 130 Product line management 131 Change management 131 Metrics and reports 132 Collaboration 132 Administration, installation and migration Known issues 134 Vector Informatik GmbH Version 6.5 SP

124 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries 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 Version 6.5 SP14 Vector Informatik GmbH

125 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Update of 3-tier environments to 6.5 SP2 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 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 PREEvision 6.5 to 6.5 SP2: 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. Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. Vector Informatik GmbH Version 6.5 SP

126 PREEvision 6.5 SP New features Refactorings of the System Software LIN and AUTOSAR The refactoring Convert SW Component of the System Software has been enhanced. The refactoring creates valid type-prototype-instance structures and considers reuses now. The following refactorings of the System Software have been adapted according to the typeprototype-instance concept which has been introduced with PREEvision 6.5: > Convert SW Component > Connect Port(s) > Update SW Component Type > Merge SW Component Types with the same name and type Designing LIN busses is now possible. LIN busses can be imported and exported via AUTOSAR and Version 6.5 SP14 Vector Informatik GmbH

127 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.5 SP2 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. > Common > Diagrams and tables > Product Goals > Logical Function > System Software > Hardware > Geometry > Communication > Product line management > Change management > Metrics and reports > Collaboration > Administration, installation and migration Common , Selection changes are now reliably propagated to the Property View Tables and statistics can now be displayed in a Portlet View , Images are now correctly displayed in LibreOffice (including the LibreOffice editor and generated reports) Certain circumstances could lead to duplicate XMIIDs. A prevention measure to solve this problem has been implemented The Config Property View is available again The compare functionality has been corrected In LibreOffice, EMF/WMF pictures are now displayed correctly if shapes are placed behind each other. The clipping problem has been solved During copy and paste of arrows from a PowerPoint document to LibreOffice in PREEvision, the arrowheads are filled correctly now. Common Common Common Common Common Common Common Common Vector Informatik GmbH Version 6.5 SP

128 PREEvision 6.5 SP Diagrams and tables Centered labels are now correctly aligned. Diagrams , In column metric cells, extra icons are no longer shown Copy and paste of formatted text into attribute columns of type Text and String works correctly now Values entered in string based table cells persist after leaving a cell with arrow keys or pressing the <Enter> key. Tables Tables Tables Product Goals During RIF import, the RequirementID is now correctly imported in the EPDM-ID field (if configured accordingly) If no context freezing point is set, the refactoring to recreate IDs is now also available on checked-in artifacts For the RIF import the automatic locking mechanism now checks which elements have to be locked. Product Goals Product Goals Product Goals Logical Function The block type for Logical Domains is now shown on the General page in the Property View Sections can be used in Logical Function diagrams now A link named "Logical Type" was added to the Property View of Logical Domains on property page General, which can be used to navigate to the corresponding logical type of a Logical Domain Required entries for creating logical port prototypes are now available in the Interface Assignment diagram palette and popup bar Port Communication Requirements can now be created for logical sender and receiver port types. Logical Function Logical Function Logical Function Logical Function Logical Function Version 6.5 SP14 Vector Informatik GmbH

129 PREEvision 6.5 SP The shortcut menu of port types works properly now References between ports and port prototypes are still available after replacing a revision of a Reuse Unit. Logical Function Logical Function System Software Connect Port(s) refactorings properly run on Compositions if the preference Connect ports of compositions is set in the Preferences dialog under PREEvision Refactoring Software Port Connector. System Software The Pull Up refactoring has been corrected. System Software The Convert SW Component refactoring is available again (see New features) The names of software types and prototypes are only synchronized if the preference option Synchronize type name and first instance name is set in the Preferences dialog under category PREEvision Type/Instance Port Types of Compositions are now also displayed in the Property View on page Port Prototypes of Sender Receiver Interfaces The button Disable Automatic Figure Completion During Drag and Drop operations is available in software diagrams again. The button can be used to avoid the creation of additional artifacts when a specific artifact is dropped (e.g. ports of a block). System Software System Software System Software System Software Hardware A checked-in System can be opened in the View. A transfer back to easee is not allowed The original Power Distribution perspective has been restored. Hardware Hardware Vector Informatik GmbH Version 6.5 SP

130 PREEvision 6.5 SP In the Wiring Harness Diagram a new error message is shown when assigning a Schematic Connection which has no assigned Pins Moving pins in the Wiring Diagram has been improved. E.g. pins can be moved by 5 pixels if the grid size is set to The shortcut menu can be opened on checked-in Network Diagrams again The populate of Schematic Pins has been corrected: Schematic Pins are now correctly placed within the given slot layout. Within the 5x5 grid, a populate creates pins which partly cover each other, since pins are placed with a space of 5 pixels and the figure size of each pin is 10 pixels The attribute Min Outer Diameter is now available on the Pin Parameters property page of Pin Types. Hardware Hardware Hardware Hardware Hardware Geometry , In the Geometry Diagram and in the Wiring Diagram, the highlighting for a selected artifact remains visible when clicking on the diagram palette Geometry Diagrams are now correctly displayed again when using different zoom factors. Geometry Geometry Communication 34775, DBC import with option Synthesize Software Level and import alternative Automatic Import with Merging works properly now Routing entries are correctly displayed in the Property View of CAN Frame Transmissions The Description field for Frames is available again in the Property View. Communication Communication Communication Version 6.5 SP14 Vector Informatik GmbH

131 PREEvision 6.5 SP When changing a sender/receiver relationship in the LIN scheduling table, consistent sender/receiver relationships are automatically set for signal transmissions and frame transmissions , Computation methods are now correctly imported during AUTOSAR import Computation methods are now correctly exported during AUTOSAR export Only the necessary required ports and mappings will be created during Fibex import The cell editor for communication attribute tables in the Property View has been correctly adapted to the data type Descriptions for prototypes will now be imported during AUTOSAR import The DBC import with enabled merge options works again AUTOSAR files containing <SW-RECORD- LAYOUT> tags can now be imported. Communication Communication Communication Communication Communication Communication Communication Communication Product line management Ports are automatically created within diagrams of Building Blocks. If the Building Block itself is checked-in or its contained diagram is checked-in, the graphical representations of the ports are not created within the diagram. The same behavior has been implemented for the software architecture and composition type diagrams. Product line management Change management Ticket attributes can be created with the [+] button on the Ticket Attributes property page. Change management Vector Informatik GmbH Version 6.5 SP

132 PREEvision 6.5 SP Metrics and reports Connected Metric Executors are now displayed on the Usage property page of the Calculation Block , , For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Metrics Reports Collaboration The check-out has been corrected to ensure new revisions can only be created on the latest revision. Older revisions can only be checked out as new branch A file artifact which has been deleted and reimported again can now be successfully committed Replacing a version with a version from its history is now possible even if the artifact type has been changed, e.g. from ECU to Sensor Creating an assembly connection between two Logical Functions now only obtains shared locks on the parent artifacts (sender/ receiver Logical Function and parent package). Collaboration Collaboration Collaboration Collaboration Administration, installation and migration The restore of project backups into a 3-tier environment has been improved to handle existing software structures from previous versions , Initializing a specific administration package with the default setup now works correctly, even if the package is not already available in the current model. For example, it is possible to individually add the Compare Configurations package to the current model. Administration Administration Version 6.5 SP14 Vector Informatik GmbH

133 PREEvision 6.5 SP The performance of the model export (Export Model to File) has been improved The enabledummyfilecreation parameter is now also considered during restore in a 3-tier environment with SVN Dialogs for the setup of Visual C Redistributable will no longer be displayed during PREEvision client installation , Perspective configuration files are now correctly created during migration from PREEvision 6.0 to 6.5 SP Performance improvements have been implemented for the migration References between interfaces and interface assignments (located in the software instance layer) are now correctly migrated. Administration Administration Installation Migration Migration Migration Vector Informatik GmbH Version 6.5 SP

134 PREEvision 6.5 SP Known issues Double click does not open the standard editor Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Artifacts referenced by a placeholder in a report are not automatically selected (34777, ) Software composition types cannot be changed via custom model import ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Sporadically, double clicking on an artifact may not open the defined standard editor. For example, instead of a table, diagram or report template, the form editor is always opened. Workaround: Keep <CTRL> pressed and double click again. Afterwards, double click again. <CTRL> and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model Version 6.5 SP14 Vector Informatik GmbH

135 PREEvision 6.5 SP1 13 PREEvision 6.5 SP1 This chapter contains the following information: 13.1 Version numbers Installation and compatibility information New features Fixed issues 140 Common 140 Diagrams and tables 141 Product Goals 143 Logical Function 143 System Software 144 Hardware 145 Geometry 146 Communication 147 Product Line Management 147 Rules, metrics and reports 148 Collaboration 149 Administration, authority, license, installation and migration Known issues 152 Vector Informatik GmbH Version 6.5 SP

136 PREEvision 6.5 SP Version numbers Version numbers Application Version number PREEvision client LibreOffice dictionaries 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 Version 6.5 SP14 Vector Informatik GmbH

137 PREEvision 6.5 SP Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision Installation and compatibility information. Installation of Visual C during client installation Reinitializing the authority model During PREEvision client installation, Visual C Redistributable is automatically installed. If Visual C Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C Redistributable to its original state. For an update of a multi-user environment from PREEvision 6.5 to 6.5 SP1, the authority model must be reinitialized. Therefore, proceed just as usual for a migration: 1. Export the latest version of the existing authority model. 2. Initialize a new authority model with PREEvision 6.5 SP1. 3. Merge customer-specific changes from the PREEvision 6.5 backup into the newly initialized authority model. Reference: For detailed information about the migration of the authority model, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP1 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 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 PREEvision 6.5 and 6.5 SP1: 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. Vector Informatik GmbH Version 6.5 SP

138 PREEvision 6.5 SP1 Execution of LibreOffice managed by PREEvision Installation of LibreOffice dictionaries To apply to internal IT guidelines, the execution of LibreOffice is now managed by PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual Version 6.5 SP14 Vector Informatik GmbH

139 PREEvision 6.5 SP New features FlexRay busload table FlexRay comparison configurations Signal and frame overview tables Support of J2602 PREEvision now offers a preconfigured FlexRay busload table. The FlexRay busload table is an example for a configured table in the area of communication showing a set of attributes for the scheduled PDUTransmissions in a FlexRay bus. This table is available on the Schedule. PREEvision now offers two preconfigured comparison configurations for FlexRay as an example for extending the comparison functionality. > The "FIBEX Elements" Compare Configuration presents the main FIBEX elements starting from a Schedule displaying them in a very similar structure as they appear in a FIBEX file. > The "FlexRay Communication Matrix" Compare Configuration prepares the data to be compared starting from a determined component (ECU, Sensor, etc.) showing only the communication aspect of it. PREEvision now offers two predefined tables available on a Communication Package. The "Signal Overview" table and the "Frame Overview" table display the main attributes of the Signals and Frames contained in the Communication Package. The LDF import/export now supports the J2602 format. Vector Informatik GmbH Version 6.5 SP

140 PREEvision 6.5 SP Fixed issues Fixed issues in PREEvision 6.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. > Common > Diagrams and tables > Product Goals > Logical Function > System Software > Hardware > Geometry > Communication > Product Line Management > Rules, metrics and reports > Collaboration > Administration, authority, license, installation and migration Common Sometimes it was not possible to shutdown PREEvision after a long work session. The problem has been fixed. Common Mapping dialogs can now be filtered. Common Resetting perspectives works correctly. Common Selection propagation from the Favorites to a historic version loaded in the Model View works as expected The value check for the number of logged actions in the preferences now covers the range [0, maxint]. The initial value is 0 and valid A progress bar for executing the online check is displayed again in the status bar of the main window All toolbar items can now be hidden via the Window Customize Perspective command The shortcut menu item Open as second project for model comparison is now always available in the Project View. In the case that no Compare Configuration is available, a corresponding information is shown in the shortcut menu. Common Common Common Common Common Version 6.5 SP14 Vector Informatik GmbH

141 PREEvision 6.5 SP Formatted texts are saved after restoring their content Mappings can now be created between artifacts in a Logical Diagram and a Software Diagram Views can now be opened even if the currently loaded model contains no perspectives When opening a URL to another project, the project will be opened. Common Common Common Common Diagrams and tables A diagram update via <F5> will also update modified background images When moving an area consisting of several artifacts and connections within a diagram, the connections are now correctly moved together with the selected area Icons are now correctly updated according to a rule-based object configuration. For example, if an icon is no longer valid because the associated rule does no longer match, the icon is changed to the default setting Icons configured via the object configuration are now correctly considered and displayed in dynamic labels Offset and relative position are considered for embedded labels. Diagrams Diagrams Diagrams Diagrams Diagrams Rectangular routing has been corrected. Diagrams Diagrams are no longer scaled during export as image. Diagrams Scrollbars within labels work correctly, now. Diagrams If label texts are too long, they will be cut during diagram export as image A diagram update via <F5> will also update and re-evaluate the object configuration of all figures. Diagrams Diagrams Vector Informatik GmbH Version 6.5 SP

142 PREEvision 6.5 SP While switching between Legend and Title Block the following behavior is now given: > The Title Block is placed on the other side if a Legend is already contained and has as position the default position of the Title Block. > If the Title Block is already contained and a Legend is inserted later, the Legend has as default position the position of the Title Block and is pasted on the opposite side. This behavior is only active while as position the option Free position is not selected For mapping boxes displayed in diagrams, scrollbars are available When dereferencing a diagram configuration from a network diagram no invalid object exception is shown in the log file anymore Mapping boxes displayed in diagrams, are now correctly updated. 9111, Table cells with content larger than the cell height can now be scrolled Actions on table cells now work properly even if columns are hidden The cell height is now calculated according to the given font size in the columns With <F5>, the table editor and all contained model queries are refreshed and reevaluated, now In table editors, scrollbars are now correctly represented in formatted text cells If in the table configuration, the Enable Delete option has been deactivated for a table column, Delete will no longer be available in the shortcut menu of this table column New columns added to the Requirement Text Editor directly show content if the content is available. Additionally, the performance for opening the Add/Remove/Reorder Columns dialog has been improved. Opening the dialog now takes between one and two seconds Copy and paste from Excel into an attribute column is now possible. Diagrams Diagrams Diagrams Diagrams Tables Tables Tables Tables Tables Tables Tables Tables Version 6.5 SP14 Vector Informatik GmbH

143 PREEvision 6.5 SP Requirement attributes which display formatted text are now exported correctly to Excel A temporarily opened table editor now shows all content even if model queries with anchors are used. Tables Tables Product Goals Undo/redo works correctly for conditions created in the Customer Feature Editor Formatting and IDs are now kept when importing requirements via the RIF import Embedded objects (OLE objects) of requirements can now be changed even if the requirements have been imported with the RIF import. The changes within the OLE objects are stored, now Formatting is now correctly imported during RIF import. XML tags for formatting, such as bold, italic etc., are taken into account In case a requirement has been reused the identification number is set to "0" because reused artifacts cannot have different values for one version attribute. Product Goals Product Goals Product Goals Product Goals Product Goals Logical Function If the artifact name is defined directly on artifact creation, e.g. in a separate dialog, the name is immediately taken over without additionally switching to name editing mode The performance of refreshing a Logical System Diagram containing labels has been improved The creation of labels for assembly nets can be prohibited by setting the option Do not create labels in the preferences. The option is available on the preference pages Logical System Diagram and Software System Diagram. Logical Function Logical Function Logical Function Vector Informatik GmbH Version 6.5 SP

144 PREEvision 6.5 SP Moving ports is now possible between components of different Logical Function Packages In Logical Diagrams, connections are now selected even if only a part of the connection is within the selection area Commit is possible again after moving Building Block Types from a subsystem to the library The relation to the Building Block Type will no longer be lost if the type is moved from the block instance to the Library The Convert Block refactoring now considers the automatic locking mechanism. Missing locks are detected and reported to the user The Create Building Block refactoring has been corrected. Logical Assembly Connectors are now correctly displayed for the newly created Building Block. Logical Function Logical Function Logical Function Logical Function Logical Function Logical Function System Software For compositions, icons can now be configured in the object configuration Connect port refactorings can now be executed on multiple ports In the System Software layer, ports can now be correctly populated , Update of a software structures is now possible within a Reuse Unit The Size Type attribute can now be set in the Property View of data type Array The Data Source values for the label graph nodes representing a port in a Software System Diagram are now properly set. System Software System Software System Software System Software System Software System Software Version 6.5 SP14 Vector Informatik GmbH

145 PREEvision 6.5 SP Hardware The name of Splices and Inline Connectors is also configurable for the KBL export within the respective configuration file Warning for the KBL export displayed in the Information View have been corrected When changing the routing to rectilinear without changing the port layout in the Electric Circuit Diagram, Pin positions are no longer changed Populate in the Wiring Harness Diagram does no longer change Pin positions The handling of Pins of Inline Connectors during KBL import has been improved During an KBL import the respective connector types are created and assigned to the connector Moving free text elements within a component is possible again Refactoring shortcut menus on ports have been aligned between diagram and Model View (as far as possible) Internal components are now version objects and reusable Connected and unconnected connectors are now displayed in the Component Diagram in the same way as in the Network Diagram It is now possible to link a Bus Connector with a Bus System, e.g. in Property View, even if both artifacts are not checked-out. The change is possible on both sides Wiring Connectors are now displayed correctly in the Wiring Harness Diagram after they have been created Rectangular routing in the Geometry Diagram routes inline Branch-Offs correctly, now For the circuit synthesis (without Wiring Harness) the Do not create Splices... option is no longer available In Network Diagrams, the Power Distribution Output Connectors are displayed as triangle again. Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Hardware Vector Informatik GmbH Version 6.5 SP

146 PREEvision 6.5 SP Internal Schematic Connections and Hardware Devices are now variant-sensitive for the current calculation If a drop operation on an existing diagram is not possible, the background color of the diagram will no longer be changed to blue Undo is now possible for operations executed before a ground spot optimization Header connectors were not migrated correctly from PREEvision 6.0 to 6.5. Header connectors are now migrated correctly when migrating from PREEvision 6.0 to New Pins and Headers are placed correctly on the grid The naming definition in the KBL export properties file is now considered during the KBL export When generating a Wiring Diagram out of an Electric Circuit Diagram, pins and header connectors are now placed correctly. Hardware Hardware Hardware Hardware Hardware Hardware Geometry The selection of Title Blocks in Geometry Diagrams has been enhanced The performance has been improved when working with many Geometry Diagrams Special characters contained in the description of Topology Inline Connectors are now correctly displayed in the refactoring Merge selected inline connectors The progress dialog for calculating highlights is mainly avoided through performance improvements. However, the dialog will still be shown if the highlight calculations exceed two second in order to provide proper feedback In the Geometry Diagram, tooltips are still displayed when adding a background image to an Installation Location. Geometry Geometry Geometry Geometry Geometry Version 6.5 SP14 Vector Informatik GmbH

147 PREEvision 6.5 SP Communication In the Signal router wizard, if only one element is available for a drop-down list, it will be automatically selected During AUTOSAR import, unnecessary PDU assignments will no longer be created The AUTOSAR export now generates the correct number of SignalIPDUs and map them to corresponding PDU-TRIGGERINGS During AUTOSAR import, signal degradation in AUTOSAR is now correctly imported Signal degradation can now be configured in the Property View During DBC export, the Frame ID of the Frame Transmission is used, if it is set there. Otherwise, the Frame ID of the Frame is used During DBC export, negative start positions are set to 0 to prevent DBC files with syntax errors (negative start values are not supported and cannot be read from DBC files) The DBC export now works correctly if the Export active variant only option is activated During AUTOSAR export, the export of embedded complex data types is possible. The category TYPE_REFERENCE is set for complex data types During AUTOSAR import, the signal length is now correctly imported The DBC export with an active variant works correctly, now. Precondition: A Frame Layout Configuration must be contained in the variant to get the expected results from the DBC export. Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Product Line Management In the Variant Diagram, it is now possible to populate a Concept Space including Concept Templates (shown as arrow) The Variant can be changed in the Variant Diagram. Product Line Management Product Line Management Vector Informatik GmbH Version 6.5 SP

148 PREEvision 6.5 SP In the Variant Diagram, delete actions have been improved for Variants Newly created EE Attributes of the variant management are only shown once in the Model View. Product Line Management Product Line Management Show Reuse works correctly on connections. Product Line Management Conditions between parent and child Customer Features are no longer lost. Reuse synchronization now works correctly The synchronization error during integration from a reuse-unit has been corrected For reusing and integrating a Reuse Unit in a Product Line, sufficient locks are now automatically obtained. Product Line Management Product Line Management Product Line Management Rules, metrics and reports Since the rule model distribution has been redesigned in PREEvision 6.0 the error consistency check not executable does no longer occur In the rule diagram, the drop-down list for selecting the role of a link pair is completely visible, now Newly created model queries are now immediately visible in the object configuration Working with Metric Diagrams no longer causes delays Accessing the SWT and JFace framework is possible within the source code of a Calculation Block The metrics Java editor window is automatically closed when switching between perspectives The content of a Metric Context Block is now correctly updated in the Metric Diagram The version history and the commit history are accessible within the source code of a Calculation Block via the methods: > getversionhistoryofobject > getcommithistoryofobject Rules Rules Rules Metrics Metrics Metrics Metrics Metrics Version 6.5 SP14 Vector Informatik GmbH

149 PREEvision 6.5 SP In the Report Result Block, it is now possible to reference a TempTable containing cells that have NULL values Undo/redo now works correctly after metric execution For creating descriptions, formatted text is used. When generating a report, formatted description texts are thus automatically integrated in the report Numbering in reports has been corrected when inserting formatted texts with a numbered lists The behavior of numbering headlines has been corrected in the report generator Only syntactically correct placeholders can be added to report templates, now With LibreOffice, a report can now be saved even if it is manually edited after generation. Metrics Metrics Reports Reports Reports Reports Reports Editing report placeholders works again. Reports Collaboration Columns of tables are now sorted correctly after master database synchronization of a table editor The performance of search in history has been improved In 3-tier environments, commit labels are set und updated correctly, now After a commit the icon states in the Model View are refreshed The performance of show version history has been improved Corrected commit error caused by multiple reuses , The performance of comparing two versions from the version history has been improved. The performance of drag and drop from the version history has been improved. Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Vector Informatik GmbH Version 6.5 SP

150 PREEvision 6.5 SP The problem that, sporadically, files were deleted in SVN but not in PREEvision has been solved If an error occurs during creation an external working copy, a useful message is now displayed. Collaboration Collaboration Administration, authority, license, installation and migration The performance of importing project backups for rule models has been improved The performance of project initialization in the 3-tier environment has been improved The robustness of the 3-tier project restore has been improved The performance of the 3-tier project restore has been improved Initializing the current model with the default setup no longer results in duplicate XMIIDs Initialization of database/server projects with an *.eea file works correctly, now Navigating to an artifact via the quick search now works correctly in the authority model Title Blocks are now displayed when changing the Diagram Configuration using a viewer license The 3-tier database server installation script can now also be executed on Linux , A file-based model can be saved after migration, again. The save button is enabled The restore information (restore.ser file) for a database restore with history is now located in the corresponding backup directory instead of the workspace directory The order of record implementation elements is now migrated correctly A tailing space directly in front of the.eea file extension is not allowed as model file name. For example. "mymodel<space>.eea" is invalid. To correctly migrate the model, rename the *.eea file. Administration Administration Administration Administration Administration Administration Authority License Installation Migration Migration Migration Migration Version 6.5 SP14 Vector Informatik GmbH

151 PREEvision 6.5 SP Perspective files are now correctly integrated during the migration from PREEvision 6.0 to Backup and restore now work correctly. For migration, the backup must be created with the new client version (PREEvision 6.5 SP1) Diagram representations of comments, timing paths and conditions associated to an assembly instance are now correctly migrated during migration from PREEvision 6.0 to During migration, header connector positions are adapted now in the same way as the pin positions Enumerations are now correctly handled during migration. Migration Migration Migration Migration Migration Vector Informatik GmbH Version 6.5 SP

152 PREEvision 6.5 SP Known issues Perspective configurations are missing/defective after migration ( , ) Double click does not open the standard editor Formatted text field cannot be edited Borders of diagrams and tables in a report are not correctly printed ( ) Initialize current model with default setup requires parent package ( ) Moving a checked-in Logical Function Type creates illegal model state ( ) When migrating a 2-tier model without files (files are excluded from the backup), perspective configuration files are not automatically added to the model during migration. When migrating with files (files are included in the backup), the perspective configuration files added during migration are partly defective. Workaround: After the migration: 1. Load the latest model version of the migrated model. 2. Delete all existing contents from the Administration Perspective Configuration Model (if available). 3. Use Administration Initialize current model with default setup and select the Perspective Configuration Model to be merged with the current model. Sporadically, double clicking on an artifact may not open the defined standard editor. For example, instead of a table, diagram or report template, the form editor is always opened. Workaround: Keep <CTRL> pressed and double click again. Afterwards, double click again. <CTRL> and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. When selecting a specific package to be initialized with the default setup, the same package has to be already available in the current model. Otherwise, the contents will not be merged. For example, selecting only the "Compare Configurations" package to be integrated in the model does only work, if the "Compare Configurations" package is already available in the current model. Workaround: Manually create the parent packages of the items to be integrated. Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library Version 6.5 SP14 Vector Informatik GmbH

153 PREEvision 6.5 SP1 "Update Reuse Unit" is only possible if latest version is contained in the model ( ) Highlighting is lost when clicking on the diagram palette ( ) Type change makes replace from history impossible ( ) Diagram layout is not correctly copied for rotated devices Viewer licenses cannot change table column widths The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. The highlighting for a selected artifact is lost when clicking on the diagram palette. The problem occurs in the Geometry Diagram and in the Wiring Diagram. Workaround: Select the artifact in the Model View or the Favorites and pin the view. Replacing a version with a version from its history is not possible if the artifact type has been changed, e.g. from ECU to Sensor. Workaround: Instead of a type change, create a new artifact. Copying a diagram layout into another diagram does not work correctly for rotated devices. Workaround: Manually adjust the diagram layout. When working with a viewer license, table column widths cannot be changed. When opening tables, the column width may not be changed either through dragging the separator with the mouse nor setting the width explicitly in the Property View. Vector Informatik GmbH Version 6.5 SP

154 PREEvision 6.5 SP Version 6.5 SP14 Vector Informatik GmbH

155 PREEvision PREEvision 6.5 This chapter contains the following information: 14.1 Version numbers Installation and compatibility information New features Fixed issues 166 Common 166 Diagrams and tables 167 Product Goals 168 Logical Function 168 System Software and AUTOSAR 169 Hardware 170 Communication 170 Product Line Management 171 Rules, metrics and reports 172 Collaboration 173 Administration, license, installation and migration Known issues 175 Vector Informatik GmbH Version 6.5 SP

156 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 Version 6.5 SP14 Vector Informatik GmbH

157 PREEvision Installation and compatibility information Compatibility 2-tier environments: The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server version 5.5 (2.0.10) Database server version 6.0/6.5 (2.0.13) Database server version 6.5 (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible 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 the same PREEvision version. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 3-tier Collaboration Platform The PREEvision Collaboration Platform is now available as 3-tier environment. Reference: For detailed information about the installation of the 3-tier environment and for migrating from 2-tier to 3-tier, refer to the Operating Manual. Reinitializing the authority model For an update of a multi-user environment from the PREEvision 6.5 release to any PREEvision 6.5 service pack, the authority model must be reinitialized. Therefore, proceed just as usual for a migration: 1. Export the latest version of the existing authority model. 2. Initialize a new authority model with PREEvision 6.5 SP. 3. Merge customer-specific changes from the PREEvision 6.5 backup into the newly initialized authority model. Reference: For detailed information about the migration of the authority model, refer to the Operating Manual. Licenses and license server For PREEvision 6.5, new licenses are required. With PREEvision 6.5, a new version (2.0.0) of the PREEvision license server is available. It is recommended to update existing license servers to version Vector Informatik GmbH Version 6.5 SP

158 PREEvision 6.5 PREEvision database server: Oracle clusters (RAC) are not supported PREEvision workspace and PREEvision.ini Operating system: character set Oracle clusters (RAC) are not supported. Existing workspaces from earlier PREEvision versions cannot be reused for PREEvision 6.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 Version 6.5 SP14 Vector Informatik GmbH

159 PREEvision New features Collaboration Platform as 3-tier environment PREEvision Collaboration Platform is available as 3-tier environment, now. The 3-tier platform contains all features of the current 2-tier platform and provides the following new and additional features: > Branches: Branches are available to check out a historic artifact revision to start a parallel development line. Branches can be created during check-out on the basis of any artifact version. In the Check-out dialog the user defines whether a new development line for an artifact shall be started by creating a new branch. Branches are visible in the Model View, the Version History and the Property View. > Search in history: The search option Current and historic model versions is available. In the search result view, historic artifacts are indicated by a grey font color. The column Model version provides the corresponding model version. A historic artifact version can be inserted in the current model as new artifact or as reuse. > Life cycle history: On the Lifecycle property page, an additional life cycle History table is available. The life cycle history displays all life cycle state changes an artifact has passed through during its life cycle. > Subversion integration: File handling in PREEvision s 3-tier environment is now supported by the open source revision control system Subversion (SVN). Working copies of file structures can be created which improves the handling of large file structures and provides the base functionality for several use cases, for example test data management. > Middleware license server (optional): Server licenses can be managed in the integrated middleware license server. Alternatively, node-locked licenses can be used. Automatic locking With PREEvision 6.5, an automatic locking concept has been introduced. The user can now directly start editing or start an action without prior locking. This works for all actions in PREEvision including diagrams and shared locks. With the automatic lock handling, lock conflicts can be reduced, since only the minimum required locks are determined and obtained. Vector Informatik GmbH Version 6.5 SP

160 PREEvision 6.5 AUTOSAR AUTOSAR 4 compliant data types as well as communication parameters are available in PREEvision. Additionally, the modeling of partial networking is supported. With the AUTOSAR use case, PREEvision is part of the Vector AUTOSAR Solution and the exchange workflow with DaVinci Developer and DaVinci Configurator Pro is possible. LIN bus communication LDF 2.0 import and export is now available. A schedule design for LIN communication can now be modeled Version 6.5 SP14 Vector Informatik GmbH

161 PREEvision 6.5 Use case oriented perspectives PREEvision now starts with a cockpit view on the user interface. The cockpit provides use case oriented entry points into PREEvision. With just a few clicks you reach the user interface that is available for your use case. An expert mode is also available that corresponds to the former PREEvision E/E standard perspective. With the help of Model View and Property View filters, perspectives can be customized to display only the artifacts relevant for the use case and keep the user interface clearly arranged. Electric details in wiring harness The following features have been introduces regarding hardware modeling: > Internal hardware components and electric details can also be modeled in the Electric Circuit Diagram and the Wiring Diagram, now. Vector Informatik GmbH Version 6.5 SP

162 PREEvision 6.5 > With the Copy Layout function, completely modeled hardware components (including internal components) can be comfortably copied from one to another hardware layer. > In the Electric Circuit Diagram, the current path can now be populated. > The wiring harness synthesis can now be executed without creating splices. Specification of diagnostic requirements PREEvision supports the specification of diagnostics master-slave systems with diagnostic-specific attributes. > Use of PREEvision Network Diagram to model diagnostic relevant information as overview. > Extended modeling of diagnostic relevant information in PREEvision (diagnostic classification, DTCs, measurement signals, controls). > Export to CANdela and complementation of diagnostic specification in CANdela Test data management PREEvision can now be combined with vtestcenter for test and test data management: Testing phases with bi-directional traceability between artifacts: > Requirements management > Test engineering > Test implementation: Automated tests and test lists for manual execution > Test execution planning > Test execution documentation import and archiving Analysis and reporting (graphical and table form) > Metrics, requirements coverage, test progress, etc Version 6.5 SP14 Vector Informatik GmbH

163 PREEvision 6.5 Usability improvements for diagrams Usability improvements for the property view Several usability improvements have been implemented in diagrams, especially for move and resize actions as well as for the alignment of labels. In the Property View, the following usability improvements have been implemented: > Recently changed property pages are now highlighted with bold font color. > The LibreOffice editor can now be opened by clicking on the Description label. > A navigation bar at the top of the Property View displays the parent hierarchy of the currently selected artifact and can be used to navigate to any artifact within the hierarchy. Usability improvements for drag and drop operations (Assistance view) An Assistance View is now available to support drag and drop operations. Depending on the currently selected drag and drop target, the Assistance View displays artifacts suitable for the drag and drop operation. The Assistance View is automatically loaded when clicking on a Property View table or a table editor to which artifacts can be added. Vector Informatik GmbH Version 6.5 SP

164 PREEvision 6.5 Compare of artifacts Software architecture Safety features The compare functionality has been revised and now supports to compare model parts. The compare can now be started from the shortcut menu via the following items: > Select as left side for compare > Compare with <artifact> > Compare with each other (if two artifacts are selected) The shortcut menu items are available in the Model View, Version/Commit History and in tables. The compare algorithm now considers reuses, files and formatted text. Additionally, configurations for the compare function can be created to determine the artifacts, attributes and relations to be compared. The compare result is now displayed in a double-tree editor and can be exported to Excel. The software architecture layer has been optimized and aligned with the AUTOSAR standard. Using a library-based approach according to AUTOSAR, it is now possible to work with types and prototypes in the Library. Additionally, the instance-based approach is supported as well. Therefore, it is now possible to work directly with software instances in the System Software while the associated (proto-) types are automatically synchronized in the Library. By these changes, the memory consumption of the complete software architecture layer has been reduced and the usability has been improved for AUTOSAR users. In PREEvision 6.5, malfunction mapping has been introduced, allowing EEarchitecture artifacts to be annotated (mapped) with malfunctions. Malfunctions carry safety-relevant constraints such as the failure rate which allows a quantitative safety approach on the annotated artifacts. PREEvision provides a safety characteristics library to create a catalogue of malfunctions which fit to the respective level of modeling Version 6.5 SP14 Vector Informatik GmbH