Exploring the non-functional properties of model transformation techniques used in industry Ronan Barrett, Ericsson AB

Transcription

1 NFP Expling the non-functional properties of model transfmation techniques used in industry Ronan Barrett, Ericsson AB Public Ericsson AB Page 1

2 Some General Background Public Ericsson AB Page 2

3 Ericsson in Numbers 40% of all Traffic 2.5 billion 180 Countries 110,000 Employees 5 th Largest 50 billion Public Ericsson AB Page 3

4 Modelling In Ericsson O&M Modelling Netwk Modelling System Modelling Business Process Modelling Public Ericsson AB Page 4 Real-Time Modelling Executable Models

5 Public Ericsson AB Page 5...

6 Some Specific Background Public Ericsson AB Page 6

7 Modeling Context Public Ericsson AB Page 7

8 Transfmation Styles Tell me what to do! Tell me What & How! Tell me How To Do it!?! ÜÝÞßà? Hybrid! Declarative Imperative Public Ericsson AB Page 8

9 Transfmation Languages Declarative Imperative ATL ÜÝÞßà XSLT JET QVT Template Public Ericsson AB Page 9 Hybrid

10 Let's Exple Some NFP(s) Public Ericsson AB Page 10

11 Table of Contents Identify NFP(s) Wanted Position ÜÝÞßà Enumerate NFP(s) Current Position Public Ericsson AB Page 11 Improvement As

12 Identified NFP(s) Readability Usability ÜÝÞßà Maintainability Scalability NFP Deploy-ability Testability Perfmance Public Ericsson AB Page 12

13 NFP Wanted Position Code dable/auditable by developers/systems guys Transfmation code should be 100% verifiable Changes in input model shouldn t require full retransfmation Bugs fixed quickly and without side-effect Parallelizable transfmation parts should be executed in parallel ÜÝÞßà Code base can grow without constant refacting Implementer should *not* have to learn a new obscure language Execution doesn t consume all resces as model size gets large Public Ericsson AB Page 13 Transfmation code should be runnable anywhere with GUI without No developer bottleneck f transfmation code

14 Readability Declarative/Hybrid Imperative?!! Often succinct Often easy to d Must know language Can be verbose Labious to d Well known language Public Ericsson AB Page 14

15 Readability Issue Read Mapping Transfm Code Mapping? ÜÝÞßà System Manager Approve Mapping Public Ericsson AB Page 15

16 Maintainability Declarative/Hybrid Imperative?!! Fixes rarely cause refacting (fast/no side-effect) Must know language Fixes often require refacting (slower/often side-effects) Well known language Public Ericsson AB Page 16

17 Maintainability Issue Implement Patch (?!) ÜÝÞßà Developer (?!) (!) Implement New feature (?!) High Efficiency Low Efficiency Public Ericsson AB Page 17

18 Scalability/Perfmance ÜÝÞßà?!! Declarative/Hybrid Imperative Public Ericsson AB Page 18

19 Scalability/Perfmance Issues Declarative/Hybrid Imperative?!! Parallel execution Incremental execution* Infinite/Event execution Explicit coding required to achieve similar execution semantics Public Ericsson AB Page 19 * Often only the declarative part can be incrementally executed

20 Usability IDE ÜÝÞßà Community Learning Resources Development Environment Debugging Public Ericsson AB Page 20

21 Usage in Industry?! ÜÝÞßà! Declarative/ Hybrid Imperative Public Ericsson AB Page 21

22 Usage Trend ÜÝÞßà Usage of Declarative/ Hybrid Time Public Ericsson AB Page 22

23 Usability Issues Declarative/Hybrid Imperative?!! Small community Development bottleneck Less robust tooling Debugging very difficult Massive community Easy to outsource Excellent tooling Debugging not so hard Public Ericsson AB Page 23

24 Deploy-ability Target (Run- Time) Design-Time Public Ericsson AB Page 24 Continuous Integration

25 Deploy-ability Issues Declarative/Hybrid Imperative?!! Nmally cannot run on target environment (exce XSLT) Can, in they, run on all deployment environments Public Ericsson AB Page 25

26 Testability Public Ericsson AB Page 26

27 Model Comparison Test Models ÜÝÞßà Golden Model (XML) JUnit Custom DOM Parser Public Ericsson AB Page 27 Test Rept

28 Model Contracts Test Models ÜÝÞßà PRE Post JUnit OCL Evaluat Public Ericsson AB Page 28 Test Rept

29 Pattern Matching (Assertions) Test Models ÜÝÞßà Assertion JUnit OCL Evaluat Public Ericsson AB Page 29 Test Rept

30 Testability Issues Declarative/Hybrid Imperative?!! Many test models needed f 100% coverage Verification is only as good as the Oracles No code coverage tools Public Ericsson AB Page 30 Many code coverage tools

31 Summary/Conclusions Public Ericsson AB Page 31

32 NFP Current Position Code not dable/ auditable by many developers/all systems guys Transfmation code is 100% verifiable if we write enough test models Changes in input model require full retransfmation Bugs are fixed quickly and without side-effect but debugging is often difficult Some parallelizable transfmation parts can be executed in parallel ÜÝÞßà Code base grows without constant refacting Resistance from developers to learn a new obscure language Execution doesn t consume all resces as model size gets large Public Ericsson AB Page 32 Transfmation code cannot be runnable anywhere but can run in GUI without Achieved Significant developer bottleneck f transfmation code Partial Not Achieved

33 Potential NFP Improvements Transfm code that non techie folks can d Debuggable transfmation code with proper execution handling Incremental/Parallel transfmation execution f imperative code Close the gap betwen imperative and declarative languages (Java8/Xtend?) Transfmation code that runs anywhere Develop a declarative language that imperative coders will ado Public Ericsson AB Page 33

34 Questions Public Ericsson AB Page 34

35