Innovator 11. Manual Version Management. Versioning Models and Model Elements.

Transcription

1 Innovator 11 Manual Version Management Versioning Models and Model Elements

2 Manual Version Management Innovator 11 (version 11.2) Edition July 2010 Copyright MID GmbH Nuremberg, Germany. All rights reserved. The copyright for Innovator software and the accompanying documentation is the property of MID GmbH. Any reproduction or publication in part or in whole requires the written authorization of MID GmbH. Any violations of this will be prosecuted in accordance with copyright protection laws. Registered trademarks and trade names are used in this documentation. Protection provisions apply to same, even if they are not marked as such. The content of the documentation is for information purposes only and MID GmbH reserves the right to change it at any time without prior notice. MID GmbH will not be held liable for any damages arising from the use of the software or documentation.

3 Contents Contents 1 Foreword...1 Versioning with Innovator File-Based Versioning Basics and Prerequisites...2 Rights Required... 3 Settings... 3 Search Command... 3 Exporting Model Configuration... 3 Path Component and File Name for Version Files... 3 Preparing and Post-Processing Exporting and Importing Version Files...4 Exporting excellence Models into Version Files... 4 Importing excellence Models from Version Files... 5 Exporting classix Models into Version Files... 6 Importing classix Models from Version Files Versioning Using the API Interface SCC Interface Integration With PVCS Version Manager and PVCS Dimensions Integrated Repository-Based Versioning Basics and Prerequisites...11 Version Management Repository Version Management Browser Management Nodes Path Names of Management Nodes Filters for Management Nodes Displaying Version Differences User Authorization Version Management Server and Repository Versioning Elements...15 Logging-In to the Version Repository Exporting Elements Releasing Elements Importing Elements Versioning Element Groups...18 Exporting Groups Releasing groups Importing Groups Copyright 2010 MID GmbH I

4 Contents Index...21 II Manual Version Management Innovator 11

5 1 Foreword Within software development, versioning is characterized as the archiving of alternative file versions. These can be both older file versions and alternative file versions which are e.g. part of a new branch of development. Versioning is carried out to enable previous versions to be restored and, in doing so, e.g. undo previous changes made. In developing new software or maintaining existing systems, you frequently need different versions of elements or groups of elements of a model, e.g. for prototyping purposes. Depending on whether a new version turns out to meet the requirements, it will either be kept or rejected in favor of one of its predecessors. In some cases, it may also be necessary to develop different versions of an element in parallel, e.g. a class with its implementation. You can easily version all elements of the Innovator online repository. You can utilize these version elements at any time. You can use version elements to reuse defined information as templates in new models. Versioning with Innovator Innovator is not file-based, but rather repository-based and, therefore, has various distinctive features when versioning. The main difference is that model elements essentially have references to other parts of a model (or in other models and/or repositories too). This means that, in principal, it is not possible to version files which are largely independent of each other. As an integrated modeling platform, Innovator provides a basis for versioning which deviates from the normal standard. This means that there are certain aspects which should be taken into consideration when starting a project. Note Innovator provides the following versioning options: File-based versioning, which enables any number of version managements to be connected (see chapter 2, page 2) Connecting foreign version management using the API interface (see chapter 3, page 9) Integrated repository-based versioning using Innovator's version management server and version management browser (see chapter 4, page 11) Copyright 2010 MID GmbH 1

6 2 File-Based Versioning 2.1 Basics and Prerequisites You can package any number of model elements together as one version file and export them to the file system using file-based versioning. Dialog Box for Exporting a Version File (in the Model Browser) You can export this file into any external version management or import from there using an customizable command line for preparing and postprocessing. The version data can also be directly imported from the file system. This mechanism can be used for external version management, as well as for copying between various Innovator models. 2 Manual Version Management Innovator 11

