EclipseCon France 2017 Squaring the Capella circle: Open Source, Agile, Traditional

Size: px

Start display at page:

Download "EclipseCon France 2017 Squaring the Capella circle: Open Source, Agile, Traditional"

Darrell Alban Francis
6 years ago
Views:

1 EclipseCon France 2017 Squaring the Capella circle: Open Source, Agile, Traditional CAPELLA OSS JUNE 22 TH 2017 Joao BARATA / Philippe DUL Squaring the Capella circle jean.barata@thalesgroup.com philippe.dul@thalesgroup.com

2 Introduction Welcome to Welcome to City of space and aerospatial Capella Sirius Eclipse Working Groups Fostering open industry collaboration to develop new industry platforms Kitalpha Arcadia 2

3 What is Capella : Model Based System Engineering tool Software Engineering (UML) Developer Architect API user Sonar maniac Code coverage (UML 3

4 What is Capella : Model Based System Engineering tool Similar needs for System Engineering 4

5 What is Capella : Model Based System Engineering tool Helps engineers to describe systems Customers Architect Design Engineering Method (=How to?) Engineers Product line manager SW/HW Designers IVVQ Requirement manager Dedicated Modeling Tool Safety Performance 5

6 What is Capella : Model Based System Engineering tool 6

7 How is Capella used ~70000 employees ~5000 system engineers About 1600 received formations on Capella ~1000 Capella users 7

8 How is Capella used Modelling Two releases per year Documentation generation Thales Workbench V&V Validation / Verification Support reactivity is essential Requirements Change Management (Jira) Several maintenance branches 8

9 Technical overview of Capella Safety Viewpoints Real Time Analysis IVVQ Advanced Add-ons Teamworking PLE Model maintenance Focus on Expertise, Know-how, Core business Share - Co-develop - Contribute - Use 9

10 Thales as an important open source contributor Open Source Roadmap

11 Challenges : Technical view : Open source Major Infrastructures changes (CI, SCM, BT) 2012 Clearcase Clearquest GIT Bugzilla 2013 GIT JIRA GIT Bugzilla 2015 Clearcase Clearquest GIT Bugzilla / 11

12 Challenges : Technical view : Global Picture ( ) Thales Workbench Connector Clearcase - Clearquest Capella-Studio SVN - Clearquest Capella Clearcase - Clearquest Kitalpha SVN - Clearquest Team 4 Capella Clearcase - Clearquest Team 4 Sirius Git - Jira Sirius Git - Jira 12

13 Challenges : Technical view : Global Picture ( ) Thales Workbench Connector Git - Jira Thales Capella Git - Jira Thales Capella-Studio Git - Jira Thales Team4Capella Git - Jira Thales Kitalpha Git - Jira Capella-Studio Git Polarsys - Bugzilla Capella Git Polarsys - Bugzilla Team 4 Capella Git - Jira Kitalpha Git Polarsys - Bugzilla Sirius <Sources> Git Eclipse <Bugs> Eclipse Team 4 Sirius Git - Jira DiffMerge Git Eclipse - Bugzilla OPEN SOURCE 13

14 Challenges : Technical view Co-developed and OS of with Sirius used in several other projects other than Capella More up-to-date technologies (git vs clearcase, jira vs clearquest) Code Review improves quality Thales network constraints (securities, proxy) > Leading to duplicated infrastructure for Thales internal builds Build complexity increased Polarsys Infrastucture Loss of control in case of service disruption Multiple bug-trackers to be synchronized (internal / external, confidentiality concerns) 14

15 Challenges : Squaring the circle Thales need capture Thales MBSE Community Companion components Thales Open Source Open Source Community Shared repositories Partnerships 15

Open Source Community +2 +3 +2 +1 +2 +0 +2

16 Challenges : Capture Need Thales need capture Thales MBSE Community Partnerships Open Source Community Forum, Wiki Ordered backlog 16

17 Challenges : Agile Process Operational Support Technical Coaching Iterative Deliveries Agile in a constrained context Roadmap defined at the beginning of the year Operational support Quality process 17

18 Challenges : Coordination Companion components Thales repository Shared repositories Partnerships Shared Roadmap Scrum of Scrum started Integration of distant contributions Obeo synchronization meeting Scrum of Scrum Release Train (TBA) 18

19 Challenges : Outside Thales : Partners Users / Interested stakeholders Currents Contributors 19 (Sirius) Intel (Git & SVN / Diffmerge integration) Inquery (Patchs, Requesting tools) Pure Systems (PLE) Independants: F. Dorner, D.Ryzhov, J.Martinez

Challenges : Squaring the circle Partnership, collaboration Shared knowledge on wikis Shared Forge and component repository Evolutions covering better user needs Small enhancement with

20 Challenges : Squaring the circle Partnership, collaboration Shared knowledge on wikis Shared Forge and component repository Evolutions covering better user needs Small enhancement with strong-addedvalue are more easily identified Top-valued features are delivered first Difficulties to get users on demo-meetings due to operational priorities Delay from Sprint Deliveries to product deployement quite long Two forums, two wikis, two bug-trackers Can t fulfill all needs, but don t hesitate to contribute! Iterative User feedback 20

21 21

Thank You! Questions? (@see you at Capella stand) Visit toulouse-tourisme.com Use polarsys.org/capella jean.

22 Thank You! Questions? you at Capella stand) Visit toulouse-tourisme.com Use polarsys.org/capella THALES GROUP INTERNAL

ARCADIA: Model-Based Collaboration for System, Software and Hardware Engineering

www.thalesgroup.com ARCADIA: Model-Based Collaboration for System, Software and Hardware Engineering An architecture-centric, tool-supported method Jean-Luc Voirin & Stéphane Bonnet RETEX AFIS - May 2014