Dr. Tom Ritter
Eclipse Con Europe, Papyrus Summit, 2014
MODELBUS®MASTERING COMPLEXITY
© F
rau
nh
ofe
r F
OK
US
2© Fraunhofer FOKUS
COMMON CHALLENGES IN SOFTWARE ENGINEERING
© B
ild
ag
en
tur,
Vo
rna
me
Nach
na
hm
e
Fo
tog
raf
Requirements Specification Function Analysis & Design Implementation …
Inconsistency, low degree of automation, insufficient common terminology
Complexity and costs
Decoupled software tools
Produced data remains proprietary and depends on specific tools
Tools
Artefacts
3
Introduction
ModelBus® is a model-driven tool integration framework
which allows you to build seamlessly integrated tool
environments for your development process.
ModelBus® connects your tools – commercial off the shelf
or in-house tools
ModelBus® helps automating your development
processes
ModelBus® uses SOA principles and well established
standards
© Fraunhofer FOKUS
MODELBUS®
©M
att
hia
s H
eyu
nh
ofe
rF
OK
US
©F
rau
nh
ofe
r F
OK
US
4
General Concept
• Lifecycle Tools are
needed for creative work
• Process Enactment
controls the development
process
• Core services are needed
to operate the ModelBus
• Modeling Services
provides back-end
functionality for
automation
© Fraunhofer FOKUS
MODELBUS®
©M
att
hia
s H
eyd
e /
Fra
un
ho
fer
FO
KU
S
5
Architecture
• Tools are connected via a
ModelBus Adapter
• Slight modification of existing
tools instead of introducing new
tools
• Services can be easily created
via ModelBus service interfaces
supported by the ModelBus
Development Kit
• Workflows can be orchestrated
and will be trigger by ModelBus
events
• Repositories store relevant
artefacts (e.g. models, code,
documents) via standardised
interfaces
© Fraunhofer FOKUS
MODELBUS®
©M
att
hia
s H
eyd
e /
Fra
un
ho
fer
FO
KU
S
Tools / Frontend
Services
RepositoriesIntranet Model
Repository
File
System
RDBMS
Common Interface
Web Interface
Existing Tool
Adapter
Service and Functionality
Discovery
Model Checking
Trans-formation
Code Generation
Simulation
Workflow
Development
Process
Indexing
Search
Reasoning
Information
gap analysis
Smart
suggestions
Model
Checking
Simulation
TransformationTesting
6
Selection of Connected Tools
Eclipse-based Tools
Papyrus, ProR, …
Rational Software Architect
Doors
Rhapsody
Simulink
Microsoft Office (Word, Excel)
Sparx Enterprise Architect
AVL InMotion
Modelling Services
QVT, ATL, OCL, Metric Computation, Report Generation, Model Repository
Traceability with Traceino
Requirements Engineering with Requino
OSLC-Compatibility
SVN, Git
© Fraunhofer FOKUS
MODELBUS®
©M
att
hia
s H
eyd
e /
Fra
un
ho
fer
FO
KU
S©
Fra
un
ho
fer
FO
KU
S
7
Avoiding merge conflicts
Locking of parts of the model
Interactive highlighting of locked
model parts
Interactive modelling
© Fraunhofer FOKUS
MODELBUS®
8
FOKUS!MBT – Customizing Papyrus for MBT
© Fraunhofer FOKUS
MODELBUS®
9
Git Integration
© Fraunhofer FOKUS
MODELBUS®
ModelBus Server
ModelBus
Server Application
ModelBus
Git
Repository
„Central“ Repository
Developer Git
Repository 1
Developer Git
Repository 2
Developer Git
Repository N
sync
sync
sync
sync
read/write
Conflict Resolution
in ModelBus Clients
ModelBus
Client
10© Fraunhofer FOKUS
OVERVIEW ON VARIES CASE STUDY
As product and consulting company for the automotive domain B&M is specialized in systems
engineering, development and testing of complex electronic and mechanical systems. Within
the case study B&M will appear as developer of automotive driver assistance software.
Traffic Sign Recognition System• Different hardware and operating
systems
• Different countries with variety of laws
and regulations
• Different directions of traffic
• Different sets of customer specific
functionalities
http://www.varies.eu/
11
VARIES CASE STUDY - EXISTING PROCESS
Requirements
Management using
Doors
Architecture
using
VISIO
Design
using
VISIO
Implementation
using
Eclipse
Testing
using
CTE XL
Professional
and
Messina
12
VARIES CASE STUDY - PROCESS AIMED AT
Testing
using
CTE XL
Professional
and
Messina
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
Architecture
using Artisan
Studio (or Papyrus)
Design
using Artisan
Studio (or Papyrus)
Implementation
using
Eclipse
Testing
using
CTE XL
Professional
and
Messina
Variability
Management using
pure::variants
Requirements
Management using
Doors & Meran
Analysis (QFD,
FMEA, Risk) using
Requino
13
Requirements
Management using
Doors & Meran
Files
via
ModelBus
VARIES CASE STUDY - PROPOSED REALIZATION
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
OSLC RM
& Meran VM
via OSLC REST
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
UML & OVM
via
ModelBus
UML & OVM
via
ModelBus
Files (p::v)
via
ModelBus
pure::variants VM
via
ModelBus
CVL
transformations
traces
Analysis (QFD,
FMEA, Risk) using
Requino
14
Requirements
Management using
Doors & Meran
Files
via
ModelBus
CONSISTENT VARIABILTY MANAGEMENT HANDLING
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
OSLC RM
& Meran VM
via OSLC REST
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
UML & OVM
via
ModelBus
UML & OVM
via
ModelBus
Files (p::v)
via
ModelBus
pure::variants VM
via
ModelBus
CVL
transformations
traces
Analysis (QFD,
FMEA, Risk) using
Requino
15
CONSISTENT VARIABILTY MANAGEMENT HANDLING
CVL
OVMMeran pure::variants
traces and
bidirectional
conservative
transformations
16
Files
via
ModelBus
CROSS FRAMEWORK TRACEBILITY
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
OSLC RM
& Meran VM
via OSLC REST
CTE XL & Files
Via
ModelBus
Requirements
Management using
Doors & Meran
Requirements
Management using
Doors & Meran
UML & OVM
via
ModelBus
UML & OVM
via
ModelBus
Files (p::v)
via
ModelBus
pure::variants VM
via
ModelBus
CVL
transformations
traces
Analysis (QFD,
FMEA) using
Requino
17
CROSS FRAMEWORK TRACEBILITY
ModelBus
EMF Model
EMF Model
EMF Model
OSLC Consumer
Adapter
OSLC Ressource
Adapter
ModelBus Client ModelBus ClientOSLC Consumer
ModelBus Repository
OSLC Ressource
18
Example Workflow
© Fraunhofer FOKUS
MODELBUS®
Eclipse/Papyrus Sparx EnterpriseArchitect
UMLconcept space
Simulink concept Space
Block Class
Port Port
LineInformation
Flow
Simulink UML
Matlab Simulink
sharedconcepts
mapping of the concepts
19© Fraunhofer FOKUS
MODELBUS PAPYRUS – SIMULINK – EA VIDEO
20
Benefits
ModelBus®
connects tools and data coming from different teams
improves consistency in the development process
makes you independent of tool providers and prevents vendor lock-in
automates tedious tasks in your development
ModelBus®
is extensible and customisable
Basic functionality is free to use and Open Source
A number of pre-existing tool adapters are available
ModelBus®: http://www.modelbus.org
YouTube Channel: http://www.youtube.com/user/ModelBusOrg
© Fraunhofer FOKUS
MODELBUS®
©F
rau
nh
ofe
r F
OK
US
We want to move ModelBus Core
and TeamProvider to Eclipse
21© Fraunhofer FOKUS
Dr. Tom Ritter
Director System Quality Center
Fraunhofer Institute
for Open Communication Systems FOKUS
Kaiserin-Augusta-Allee 31, 10589 Berlin, Germany
Tel: +49 (30) 34 63 – 7278
Fax: +49 (30) 34 63 – 99 7278
SQC: http://www.fokus.fraunhofer.de/go/sqc
ModelBus®: http://www.modelbus.org
YouTube Channel: http://www.youtube.com/user/ModelBusOrg
CONTACT