7 You require the VM (classsix) or Version (excellence) privilege for exporting and importing version files. You need to have the execution right if you want to use a search for the selection. You can get this by assigning your user role with model administrator rights. Rights Required You can save all settings in the dialog boxes for export or import. Selecting a stored settings saves having to type in the same information again. Settings You can enter a search when exporting for specifying the selection; you require execution rights for this. No selection needs to be made when importing as the file to be imported contains information about assignment of the element. Search Command The profile elements required are automatically exported and created as wildcards in the configuration when checked-in in excellence models. You can specify whether the model configuration should also be exported when exporting in classix models. Model configuration is not necessary if the file should be loaded into the same model or into a model with identical configuration at a later stage; the file does not need as much storage space in this case. The model configuration also needs to be imported when importing the file into another type of model so that inconsistencies are avoided. Exporting Model Configuration The path component and file name are only stored once (i.e. not separately) in the file with the settings when exporting and importing. The path component should never be modified when using an external version management. To avoid accidental changes being made, it is only possible to change the path component in the file selection box if another file is selected. Path Component and File Name for Version Files A command line can be entered in front of the command. This can be a command line call for an external version tool so that the object can be checked-out and reserved. There is a post-process after the command upon export. You can use this command line to import the element into the external tool. You can configure the command line for preparing and post-processing to suit your needs. The following wildcards are available for this: %1 Complete file path component %p Complete directory path component %n File name or extension %e File extension %m Model name Preparing and Post- Processing Copyright 2010 MID GmbH 3

8 %r Repository name %u Name of the user logged-in 2.2 Exporting and Importing Version Files You can export a model into one or more version files and then import into a target repository in a (preferably new, empty) model of the same type and Innovator version (Release, XX.X). You can also copy or move a model into a target repository which is not available in the source repository's administration program in the same way. (Otherwise, copying and pasting is the correct choice.) The source model can be deleted after inserting the target model so that the model can be moved. Attention Existing model-external references (mapping, references to drives etc.) cannot be copied or moved into another repository, as version files moved or copied in this way are not exact 1:1 copies of the source model 1. Note Bear in mind when moving models that a repository server is a serial process: the processing times may be increased by the more models collected in a repository and the more users that work in these models at the same time as one another. If e.g. a user creates a documentation in a model, all other users in all models have to wait for them to do this! You can find the menu items for file-based versioning in the model browser in the Model>Version File submenu; they can also be found in the Configuration menu in the configuration editor for excellence models (Configuration>Export>To Version File... or Configuration>Import>From Version File...). Exporting excellence Models into Version Files The configuration is managed separately in the configuration editor for excellence models. This means that the configuration (including browser configuration, if applicable) and the model should be exported and imported separately. You need to be logged-in to the model as administrator to be able to export a model and its profiles into a version file. 1. Report models cannot be exported as version files as they are mostly based-on modelexternal references. This means that they cannot be copied or moved. 4 Manual Version Management Innovator 11

9 How to proceed To export an excellence model s profiles into a version file:» Jump to the source model s configuration editor.» Select the bottom profile in the profile tree on the left-hand side in any view, then with [Shift]+[LMB 1 ] pressed, the top profile (<model type> excellence) and then with [Ctrl]+[LMB] pressed, the model s root node. The root node and all profiles are selected.» Select Configuration>Export>To Version File... The dialog box of the same name appears.» Rename the version file in the Filename field and save it under the $(INOTMP) path or Select the directory and filename using the selection dialog box. Enter a file name for the copy of the profile with the.aob file ending.» Confirm the selection with [OK]. Export of the model s profiles as a version file starts; this may take some time. How to proceed To export an excellence model into a version file:» Jump to the source model's model browser with Jump>Model Browser.» If you are already logged-in to the model with your user name, select Model>Administration>Login... to gain administrator rights. The icon in front of the user name becomes a key in the status bar.» Select the model s root node in the model tree on the left-hand side.» Select Model>Version File>Export The dialog box of the same name appears.» Select the Package Contents Recursive entry from the Use Search drop-down list.» Rename the version file in the Filename field and save it under the $(INOTMP) path or Select the directory and filename using the selection dialog box. Enter a file name for the model copy with the.aob file ending.» Confirm the selection with [OK]. Export of the model as a version file starts; this may take some time. You must be logged-in as an administrator for the repository in order to be able to create a new model. You must be logged-in as an administrator for the model in order to be able to import a version file. Importing excellence Models from Version Files 1. LMB = left mouse button Copyright 2010 MID GmbH 5

