PREEvision ReleaseNotes 7.5.8 EN · 7.5.6 7.5.6 7.5.5.02 7.5.7 7.5.7 7.5.7.02 For an update of an...

PREEvisionRelease Notes

Version 7.5 SP8English

Imprint

Vector Informatik GmbHIngersheimer Straße 2470499 Stuttgart, Germany

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

Contents

© Vector Informatik GmbH Version 7.5 SP8 3

Contents

1 PREEvision 7.5 SP8 71.1 Version numbers 8

1.2 Installation and compatibility information 9

1.3 Fixed issues 10

1.4 Known issues 11



2.3 Fixed issues 152.3.1 Common 152.3.2 Diagrams 162.3.3 Tables 162.3.4 Requirements 162.3.5 Communication 162.3.6 Hardware architecture 162.3.7 Geometry 172.3.8 Product line approach 172.3.9 Rules 172.3.10 Collaboration 182.3.11 Migration 182.3.12 License 18

2.4 Known issues 20



3.3 Fixed issues 243.3.1 Common 243.3.2 Diagrams and tables 243.3.3 Hardware architecture 253.3.4 Product line management 253.3.5 Functional safety 263.3.6 Change and release management 263.3.7 Metrics and reports 263.3.8 Collaboration 273.3.9 Administration and license 27

Contents


3.4 Known issues 29



4.3 New features 33

4.4 Fixed issues 344.4.1 Common 344.4.2 Diagrams 354.4.3 Tables 354.4.4 Product goals 354.4.5 Logical function architecture 354.4.6 AUTOSAR 364.4.7 Software architecture 364.4.8 Communication 364.4.9 Hardware architecture 374.4.10 Geometry 374.4.11 Functional safety 374.4.12 Rules 384.4.13 Metrics 384.4.14 Reports 384.4.15 Collaboration 384.4.16 Administration 404.4.17 Migration 404.4.18 License 40

4.5 Known issues 41



5.3 Fixed issues 455.3.1 Common 455.3.2 Tables 455.3.3 AUTOSAR 465.3.4 Software architecture 475.3.5 Communication 475.3.6 Hardware architecture 485.3.7 Geometry 485.3.8 Rules and reports 485.3.9 Collaboration 485.3.10 Administration and migration 49

5.4 Known issues 50



6.3 Fixed issues 546.3.1 Common 546.3.2 Tables 546.3.3 Logical function architecture 556.3.4 AUTOSAR 556.3.5 Communication 55

Contents


6.3.6 Product line approach 566.3.7 Functional safety 566.3.8 Rules and metrics 566.3.9 Collaboration 566.3.10 Administration 57

6.4 Known issues 58



7.3 Fixed issues 627.3.1 Common 627.3.2 Diagrams and tables 627.3.3 AUTOSAR 627.3.4 System software architecture 637.3.5 Communication 637.3.6 Hardware architecture 637.3.7 Geometry 647.3.8 Product line management 647.3.9 Rules, metrics and reports 647.3.10 Collaboration 647.3.11 Roles and rights 65

7.4 Known issues 66



8.3 Fixed issues 708.3.1 Common 708.3.2 Diagrams and tables 718.3.3 Product goals 718.3.4 Logical function architecture 718.3.5 AUTOSAR 718.3.6 Hardware architecture 738.3.7 Geometry 748.3.8 Product line approach 748.3.9 Functional safety 748.3.10 Rules, metrics and reports 758.3.11 Collaboration 758.3.12 Roles and rights 768.3.13 Administration and migration 76

8.4 Known issues 77

9 PREEvision 7.5 789.1 Version numbers 79


9.3 New features 829.3.1 Feature highlights 829.3.2 Requirements engineering 879.3.3 AUTOSAR software, system and communication design 899.3.4 Communication design 929.3.5 Wiring harness design 93

Contents


9.3.6 Design of safety relevant systems 989.3.7 Product line engineering 1009.3.8 Collaboration 1009.3.9 Usability improvements 1019.3.10 Administration 108

9.4 Fixed issues 1099.4.1 Common 1099.4.2 Diagrams and tables 1119.4.3 Product goals 1129.4.4 Logical function architecture 1129.4.5 Software architecture 1129.4.6 AUTOSAR 1139.4.7 Communication 1139.4.8 Hardware architecture 1149.4.9 Geometry 1169.4.10 Product line approach 1179.4.11 Functional safety 1179.4.12 Rules, metrics and reports 1179.4.13 Collaboration 1189.4.14 Administration and license 120

9.5 Known issues 121

PREEvision 7.5 SP8


1 PREEvision 7.5 SP8

This chapter contains the following information:

1.1 Version numbers 8


1.3 Fixed issues 10

1.4 Known issues 11

PREEvision 7.5 SP8


1.1 Version numbers

Version numbers Application Version number

PREEvision client 7.5.8

PREEvision license server 2.0.6

PREEvision database server (2-tier) 2.0.14

PREEvision database server (3-tier) 7.5.7.02

PREEvision application server (3-tier) 7.5.8

Documentation Manual Version number

PREEvision manual 7.5.2

PREEvision operating manual 7.5.6

PREEvision system requirements 7.5.6

PREEvision 7.5 SP8


1.2 Installation and compatibility information

Reference: For detailed information about the installation and compatibility ofPREEvision 7.5 in general, refer to PREEvision 7.5 - Installation and compatibilityinformation.

Update of 3-tierenvironments

In a 3-tier environment, the PREEvision client, the database server and the PREEvisionapplication on the application server are only compatible within exactly the samePREEvision version. Using a new client version on a previous server version or aprevious client version on a new server version is not supported and may lead to datainconsistencies or data loss.The following table shows compatible client, server application and database server scriptversions for specific PREEvision 7.5 versions:

Client version Server application version Database server script version

7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00

7.5.4 7.5.4 7.5.3.00

7.5.5 7.5.5 7.5.5.02

7.5.6 7.5.6 7.5.5.02

7.5.7 7.5.7 7.5.7.02

7.5.8 7.5.8 7.5.7.02

For an update of an existing 3-tier environment, all components with a changed versionnumber 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 tothe Operating Manual.

Further information > Installation and compatibility information

PREEvision 7.5 SP8


1.3 Fixed issues

Fixed issues inPREEvision 7.5 SP8

You will find the important fixed issues in the following tables. Please note that someissues are depending on specific configurations, views or models.

ID Issue Category

17938287531262687 Error handling has been improved whenpreparing a model for the migration andrepairing model inconsistencies. The erroroutput has been minimized.

Migration

PREEvision 7.5 SP8


1.4 Known issues

Caution: Please contact the Vector support for getting information about:> the appropriate migration procedure if you are planning to migrate to a newPREEvision version.> which PREEvision version shall be used for valid backup and restore.

Online help is notdisplayed correctly(1792665292793)

Depending on which default browser and which settings are configured on the clientcomputer, the online help may not be displayed correctly, in this way that:> images are not automatically fitted to page size,> the help navigation tree cannot be expanded and> the top of the page is cut off.Workaround:1. Activate active scripting in your system browser.2. Open the PREEvision online help in a separate browser instead of in the integrated

help browser of PREEvision. Therefore, define the following preference under Window | Preferences | Help: Set Open help contents to "In an external browser".

Meta class cannot becreated for meta classartifact picker

For the configuration of a Meta Class Artifact Picker, it is not possible to create new MetaClass proxies on the Meta Class Artifact Picker.Workaround: Existing Meta Class proxies can be assigned to the Meta Class ArtifactPicker via drag and drop to the Meta Classes property page.

PREEvision 7.5 SP7






2.3 Fixed issues 15Common 15Diagrams 16Tables 16Requirements 16Communication 16Hardware architecture 16Geometry 17Product line approach 17Rules 17Collaboration 18Migration 18License 18

2.4 Known issues 20

PREEvision 7.5 SP7


2.1 Version numbers











PREEvision 7.5 SP7







7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00

7.5.4 7.5.4 7.5.3.00

7.5.5 7.5.5 7.5.5.02

7.5.6 7.5.6 7.5.5.02

7.5.7 7.5.7 7.5.7.02




PREEvision 7.5 SP7


2.3 Fixed issues



Further information > Common> Diagrams> Tables> Requirements> Communication> Hardware architecture> Geometry> Product line approach> Rules> Collaboration> Migration> License

2.3.1 Common

ID Issue Category

1793971962647 Multi-selection editing in the Property Viewis now also available for custom attributes.

Common

1794004622647 The Show Change History action is nowonly enabled if there is a valid selectionfound.

Common

1794156632647 The action Window | Hide Tabs forPerspective is correctly applied to theperspective even if the window is resized.

Common

1794169022647 The Dereference and the Delete action thatare available in tables of the Property Viewhave been adapted. The Dereferenceaction is only available if a relation existsbetween the artifacts. The Delete action isavailable for source or target compositerelations or if no relation exists between theartifacts.

Common

17938285568737721 PREEvision is closed without exception. Common

17938286039798215 LibreOffice cannot be started if theenvironment variable UserDataDir is set.The variable UserDataDir is removedfrom the process environment when startingLibreOffice.

Common

17938287421779051 The copy command in the startup.ps filehas been corrected. The startup.ps fileis located in the startup folder within theclient installation directory.

Common

PREEvision 7.5 SP7


2.3.2 Diagrams

ID Issue Category

17938287417929012 After changing a diagram Title Block,commit is now possible without errormessage.

Diagrams

2.3.3 Tables

ID Issue Category

1794005272647 Object configurations that are set on a tablevia the Table Settings are now alsoconsidered by categorized columns that areconfigured via a Prototype for Tables.

Tables

1793917749051 The context menu no longer showsduplicate entries for table editors. Entries inthe Open With context menu can becategorized.

Tables

17938287215572647 In drop-down lists within tables, the selectedartifact is now correctly processed in casethat:> the drop-down list contains several

artifacts with the same name and> the drop-down list is filtered.

Tables

17938287369259012 In tables that are displayed on a PortletView, Open With is now available in thecontext menu.

Tables

2.3.4 Requirements

ID Issue Category

17938287277722647 When using the Product Goals importfrom Excel, importing product goals withattribute values without existing attributedefinition no longer leads to an error.

Requirements

2.3.5 Communication

ID Issue Category

1792981999118 DBC import: DBC synchronization rules arecorrectly applied. Synchronized results aredisplayed in the Information View.

Communication

2.3.6 Hardware architecture

ID Issue Category

1794191140452 Cables can be routed again. Hardwarearchitecture

PREEvision 7.5 SP7


ID Issue Category

17943545519012 In Wiring Diagrams, Border Width settingsare now applied to Wiring Connectorfigures.

Hardwarearchitecture

17943547099051 Connecting Wire Pins with wires in WiringDiagrams, reliably shows the SelectSchematic Connection dialog. Editingwires in Wiring Diagrams does not changeSchematic Connection assignments.Automatic assignments are only performedif there are no previous assignments.


17943701279005 The routing of a wire between two WiringConnectors of one Installation Locationworks correctly again and considers theoption to route through the InstallationLocation or not.


17938286119189005 It is now possible to configure the label ofWire Pins in the label configuration.


17938286657867721 Cycles in Component Circuit Diagrams arehandled correctly now.


17938287413219051 Creating a Single Wire from a WiringHarness Inline Connector to a Componentis possible again.


2.3.7 Geometry

ID Issue Category

1793972247721 Topology edge points can be converted intoBranch-Offs again.

Geometry

2.3.8 Product line approach

ID Issue Category

17938285645712647 Atomic SW Components are correctlyrepresented in the Core Artifacts table ofthe Asset.

Product lineapproach

17938286274202647 Integration of Atomic SW Components froman Asset is possible now.


2.3.9 Rules

ID Issue Category

17938286880418454 After client start, no error messages ofonline check indicators are thrown.

Rules

PREEvision 7.5 SP7


2.3.10 Collaboration

ID Issue Category

1794287082647 Lock works after editing or viewing VariantDiagrams.

Collaboration

17943545749132 Updating the model in scope definitionmode works for artifacts that are not visible.

Collaboration

17938285394252647 When a scope is deactivated, then theauthority management is refreshed as theprevious call might not reset the cachedauthority of the referenced class.

Collaboration

17938286870229134 The Check-out operation is available in thecontext menu.

Collaboration

17938287274978454 A commit error occurred after using therefactoring Type change toEEComponent. A workaround has beenprovided by deleting attribute values beforeexecuting the refactoring.

Collaboration

17938286121029132 Creation of a reuse is now possible if parentand child artifacts are selected by multi-selection. The child artifact is not reusedseparately.

Collaboration

17938286120339180 A sporadic problem has been solved thatcaused lost and founds while openingdiagrams.

Collaboration

17938286091092709 A mapping target is still available if themapping target is moved out of the scopevia an update.

Collaboration

17938287119698157 Within the 2-tier Collaboration Platform,changed values of custom attributes werenot displayed after commit. The issue hasbeen fixed.

Collaboration

17938286870109106 The handling of database connections hasbeen improved in case of interrupts.

Collaboration

17938287278399051 Commit in the database of one model nolonger blocks transactions on other models.

Collaboration

2.3.11 Migration

ID Issue Category

17943217708454 A compatibility check has been added withinthe database migration scripts.

Migration

2.3.12 License

ID Issue Category

1792898359824 The PREEvision Search is available whenusing a viewer license.

License

PREEvision 7.5 SP7


