Page History
This page outlines the steps to set up a Jazz platform. The abbreviations used in the description are detailed below:
- TWC - Teamwork Cloud Server
- DNG - Doors Next Generation
...
| Note | ||
|---|---|---|
| ||
OSLC root services document URI can be found using the following pattern - http(s)://TWC_IP:PORT/oslc/rootservices. For more information, see OSLC API. |
You must also publish the project as an OSLC resource in Cameo Collaborator for Teamwork Cloud.
After establishing server and project-level relationships, open your modeling tool (MagicDraw, Cameo Systems Modeler, or Cameo Enterprise Architecture), and perform the following steps:
Add requirements (import or sync) from DNG through DataHub as described at Adding IBM Rational DOORS Next Generation Data Sources.
Copy requirements from DataHub to your model as described at Copy Data with Sync operations.
Note The adding of requirements has been enhanced during OSLC consumer implementation in version 19.0. Users are able to see the DNG requirement’s OSLC Previews in the OSLC Preview tab of a modeling tool.
After importing requirement(s) to your model under the Copy Data with Sync mode, create «Satisfy» relationships to/from those requirements to system model elements.
Note Currently, only SysML’s «Satisfy» is fully covered under this Business Case.
- Synchronize changes back to the DNG side, as described at Synchronizing Requirements.
After the synchronization, the changed requirement’s properties will be reflected on the DNG’s requirements artifact. Additionally, an OSLC backlink is created in DNG. Thus, if the «Satisfy» relationship between a Block <B> and Requirement <R> was established in your model, a backlink relationship «Satisfied by» is created in DNG, pointing to the Block’s <B> identifier, which in OSLC’s context is an http URL.
Note Currently, only SysML’s «Satisfy» is fully covered under this Business Case.
The figure below depicts an OSLC UI preview of the linked Block <B>.(this is not a CC preview!):
...