Capella adapter

Capella adapter on GitHub

This section provides basic materials for use by CDF Domain Experts.

PURPOSE OF THE SOFTWARE

The Capella adapter is a plugin for Capella 5.0, 5.1 and 5.2. It provides a way to exchange data between an ECSS-E-TM-10-25 hub data source and a Capella instance. Between the setting up of the mapping and the transfer, the adapter provides a preview of mapped things by Highlighting changes in the relevant data trees and displaying representation of things that have been mapped. It is also possible to filter the preview by selection and to select what can be transferred from the things that are mapped. The adapter keeps track of the mapping and saves in the ExternalIdentifierMap of the open Iteration. The Capella Adapter eases the way engineer will use Capella modelling and COMET®, by providing easy data exchange.

EXTERNAL VIEW OF THE SOFTWARE

The adapter needs two data sources to be operational.

  • A WSP or a COMET® server connected to a COMET® database.
  • A running instance of Capella with the DEHP adapter plugin installed.

OPERATIONS ENVIRONMENT

General

The Capella adapter is a plugin for the Capella software. It is installed like any eclipse plugin.

Hardware Configuration

The following minimum hardware configuration is tied to the Capella software:

  • 2 GHz or faster processor
  • 4 GB of RAM
  • 15 GB of available hard disk space
  • A display with a minimum resolution of 800 pixels by 600 pixels

Software Configuration

Supported Operating System

The Capella adapter depends on the Capella software system requirements. According to Capella documentation it is compatible with the following platforms:

  • 64 bits computer with Windows, Linux, or Mac Operating System. (Linux and Mac have not yet been field-proven tested).

Runtime

The Capella adapters is targeting Capella 5.0, Capella 5.1, and Capella 5.2. Therefore, it will be executed by the Java Runtime Environment that runs Capella.

Capella

The Capella adapter is built as a plugin for Capella. Therefore, to install the adapter, a version no lower than 5.0 should be installed to setup the Capella adapter.  

COMET® WebServices

The minimal version of the COMET® WebServices is version 7.0.5. The recommended version is 7.0.7.

Operational Constraints

Start-up

When Capella starts, on common file ribbon control of the software, you will find a COMET® button that can open/close a panel where you can connect to an E-TM-10-25 model, another one that display the impact views and one that open the local exchange history window. Once a connection is open, you should be able to browse the ElementDefinition tree as well as the RequirementsSpecification tree. You can then now open a Capella model as usual if not done already.

Mapping

After your Capella model has been loaded, you can define a mapping between the data sources, the connected hub model, and the Capella model. If you choose to load an existing mapping it will be applied automatically upon loading. To load a mapping configuration, select one on the provided list and proceed with clicking on the button next to the provided list. To create a new one, type the name of the mapping configuration that you want to create and proceed with the same action. Defined mappings are not editable after they has been saved. The persistence of a mapping is done after a transfer. Currently, there is no possibility to remove or modify a defined mapping. The mapping configuration is only able to add new mapping.

Transfer

The Capella adapter lets you transfer Capella structural information to A E-TM-10-25 model and the other way around.

Impact view

The described functionalities in 2.4.3 register themselves in a process where once you have defined what element to transfer to what destination, you have the possibility to preview the impact on the target model. At this stage, it is also possible to select among mapped things of what element to transfer. For convenience, the context menu proposes two commands:

  • A select all things that can be transferred to transfer.
  • A deselect all things that can be transferred to transfer.

Then you can transfer the selection of mapped things to their configured destination.

Transfer

When you choose to transfer, the mapped elements are then transferred to the configured target model. In the case anything goes wrong at this stage, you can cancel, and it will delete every configured mapping. In case the selected mapping configuration contains any saved mapping, the mapping is re-applied.

Saved Mapping Configuration

When a transfer has been done, the mapping configuration is saved in the open E-TM-10-25 Iteration. This mapping can be overridden.

Operations Basics

From the moment Capella has started. In order you can

  • Connect to a E-TM-10-25 source.
  • Open a Capella model.
  • Map some element from the open Capella model to elements from the connected E-TM-10-25 Model or create a new one.
  • Preview the net change.
  • Select some of the mapped elements.
  • Transfer the selection.
  • Map some element from the open Comet model
  • Preview the net change.
  • Select some of the mapped elements.
  • Transfer the selection.

Table of contents