ID Issue Category

1793904982709 The user password can be changed whenusing a PREEvision Architect license.

License

17938287382129012 The Set Content View shows the correctcontents when using a viewer license.

License

17938287274339012 The context menu Open With | <table>works when using a viewer license.

License

PREEvision 7.5 SP7


2.4 Known issues







PREEvision 7.5 SP6






3.3 Fixed issues 24Common 24Diagrams and tables 24Hardware architecture 25Product line management 25Functional safety 26Change and release management 26Metrics and reports 26Collaboration 27Administration and license 27

3.4 Known issues 29

PREEvision 7.5 SP6


3.1 Version numbers











PREEvision 7.5 SP6




New Java version Java 1.8.0_112 is now provided with the PREEvision client installation.Existing application server runtimes should also be updated to Java version 1.8.0_112.

License server version2.0.6

The new version 2.0.6 of the stand-alone license server is available.Java 1.8.0_112 is provided with the Windows installer of license server version 2.0.6.




7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00

7.5.4 7.5.4 7.5.3.00

7.5.5 7.5.5 7.5.5.02

7.5.6 7.5.6 7.5.5.02




PREEvision 7.5 SP6


3.3 Fixed issues



Further information > Common> Diagrams and tables> Hardware architecture> Product line management> Functional safety> Change and release management> Metrics and reports> Collaboration> Administration and license

3.3.1 Common

ID Issue Category

1793585132689 Enumeration entries of custom attributes arenow correctly displayed in the list-style propertypage

Common

1793978982647 Tables now keep the sorting of metric-basedcolumns. The column must own a genericattribute named "sort" which is set to "false".

Common

3.3.2 Diagrams and tables

ID Issue Category

1793971962709 When displaying a table in a diagram,calculating the optimal width of a cell alsoconsiders the font setting in the objectconfiguration.

Diagrams

1793971982709 The label of a connection within a diagramshows the complete text if the connection islong enough.

Diagrams

1793981842709 The PDF export of a diagram no longerdisplays a white rectangle for configured labelsthat contain no text.

Diagrams

1794192229051 Elements in Legends are no longer selectedwhen using <SHIFT> + click to select allartifacts of the same class.

Diagrams

1793967462647 The calculation of grouped columns has beenfixed in case that no input is set for the group.

Tables

1793967612647 Content within prototype columns is nowcorrectly represented.

Tables

PREEvision 7.5 SP6


ID Issue Category

1793971902647 Table prototype columns that are dynamicallycreated via rules cannot be renamed in theAdd/Remove/Reorder Columns dialog.[Rename], double click and <F2> cannot beused for renaming as well.

Tables

1794099079132 Combined table editors are correctly exportedas image and PDF.

Tables

1794181272647 When configuring tables, anchor ports are alsoevaluated for prototype table columns.

Tables


ID Issue Category

1793585450452 Cable routing with Splices works correctly now.An additional check has been added forcommon Branch-Offs. If there are differences,then an error is reported in the InformationView. The start and the end Wire Pin are setcorrectly now, if the mapped artifact is alreadya Branch-Off.


1793826067721 Deletion of components correctly handles allaffected artifacts in the diagram.


1793828539051 Pins are placed according to the chosen layoutafter executing populate in diagrams.


1793988849012 During a KBL export the Wire Type ofconductors is exported to Cores for everyCable Type.


1794015429012 During a KBL export the colors of the WireType of conductors is exported correctly.


1794026000452 Defined attributes of hardware elements areshown correctly in diagrams again with the unitentered in the template diagram.


1794104882709 Plug Cab Types can now be created via theNew context menu on the Library package –Wiring Types.


1794191140452 Cables can be routed again. Hardwarearchitecture

3.3.4 Product line management

ID Issue Category

1793642149000 Integrating core artifacts of an Asset via metricworks now.

Product linemanagement

PREEvision 7.5 SP6


3.3.5 Functional safety

ID Issue Category

1793943718454 The calculation of probabilities was optimizedfor the quantitative fault tree analysis.

Functional safety

3.3.6 Change and release management

ID Issue Category

1793977712647 Roles can now be added via the New contextmenu on the Resource Package.

Change andreleasemanagement

1793977722647 Ressources can now be assigned to a Role viadrag and drop to the property page.

Change andreleasemanagement

3.3.7 Metrics and reports

ID Issue Category

1793935108454 A new method has been added to metric baseclass:createRefObjectWithSuppressedNameConventionWarnings allows creation ofRefObjects without any visible warnings (e.g.in Status View) that might be caused bypossible name conventions. This new methodis equal to the existingcreateRefObject(Class<T> metaClass,RefObject parent, StringroleNameToParent, booleanuseNameConvention) method, but with theadditional feature of suppressed warnings.

Metrics

1793939239106 A missing plug-in has been added to metricsystem class path so that Velocity JARs can beused again.

Metrics

1794003698454 A buffer size has been added toTempTable.toString, in order thatTempTables bigger than the Integer maximumsize do not cause OutOfMemoryErrorserrors anymore.

Metrics

1793970499106 When generating a report, tables withindiagrams are rendered only during printprocess to improve the report generation.

Reports

1794107258157 If errors in diagrams occur during reportgeneration an information message is postedto the Information View.

Reports

1794107268157 Reports can be now generated even if adiagram has wrong background images.

Reports

PREEvision 7.5 SP6


3.3.8 Collaboration

ID Issue Category

1793015080452 Performance of auto-check-out has beenimproved. Calculation of existing branch namesin the Check-out dialog is only executed ifmanually started by the user.

Collaboration

1793140012687 Connecting to a model is only allowed after themodel is fully initialized on the server and allonline checks are executed.

Collaboration

1793836242687 A validation of the delta has been added toavoid commit errors.

Collaboration

1793837987721 The algorithm of the model update has beenimproved in case that many commit versionsare needed to update the model.

Collaboration

1793969259012 The metric "EnumEntySync" has been adaptedto avoid check-in errors. Changes in achecked-in reuse trigger the check-out only onthe artifact itself and not on other reuses.

Collaboration

1793949102697 Commit of systems is possible. Collaboration

1793975602676 If an error is reported, e.g. because of amissing lock, the Information View no longerdisplays hidden artifacts but their next visibleparent artifact instead.

Collaboration

1793976002647 Replacing an artifact with another revision andbranch keeps external relations of the artifactto be replaced.

Collaboration

1794092359051 Illegal model changes are not reverted, if themodel cache does not fit.

Collaboration

1794102979051 Hiding components in a diagram no longercauses a commit error.

Collaboration

1794171068454 The commit error "Multiple roots after mergesize" has been fixed.

Collaboration

3.3.9 Administration and license

ID Issue Category

1792593482687 Removed unnecessary error message in logfile.

Administration

1792970929106 The message "Model <model> is unavailablebut being loaded." is no longer logged in theserver log file. Instead, when connecting to amodel which is currently loaded by the server,the user gets the following message in theclient: "The model <model> is currently beingloaded by the server. Please try again later."

Administration

1793903249824 The files in Subversion are not removed after afailure during initializing with file.

Administration

PREEvision 7.5 SP6


ID Issue Category

1793956038454 Only visible artifacts are considered forinitialization a server model with an existingmodel file. Invisible artifacts are ignored.

Administration

1794182032647 More information about the executed, undoneand redone operations is now provided in thebug report.

Administration

1793904830451 A user no longer blocks two licenses afterswitching from LAN to WiFi connection.

License

1793924492687 Corrupt licenses are deleted during middlewareserver startup. The license server is accessibleand new licenses can be uploaded.

License

PREEvision 7.5 SP6


3.4 Known issues







PREEvision 7.5 SP5






4.3 New features 33

4.4 Fixed issues 34Common 34Diagrams 35Tables 35Product goals 35Logical function architecture 35AUTOSAR 36Software architecture 36Communication 36Hardware architecture 37Geometry 37Functional safety 37Rules 38Metrics 38Reports 38Collaboration 38Administration 40Migration 40License 40

4.5 Known issues 41

PREEvision 7.5 SP5


4.1 Version numbers











PREEvision 7.5 SP5








7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00

7.5.4 7.5.4 7.5.3.00

7.5.5 7.5.5 7.5.5.02




PREEvision 7.5 SP5


4.3 New features

KBL import and exportusing metrics

The import or export of KBL files can now be started via metrics. Therefore, a KBL ImportBlock and a KBL Export Block are available. This allows the simple execution of a seriesof exports or imports and also the automation without user interaction.

Synchronize lightweightenumeration attributevalues across reuses

The attribute values of lightweight custom attributes of data type Application Enumerationare now kept synchronous across reuses. An event-triggered metric ensures that theattribute values are identical for all reuses. Therefore, the metric "simulates" a type-ofrelation between the attribute value of the enumeration and the enumeration literaldefined in the data type. The metric is only executed if the respective artifact is changed.If the attribute value is not identical for all reuses, the metric aligns the values and setsthe value that was changed last as attribute value for all reuses.

Caution: The Metric Executor EnumEntrySync is contained in the demo andinitialization model under Administration | Metrics | Utilities | EnumEntrySync MetricPackage and must be initialized via Factory Reset or manually integrated.

PREEvision 7.5 SP5


4.4 Fixed issues



Further information > Common> Diagrams> Tables> Product goals> Logical function architecture> AUTOSAR> Software architecture> Communication> Hardware architecture> Geometry> Functional safety> Rules> Metrics> Reports> Collaboration> Administration> Migration> License

4.4.1 Common

ID Issue Category

1792831997721 The column width of tables in the PropertyView is persisted for the client session.

Common

1792995949824 The quick search shows 500 results by default.The description of the search is adapted incase of more than 500 results are provided.

Common

1792674358454 Sorting Property View tables via the sortbuttons in the table toolbar works again.

Common

1792674368454 If types within the Library only allow readaccess, they can be set on instances whichallow write access.

Common

1793774509051 The Artifacts page is available again anddisplays included and excluded artifacts of aSet.

Common

1793814108454 The E/E-Model Online Check view showsonline check results again.

Common

PREEvision 7.5 SP5


4.4.2 Diagrams

ID Issue Category

1793772832709 If a Perspective Configuration is displayed in adynamic label within a diagram, the perspectivecan be opened via double click in the dynamiclabel.

Diagrams

1792381249005 Within diagrams, free text fields, which areinside of graphical objects (like rectangle etc.),are changeable again.

Diagrams

4.4.3 Tables

ID Issue Category

1793067028454 All column types within a table can be moved,including table prototype columns.

Tables

1793437692647 Custom attribute values of type Integer cannow be show in hexadecimal notation in tableeditors.

Tables

1793579672647 When sorting a table editor which displays atree, children are sorted.

Tables

1793911762647 Ordering of table prototype columns has beenfixed.

Tables

4.4.4 Product goals

ID Issue Category

1792905282647 For the requirement list import (ImportRequirements From an Excel File) it is nolonger required to select a library package.

Product goals

1793034809051 The context menu for Use Case artifacts canbe opened quickly in tables and in the ModelView.

Product goals

1793618577721 During the requirement list import, empty linesin the Excel file are handled.

Product goals

1793618587721 If the Excel file for the requirement list importcontains special characters, these charactersare removed and the file is now imported. Theinformation about not importable specialcharacters is posted to the Information View.

Product goals

4.4.5 Logical function architecture

ID Issue Category

1792972252687 The highlighting within Activity Chains iscalculated correctly. Therefore, sense andactuation are updated after a diagram hasbeen opened.

Logical functionarchitecture

PREEvision 7.5 SP5


ID Issue Category

1792972252687 The highlighting within Activity Chains iscalculated correctly. Therefore, sense andactuation are updated after a diagram hasbeen opened.


1793910588157 Activity Chains can be extended in reuseddiagram over a connection.


4.4.6 AUTOSAR

ID Issue Category

1793147452791 AUTOSAR export: SIGNAL-TO-I-PDU-MAPPINGs and I-PDU-TO-FRAME-MAPPINGsare sorted by their start positions.

AUTOSAR

1793623238454 Commit after an AUTOSAR import is nowensured.

AUTOSAR

4.4.7 Software architecture

ID Issue Category

1793554409824 On the Usage property page, the correctprototype owner is now displayed in the tablefor the Application SW Component Type andthe Composition Type.

Softwarearchitecture

1793806768454 The Application Enumeration value can be setvia drop-down list now.


4.4.8 Communication

ID Issue Category

1792989619822 The Information View is optimized to enhancethe performance of the signal router.

Communication

1793144129822 During signal routing, Gateway Routing Entriesare reused when their in and out transmissionsare also reused.

Communication

1793482649822 During frame synthesis, no PDU Transmissionis created if there already exists a valid PDUTransmission.

Communication

1793574982689 The DBC ECU extract considers the customattributes.

Communication

1793578319005 For the signal router, the option Pass routingsolution to information view for analysis nolonger overrides the option Suppressstandard output to log file and informationview.

Communication

1793604269005 Results of the signal router are also displayedcorrectly if the results are long strings.

Communication

PREEvision 7.5 SP5



ID Issue Category

1792903572709 A performance problem has been solved thatoccurred when performing a double click onWiring Harness.


1792971482647 An error which caused the Error Log view tobe shown during working within an ElectricCircuit Diagram was corrected so that theError Log view is not shown anymore.


1793067328454 The refactorings to replace the wire type andthe refactoring to replace the synthesisconstraint descriptor have been corrected andwork again.