10 How to proceed To import the exported version file with the model copy into a new model:» Login as repository administrator in the target repository in the administration program. To do this, select the repository and go to Administration>Repository>Administrator Login...» Select Administration>New Model><Model Type>... to create an empty model of the exported type.» Select Container for Version Import as model template and None as User/group configuration. If required, enter a password.» Login as administrator in the new model (using the password just entered, if required).» In the model browser, select Model>Version File>Import The dialog box of the same name appears.» Select the exported version file with the model copy using the selection dialog box and confirm the selection with [OK]. Import of the model starts; this may take some time.» Check the copied model. How to proceed To import the exported version file with the profiles into a new model:» Jump to the new model s configuration editor using Jump>Configuration.» Select Configuration>Import>From Version File... The dialog box of the same name appears.» Select the exported version file with the profiles using the selection dialog box and confirm the selection with [OK]. Import of the model s profiles starts; this may take some time.» Check the copied profiles. How to proceed To move the model:» If you want to move the model, delete the copied model in the source repository in the administration program. The model and its profiles are deleted. Exporting classix Models into Version Files classix models also contain their configuration, which comprises both the model and the user configuration. You need to have the VM (version management) execution right to be able to export a model into a version file. 6 Manual Version Management Innovator 11

11 How to proceed To export a classix model into a version file:» Jump to the model browser of the classix model you want to export into a version file.» If you are already logged-in to the model with your user name, select Model>Administration>Login... to gain administrator rights. The icon in front of the user name becomes a key in the status bar.» Select the model s root node in the model tree on the left-hand side.» Select Model>Version File>Export The dialog box of the same name appears.» Select the Package Contents Recursive entry from the Use Search drop-down list.» Activate the Including Model Configuration check box.» Rename the version file in the Filename field and save it under the $(INOTMP) path or Select the directory and filename using the selection dialog box. Enter a file name with the.tob file ending.» Confirm the selection with [OK]. Export of the model as a version file starts; this may take some time. You must be logged-in as an administrator for the repository in order to be able to create a new model. You must be logged-in as an administrator for the model in order to be able to import a version file. Importing classix Models from Version Files How to proceed To import a classix model's version file into a new model:» Login to the target repository in the administration program as repository administrator to import the exported version file into a new model. To do this, select the repository and go to Administration>Repository>Administrator Login...» Select Administration>New Model><Model Type>... to create an empty model of the exported type.» Select Container for Version Import as model template and None as User/group configuration. If required, enter a password.» Login as administrator in the new model (using the password just entered, if required).» In the model browser, select Model>Version File>Import The dialog box of the same name appears.» Select the version file which has just been exported using the file selection dialog and confirm the selection with [OK].» Check the copied model. Copyright 2010 MID GmbH 7

12 » If you want to move the model, delete the moved model in the source repository in the administration program. 8 Manual Version Management Innovator 11

13 3 Versioning Using the API Interface 3.1 SCC Interface It is also possible to connect foreign version managements in Innovator via API interfaces. An interface defined by Microsoft is used with source code control (SCC) to connect version management systems. The integration is only available under Microsoft Windows as the interface is only defined for Windows. Note The following systems are integrated via the SCC interface: Rational ClearCase (co. IBM) PVCS Version Manager (co. SERENA) Other version control systems that support this standard interface can be integrated. The Java program or Tcl script needs to be customized accordingly. You can load the CONNECT ClearCase (en) add-on for connecting ClearCase; this provides the required engineering actions, configuration and icons. Execution is different for excellence and classix models. Innovator excellence Innovator excellence executes the connection using the Innovator Java API with the inoscc.jar archive. Innovator classix Innovator classix executes the connection using the Innovator Tcl API with the kmtools.tcl Tcl script. 3.2 Integration With PVCS Version Manager and PVCS Dimensions Only Innovator classix has the traditional option of integrating the SER- ENA company with PVCS Version Manager and PVCS Dimensions. Copyright 2010 MID GmbH 9

