LieberLieber Connector

Data integration solutions for Enterprise Architect

✓ Avoid multiple manual data entry
✓ Display requirements traceability in EA, e.g. from IBM DOORS, Polarion, MS Team Foundation Server, …
✓ Three integration options – full, lite or hybrid – offer a solution for a diversity of use cases
✓ Integration of Enterprise Architect in your ALM environment based on the Requirements Interchange Format (ReqIF)

With the help of LieberLieber Connector, data from other tools is integrated into your Enterprise Architect model or converted from an Enterprise Architect model in such a way that other tools can read it and re-use it. Multiple entry of the same data is thereby avoided. Traceability of requirements (e.g. from DOORS) to system and software architecture are displayed in EA.

These characteristics contribute to consistency in your development data and help you to optimize time and costs in your project. Your professionals can concentrate on tasks that are more important than manual data entry.

When it comes to data integration, it is important that a data source (leading system) is linked with other tools (non-leading system of the data to be integrated) in such a way that the already-existing data can already be re-used. Typical scenarios are the integration of requirements management systems (e.g. IBM DOORS, Polarion, MS Team Foundation Server, etc.) and architecture and/or testing toold (e.g. Sparx Systems Enterprise Architect, HP Quality Center, Code Beamer, etc.).

There are three different options to integrate data through a LieberLieber Connector.

  • Option 1: Integration of content with Enterprise Architect as the leading system

Import (and synchronization) of selected content either file-based or via direct access to the third-party system. The elements should be completely available in EA and can be processed further. Updates from third-party systems are started by user interaction (active calling of synchronization).

  • Option 2: Lightweight integration via link (e.g. OSLC approach) – EA is not the leading system for the data to be integrated

Direct (online) interface to the third-party system. The elements in EA are usually placeholders with no content. All information pertaining to requirements are found in the third-party system. The contents can be viewed and edited directly in the third-party system to which the connection has been established. Only the most current data is found in EA, since no requirements data is filed in EA.

  • Option 3: Hybrid solution – integration by proxy – EA is not the leading system for the data to be integrated

Important content (e.g. description, status, etc.) is flagged accordingly and carried over into EA where it can be viewed. Editing in EA opens the third-party system’s editing UI. By way of synchronization, content in the leading system overwrites content in EA and the changes are logged. A so-called impact analysis can then be added to such a synchronization process.

The following integration solutions have been implemented by us:

ALM data – Requirements, architecture, change management

  • LieberLieber Connector TFS: Requirements & work item integration for Enterprise Architect with the Microsoft Team Foundation Server (TFS)
  • LieberLieber Connector ReqIF: Integration of Enterprise Architect in your ALM environment based on the Requirements Interchange Format (ReqIF)
  • LieberLieber Connector PTC: Requirements data integration from PTC-RM – previously MKS-RM.

Engineering data

  • LieberLieber Connector DBC: Integration of Data Base CAN (Controller Area Network) data for Enterprise Architect
  • LieberLieber Connector AUTOSAR: Integration of Enterprise Architect in your AUTOSAR tool chain using data exchange with the AUTOSAR ARXML format as a component of LieberLieber AUTOSAR Engineer.

Is your desired integration not here?

No problem. We are happy to develop a tailored integration solution for your tool.

Contact us today!