1793492020452 The refactoring to create missing WiringConnectors has been enhanced and nowconsiders a set workspace.


1793565470452 Offsheet connectors can be created even if asection is not changeable, because theconnector is created in diagram connection andnot in the section.


1793571888454 In diagrams of the hardware architecture layer,the positioning of Name labels is nowavailable.


1793578477721 Routing of cores that end in differentcomponents works correctly now. A problemwith routing in different directions wascorrected.


1793619717721 The refactoring of a Branch-Off into a TopologyPoint was corrected and works correctly again.


1793909787721 The ground spot optimization dialog nowconsistently supports selection and deselectionof solutions using the check boxes.


4.4.10 Geometry

ID Issue Category

1792666732709 Executing a cut and paste action in theGeometry Diagram no longer leads to a clientfreeze.

Geometry


ID Issue Category

1792993348454 When generating an FTA diagram via the "FTALayouter" metric, all blocks have an identicalblock size. The block size is calculated andaligned after all blocks are drawn in thediagram.

Functional safety

PREEvision 7.5 SP5


ID Issue Category

1792993358454 When generating an FTA diagram via the "FTALayouter" metric, condition assignments aredisplayed according to the defined block size.

Functional safety

1793406898454 Performance of generating an FTA diagram viathe "FTA Layouter" has been improved.

Functional safety

4.4.12 Rules

ID Issue Category

1793565350452 Online check of rule models has beenenhanced to detect rules with corrupt links.

Rules

1792982782644 Two-step migration has been fixed for rulemodel from PREEvision 6.5 to 7.5.

Rules

4.4.13 Metrics

ID Issue Category

1792993308454 The auto-creation factory for diagrams createsnow correct lines if connections areoverlapping.

Metrics

1793465848454 In the ANT script runmetric.xml that is usedfor automated metric execution, the referenceto the MetricSuite.xml is removed. Thisreference could not be resolved and thus led toan error.

Metrics

1793465878454 For loading a file-based model for automatedmetric execution, a port no longer has to bespecified in the parameters.propertiesfile.

Metrics

4.4.14 Reports

ID Issue Category

1793584498157 Table rendering is finished before a report isfully generated. In that way, no hour glass isdisplayed in the generated report anymore.

Reports


ID Issue Category

1792677389051 Undo All Locks works after doing specialdiagram modifications.

Collaboration

1792678678454 A performance problem has been solved thatoccurred when updating the model from theserver.

Collaboration

PREEvision 7.5 SP5


ID Issue Category

1792935739824 Performance has been improved for comparingtwo model versions of a selected subtree.

Collaboration

1792952649051 A deadlock has been fixed that occurred afterperforming the Undo All Locks action.

Collaboration

1792960079823 Model cache files are removed from the serverafter they have been fetched by the client (orautomatically after one hour).

Collaboration

1792969079051 A performance problem has been fixed thatoccurred when locking artifacts.

Collaboration

1792995959051 Deleting artifact no longer leads to a clientfreeze.

Collaboration

1793087529051 Requesting a lock after editing and saving aSource Code no longer leads to a client freeze.

Collaboration

1793087332647 A deadlock has been fixed that occurred afterperforming the Undo action.

Collaboration

1793088782647 When switching between scopes no modelartifacts are shown grayed out, i.e. disabled.

Collaboration

1793137969106 To support long running commit transactions,the default value formiddlewareCallTimeout has beenincreased. Instead of 30 seconds, it is now setto 120 seconds. The error message that isdisplayed if a commit fails because of aSocketTimeoutException was improved.

Collaboration

1793137989106 An update of the model can be executed evenif the client is in scope definition mode.

Collaboration

1793146589824 An error occurred when connecting to themodel. The error has been fixed; writing themodel to the cache file has been improved.

Collaboration

1793306929106 The thread handling in the server has beenimproved. To avoid deadlocks, lockingstatements have a timeout.

Collaboration

1793413492709 The commit dialog disappears when thecommit is finished.

Collaboration

1793420029129 To prevent inconsistencies, the set of changedartifacts is validated after every operation in theclient. In case of invalid changes, the commitfails and a rollback is performed.

Collaboration

1793769682644 The demo model contains a completeUniqueness Cache configuration now.

Collaboration

1793810588454 The check-out life cycle trigger is alsoperformed on automatic check-out.

Collaboration

1793759358454 The handling after a client crash has beenimproved and no longer leads to connectionerrors.

Collaboration

1793838162709 A commit error occurred after creating a reuseand branch of a Component Package andcreating a Wiring Harness and Wiring HarnessDiagram. The problem was solved.

Collaboration

PREEvision 7.5 SP5


ID Issue Category

1793839582709 A commit error occurred after changing aWiring Harness Diagram. The problem wassolved.

Collaboration

4.4.16 Administration

ID Issue Category

1793585609129 Factory Reset has been reworked to resetphysical files on hard disk correctly.

Administration

4.4.17 Migration

ID Issue Category

1793838049106 Database restore has been enhanced tohandle checked-in state of artifacts in backuphistory.

Migration

1793838049106 Database restore has been enhanced tohandle checked-in state of artifacts in backuphistory.

Migration

4.4.18 License

ID Issue Category

1792629148216 Invalid licenses no longer produce a clientcrash.

License

1792951839051 Metrics that perform model changes cannot beexecuted with a viewer license.

License

1792951859051 Printing is possible when using a viewerlicense.

License

1792951849051 Selecting artifacts in the model tree is possibleeven if using a viewer license.

License

1792951839051 Metrics which perform model changes cannotbe executed with a viewer license.

License

1792980649051 When using a viewer license, the Excel exportof tables is available.

License

1793146599051 When using a viewer license, diagrams can beexported via the diagram export.

License

1793482698454 The "Insert Smart Card" request is onlydisplayed if a HTTPs connection is used andcertificate is required.

License

1793774419051 When using a viewer license, scopes can bedefined.

License

PREEvision 7.5 SP5


4.5 Known issues




PREEvision 7.5 SP4






5.3 Fixed issues 45Common 45Tables 45AUTOSAR 46Software architecture 47Communication 47Hardware architecture 48Geometry 48Rules and reports 48Collaboration 48Administration and migration 49

5.4 Known issues 50

PREEvision 7.5 SP4


5.1 Version numbers











PREEvision 7.5 SP4








7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00

7.5.4 7.5.4 7.5.3.00




PREEvision 7.5 SP4


5.3 Fixed issues



Further information > Common> Tables> AUTOSAR> Software architecture> Communication> Hardware architecture> Geometry> Rules and reports> Collaboration> Administration and migration

5.3.1 Common

ID Issue Category

1792969659005 For performance optimization, the online checkdecoration of parents has been disabled. Onlythe concrete artifacts with findings areindicated by an online check decorator in theModel View. In the E/E-Model Online Checkview, the findings of the selected artifact and itschildren are presented by default. A new buttonhas been added to toggle between displayingfindings with or without children.

Common

1793014790451 The compare table works again for comparingcomplete models.

Common

1793015009106 When saving the model on disconnect, an errormessage is no longer displayed.

Common

1793406937721 If the Model View is extended via ModelQueries, navigation on artifacts displayed bythe Model Query is possible again by pressing<SPACE>.

Common

1793420182647 Missing mapping property pages are availableagain for Requirement Packages. Note: Theproperty page "Mappings" is only relevant forRequirements.

Common

5.3.2 Tables

ID Issue Category

1792996388454 Table prototypes are no longer removed onopening the Add/Remove/Reorder Columnsdialog.

Tables

PREEvision 7.5 SP4


ID Issue Category

1792996392647 Opening tables on any artifact is possibleagain. Creating tables is still only possible forartifacts which are set as TableOwner in themeta model.

Tables

1793146429129 When changing attribute values in theProperty View, corresponding table cellswithin a table editor are directly updated.

Tables

1793437569129 A currently opened LibreOffice editor isrefreshed if the associated formatted text ischanged somewhere else, e.g. in the PropertyView.

Tables

5.3.3 AUTOSAR

ID Issue Category

1792952452791 AUTOSAR files causing import problems canbe imported now as far as they are compatiblewith the schema.

AUTOSAR

1792953742791 An error has been fixed regarding theAUTOSAR import.

AUTOSAR

1792959802791 During AUTOSAR import and export, I-SIGNAL.initValue is now imported to /exported from the attribute Raw Initial Value ofthe Signal.

AUTOSAR

1792961329119 Problems with the variant-sensitive AUTOSARexport have been fixed.

AUTOSAR

1792969487721 During AUTOSAR export, Bus Connectorswhich are not referenced are not exported.

AUTOSAR

1792970119119 During AUTOSAR import and export, theProtocol Name of CAN Clusters is importedand exported.

AUTOSAR

1793045182791 ISignal generation for fan-out scenarios directlyworks after changing the flag in the AUTOSARimport/export configuration file without havingto restart the client.

AUTOSAR

1793055007721 During AUTOSAR import, record elementswithout value can be imported.

AUTOSAR

1793138032791 During AUTOSAR export, the completecontroller configuration including CANparameters of a CAN FD ControllerConfiguration is exported.

AUTOSAR

1793144349118 During AUTOSAR export of a system extract,only Sender Receiver Interfaces which belongto the selected ECU are exported.

AUTOSAR

1793146737721 During AUTOSAR export of an ECU extract,the value for "Invalid" is exported.

AUTOSAR

1793421219118 During AUTOSAR export, the start position iscorrectly exported if byte order "Opaque" is set.

AUTOSAR

PREEvision 7.5 SP4



ID Issue Category

1792970729005 The Port Types property page of the SenderReceiver Interface shows the port types now.


1793013069129 Mode Access Points can now be created viathe New context menu on the Runnable Entity.


1793013079129 Typed Per Instance Memory can now becreated via the New context menu on InternalBehavior.


1793013109129 New property page pages for Per InstanceMemory and Typed Per Instance Memory havebeen added. The Typed Per Instance Memorycan be created via the New context menu onthe Internal Behavior artifact and the createdTyped Per Instance Memory artifact isdisplayed as a child of the virtual folder "Per-Instance Memories".


5.3.5 Communication

ID Issue Category

1792884979118 If a Signal Group is used in different Frames,during DBC export, for each Frame a SignalGroup is exported. In that way, no Frames aremerged because of the Signal Group.

Communication

1792894329118 During DBC import and export, the name of theECU is adjusted. The export of attributes of TxMessage and Rx Signal works correctly.

Communication

1792996369118 The Frame Synthesis also considers CANFrames for CAN FD buses. That can bechanges with a new setting on the preferencespage.

Communication

1792936289119 The DBC export wizard filters out the checkedelements in the same way as the AUTOSARexport. Performance is improved significantly.

Communication

1792966309118 During DBC export, unrelated Signal Groupsare not exported.

Communication

1792982699118 During DBC export, Scale Linear Verbal TableConversion is exported like Linear Verbal TableConversion.

Communication

1793139982791 The actions Add Controller Configurationand Add Controller Requirements create aCAN FD Connector Configuration and a CANConnector Configuration if the selectedelement is a CAN FD Connector Type. TheDelete action on the selected CAN FDConnector Type removes the created CAN FDConnector Configuration and the CANConnector Configuration. Two groups are

Communication

PREEvision 7.5 SP4


ID Issue Category

added which separately display the CAN FDController Configurations and the CANController Configurations.

1793307642689 During DBC export, enumeration entries ofAttribute Definitions which are used by severalMeta Classes are exported only once.

Communication


ID Issue Category

1792920720452 The KBL import and export has been enhancedand supports now the KBL attributehousingCode of connector housing. It isimported and exported to the attribute Codingof a Connector Type.


1792969432647 Merging Hardware Devices with the sameHardware Device Type works now.


5.3.7 Geometry

ID Issue Category

1793307548454 Diagrams can be opened even if they have seta small zooming size.

Geometry

5.3.8 Rules and reports

ID Issue Category

1792830102689 During synchronization of rules, the internalrule cache is now handled correctly. Existingrules are no longer marked as to be deleted.

Rules

1793012737721 Consistency rule results are displayed even ifthe affected artifact has no name.

Rules

1792969299106 The Generate Report dialog handles longpaths correctly now: The report is no longercreated in the installation directory and the fullpath is persisted.

Reports

5.3.9 Collaboration

ID Issue Category

1792954528157 Replace with latest revision works even if areuse exists which is out of scope.

Collaboration

1792970019106 Activating and deactivating scopes has beenstabilized.

Collaboration

PREEvision 7.5 SP4


ID Issue Category

1792984658454 To avoid commit problems, the UUID is alsochecked before handling container instancesand types.

Collaboration

1792990459051 Performance has been improved for deletingversion artifacts with a large number ofdependable-versioned child artifacts (like invery big diagrams).

Collaboration

1792995949051 A lock is possible after several refreshes of adiagram which contains query labels thatgenerate model changes.

Collaboration

1793152118454 Importing a Product Line no longer locks siblingProduct Lines.

Collaboration

1793152400452 External relations are maintained whenreplacing artifacts, e.g. during a specific import.

Collaboration

5.3.10 Administration and migration

ID Issue Category

1792995552663 During factory reset, branches within thefactory reset source model are ignored.

Administration

1792991659106 Post migration considers cases where newlycreates relations are not corrected afterdeleting artifacts. This prevented the deleteoperation.

Migration

PREEvision 7.5 SP4


5.4 Known issues