14 This integration enables access to any version, both via the Innovator GUI and the PVCS Version Manager or PVCS Dimensions GUIs. The integration provides the following functions: Checking-in/out of all lockable elements, element groups or whole models Checking-in/out via convenient dialog interfaces or in batch mode Representation of the Innovator elements directly in PVCS via the integration of the appropriate Innovator editors Support for all call options of the PVCS commands put and get Transparent control of Innovator integration via engineering actions The inoaob.exe help program can be used for supporting these connections by e.g. displaying certain version objects (artifacts, code etc.) in the respective editors. 10 Manual Version Management Innovator 11

15 4 Integrated Repository-Based Versioning 4.1 Basics and Prerequisites The repository-based versioning is characterized by the following aspects: Separate version repositories which can be edited via the model browser or version management browser Logging-in to the version repository as a user with read only rights (including import for activating version elements and groups) Logging-in to the version repository as administrator with all rights Log-in occurs globally, i.e. all models of all repositories can access the version repository which the connection is made to. Connection is canceled if you explicitly log-out or if the application is closed. Importing and exporting model elements, groups of model elements and models You can check-in individual elements and element groups from a model and external objects in an Innovator version repository and keep them there in various versions. External objects must exist in an ASCII-coded form. When checking-in an element, the user may create a note that can, for example, include the reason for the element being checked-in. In addition to checking-in and out, the following functions are available for version elements: Releasing and locking version elements so that version elements can be reused. Deleting version elements and groups Assigning key words Displaying, searching and comparing version elements When version elements are checked-out, released or deleted, you can search for key words or persons who checked-in the version element. Version Management Repository The version management browser shows you the contents of a version repository, similar to a file system. In the version management server, the concept of a folder in a file system is represented by the management node. Version Management Browser Copyright 2010 MID GmbH 11

16 In addition to the Innovator version management browser, you may also use the Innovator model browser for moving individual elements and completing element groups from the model repository to the version repository and vice versa. This way, older versions can be edited in the model repository and written back to the version repository. You can find the menu items for repository-based versioning in the model browser in the Model>Version Repository submenu. Note Versioning Element Groups and chapter "Versioning Elements" describe versioning from the perspective of the model browser and not from the version management browser's view. Management Nodes Management nodes are used for grouping version elements in the version management repository and can be hierarchically structured. Version elements are always assigned to a management node. An element may also be stored below different management nodes. Since elements are not versioned globally but only below a management node, it is possible to keep and implement different instances of an element in parallel in the version repository. Versioned elements can be identified by their name and element type in the version repository. If an element with the same name and element type already exists in the management node when an element is checked-in, a new version of this element is created. Only the differences between versions (delta information) are stored. If two elements with the same name and element type exist below two different management nodes, these are treated as two different elements. Path Names of Management Nodes Individual components of management node paths are separated by \\. The version number appears in square brackets after the name of the nodes and the element. Example: project[0]\\node[1]\\object[1] When checking-in an element or group, the next highest version number is assigned or [0] is assigned for the first version. Example: If there are already 2 versions ([0] and [1]) in the node management node, project[0]\\node must be entered if a new version of the node group is checked-in. Version project[0]\\node[2] is then created. If a new element element (which doesn't contain a version yet) needs to be checked-in for the node management node's second version, the project[0]\\node[1]\\element[0] version appears once project[0]\\node[1] \\element is entered. 12 Manual Version Management Innovator 11

