Presented at the

1. Sirius
graphical
editors
for your
DSL
Polarsys Day
December 3rd, 2013
Mikaël Barbero
Obeo

2. 1
Domain
Specific
Language

3. Domain
Specific
Language
Introduction to DSLs borrowed from
http://www.slideshare.net/peterfriese/overcoming-the-impedance-mismatch-between-source-code-and-architecture

8. Domain
Specific
Language

9. Imagine you want
to peal an apple…

10. What is the
appropriate tool?

11. Your good old
Swiss army knife!

12. Because it does
so many things!

13. Imagine you want
to peal a bit more apples…

14. Is it still the best tool?

15. Better use this one…

16. and this one!

17. while avoiding
the unitasker

18. Domain
Specific
Language

21. =

22. SELECT name, salary, age
FROM person
WHERE salary > 2000
ORDER BY salary, age

23. all: hello
!
hello: main.o factorial.o hello.o
g++ main.o factorial.o hello.o -o hello
!
main.o: main.cpp
g++ -c main.cpp
!
factorial.o: factorial.cpp
g++ -c factorial.cpp

28. Domain
Specific
Language

32. $
$

33. $
$

36. Sirius

37. Sirius

38. 2
Introducing
Sirius

39. In a nutshell
Tool to quickly
define custom
multi-view
workbenches
Based on Eclipse
Modeling
technology stack
New Eclipse
Project
Based on
graphical editors
/ modelers
No need to be
an expert for
most uses
But already
proven
technology

40. In a nutshell
Tool to quickly
define custom
multi-view
workbenches
Based on Eclipse
Modeling
technology stack
New Eclipse
Project
Based on
graphical editors
/ modelers
No need to be
an expert for
most uses
But already
proven
technology

41. In a nutshell
Tool to quickly
define custom
multi-view
workbenches
Based on Eclipse
Modeling
technology stack
New Eclipse
Project
Based on
graphical editors
/ modelers
No need to be
an expert for
most uses
But already
proven
technology

42. In a nutshell
Tool to quickly
define custom
multi-view
workbenches
Based on Eclipse
Modeling
technology stack
New Eclipse
Project
Based on
graphical editors
/ modelers
No need to be
an expert for
most uses
But already
proven
technology

43. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

44. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

45. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

46. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

47. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

48. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

49. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

50. What benefits?
Developers
End users
Reduce cost and
complexity
Tools adapted to their
needs and workflows
No need to be a
GMF expert
Improved experience
(compared to raw GMF)
Dynamic and iterative
(live) development
Common experience
across multiple DSLs

51. Two parts for two
kinds of users
Specification environment
Runtime environment
(Specifier / Developer)
(End-user)

52. The Specification
Environment
•
Define custom multi-view
workbenches
•
•
•
Diagrams, Trees, Tables
With little technical
knowledge
Get a working modeler fast
•
•
Instant feedback
Highly customizable
•
Native tooling
•
Java or extension points

53. The Runtime
Environment
•
Executes the
specification
•
•
Environment adapted to
user needs
•
•
No code generation
Viewpoint-based
Simplified workflow
•
Modeling Project

54. Showtime

55. 3
History &
Plans

56. e 2009
Sinc

57. Obeo
Designer
Obeo’s flagship commercial product that
is embedding the Sirius technology

58. Viewpoint
The name of the Sirius technology
within Obeo Designer at that time

59. 2013
The Viewpoint technology is made
open-source as an Eclipse project: Sirius

61. 5
Modeling Workbenches

62. 500+
Diagrams in some Models

63. 1.3M+
Elements in Biggest Models

65. 4
Conclusion

66. Sirius
What you should remember
•
•
•
Full featured environment
to create custom graphical
modelers
Mature, many deployments
Official Eclipse project

67. http://www.eclipse.org/sirius/
http://www.obeodesigner.com/
http://www.obeo.fr