PREEvision 7.5 SP3






6.3 Fixed issues 54Common 54Tables 54Logical function architecture 55AUTOSAR 55Communication 55Product line approach 56Functional safety 56Rules and metrics 56Collaboration 56Administration 57

6.4 Known issues 58

PREEvision 7.5 SP3


6.1 Version numbers











PREEvision 7.5 SP3








7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00

7.5.3 7.5.3 7.5.3.00




PREEvision 7.5 SP3


6.3 Fixed issues



Further information > Common> Tables> Logical function architecture> AUTOSAR> Communication> Product line approach> Functional safety> Rules and metrics> Collaboration> Administration

6.3.1 Common

ID Issue Category

1792936299129 Default values of custom attributes are nowcorrectly set and reset.

Common

1792936562791 The Constant Specification property pagehas been removed, the new Usage propertypage has been added for the ConstantSpecification.

Common

1792979427721 Custom EEA import works correctly now onmulti-user environments.

Common

6.3.2 Tables

ID Issue Category

1792902099822 Filtering metric-based table columns workscorrectly now.

Tables

1792957459005 Table actions such as creating an artifact in aData Providing Table Column are possibleeven if the associated table artifacts are notlocked. Necessary locks are requested viaauto-lock.

Tables

1792980369129 Opening and closing the LibreOffice editor froma table no longer leads to an empty formattedtext.

Tables

1792980449822 Tables are now correctly refreshed afterperforming a Dereference action in the table.

Tables

PREEvision 7.5 SP3



ID Issue Category

1792938258454 Executing the Pull Up refactoring on a BuildingBlock no longer creates duplicated ports andcorrectly connects assemblies.


1792938288454 Line routings are correctly maintained afterexecuting the Creating Building Blockrefactoring.


6.3.4 AUTOSAR

ID Issue Category

1792931910455 Roundtrip of NvBlockNeeds has beenimproved.

AUTOSAR

1792952558454 AUTOSAR import of a folder with several filesworks correctly.

AUTOSAR

1792970222647 For the AUTOSAR import the transformation ofY-Axis and X-Axis has been corrected.

AUTOSAR

6.3.5 Communication

ID Issue Category

1792913242791 The Interfaces property page available forSender Port Types and Receiver Port Typeshas been corrected. The property page is onlydisplayed once and the assigned interface withits content is displayed.

Communication

1792932772663 DBC files can be parsed even if there is no LFat the end of the file and even if Strings containsigns for escaping like ”\”.

Communication

1792953849005 If the option Create new gatewaysautomatically if necessary is activated duringsignal routing, new gateways are created onlyif no gateway exists or an existing gateway hasa condition.

Communication

1792957452644 PDU Assignments are merged during DBCimport if they address the same Signal IPDUsand Frames.

Communication

1792966102647 An Nm Node can now be assigned to an ECUInterface via drag and drop to the NetworkManagement property page.

Communication

PREEvision 7.5 SP3



ID Issue Category

1792617017721 Assets and sub Assets are added to the activescope when replacing with revision.Additionally all core and boundary artifacts areadded to the active scope as well.


1792913809822 Closing the PREEvision client is possible afterworking within the variant management.


1792953938454 Creating a Product Line with substructurecreates those artefacts which are supported bythe selected license.



ID Issue Category

1792594128454 Safe States can now be associated with SafetyGoals via drag and drop in the hazard analysiseditor.

Functional safety

1792940308454 After calculating Minimal Cut Sets, the topevent of the fault tree analysis will berepresented in the Property View now.

Functional safety

6.3.8 Rules and metrics

ID Issue Category

1792936072663 Model queries now respect the execution orderdefined in Rule Dependency Diagrams.

Rules

1792957449005 A „type mismatch“ error which occurred duringrule generation has been resolved.

Rules

1792979429158 Rules can be generated now if the “source”Object has been changed.

Rules

1792966249005 When calculating signal router results viametric, the results use less memory now. Inthis way, the application no longer slows downafter running the metric multiple times.

Metrics

1792983388454 Overlapping connections in diagrams can nowbe configured when using the auto-creationframework for creating diagrams via metrics.

Metrics

6.3.9 Collaboration

ID Issue Category

1792966389005 If the client was closed abnormally the localdelta model could become invalid and localchanges could no longer be committed. Theissue has been fixed.

Collaboration

PREEvision 7.5 SP3


ID Issue Category

1792977179132 Edited Reports and Report Modules can becommitted without error message.

Collaboration

1792984592687 Displaying the commit history for an artifactallocates significantly less TEMP tablespace.The underlying SQL statement has beenoptimized.

Collaboration


ID Issue Category

1792988492645 An exclusive full lock of the whole model is nolonger required to perform a factory reset.

Administration

1792989038226 External relations are correctly maintainedduring factory reset.

Administration

1792991219822 Several issues have been fixed with regard tothe factory reset on 3-tier environments.

Administration

1792994102663 Isolating artifacts for the custom factory resetnow works correctly with the provided migrationtools (metrics).

Administration

1792995542663 Custom factory reset files created with Vectormetrics do not contain revision and branchinformation anymore.

Administration

PREEvision 7.5 SP3


6.4 Known issues




PREEvision 7.5 SP2






7.3 Fixed issues 62Common 62Diagrams and tables 62AUTOSAR 62System software architecture 63Communication 63Hardware architecture 63Geometry 64Product line management 64Rules, metrics and reports 64Collaboration 64Roles and rights 65

7.4 Known issues 66

PREEvision 7.5 SP2


7.1 Version numbers











PREEvision 7.5 SP2








7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27

7.5.2 7.5.2 7.5.2.00




PREEvision 7.5 SP2


7.3 Fixed issues



Further information > Common> Diagrams and tables> AUTOSAR> System software architecture> Communication> Hardware architecture> Geometry> Product line management> Rules, metrics and reports> Collaboration> Roles and rights

7.3.1 Common

ID Issue Category

1792649528454 The performance of the model comparefunction has been improved.

Common

1792665172666 Default value handling of custom attributesworks correctly now on the list-based page ofthe Property View (displaying and resetting todefault value is possible now).

Common

1792904969106 Subversion errors during commit of files havebeen resolved.

Common


ID Issue Category

1792903622985 The automatic creation of diagramsmechanism has been extended by two newmethods for defining the diagram name duringcreation of diagrams.

Diagrams

1792649548454 Tables are properly refreshed now whenadding or deleting artifacts to or from tables.

Tables

1792902129822 Hexadecimal values can now be edited intables if enabled via object configuration.

Tables

7.3.3 AUTOSAR

ID Issue Category

1792931930455 ApplicationArrayTypes are correctly exported inAUTOSAR now.

AUTOSAR

PREEvision 7.5 SP2


ID Issue Category

1792931970455 Constant Specifications are correctly exportedin AUTOSAR now.

AUTOSAR

7.3.4 System software architecture

ID Issue Category

1792913652791 For internal behavior, Service Dependenciesare now created within a virtual folder. DataType Sets and Mode Declaration Sets aregrouped together within a virtual folder calledIncluded Sets.

System softwarearchitecture

7.3.5 Communication

ID Issue Category

1792902109822 Only CAN Frames with CAN FD FrameSupport=true are correctly handled by theFrame-PDU Synthesis now, if the Bus Type isa CAN FD Type.

Communication

1792902119822 A read only validator for the attribute CAN FDFrame Support has been implemented. Thecorresponding attribute on the CAN Frame canbe set now, independent of the CAN FrameTransmission.

Communication

1792935582689 The refactoring enabling the merge of PDUsapplies to all PDU types now.

Communication


ID Issue Category

1792602380452 The wiring harness router now also creates thenecessary mappings for Wiring Connectors tothe respective Inline Connectors.


1792832017721 The refactoring for a type change of aconnector works now, even if more than twoconnectors participate in the bus system.


1792832047721 The wiring harness router is now also able tosplit off cable cores if the Connector Locationsare part of different Installation Locations (splitoff only for the last part after the last Branch-Off).


PREEvision 7.5 SP2


7.3.7 Geometry

ID Issue Category

1792832077721 When creating a new Geometry Diagram from3D coordinates it can be decided whetherInstallation Spaces shall also be created or not.

Geometry

7.3.8 Product line management

ID Issue Category

1792936299005 Creating Assets properly is possible now. Product linemanagement

7.3.9 Rules, metrics and reports

ID Issue Category

1792898809824 Assigning a Calculation Block to source code ispossible again after import.

Rules, metricsand reports

1792913607721 Hits of indirect referenced java-based Rulesare now correctly updated in the Rule ModelOnline Check view.


1792913619822 Closing rule model is possible now, while lockis missing in .eea model.


1792954012709 The initialization of query rule models workscorrectly now.



ID Issue Category

1792574529051 All necessary artifacts are locked automaticallyagain when working with Wiring diagrams.

Collaboration

1792574948454 Auto lock strategy considers delete operationscorrectly.

Collaboration

1792666212687 Bug reports with any legal file name can becommitted now.

Collaboration

1792902132687 Commit of files works correctly now. Collaboration

1792929792689 Auto-lock for synchronized custom attributesworks correctly now.

Collaboration

1792954529822 During an update with latest revision, theincorrect error message is not shown anymore, if the latest revision is not checked in.

Collaboration

PREEvision 7.5 SP2


7.3.11 Roles and rights

ID Issue Category

1792651299823 Recursions within role inheritance are nowidentified and prevented.

Roles and rights

PREEvision 7.5 SP2


7.4 Known issues




PREEvision 7.5 SP1






8.3 Fixed issues 70Common 70Diagrams and tables 71Product goals 71Logical function architecture 71AUTOSAR 71Hardware architecture 73Geometry 74Product line approach 74Functional safety 74Rules, metrics and reports 75Collaboration 75Roles and rights 76Administration and migration 76

8.4 Known issues 77

PREEvision 7.5 SP1


8.1 Version numbers











PREEvision 7.5 SP1







7.5.0 7.5.0 7.5.0.27

7.5.1 7.5.1 7.5.0.27




PREEvision 7.5 SP1


8.3 Fixed issues


You will find the important fixed issues in the following table. Please note that someissues are depending on specific configurations, views or models.

Further information > Common> Diagrams and tables> Product goals> Logical function architecture> AUTOSAR> Hardware architecture> Geometry> Product line approach> Functional safety> Rules, metrics and reports> Collaboration> Roles and rights> Administration and migration

8.3.1 Common

ID Issue Category

1792621028454 Within the comparison perspective, PropertyView filters can be saved for the left and rightside Property View.

Common

1792621058454 Due to the new custom attributes concept, textvalues of additional requirement attributes canbe displayed within the comparisonperspective.

Common

1792621772709 Performance of the model merge has beenrestored to performance within previousPREEvision versions.

Common

1792649498454 Formatted text attributes will be correctlydisplayed in the comparison perspective.

Common

1792649518454 Comparing formatted texts works again. Common

1792663388454 The documentation for the automatic metricexecution has been extended and describes allnecessary configuration files now.

Common

1792678187721 Performance of selecting and deselecting alarge number of artifacts has been improved.

Common

1792539822709 Performance of model queries and ModelView has been improved.

Common

PREEvision 7.5 SP1



ID Issue Category

1792897529129 Results of model query rules are displayed indynamic labels again.

Diagrams

1792664159822 Drag and drop actions are shown in the correctcolumn now even if columns are hidden.

Tables

1792676068454 Data within a table will not be changed ifselecting a value within a drop-down list iscancelled, e.g. by pressing <ESC> or byclicking into another table cell.

Tables

1792897919822 For selecting custom attribute columns in theAdd/Remove/Reorder Columns dialog oftable editors, the Type Definition Package mustbe associated to the Query Package whichcontains the table definition.

Tables

1792664179822 A MetricCellInformation object can nowbe delegated to metrics if requested via ModelContext.

Tables

8.3.3 Product goals

ID Issue Category

1792629212689 Drag and drop of modified and affectedartifacts is possible in the Property View now.

Product goals

1792654952647 During RIF import, the file name of the RIFimport file is used as name for new DefinitionSub Sets and new Definition Sets.

Product goals


ID Issue Category

1792211672689 Logical assembly connectors presented insystem diagrams are listed in the Open withcontext menu.


1792577019822 Assembly connectors can be deleted from adiagram independently from each other.


8.3.5 AUTOSAR

ID Issue Category

1792593320455 Performance of exporting an AUTOSAR ECUextract has been improved.

AUTOSAR

1792655300455 During AUTOSAR export, the attribute SHORT-LABEL of a NUMERICAL-VALUE-SPECIFICATION is only exported when it hasa value.

AUTOSAR

PREEvision 7.5 SP1


ID Issue Category

1792655340455 During AUTOSAR export, the AttributeCATEGORY of the APPLICATON-ARRAY-DATA-TYPE is correctly exported now.

AUTOSAR

1792655350455 For the AUTOSAR import and export, handlingof "not set" has been added for the attributesSW-IMPL-POLICY, SW-INTERPOLATION-METHOD, SW-REFRESH-TIMING of theAPPLICATION-PRIMITIVE-DATA-TYPE.

AUTOSAR

1792655370455 Attributes of the Base Type are correct afterroundtrip with AUTOSAR import and export.

AUTOSAR

1792655380455 The AUTOSAR export of Computation Methodlimit constraints has been corrected.

AUTOSAR

1792664938454 The attribute Invalid Value of Signals isexported to AUTOSAR.