17 A new higher level can also be created at the same time as checking-in. version number needs to be entered for this. Example: project[0]\\node[1]\\subnode[@]\\object creates the project[0]\\node[1]\\subnode[0]\\object[0] version according to the prerequisites described above. This method can be used to created a completely new root node. A filter can be used in dialog boxes for selecting management nodes and elements. The full name of all specified nodes must be entered. You can do this below all top-most hierarchy levels. The following options are, however, available to the user for constraints regarding the path nodes' versions: It is assumed that the node node has versions 0,1 and 2, which contain the element element respectively. The node[0]\\ filter then delivers all elements of the node node's first version: element[0.0] If no version is entered in the path component for the node which is entered last, the selection remains parallel. Subnodes or elements for all versions are then displayed. The node\\ filter then delivers elements of all node node's versions: element[0.0] element[1.0] element[2.0] Intervals can also be entered for version numbers. The node[0-1]\\ filter only delivers the elements of the node node's first two versions: element[0.0] element[1.0] The newest version always appears is entered. The node[@] filter then delivers elements of the node node's version 2: element[2.0] Filters for Management Nodes You can use Innovator's integrated difference comparison program to compare the logical differences between versioned models or parts of models with each other or with the current online model. For more information, read Diff Utility Manual. Displaying Version Differences There are two ways of versioning elements with Innovator. Firstly, individual elements (e.g. classes) can be exported or imported as so-called objects. Another option is to combine a set of individual elements as a group. This means that it is possible to e.g. check-out an entire analysis model from a running project and import it into a new project. An administrator needs to release a version repository before elements can be imported from other models. User Authorization Copyright 2010 MID GmbH 13

18 The authorizations needed for exporting or importing elements are clarified in the following table: Elements or Element Groups Standard User Administrator... Exporting Not possible Possible... Importing From other models - only possible after release by administrator All elements - not just those which have been released Authorization Requirements When Exporting or Importing Elements Version Management Server and Repository You need to start the version management server using the version repository before exporting or importing elements or groups of elements. These then need to be logged-in to the model which you want to export elements from. Note Data and version repositories with the same name cannot be created in the same directory as the repository name is also the same as the repository's directory name. How to proceed To start the version management server with a version repository:» Start the Innovator program and start the version management server program in the version management folder (inovsrv.exe). A: To use an existing version repository, select the directory and directory repository in the corresponding fields. B: To create a new version repository, select the desired directory in the appropriate field and enter the desired name in the Repository field. The information, Repository will be created, is displayed.» Confirm the selection with [OK]. The version repository is started and should now be visible in the administration program's repository tree under the entry Version Repository/Company Repository or Local Repository.» Log-in to your model with your user name. You can find more information about the version management server using the "more" link in the [F1] help. 14 Manual Version Management Innovator 11

19 4.2 Versioning Elements Before you can export elements from a model, you first need to be loggedin to a version repository. You can only export elements if you are logged-in as the administrator. Logging-In to the Version Repository How to proceed To log-in to a version repository:» Select the Model>Version Repository>Login... menu item in the model browser.» Select the desired version repository from the Repository drop-down list.» Activate the Login as Administrator check box.» If there is a password, enter the respective administrator password.» Click on [OK]. You have now logged-in to the version repository as administrator. You can check if you have successfully logged-in by looking for the version repository icon in the third section of the model browser's status bar and in the Versionsrepository:<name>(Administrator) tool tip. (If you have not logged-in, there is no icon there and the No connection to a version repository tool tip.) There are two options for specifying which elements can be checked-in in the version repository: Exporting Elements A: Selecting the element in the model browser's detail view B: Selecting the element and transferring it in the model browser's result region It is assumed that the elements have now been moved to the result region and are selected. How to proceed To export elements in a version repository:» In the model browser, select the element (e.g. a class) to be exported and select the Edit>Result Region>Add Selection menu item. If required, repeat this step for further elements.» Ensure that the elements to be exported are selected in the result region.» Select the Model>Version Repository>Export Objects... menu item The dialog box of the same name appears. Copyright 2010 MID GmbH 15

