This document summarizes a webinar about connecting Capella models to IBM ELM. It introduces Obeo and Persistent Systems, describes IBM ELM and Capella, and demonstrates how Publication for Capella can be used to publish Capella models on the web and connect them to IBM ELM through traceability links. The integration allows engineering teams to link requirements, tests, and tasks in IBM ELM to model elements in Capella. The demonstration shows creating links between different artifacts as a project progresses from requirements to architecture to testing.

1. Connecting Capella
to IBM ELM
Laurent DELAIGUE
Eclipse Modeling consultant, Obeo
laurent.delaigue@obeosoft.com
Philippe LEBLANC
Principal Architect en System Engineering & ALM,
Persistent Systems
philippe.leblanc@persistent.com
WEBINAR
Copyright
Obeo
2021

2. WebEx session
Copyright
Obeo
2021
WEBINAR
Please note your
microphone is muted
Click the Q&A icon and ask
your questions 10+ min at the
end of the presentation
Chat is not enabled during
the presentation

3. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

4. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

5. Obeo | Visual Tools for Designing Innovation
We create modeling tools
For systems engineers,
Software engineers and
Domain modeling experts.

6. Obeo | Ready to use, or tailor-made for your needs
Enterprise
Architecture
Systems
Engineering
Your Specific
Engineering Domain
#MBSE #Arcadia #ArchiMate #BPMN #DSL #MDE

7. Why Persistent?

8. Context
• Capella is the leading open-source workbench for Systems Engineering Modeling.
• IBM Engineering Lifecycle Management (ELM) is an integrated set of tools for system
engineering covering requirement management, test management, task management, change
management and source code management.
• Publication for Capella (P4C) is an Obeo product to expose Capella models in Web clients and
connect 3rd
-party tools.
• The IBM ELM – P4C integration enables engineering teams to connect requirements, tests and
tasks with model elements providing a fine-grain traceability throughout project lifecycles.
Obeo P4C
IBM ELM
OSLC

9. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

10. The IBM Engineering Lifecycle Management (ELM) Solution for System Engineering
IBM Engineering Lifecycle Management (ELM)
Global
Config
SysML/UML
Model
IBM Engineering Lifecycle Management
(ELM)
IBM ELM ETM
IBM ELM
DOORS Next
IBM ELM
Rhapsody
IBM ELM EWM
R
e
p
o
r
t
B
u
i
l
d
e
r
&
P
U
B
Global
Config

11. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

12. ARCADIA | The Method
Architectural Design model elements are linked to
Requirements
=> Consistency, Verification & Justification
ARCADIA is a methodology
to capture the needs and design
solutions

13. Capella | The Workbench
Better understand the customer need
Define and share the solution among stakeholders
Secure SYS/SW/HW engineering, prepare subcontracting
Early evaluate and justify architectural design
Prepare and masterV&V
Capella is a comprehensive, extensible, and field-proven
MBSE tool to successfully design systems architecture

14. “The spirit of Arcadia and Capella in 7 minutes“ Tutorial “Catapult“
Website : eclipse.org/capella
Youtube : youtube.com/channel/UCfgwbb2h10V3tgJ59sbGBnQ/videos
Forum : forum.mbse-capella.org
LinkedIn : linkedin.com/in/capella-mbse-tool/
youtube.com/watch?v=BtzhlZUaWA8 esd.sutd.edu.sg/40014-capella-tutorial/index.html
Capella | Learn more about Capella and its community

15. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

16. Publication for Capella | Expose Capella models on the web
Capella Documentation
Capella
Semantic Browser

17. Publication for Capella | Connect Capella with ALM and RM tools
Fine-grained integration between Capella
and OSLC-compliant repositories (Doors Next, Jazz platform, Polarion…)
Manage traceability from
Requirements, Tasks, Issues, Change Requests, Test Cases, Releases...

18. Publication for Capella | Fined grained traceability between ALM artifacts and System Design
Digital continuity from
requirements to
architecture
Better communication
and collaboration
Single and integrated
sources of truth

19. Test Case
Task
Issue
Release
Change
Request
Requirement
Publication for Capella | Process Neutral Approach

20. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

21. Demonstration Scenario
Main objective of the scenario: implement a requirement in the model and validate
• Phase 1: Show the current version of the project.
• Phase 2: Implement a change request in a development task and link this task to the
requirements and high-level model elements that are impacted.
• Phase 3: Deliver a new version of the model and create links with the modified low-level
model elements.
• Phase 4: Prepare the test campaign for validating this development.
• Phase 5: Display a traceability view consolidating all the performed engineering activities.

22. Phase 1: Show the existing links between the DN requirements and the Capella model
in P4C
• Links have been created between requirements and model elements according to the following methodological rules
- ‘Derive’ links have been created between requirement sections and operational capabilities
- ‘Satisfied by’ links have been created between requirements and capabilities
- ‘Refined by’ links have been created between requirements and functional chains & diagrams
These rules have to
be defined by the
user organization –
there are no
constraints coming
from the integration

23. Phase 2: Create a development task and link this task to the impacted requirements
and high-level model elements
• In EWM, open the ‘Sprint 1 (1.0)’ plan
• Create a task ‘Implement on-board announcements’
• Open the task and fill in its attributes
- Create a link to requirement section 2.2
- Switch the task to ‘Working’ state

24. Phase 3: Update the model and create links with the modified low-level model
elements
• Update the system model in order to implement the task
- For demonstration purpose, we consider the model has already been updated
• Create a ‘Elaborated by Architecture Element’ link with diagram ‘[FS] Perform Audio Announcement’
- Use filter DDiagram + ‘Announc’
• Open the 1st requirement of section 2.2
• Create a ‘Refined by’ link with ‘[ES] Perform Audio Announcement’
- Use filter DDiagram + ‘Announc’
• Reopen the module and display the diagam with the rich hover
• Click on the linked model element it is directly open in P4C

• In P4C, click on the backlink displayed below the diagram to open the module

25. Phase 3: Update the model and create links with the modified low-level model
elements

26. Phase 4: Prepare the test campaign for validating this development
• Open the project plan and create a ‘Tested by’ link from the dev task to
the test case associated to the 1st
requirement of section 2.2
• Open the test case and create a link to the model element ‘[SFCD] Watch
Imposed Movie on Cabin Screen’
- Use filter DDiagram + ‘SFCD’
• Display the model diagram with the rich hover

27. Phase 5: Display a traceability view consolidating all the performed engineering
activities
• Open the project plan in view ‘Traceability’ and the requirement module
- We can see the complete traceability between dev tasks, requirements, test cases and model elements

28. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

29. Publication for Capella | Tentative Roadmap
• Topics of interest
- UX improvements:

Model Tree

Improve Form to search for object to link (search by diagram, by model tree, simplify list of types, multi-select, …)

Improve model object web pages
- Link creation in Capella by drag-and-drop from IBM ELM tools
- Improve reporting to include linked Capella model elements
- Support the Global Configuration service provided by IBM ELM
- Keep old versions of model on publish
- Report on links impacted by publication of new model version
- Support Model Review
- API to ease integration in user’s IT, ...
• You can influence this roadmap!
- By providing your feedback, topics of interest, priorities
- By funding Obeo and/or Persistent/IBM development tasks (accelerated development)

30. Takeaways
• Integration capabilities
- Links can be created between any ELM element and any Capella element
- Process neutral
- Links created from within IBM ELM
- Links navigated from both sides
• Available off-the-shelf with IBM ELM 6.x/7.x
- No extra add-on
• Integration delivered in Publication for Capella
- Product sold by Obeo
- Supports Capella 1.3 to 5.x (i.e. all versions since 1.3.0)

31. Agenda
Brief Introduction - Obeo and Persistent
IBM ELM
Capella
Publication for Capella
Demonstration
Quick Sum-up
Q&A

32. Thanks for listening!
Q&A
WEBINAR
Copyright
Obeo
@2021
Obeo –
https://www.obeosoft.com/en/solutions/systems-engineering
Persistent Systems –
https://www.persistent.com/industries/industrial/plm-and-systems-engineering-solutions/
ibm-engineering-lifecycle-management-software/