AUTOSAR

1792666280455 The value of the Data Filter Type of aReceiver Communication Specification isexported to AUTOSAR.

AUTOSAR

1792666300455 In the AUTOSAR export wizard, the new optionNo datatype restriction has been introducedto disable the data types restrictions.

AUTOSAR

1792666310455 The initial value of a shared Parameter isexported to AUTOSAR.

AUTOSAR

1792666320455 The Implementation Policy of the DataElement is imported from AUTOSAR

AUTOSAR

1792833332791 During AUTOSAR import, the Sender of LINTp Connections is imported.

AUTOSAR

1792833542791 PDU Frame Assignments of Xcp PDU,User defined PDU and Nm PDU are exportedto AUTOSAR.

AUTOSAR

1792833552791 LENGTH of USER-DEFINED-PDU and XCP-PDUare imported from AUTOSAR.

AUTOSAR

1792894629822 The AUTOSAR import metric custom blockprovides the created Product Line on the resultport.

AUTOSAR

1792894639822 A NullPointer Exception which occurredwithin the metric-based AUTOSAR modelmerge has been fixed.

AUTOSAR

1792901412791 Custom attributes with type Opaque Referenceare exported to AUTOSAR as SDX-RFs.

AUTOSAR

1792901422791 The AUTOSAR export of DATA-TYPE-MAPshas been corrected.

AUTOSAR

1792902032791 During AUTOSAR export, date constraints areexported to an AUTOSAR package. InPREEvision this is indicated by a VirtualPackage with a Model Context named "DATA-CONSTR".

AUTOSAR

1792903572791 During AUTOSAR export, the value "-1" ishandled for SW-ALIGNMENT.

AUTOSAR

PREEvision 7.5 SP1


ID Issue Category

1792903902791 Ports with Trigger Interfaces will be importedand exported in AUTOSAR

AUTOSAR

1792904712791 During AUTOSAR export, the value "-1" ishandled for REFRESH-TIMING.

AUTOSAR

1792904892791 SW-CALIBRATION-ACCESS (CalibrationAccess) and SW-IMPL-POLICY(Implementation Policy) are imported andexported in AUTOSAR

AUTOSAR

1792904902791 The Application Data Type of the OperationArgument will be imported from AUTOSAR.

AUTOSAR

1792904962791 Calibration Access of the Mode DeclarationGroup Prototype is imported from AUTOSAR.

AUTOSAR

1792904972791 During AUTOSAR export, data constraints getthe suffix "DC_".

AUTOSAR

1792913192791 DATA-TYPE-MAPPING-REFS of theComposition Type are imported fromAUTOSAR.

AUTOSAR

1792913292791 Port API Options are completely importedfrom AUTOSAR.

AUTOSAR

1792913610455 Ports with Nv Data Interface are imported fromAUTOSAR.

AUTOSAR

1792915422791 CONNECTION-TYPE of OBD-RATIO-SERVICE-NEEDS is imported from AUTOSAR.

AUTOSAR

1792915452791 CALC-RAM-BLOCK-CRC of the NV-BLOCK-NEEDS is imported from AUTOSAR.

AUTOSAR

1792916012791 Configuration of SWC description export hasbeen extended to export initial values.

AUTOSAR

1792916612791 COMPU-CONST of computation methods withCATEGORY=TEXTTABLE are now correctlyimported and exported in AUTOSAR.

AUTOSAR

1792931840455 During AUTOSAR export of a SWCdescription, Application Literals which are setas initial value for CommunicationSpecifications are exported.

AUTOSAR

1792931960455 Base data types of Implementation DataPointers has been added to the SWCdescription export configuration.

AUTOSAR

1792938490455 SWC description configuration has beenextended to export possible errors.

AUTOSAR


ID Issue Category

1792575509822 AWG values no longer have a decimal formatand are correctly transferred to full numberswhen changing the systems.


PREEvision 7.5 SP1


ID Issue Category

1792587349005 Within the Wiring Harness Diagram the pop-upbar for the cable was corrected and containsthe shielding and the conductor now.


1792625707721 If the option for merging inline connectors withmore than two pins with the same name isalready activated no additional hint is given inthe Information View.


1792832007721 The refactoring of connections into poweroutputs has been corrected and works now asexpected.


8.3.7 Geometry

ID Issue Category

1792665238454 Moving Geometry Diagrams has beencorrected and is performed quickly now.

Geometry

1792665618454 The performance of creating new GeometryDiagrams with content based on existing datahas been improved.

Geometry


ID Issue Category

1792894122647 Numbering of Customer Features is displayedin the VM Template View again.


1792896018454 Highlighting is available in the VM TemplateView.



ID Issue Category

1791679962727 The requirement decomposition metric on asafety goal provides initial names for thefunctional safety requirements.

Functional safety

1792594148454 A new drag and drop operation for the FMEACause has been introduced in the Model View.The action facilitates creating a link to anexisting FMEA Effect under the same FMEAFailure Mode.

Functional safety

1792896008454 Drag and drop from Safety Goal to HazardousEvent and vice versa is possible now. Drag anddrop from Hazardous Event to Malfunction andvice versa is possible now.

Functional safety

PREEvision 7.5 SP1



ID Issue Category

1792439680452 Performance of generating and synchronizingrules has been improved.

Rules

1792672399822 Performance of selecting rule packages hasbeen improved for the rule model import.

Rules

1792892519822 An error has been fixed which caused a clientfreeze when modeling rules.

Rules

1792475382689 The attributes xIndex and yIndex will now bedisplayed correctly for the Sort Filter Block.

Metrics

1792832287721 The CurrentCalc class is now available inmetrics again.

Metrics

1792292719823 For rendering diagrams during reportgeneration, the diagram height is calculatedaccording to the first page of the report.

Reports

1792391718454 Embedded images in formatted texts are nowcorrectly integrated in reports.

Reports

1792485909823 For rendering diagrams during reportgeneration, the option Scale down if diagramis too big now considers preferences settingslike Resize diagram height.

Reports

1792593489078 Editing include placeholders in a reporttemplate now correctly updates the contexts inthe placeholder dialog.

Reports

1792649958454 In the Generate Report dialog, the fileextension displayed in the file Name text fieldand the File Type selected in the drop-downlist are synchronized.

Reports


ID Issue Category

1792401988454 Fixed paste of files from history in cases wherethe ID of artifacts should be adopted during thepaste operation (e.g. Requirements,Requirement Packages, Customer Features).

Collaboration

1792654198454 A commit error caused by an error in thehandling of formatted texts has been fixed. Handling of formatted texts has been correctedfor the case that an artifact changes its classand the new class does not have the formerformatted text attribute.

Collaboration

1792665339824 After executing the Undo All Locks operationit is possible again to change to anotherproject.

Collaboration

PREEvision 7.5 SP1


ID Issue Category

1792674002644 Collected actions in the delta are nowsynchronous with the model in case newartifacts are created after an undo and gettingdeleted artifacts again by the following deleteoperation.

Collaboration

1792676852647 Show Reuse action is now available in offlinemode.

Collaboration

1792830019822 An SVN error which prevented a commit hasbeen fixed.

Collaboration

8.3.12 Roles and rights

ID Issue Category

1792651299823 Recursions within role inheritance are nowidentified and prevented.

Roles and rights

8.3.13 Administration and migration

ID Issue Category

1792666212687 Bug reports with any legal file name can becommitted.

Administration

1792671689822 Initializing with custom factory settings doesnow handle reuses and assets correctly.

Administration

1792913369822 Initializing via Factory Reset correctlyinitializes Excel files.

Administration

1792679609822 Trace Assignment Relations between Assetsare now correctly handled during automaticdata migration.

Migration

PREEvision 7.5 SP1


8.4 Known issues




Default value handlingdoes not work correctly(1792665172666)

Default value handling for custom attributes does not work correctly on the list-basedpage of the Property View (display and reset to default value not possible).Workaround: Use the table-based property page for displaying and resetting defaultvalues of custom attributes.

PREEvision 7.5


9 PREEvision 7.5




9.3 New features 82Feature highlights 82Requirements engineering 87AUTOSAR software, system and communication design 89Communication design 92Wiring harness design 93Design of safety relevant systems 98Product line engineering 100Collaboration 100Usability improvements 101Administration 108

9.4 Fixed issues 109Common 109Diagrams and tables 111Product goals 112Logical function architecture 112Software architecture 112AUTOSAR 113Communication 113Hardware architecture 114Geometry 116Product line approach 117Functional safety 117Rules, metrics and reports 117Collaboration 118Administration and license 120

9.5 Known issues 121

PREEvision 7.5


9.1 Version numbers











PREEvision 7.5



Reference: For detailed information about the installation, update and migration ofPREEvision, refer to the Operating Manual.

System requirements The following client system requirements have been changed:> Windows 8 is now supported.> Windows 10 is now supported.> Windows XP is no longer supported.> Tomcat 6 is no longer supported.

Middleware licenseserver login

For login to the middleware license server, a PREEvision user account withadministration rights is now required. For login to the middleware license server, thePREEvision user account and password must be specified.The login of the stand-alone license server remains unchanged.

Backup/restore andmigration

The following migration paths from PREEvision 7.0 to PREEvision 7.5 are supported withthe mentioned restrictions:

2-tier to 2-tier migration from PREEvision 7.0 to 7.5> without history (migration of latest model version only)

2-tier to 3-tier migration from PREEvision 7.0 to 7.5:> without history (migration of latest model version only)> must be carried out in two steps:1. Technology change from 2-tier to 3-tier must be performed first (on

PREEvision 7.0)2. Afterwards, data migration from PREEvision 7.0 to 7.5 can be performed.

3-tier to 3-tier migration from PREEvision 7.0 to 7.5:> with or without history possible> improved performance of history migration

Backup of 2-tier models from PREEvision 7.5 and restore to PREEvision 7.5 is onlysupported without history (last model version only). For backup/restore including historyuse a database dump instead.

PREEvision 7.5


Caution: Please contact the Vector support for getting information about:> the appropriate migration procedure if you are planning to migrate to a newPREEvision version.> the appropriate migration procedure if you are planning to switch the systemarchitecture from 2-tier to 3-tier> which PREEvision version shall be used for valid backup and restore.

Compatibility 2-tier environments:The following table shows compatible client and database server script versions forspecific PREEvision versions:

Client version Database serverversion 5.5 (2.0.10)

Database serverversion 6.0/6.5/7.0 (2.0.13)

Database serverversion 6.5/7.0/7.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

6.5.0 - 6.5.8 not compatible compatible compatible

from 6.5.9 not compatible not compatible compatible

7.0.0 - 7.0.2 not compatible compatible compatible

from 7.0.3 not compatible not compatible compatible

3-tier environments:In a 3-tier environment, the PREEvision client, the database server and the PREEvisionapplication on the application server are only compatible within exactly the samePREEvision version. Using a new client version on a previous server version or aprevious client version on a new server version is not supported and may lead to datainconsistencies or data loss.


7.5.0 7.5.0 7.5.0.27

Licenses and licenseserver

For PREEvision 7.5, new licenses are required.

PREEvision workspaceand PREEvision.ini

Existing workspaces from earlier PREEvision versions cannot be reused for PREEvision7.5. Overwriting the PREEvision.ini is not allowed as well.

Operating system:character set

Please do use an operating system with a full character set of your language. Forexample, in order to support Japanese in PREEvision, the Japanese operating systemhas to be installed. An English operating system with Japanese character set might notsupport all characters. As a consequence, this may result in displaying wrong charactersin PREEvision.

PREEvision 7.5


9.3 New features

Further information > Feature highlights> Requirements engineering> AUTOSAR software, system and communication design> Communication design> Wiring harness design> Design of safety relevant systems> Product line engineering> Collaboration> Usability improvements> Administration

9.3.1 Feature highlights

Complete support ofAUTOSAR SoftwareComponent Template

PREEvision now fully supports the AUTOSAR Software Component Template. Missingevent types and artifacts to model internal behavior of software components have beenadded.Further new AUTOSAR features are:> Import and export for AUTOSAR 4.2.1> Customizable export of AUTOSAR extracts beyond ECU and system extract, e.g. for

bus or communication based AUTOSAR extracts> Extended consistency checks for AUTOSAR compliant modeling

CAN Design accordingto SAE J1939

PREEvision supports the network protocol SAE J1939 for commercial vehicles includingISOBUS 11783 for forestry or agricultural tractors and implements. J1939 allows easyintegration of tractors with engines, transmissions and implements. ISOBUS 11783supports a unified and easy control of the additional equipment from the cockpit of thetractor. PREEvision is now ready to model and manage the increasing communicationcomplexity of commercial vehicles:

PREEvision 7.5


> Import and export of J1939 designs via DBC and AUTOSAR> Extended multiplexing for CAN> Modeling of controller applications> AUTOSAR compliant software and hardware network design> Dedicated editors

Custom attributes PREEvision offers a new concept for customizable attributes. The former concept ofdifferent attributes for different layers with e.g. requirement attributes, diagnosticattributes or attributes for tests and tickets is replaced by this new concept, which isapplicable in every layer. If there is an attribute missing for a special purpose, just oneattribute for this demand can be created. The appearance and presentation of the newattributes in the property editor can be defined in an easy way.

With this concept it is also possible to implement AUTOSAR Special Data Groups (SDGs)including support of AUTOSAR import and export.Additionally, custom attributes are supported for the DBC and KBL import and export.