20 » If necessary, enter a note about the elements.» Close the dialog with [OK]. The Export Information info window provides information about the export's progress. Releasing Elements An element must be released by the version repository's administrator before a standard user can import it. This is carried out with the Version management browser program (inovb.exe). How to proceed To release elements for import using the version management browser:» Start the Innovator program group and start the Version management browser program in the version management folder (inovb.exe).» Jump to the repository tree and click on the icon next to the name of the version repository.» Log-in as administrator.» Select the Edit>Release>Object menu item in the version management browser. The models which contain elements which have already been exported in the version repository are displayed in the Nodes list.» Select the model which contains the elements which should be released for import. The elements which have been exported from the model are displayed in the Objects list.» If necessary, restrict which elements are displayed using a filter. The following options can be used for this: - User Shows the elements which were checked-in by a certain user (e.g. MID GmbH) in the Objects list. - Element Types Shows the elements which belong to a certain type (e.g. class, class diagram,...) in the Objects list. - Key word Shows the elements which are associated with a certain key word in the Objects list.» Select the element which you want to release for a standard user to import in the Objects list. The number at the end of the element entry shows the element's respective version, e.g. 'Account.java (Business Objects::Java Implementation::Account)[0] component» Click on the [Show] button to display the versioned element.» Activate the Grant radio button. 16 Manual Version Management Innovator 11

21 » Click on [Grant...]. You can also enter a release text about the element in the resulting dialog.» Click on [OK]. After the element has been successfully released, it disappears from the Objects list and a standard user can subsequently import it. You need the VM privilege (version management) for importing elements. If you are not logged-in as administrator in the version repository, you can only check-out version elements which were explicitly released by the administrator. It is assumed that the elements have been released by an administrator. Importing Elements If an element is imported into a model which contains an element with the same name (including the path component), this is overwritten upon import. Note How to proceed To import elements:» Log-in to the version repository as a standard user in the model browser using the Model>Version Repository>Login... menu item.» Select the Model>Version Repository>Import Objects... menu item» Select the desired model in the Nodes list.» If necessary, restrict the elements found by selecting the User, Element Type or Key Word filters and clicking on [Filter].» The elements which can be imported (dependent on the filters) are displayed in the Objects list. If there are various versions of an element, the respective valid version number can be seen at the end of the element's name (e.g. Class `Standing-Order(...)[1]`).» Select the element you want to import.» If you want to view the versioned element, click on the [Show] button.» Click on [Apply]. The selected element is imported in the model as a current element. If an element with the same name already exists in the model, this is overwritten when the element is imported. Copyright 2010 MID GmbH 17

22 4.3 Versioning Element Groups Versioning of groups enables you to combine elements of various types (e.g. classes and use case diagrams) as one logical group. Exporting Groups Groups can only be exported by a version repository administrator. How to proceed To export groups:» Log-in to the version repository as administrator in the model browser using the Model>Version Repository>Login... menu item.» In the model browser, select the elements which you want to export as a group or move these to the result region using the Edit>Result Region>Add Selection menu item and select it there.» Select the Model>Version Repository>Export Groups... menu item in the model browser.» Either assign a new name for the group in the Group Name drop-down list in the dialog box of the same name or select a group which already exists. If you choose a group which already exists, a new version of the selected group is created which contains the marked elements. You can set whether the complete model should be exported or whether you want to combine the marked elements in the results region to form a group using the Complete Model and Selected Nodes Only radio buttons.» Activate the Selected Nodes Only radio button. (If you want to 'freeze' a model's complete state, activate the Complete Model radio button.)» Close the dialog with [OK]. The Export Information info window provides information about the export's progress. Releasing groups A standard user can only import groups of elements from other models if the version repository's administrator has already released these for import. This release is carried out as with individual elements with the Version management browser program (inovb.exe). 18 Manual Version Management Innovator 11

23 How to proceed To release groups for import:» Start the Innovator program group and start the Version management browser program in the version management folder (inovb.exe).» Jump to the repository tree and click on the icon next to the name of the version repository.» Log-in as administrator.» Select the Edit>Release>Group menu item. The models which contain groups which have already been exported are displayed in the Nodes list.» If necessary, restrict which groups are displayed using a filter. The following options can be used for this: - User Shows the groups which were checked-in by a certain user (e.g. MID GmbH) in the Nodes list. - Element Types Shows the groups which belong to a certain type (e.g. class, class diagram) in the Nodes list. - Key word Shows the groups which are associated with a certain key word in the Nodes list.» Set the type of release using the check boxes: - Current If you activate the check box, the newest version of all elements in the group is released, otherwise older versions are released. - Hierarchical If you activate the check box, all newest or oldest elements in the complete hierarchy below the selected verification node are covered, otherwise only the elements in the level directly below the node. - Overwriting If you activate the check box, if applicable, a release text which already exists is overwritten during this pre-defined release action.» Double-click on the corresponding model in the Nodes list. A model's groups are then displayed with the corresponding version numbers. If a note about the group was created upon check-in, this appears in the field with the same name.» Select the group and desired version in the Versions list.» Activate the Grant radio button.» Click on [Grant...]. You can also enter a release text about the selected groups in the resulting dialog.» Click on [OK]. The elements affected are now also available to normal users. Copyright 2010 MID GmbH 19

24 Importing Groups You need the VM privilege (version management) for importing groups. If you are not logged-in as administrator in the version repository, you can only import version elements which were explicitly released by the administrator. It is assumed that the elements have been released by an administrator. Note If a group is imported into a model which contains an element with the same name (including the path component), this is overwritten upon import. How to proceed To import groups:» Log-in to the version repository as administrator in the model browser using the Model>Version Repository>Login... menu item.» Select the Model>Version Repository>Import Groups... menu item» If necessary, restrict which groups are displayed using the User filter which shows the groups which were checked-in by a certain user (e.g. MID GmbH) in the Nodes list.» If the newest versions of all elements in the group should be imported, activate the Current check box.» Double-click on the desired model in the Nodes list. The groups contained within this are then displayed with the corresponding version numbers. By double-clicking on the node again you can see the group's structure which corresponds to the model's package structure.» Select the group to be imported and the desired version.» Click on [Apply]. The elements which belong to the selected group are now imported as current elements in the existing model. Elements which already exist and have the same name are overwritten when the elements are imported. 20 Manual Version Management Innovator 11

25 Index Index C Configuration -Exporting the model~ 3 Current (release) 19 D Delta information 12 Difference comparison program 13 Displaying -Version differences 13 E Element -Releasing 16 -Versioning 15 -Versioning of groups 18 Element Types -(Filter) 16, 19 F Filter -Element Types 16, 19 -For management nodes 13 -Key word 16, 19 -User 16, 19 H Hierarchical (release) 19 K Key word -(Filter) 16, 19 M Management nodes 12 Model -Copying into another repository 4 -Exporting classix ~ into version files 6 -Exporting excellence ~ into version files 4 -Importing classix ~ from version files 7 -Importing excellence ~ from version files 5 O Overwriting (release) 19 P Post-processing (version file) 3 Preparing (version file) 3 R Release 16, 18 -Current 19 -Hierarchical 19 -Overwriting 19 S Settings (version file) 3 U User -(Filter) 16, 19 V Version differences -Displaying 13 Version element 12 Version file 4 -Exporting (classix) 6 -Exporting (excellence) 4 -Importing (classix) 7 -Importing (excellence) 5 Version management browser 11 -Releasing elements 16 Version management server 14 -Starting 14 Version repository 11 -Exporting elements in ~ 15 -Importing elements from ~ 17 -Logging-in to ~ 15 -Starting 14 Versioning -Exporting groups 18 -File-based 2 -Importing groups 20 -Prerequisites (file-based) 2 -Prerequisites (repository-based) 11 -Releasing groups 18 -Repository-based 11 -User Authorizations 13 Copyright 2010 MID GmbH 21

26

27

28 MID GmbH Headquarters Nuremberg Kressengartenstrasse Nuremberg Germany Tel.: Fax: Branch Cologne Ettore-Bugatti-Strasse Cologne Germany Tel.: +49 (0) Fax: +49 (0) Branch Stuttgart Silberburgstrasse Stuttgart Germany Tel.: +49 (0) Fax: +49 (0) Branch Munich Keltenring Oberhaching Germany Tel.: +49 (0) Fax: +49 (0)