PREEvision 7.5


Change marker When working in the team it is crucial to be aware of any changes that were made byother team members or outside partners. The new change marker concept allows theeasy and reliable identification of any changes made during development. No matter if anattribute, a value, a relation or even a hidden artifact has been changed. The changemarker is a delta icon that is shown in the Model View, Property View and in tables. Thechange marker can easily be removed, either manually by the user or automatically vialife cycle change or check-in.A change history is available for detailed information of the changes and offers apossibility to compare formatted texts.

The benefits of the change marker at a glance:> Reliable tracking of all the changes made in the model> Fast and reliable identification of all the changes made in the model> Easier cooperation between OEM and supplier> Easy removing of change markers

Scratchpad and merge The scratchpad is a safe working environment stored in the PREEvision database to findnew solutions, because all the work done in the scratchpad is not immediately integratedinto the bigger model context. In the scratchpad new artifacts can be designed andexisting artifacts can be redesigned as copy or branch. The benefits of the scratchpad ata glance:> Fast and easy drag and drop to start sketching out ideas> Safe working environment to find new solutions> Easy merging of artifacts created in the scratchpad back to the model

PREEvision 7.5


After finishing the design in the scratchpad the artifacts can be integrated into the biggermodel context with the new merge functions. The new merge operation considersidentities, attributes, relations and child artifacts and support six different mergestrategies.

Partial model support The partial model support of PREEvision provides a tailored view showing only dedicatedparts of the entire PREEvision database model to the user. The model parts of interestare defined in the Scope Definition Perspective and only these model parts aredelivered to the client of the user. This concept reduces resource needs of the client PCand hides unnecessary model complexity from the user.

PREEvision 7.5


If partial model support is activated, the scope definition is a mandatory step after initiallogin to the client. When loading the E/E model for the first time or if no scope has beendefined, the Scope Definition Perspective will be displayed. Within this perspective, theModel View only displays the package structure of the E/E model.To define and activate a scope, the following steps are necessary:1. Select the packages to be included in the scope.2. Drag them to the Project and Scope View and drop them on the project.

A scope is created containing the selected packages and the Administration.3. Select the scope, open the context menu and select Activate Scope.

The scope is activated.When reconnecting to the project the scope will be automatically loaded.

PREEvision 7.5


9.3.2 Requirements engineering

Use case diagram Use case diagrams provide a user-centric perspective on a system by showing theintended functionality and the benefits of the system from the perspective of the users.They visualize the relations and dependencies between users and use cases.

Use case diagrams are behavior diagrams and follow the Unified Modeling Language 2.0(UML 2.0) specification.Available elements are:> Use cases> Use case systems> Actors> Include and extend relations> Extension points> GeneralizationsAdditionally, a fulfillment association between Requirements, Customer Features andUse Cases is available.All general diagram features are also supported by use case diagrams. Use casediagrams can be created under any artifact in the Product Goals layer.

RIF 1.2 import RIF 1.2 files can now be imported as Requirements, Customer Features or test artifacts.The RIF format (RIF 1.1a or RIF 1.2) is automatically recognized during the importwithout user interaction.The RIF configuration files have been extended. It is now possible to define settings forthe Property View for the imported requirement attributes including:> the position, where the attributes page is shown in the categories list.> definition to show attributes as a list page and/or as a table.> definition of attribute grouping.

Support Excel import forcustomer features

The Product Goals import via Excel now also supports Customer Features.

Configurable reports Comprehensive and flexible control of the reporting content is now possible. This allowscreating single-source report templates which can be tailored to different audiences anddepths during report generation.The report template defines:

PREEvision 7.5


> the content and structure of the report> mandatory report sections> optional report sections which can be flexibly included/excluded in/from the report> additional parameters, e.g. the start and end date for generating chartsFor report generation, the sections/content to be included in the report can be selectedand available parameters can be defined. The settings for report generation can be savedto a configuration file for later use.

PREEvision 7.5


9.3.3 AUTOSAR software, system and communication design

AUTOSAR import andexport versions

AUTOSAR 4.2.1 import and export is now supported.AUTOSAR 3.1.4 import and export is no longer supported.

AUTOSAR perspectives The predefined perspectives for AUTOSAR have been simplified and the number hasbeen reduced.

AUTOSAR packages AUTOSAR packages are now supported for the roundtrip with other tools.Therefore, within the Library, a Virtual Package Root containing a Virtual Packagestructure can be created.By using the new Virtual Package structure it is possible to determine the AUTOSARpackage structure and content to be exported.On AUTOSAR import, the AUTOSAR package structure is imported in a Virtual Packagestructure with the same structure.New artifacts may be assigned to specific virtual packages.

AUTOSAR special datagroups (SDG)

AUTOSAR special data groups are fully supported now including definition, editing,import and export.

PREEvision 7.5


Configurablecustomized AUTOSARexport

The customized AUTOSAR export can be preconfigured now.By using model queries, customer-specific AUTOSAR extracts can be generated.Example: Export a "Cluster Extract" containing only communication content to protect theIP of the software architecture.

Customer-specific propagation rules are executed during the customized AUTOSARexport. The result is a customer-specific AUTOSAR extract.

Support of system signaland system signal group

For supporting AUTOSAR communication fan-out scenarios it is possible to designSYSTEM-SIGNALs (System Signal) and I-SIGNALs (Signal) as well as SYSTEM-SIGNAL-GROUPs (System Signal Group) and I-SIGNAL-GROUPs (Signal Group).One System Signal has different I-Signals for the same bus for different receivers:

One System Signal has different I-Signals for different buses:

PREEvision 7.5


PREEvision 7.5


9.3.4 Communication design

Additional constraints forthe signal router

New constraints can be defined for the signal router.

CAN: Support of framewith different frame IDon same bus

Frame IDs for CAN bus systems can be flexibly configured considering the following usecases:> The same frame has different frame IDs on different bus systems.> The same frame has different frame IDs for different senders on the same bus

system.

CAN FD: Mode 2 andcontainer IPDU concept

Via AUTOSAR 4.2.1, CAN FD Mode 2 (extended payload) is fully supported.With the introduction of the AUTOSAR container IPDU, dynamic payload mapping, e.g.for CAN - CAN FD gateways, is now possible.

Default values for metamodel attributes

Global default values for meta model attributes can be defined in the Administration.When creating a new artifact the default value is set and a default marker indicates thatthe current value is a default value and has not been changed by the user.Inconsistencies between default values of custom attributes, which are synchronized withPREEvision meta model attributes, can be avoided.

PREEvision 7.5


9.3.5 Wiring harness design

Abstraction concept In the ECU network and wiring harness design different user groups work on differentabstraction levels together.These groups work in separated product lines, but need a possibility to link their artifacts.This is possible with the new abstraction relation.

The abstraction relation is available for specific artifacts and is a "type-of" relation:> The abstract artifact is the "type".> The concrete artifacts are the "instances".The abstraction relation can be set on the Abstraction property page.

Material data Materials are introduced in the library. Materials can be grouped into different categories(hierarchically). Each material can be described with its characteristics.

PREEvision 7.5


Materials can be assigned to:> components> hardware parts> hardware typesThe classification of the materials at the instance is supported:

Extensions for wiringharness router

The routing behavior for cables has been changed:> The complete cable is no longer routed within the geometry.> Now, each core of a cable is routed within the geometry.Behavior of the routing of cable cores:> All cores are routed separately and parallel through the same segments.> Exception at the beginning and the end of a cable:

Cable cores are allowed to be routed in different segments, but only after/before thelast branch-off.

PREEvision 7.5


KBL installationinstructions

The existing KBL import and export was extended to support KBLinstallation_instructions.No mapping to standard PREEvision attributes is possible as instruction types can befreely defined:> Import to and export from the newly introduced custom attributes.> For each instruction type an attribute definition is created in PREEvision.> Predefined attribute definitions in PREEvision can be used and will be recognized.

Installation instruction values are stored at the artifact where the parent information (inKBL) is stored:Example: Connector occurrence with installation_instruction in KBL leads to WiringConnector with attribute value for the defined instruction type.

Hardware modules indiagram palette

Hardware Module Types can be displayed in the palette of the Electric Circuit Diagram(extra section).Adding a new Hardware Module with the selected type to the diagram from the palette ispossible.

PREEvision 7.5


The icon, which is set on the type, is displayed in the palette and is used in the diagram.

New refactoring The new refactoring Type change to EEComponent is available and supports the typechange from a Wiring Harness Inline Connector to an EE-Component.

Wiring harness andschematic diagramimprovements

The following diagram improvements are available:> Select all via <CTRL>+<A>> Move> Select and move in one action> Change routing option (e.g. from oblique to rectangular)> Placing and moving of components in Wiring Harness and Connector Template

Diagram> Populate: no more loops and merging of overlapping edges> Permanently displaying fan area

PREEvision 7.5


PREEvision 7.5


9.3.6 Design of safety relevant systems

Safety analysis: Faulttree analysis

The following extensions have been made with regard to fault tree modeling:> Support of AND, OR, NOT and XOR gates> Improved visualization of gate symbols> House events with probability 0 or 1> Reuse of Malfunctions with alias names> Support of variants of fault trees

For the qualitative FTA, the following improvements have been introduced for performantcalculation of minimal cut sets:> Cut off order can be defined> Quantitative importance is calculated> Results are structured in packages according to cut set order> Advanced highlighting for malfunctions included in minimal cut sets

The following improvements have been introduced for the quantitative FTA:> Exponents of failure rate can be added easily> Calculation and diagram configuration considers unit of failure rate lambda> Improved visualization of failure rates and calculated probabilities in fault tree

PREEvision 7.5


Safety requirements New artifact classes for safety requirements are supported:> Hardware Safety Requirements> Software Safety Requirements

Other technology A new artifact class Other Technology has been introduced:> According to ISO26262 for description of technology different from E/E technologies

(e.g. mechanical or hydraulic technology)> Supported in Component, Network, Electric Circuit and Wiring Harness Diagram

PREEvision 7.5


9.3.7 Product line engineering

Reuse unit renamed toasset

Reuse Unit has been renamed to Asset. All artifact classes, views and attributes havebeen renamed accordingly.

Reuse of product lines Reuse of Product Lines is now possible if no checked-out Assets are contained in theProduct Line.When trying to reuse a Product Line which contains checked-out Assets, an error will bedisplayed and the checked-out Assets will be displayed in the Information View.

9.3.8 Collaboration

Improved roles andrights concept

The roles and rights concept has been improved:> Only visible artifacts are transferred from the application server to the client.> Invisible artifacts are no longer transferred to the client.

Concurrent modeloperations

Collaboration has been improved with regard to concurrent model operations:> The waiting time of client users for dedicated server actions has been reduced.> Model update operations of different users are running concurrently on the

application server.> Commit operations of different users are running sequentially.> Parallel read operations during a write operation are possible.

PREEvision 7.5


9.3.9 Usability improvements

Property view The following improvements have been introduced for the Property View:> In the Property View, recently visited pages are now highlighted by a light green

background color.

> The table sort mode has been removed. If table entries are sortable, the up/downbuttons are always displayed in the table toolbar.

> Drag and drop to the Property View has been improved. During the drop action onlyallowed target pages are displayed.

> It is possible to define a grid layout for the Property View. In this way, properties canbe displayed next to each other.

> The quick search is now available in the Property View to search for attribute names

and values. The quick search field can be displayed in the Property View via the button in the action bar or via the shortcut <CTRL>+<F>.

PREEvision 7.5


Tables The following improvements have been introduced for table editors:> Columns can be grouped via table context menu Group Columns. Several groups

can be defined. Groups can be configured in the Add/Remove/Reorder Columnsdialog.

> Predefined column filters are persisted. All filter options are displayed. In this way, asimple change of the filter options is now possible.

> Table filters can be defined directly in the table editor via table context menu Filter.

Tables: Copy and pastebehavior

The copy and paste behavior of multi-selections in tables has been improved:> Discontiguous values can be pasted without empty cells.> Only contiguous values from different columns can be copied.> A preference is available to define if empty values overwrite existing values.> The paste action is only performed for the visible area. The tree is not automatically

expanded.

PREEvision 7.5


> The paste action is automatically aborted, when a read-only cell is reached.> The paste action is available for a selected cell range:

> Case 1: If the target quantity is smaller than copied values: paste only into targetrange.

> Case 2: If the target quantity is bigger than copied values: paste with repetition.

Tables: Chart wizard Creation of charts for tables is now supported via wizard.

The underlying ODT template is created automatically. Several charts and ODTs can bedefined. For configuring the chart, predefined filters and aggregation functions areavailable.

Copy and special paste In addition to the universal paste behavior, a customized behavior is needed, forexample, to paste the structure of a copied Requirement Package and reuse all leafartifacts.Therefore, a custom paste action can be defined for a meta class via a new metricexecutor (Metric Executor Paste). This allows to define which relations are to be copied(default: all external relations are copied) and whether the new Relation Editor should beopened or not.

The Relation Editor can also be manually opened by the user via context menu Openwith | Relation Editor to view and detach relations.If a metric for a special paste action has been configured, it can be selected in the contextmenu, the drag and drop menu or via the Special Paste dialog (shortcut <CTRL>+<SHIFT>+<V>). The Special Paste dialog offers all paste actions for the selected metaclass.

PREEvision 7.5


The standard paste action is still available and unchanged.

Automatic groupingfolders

Artifacts can be automatically grouped in folders. The grouping algorithm can beconfigured in the object configuration (Grouping Folder).

Unique attribute values Uniqueness checks and unique ID generation has been introduced.Uniqueness checks can be implemented to check whether an attribute value, entered bythe user, is unique, e.g. the name of an ECU shall be unique. Furthermore, it is possibleto generate short unique IDs that are compliant to a customer-defined pattern. Forexample, human readable IDs for Tickets or Requirements can be defined.Uniqueness is ensured for the current model including the history of the current model.Attribute values which are not unique cannot be committed and have to be changed forbeing able to perform a commit.Uniqueness checks and ID generation are configured within the model and can beapplied to customer-defined meta classes and attributes.

Server-side consistencychecks

Server-side consistency checks have been introduced to:> improve performance,> enable uniqueness checks and> ensure consistency checks are executed on the complete model, even if only a partial

model is loaded in the client.

PREEvision 7.5


Online checks are executed on client side during runtime and on server side before acommit operation. Findings reported by the online check are highlighted in the ModelView and displayed in the E/E Online Check view. Online check results are alsoassociated to the corresponding artifacts and are displayed on the Online Checksproperty page of the artifact.

The highlighting of online check findings in the Model View has been adapted as follows:> Artifacts with a finding are indicated by a colored decorator according to the severity.> Artifacts without a finding, but containing a child artifact with a finding are indicated by

a grey decorator.Online checks are automatically initialized on the server. For existing E/E models, theaction Administration | Execute Online Checks on whole model has to be executedonce by an administrator in order to create the finding associations.It is possible to ignore online check findings for a specific artifact or meta class. In thiscase, the finding association is still set but the finding is no longer displayed in the ModelView and the E/E Online Check view.

Automatically creatingand arranging diagrams

PREEvision now provides a possibility to automatically create, arrange and refactordiagrams.With the help of metrics, diagrams can be automatically created and arranged accordingto a predefined layout. In this way, for example, it is possible to quickly create a newdiagram for a large number of newly imported artifacts or to rearrange an existingdiagram.

PREEvision 7.5


Artifact picker The Assistance View has been renamed to Artifact Picker.The following improvements have been made for the Artifact Picker:> A navigation bar (breadcrumbs) is displayed within the Artifact Picker to show the

parent hierarchy of a selected artifact.> The type-ahead filter now also works for trees.> From the Property View, the Artifact Picker can also be opened for drop-down lists.

Diagram handling The following improvements have been introduced for the general diagram handling:> Artifact Pickers can now be configured for diagrams. The definition of the Artifact

Picker is attached to the Diagram Configuration. Direct drag and drop from theArtifact Picker to the diagram is supported.

> Reusing an artifact in the current workspace and inserting it into a diagram can nowbe performed in one step via <SHIFT> and drag and drop.

> Formatting of number is now possible in the label configuration. For example, it canbe configured to display no decimal digit for the segment length in a GeometryDiagram. By default, no decimal digit is displayed if the value does not have one. Thedecimal digits can be configured in the label configuration, e.g. to display two decimaldigits: {0,number,#.00}; to display the value as defined in the attribute field: {0}.

> The populate behavior has been aligned. <F8> opens the Populate dialog on alldiagrams now. The selected populate options are stored for each diagram type.

Extensions for editors A new editor reference type Default To Command-ID Reference has been introducedwhich allows to register further (third party) editors for an artifact class.Registered editors are available in the Open with context menu. Optionally, it is possibleto configure the editor to be opened via double click on the registered artifact class.

PREEvision 7.5


Miscellaneous > Clustering the Open with context menu is possible by editor type. The result can bepasted in the search result view.

> An undo/redo history is available. The last ten actions are displayed when clicking onthe arrow next to the action button.

> Switching to the previous/next perspective is now possible via the arrows in theperspectives toolbar. By clicking on the arrow next to the action button, a history ofthe previously opened perspectives is displayed.

> The common parent can now be displayed to identify if context relations can bechanged although the artifact itself is checked-in.Displaying the common parent can be activated by the preference Show commonparent in property tables and in set content view. If enabled, tables in theProperty View show an additional column with the common parent to quickly identifyif the common parent is checked-in or not. Additionally, an icon in front of drop-downlists indicates that the association can be changed.

> The placeholder preview is now displayed by default.> Templates for commit and check-in comments can now be defined via configuration

files.

PREEvision 7.5



Reference: For detailed information about the installation, administration, operating andmigration, refer to the Operating Manual.

Factory reset A guided reset of the product delivery to the latest version is now possible viaAdministration | Perform Factory Reset....For existing E/E models, the artifacts which are part of the product delivery first have tobe annotated via the Administration | Annotate Artifacts for Factory Reset action.

Check for versioncompatibility

The application server now checks during login of the client, if the versions of the serverand the connecting clients are identical. If the versions are not identical the server deniesthe connection.

Anonymization ofdatabase models

Database models can be anonymized by the administrator. Anonymized models can betransferred to Vector for reproduction of bugs or for performance and migration tests.

Automatic bug reports Creating bug reports can be triggered manually or automatically. Bug reports aretransferred to the server and stored in the database. Stored bug reports can bedownloaded by an administrator and can be used for monitoring the system stability andfor reporting and reproducing bugs.

Improved data migration Data migration from 2-tier to 2-tier and 2-tier to 3-tier environments are only supported forthe head model, i.e. without history.Data migration from 3-tier to 3-tier environments is supported with or without history.Migration performance within 3-tier environments has been improved.Inconsistencies with regard to reuses and version history are automatically repairedduring migration.

Extended modelconsistency checks

Model inconsistencies with regard to asynchronous types, prototypes and instances canbe found via the Check Model Consistency action in the Administration menu.Inconsistent artifacts are displayed in the Information View and can either be repairedmanually or via metrics. The checks are also automatically executed to preventcommitting new inconsistencies.

Migration of the attributeEPDM-ID

The EPDM-ID has been renamed to ImEx-ID and is used for the AUTOSAR and FIBEXimport and export.For integration with third party IT systems, a custom EPDM-ID can be configured with thehelp of the new custom attributes concept.

PREEvision 7.5


9.4 Fixed issues

Fixed issues inPREEvision 7.5

You will find the important fixed issues in the following table. Please note that someissues are depending on specific configurations, views or models.

Further information > Common> Diagrams and tables> Product goals> Logical function architecture> Software architecture> AUTOSAR> Communication> Hardware architecture> Geometry> Product line approach> Functional safety> Rules, metrics and reports> Collaboration> Administration and license

9.4.1 Common

ID Issue Category

1790687424828 Meta classes and attributes related to editorreferences have been renamed according tothe display name. "Redirect" has beenrenamed to "Reference".

Common

1790689774828 Meta classes and attributes related to the chartconfiguration have been renamed according tothe display name.

Common

1790753028454 In the Artifact Picker, the type-ahead filter isnow also available for trees.

Common

1791069964825 The menu action Create URL now provides> the artifact URL or> a formatted text with the artifact's name

including the link to the artifactdepending on the formatting possibilities of thetarget application the URL is pasted to.

Common

1791675577721 Drag and drop menu actions are correctlyapplied without the <SHIFT> modifier, even if<SHIFT> has been pressed to select multipleartifact.

Common

1791676198454 The value of Integer Literals is set correctlywhen leaving the cell in which the value hasbeen defined.

Common

1791679880452 Favorites are now persisted locally and in SVN. Common

PREEvision 7.5


ID Issue Category

1791682410452 The Delete action is available on artifactswhich are placed within a virtual folder in theFavorites view.

Common

1791682420452 The wiring harness router action is nowavailable in the Favorites view.

Common

1791682430452 The circuit synthesis actions are now availablein the Favorites view.

Common

1792033809823 Diagrams and tables which are not included inthe active scope, are no longer displayed in theProject and Scope View.

Common

1792064898454 The drag and drop menu entries for drag anddrop of a Requirement, Customer Feature etc.are sorted as follows:> Copy after...> Copy before...> Move after...> Move before...Duplicate entries for Move after... and Movebefore... are removed. The drag and dropmenu entries Paste after... and Pastebefore... have been renamed to Copy after...and Copy before....

Common

1792065982791 The attributes Factor SI To Unit and Offset SITo Unit are now displayed on the Generalproperty page of a Data Type Unit.

Common

1792127248454 If the Search result view displays a largenumber of artifacts and all artifacts areselected, a dialog is shown to inform the userthat further artifacts are loaded into the view.

Common

1792276632791 For Base Types, the attribute Termination isnow available on the Base Type Attributesproperty page.

Common

1792362908454 Application Value Types can be moved andcopied now.

Common

1792382312647 The authority check for the Project View hasbeen removed to ensure that opening URLsalways succeeds.

Common

1792390569823 The Eclipse workspace no longer getscorrupted.

Common

1792398539824 The Search dialog can be opened again. Common

1792430542647 Within the Property View, External Links areshown as links even if there are white spacesin the link.

Common

1792574532689 Deleting the shortcut for opening theLibreOffice editor in the preferences no longercauses a LibreOffice crash.

Common

1792575409051 Changing the object configuration of anApplication Type Enumeration does no longerfreeze the user interface.

Common

PREEvision 7.5


ID Issue Category

1792575479822 LibreOffice no longer crashes when clickinginto a formatted text field.

Common

1792578288224 Performance of selection has been optimizedin the Model View. Fast navigation is possiblenow.

Common


ID Issue Category

1792074478454 The object configuration of Legend artifacts isnow consistent when opened from the ModelView or opened in the Legend diagram.

Diagrams

1792452822689 Labels can be made invisible in diagrams. Diagrams

1792466118454 Exporting a diagram as GIF file works correctlynow.

Diagrams

1792473022676 The diagram configuration can now bechanged even if a diagram is checked-in orcannot be edited, e.g. with a viewer license. Inthis case, the diagram configuration and thediagram will only be temporarily changed.

Diagrams

1792474842790 Multiple attributes can be integrated in a TitleBlock via query and are shown in the diagram.

Diagrams

1792575949051 Changing the header size is possible now. Diagrams

1782614729051 Copy and paste with multi-selection works intables now.

Tables

1791150242644 Refresh of tables works correctly now if anartifact is changed, also if more than oneartifact is displayed in one cell.

Tables

1792437368454 The buttons for expanding and collapsing fivelevels of the selected artifact are now workingin the whole table not only the ID column.Collapsing starts with the first expandableparent.

Tables

1792452288454 The column width can now be locally changedeven if the table is locked by another user.

Tables

1792524692689 Combined tables are now correctly opened bythe Open with command.

Tables

1792580409106 Drop down lists in tables are now sortedaccording to settings defined in the underlyingModel Query. The content is alphabeticallysorted if there is no sort order defined.

Tables

1792631732689, 1792631742689

The Excel export of a table regards hiddencolumns now.

Tables

PREEvision 7.5


9.4.3 Product goals

ID Issue Category

1792358909051 IDs of Safety Requirements are generatedcorrectly when using the Recreate IDrefactoring.

Product goals

1792438912709 During RIF import, special characters like ">"are correctly imported now.

Product goals

1792443162709 Attribute values imported during RIF import, dono longer contain XHTML tags.

Product goals

1792467057721 When pasting a multi-selection of CustomerFeatures as new artifacts in another package,IDs are correctly generated.

Product goals

1792485128454 Copying a Requirement and pasting it as copyinto the same package no longer causes aclient freeze.

Product goals


ID Issue Category

1791660768454 An Activity Chain can be selected as parent forthe Logical Architecture System Diagram.


1791208779824 Inheritance for mapping target is added toenable mapping of logical architecture blocksto external connector.


1792058519822 No message dialog is shown at refactoringConvert Block in case of creating a new type.


1792072579051 Labels are automatically updated in the LogicalArchitecture Diagram when changing the objectconfiguration of an artifact.


1792078402647 The context menu action Change to rectanglelayout is available for Activity Chains in theLogical Architecture System Diagram now.


1792079272647 Copying of Building Blocks has been enabled. Logical functionarchitecture

1792206382689 Creating mappings for a multi-selection ofblocks within a diagram works like in the ModelView now.


1792381148454 Deletion of an assembly connector does notgraphically delete the connected ports.


1792474192647 Assemblies can be modified in the PropertyView.



ID Issue Category

1790903842689 Problems with sender-receiver bus on softwarediagrams have been fixed.


PREEvision 7.5


ID Issue Category

1792066329822 Legend configuration has been unified and canbe defined either on the model or on thediagram in the same way.


1792477862647 Interfaces can be moved again via drag anddrop.


1792598527721 Not applicable settings are no longer offered inthe object configuration of compositions.


9.4.6 AUTOSAR

ID Issue Category

1791063226486 Importing Service Components creates theright UUID.

AUTOSAR

1792476930455 Frame Gateway Routing Entries are no longerexported in AUTOSAR.

AUTOSAR

1792583340455 Problems during AUTOSAR merge withassemblies connected to one port have beenfixed.

AUTOSAR

1792584030455 During AUTOSAR import, System Signals areset as transmittableSignal on the port.

AUTOSAR

1792655220455 When importing an AUTOSAR file with invalidor redundant UUIDs, more information isprovided in the log file to quickly identify theproblem.

AUTOSAR

1792655310455 During AUTOSAR import, theDataTypeFilter of the ReceiverComSpecis imported

AUTOSAR

1792655320455 During AUTOSAR import and export, attributesof the internal behavior are correctly importedand exported.

AUTOSAR

1792655330455 During AUTOSAR export, Timeout ofOperation Invoke (ServerCallPoint) isexported.

AUTOSAR

9.4.7 Communication

ID Issue Category

1790766066486 J2602 attributes, imported during LDF import,have been adapted to the new custom attributeconcept.

Communication

1791090990455 A new option is realized to route the SignalGroup itself instead of the single Signals of aSignal Group. The frame synthesis will thenuse and process these signal transmissions ofthe Signal Group.

Communication

PREEvision 7.5


ID Issue Category

1791205242709 For the DBC attribute GenSigStartValue bigvalues are supported by transforming the valueto a Long Literal, which can handle a value"0x80000000".

Communication

1792074730451 Multi-range coding for LIN signals are mappedto Linear Verbal Table Conversion during LDFimport and export.

Communication

1792268478454 Filter by sending component is possible inthe Advanced Settings dialog of theFlexRayCycleOrientedStatic table.

Communication

1792451478454 The FIBEX export creates a valid XML file. Communication

1792466440451 The performance of the DBC import has beenimproved.

Communication

1792524470455 Array Specifications can now be assigned toSignals as Initial Value and Raw Initial Valuevia the corresponding drop-down boxes on theSignal Attributes property page.

Communication


ID Issue Category

21938 All type artifacts are able to own multiple partnumbers.


22344 Attribute for electrical conductivity is added tothe wiring types.


1790851450452 It is now possible to create an instance of aConnector Type or of a Connector Prototype ata component by using drag and drop from theModel View to the component.


1791202012647 Changing the value of the attribute Direction ofan Internal Logical Connector is now possiblein the Property View.


1791315232693 Left and right connector side of the WiringHarness Inline Connector is now displayed onthe Pins property page.


1792032680452 The Connector Type has a new attribute for thecoding.


1792032690452, 1792067759051

The data model for Wiring Connectors hasbeen enhanced. It is now possible to define aPlug Cap Type and associate it with a WiringConnector.


1792033819823 It is now possible within the Wiring HarnessDiagram to move a splice along an alreadyconnected wire.


1792049960452 Attribute reference code is added to HardwareModule and Hardware Device.


1792050150452 Attribute alias name is added to HardwareModule and Hardware Device.


PREEvision 7.5


ID Issue Category

1792073182647 The Populate dialog of an Electric Electronicwas corrected within the Component Diagramand now contains options for adding hardwaremodules, memory modules, etc.


1792080140452 Via the Add/Remove/Reorder columnsdialog, a column to display the attribute Weightcan be added to a generic table which displaysconnector types.


1792254952647 During the refactoring of a Network Diagram toa respective System Diagram the completepath is displayed now within the dialogs forchoosing artifacts.


1792270500452 Within hardware diagrams no locks arerequired (for the Pin and Header) forgraphically moving a pin to the same headerconnector (if header connector is displayedmore than once).


1792399010452 During a KBL import all fixings will be importednow even those without an assignment to asegment.


1792451460452 The following artifact types are versionablenow: Schematic Pin, Wire Pin, Component Pin,Topology Segment, Branch Off, InlineConnector, Installation Location and ConnectorLocation.


1792456187721 Lower bounds for Conventional Connection,Ground Connection and Power DistributionConnection are adjusted, so that deletion ispossible without check-out.


1792461049051 The KBL import is now capable of recognizingKBL headers that do not include line breaks.


1792463979051 During a KBL import the value of abbreviationof Connector_housing or Fixing will beimported to the name of the connector PlugType or Topology Type if no part number isdefined or the part number has value /NULL.Otherwise, the value of part number will beimported as name.


1792474988454 Pins can be selected in the Resolve Splicerefactoring dialog.


1792480859051 The offset values for Topology Segmentintervals can now also be filled with negativevalues from within the Property View.


1792481239005 During a KBL export the description of aTopology Type will now be exported as adescription of the fixing in KBL.


1792481289005 During a KBL export the name of a TopologyType will now be exported as an abbreviationof the fixing in KBL.


PREEvision 7.5


ID Issue Category

1792484039005 During a KBL export the description of theconnector type is now exported to KBL-ConnectorHousing.


1792489067721 Refactorings for converting a PowerDistribution Input Connector to a PowerDistribution Output Connector and vice versahave been added.


1792489077721 Refactorings for changing connectors are nowavailable on the connector itself.


1792595402790 During a KBL import, KBL modules areimported as sets in PREEvision.If a KBL module belongs to a ModuleFamily,the attributes (like the name) are also correctlytransformed.More than one ModuleFamily (being mappedto variant packages) are now supported.


1792625727721 During a KBL import the EPDM-ID (new ImEx-ID) in PREEvision is no longer set. The partnumber of the KBL module is now mapped tothe ID of the set. The KBLLogistic_control_information is nowmapped to the code of the set.


1792583989005 During a KBL export the description of theconnector plug type is now exported to KBL.


9.4.9 Geometry

ID Issue Category

1774844422689 Geometry Diagrams containing Sections areprinted correctly now.

Geometry

1792044542696 The actions to set the size of a Section, toshow or hide the coordinate system and tochange the column count of labels are nowavailable in diagrams without a lock. The auto-lock mechanism is used now.

Geometry

1792050170452 Attribute offset absolute is added to TopologySegment Point.

Geometry

1792067719051 The Topology Type has an enumeration to setthe type kind. This type kind has beenenhanced with two new values ("Marker" and"Other").

Geometry

1792353282709 Topology Segment points and intervals arenow displayed correctly when executing apopulate on a segment within the GeometryDiagram.

Geometry

1792451010452 It is now supported that a multi-selection ofsegments is not lost when changing to thediagram. This allows to open the context menuon multiple selected segments and perform anaction on this selection.

Geometry

PREEvision 7.5


ID Issue Category

1792648212709 3D Way Point can be deleted without deletingits parent artifact.

Geometry


ID Issue Category

1746374792689 Planning relations are added to the Asset, sothat the Asset is a plannable artifact.


1791300802714 When moving artifacts which have beenreused, the reuses are now consistent after themove action.


1791321589823 A scrollbar has been integrated in the Reuse-dialog to enable displaying a large number ofartifacts.


1791525798157 If a new Set is added to a Template, it will beautomatically added as non-selected in theAlternative.


1792388952647 It is now possible to reuse a Product Line. Product lineapproach

1792476210455 Application Type Implementation TypeMapping is a version artifact now and can beassigned to an Asset.


1792488917721 Merging Asset artifacts is possible even if thetarget is checked-in.



ID Issue Category

1792403627721 A Malfunction Mappings package can bemoved now.

Functional safety

1792432772727 Requirements can now also be mapped onSW-NET mappings.

Functional safety

1792452338454 The performance of the minimal cut setanalysis was optimized. Additionally, aparameter for the order cut off can be set.

Functional safety

1792452358454 The minimal cut set analysis takes reuse ofmalfunctions into account.

Functional safety

1792584452647 The Analysis package is now copyable andmoveable.

Functional safety


ID Issue Category

1792077199823 Consistency checks can now also be executedon a multi-selection.

Rules

PREEvision 7.5


ID Issue Category

1792216638454 Exception is handled now when dropping ameta class of one rule model e.g. consistencyrule model into a rule diagram of another rulemodel e.g. query rule model.

Rules

1792352398157 If a multi-user EE model contains a file-basedrule model and the rule model is openedwithout having been locked a warning isdisplayed, indicating that changes to the modelcannot be saved. In addition, no changes to themodel are possible anymore until the modelhas been locked.

Rules

1790468317721 Metric blocks in the metric editor are no longerhighlighted by the variant highlighting.

Metrics

1792066357721 The context of a Metric Context Block in aMetric Diagram can be dereferenced again.

Metrics

1792623240451 Creating a Calculation Block in a MetricDiagram works correctly again.

Metrics

1792047379823 Multi-line labels in diagrams are renderedcorrectly during report generation.

Reports

1792047379823 Static text fields in in diagrams are renderedcorrectly during report generation.

Reports

1791216669823 The report generator can now handle reportswith many diagrams.

Reports

1792442629005 The Diagram Render Block now considers thediagram state before execution: openeddiagrams remain opened afterwards.

Reports

1792466497721 Header style in lists of a report template arenow correctly generated.

Reports

1792574768454 If Report Module is configured correctly theheader in the generated report will be showncorrectly.

Reports

1792601242690 The property "versionInDB" of the ApplicationContext is available again.

Reports


ID Issue Category

1715176508454 Check-in and commit comments can bepredefined with a global template (configurationfile).

Collaboration

1791676268454 The commit history works now when switchingfrom offline mode to online mode.

Collaboration

1792038238454 Formatted texts which have been madeavailable for offline use are no longer lost ifPREEvision was not closed correctly.

Collaboration

1792074482687 Database user can always authenticateirrespective of the LDAP configuration.

Collaboration

PREEvision 7.5


ID Issue Category

1792074628454 A commit which contains changed files can beexecuted without error message.

Collaboration

1792207849005 An error message is added for writing toprotected XMI file.

Collaboration

1792279092644 Performance of commit is improved whenworking with the multi-selection feature in theProperty View.

Collaboration

1792358898454 Changing the user password is now handledcorrectly. When opening a project whichreferences the old password, the user isrequested to enter the new password.

Collaboration

1792398618454 The default socketTimeout value of theclient was changed to 30 seconds.

Collaboration

1792401988454 When reading the file resources, during copy offiles, the file attributes are not set again.

Collaboration

1792432692647 The context menu for life cycles is only shownif a life cycle is assigned to the meta class ofthe selected artifact.

Collaboration

1792452822687 Locking and creating lost and founds isprevented when the user does not have accessrights to lock or create artifacts (e.g. with aviewer role).

Collaboration

1792470678454 Comparing two revisions of a Requirement viathe Property View is now possible. The usedSQL statements have been changed to preventa database freeze.

Collaboration

1792482320455 The action to undo all own locks consists oftwo parts:1. Undo local changes.2. Undo locks.Undo of local changes is executed prior toundo all locks by a server call. If that actionsfails a message is displayed instructing theuser to disconnect and clear the client cache.

Collaboration

1792524602689 If a commit of a file artifact is made from anexternal SVN client into PREEvision, thecorrect PREEvision user is used as changeauthor now.

Collaboration

1792541472709 Metric execution helper for check-out no longerexecutes as job causing no more deadlocks.

Collaboration

1792570688454 Handling of exceptions which occur duringauto-lock: Per default, error status will bereturned. Only if auto-lock was successful, thestatus will be set to OK.

Collaboration

1792578118454 Setting a new attribute value does not trigger acheck-out if the new value is the same as theold value.

Collaboration

1792593908454 Reuse created after Replace with latestrevision can be committed successfully.

Collaboration

PREEvision 7.5


9.4.14 Administration and license

ID Issue Category

1791313602677 For performance reasons, the Oracle feature"cardinality feedback" should be disabled in thedatabase. If this is not possible, an additionalinitialization parameter to disable the feature isnow automatically set each time when getting adatabase connection.If the "cardinality feedback" can be disabled inthe database, the parameter does not have tobe set for each connection. To prevent, that thesetting is applied to each connectionindividually, the following parameter should beset for startup of the application server:-DdbPerformanceParametersSet=true

Administration

1792212828216 The project name may only contain letters,numbers, "_" and "-". The maximum length ofthe project name is 20 characters in 3-tier and27 characters in 2-tier environments.

Administration

1792443592687 HTTPS connections can now be establishedwith multiple certificates in the cert store. Thecorrect certificate is chosen at runtime with thehelp of a regular expression.

Administration

1792467582687 In the User Management view, multi-selectionof users to be deleted works again.

Administration

1792476752689 Cheat sheets are immediately available afterstart of the client.

Administration

1792602389079 Client and server side system properties arenow added as entries to the bug report dialog.If these entries are selected, the systemproperties are collected, sorted and saved intotwo different text files for server(ServerSystemProperties.txt) and client(ClientSystemProperties.txt). Thesetwo files are stored into the bug report ZIP fileunder the subfolder systemproperties.Additionally, the client INI file is also included inthe bug report.

Administration

1792603009824 Messages displayed in the Status View onstarting the client have been corrected.

Administration

1792464922687 In the license server dialog, the web applicationname is provided in the web application fieldafter an upload of a middleware license file.

License

1792464932687 In the license server dialog, the default port forthe middleware license server is set to 8080.

License

1792602832687 For the middleware license server, the licenseserver user is authenticated by the databaseuser accounts. Administration rights arerequired to access the license server.

License

PREEvision 7.5


9.5 Known issues




Default value handlingdoes not work correctly(1792665172666)

Default value handling for custom attributes does not work correctly on the list-basedpage of the Property View (display and reset to default value not possible).Workaround: Use the table-based property page for displaying and resetting defaultvalues of custom attributes.

Get more Information

Visit our Website for:> News> Products> Demo Software> Support> Training Classes> Addresses

www.vector.com

PREEvision ReleaseNotes 7.5.8 EN · 7.5.6 7.5.6 7.5.5.02 7.5.7 7.5.7 7.5.7.02 For an update of an...

Documents

Transcript of PREEvision ReleaseNotes 7.5.8 EN · 7.5.6 7.5.6 7.5.5.02 7.5.7 7.5.7 7.5.7.02 For an update of an...