Presentation from our CTO, Dr. Stéphane Barbey, at the SiriusCon 2015 in Paris (www.siriuscon.org). Brief introduction of Paranor, our modernization approach, how we do business rule mining and how Obeo Sirius can be used to describe the system by means of a set of viewpoints.

1. Sirius Viewpoints &
Software Modernization
Stéphane Barbey, PhD
December 2015

2. About Paranor
02/12/15 Sirius Viewpoints & Software Modernization 2
Founded in 1978
35 Employees
PhD/Msc/Bsc
Individual Software
Development
Modernization
Consulting
High Standards
Model Based
Approaches
DSLs
Offices in
Wahlendorf (CH)
Stansstadt (CH)
Cebu (PH)
Finance
Public
Administration
Transportation
Energy
Communications
Continuous
innovation
state-of-the-art
methods
and technologies

3. Agenda
Software Modernization
The Respec Approach
to Business Rules mining
Its Tooling
The Use of Sirius Viewpoints
02/12/15 Sirius Viewpoints & Software Modernization 3

4. I – Modernization
02/12/15 Sirius Viewpoints & Software Modernization 4

5. 02/12/15 SiriusViewpoints & Software Modernization 5

6. 02/12/14 Software ModernizationWorkbench 6

7. 02/12/14 Software ModernizationWorkbench 7

8. Why Replace?
02/12/15 Sirius Viewpoints & Software Modernization 8
Skills
shortage
Vendor
support
Regulatory
compliance
Maintenance
costs
Access to
data
Meeting
client
expectations
Security Green IT
initiatives
Disaster
recovery
Inter
operability
Source: TSRi

9. 02/12/15 SiriusViewpoints & Software Modernization 9

10. Architecture-Driven Modernization
Horseshoe Model (OMG)
02/12/15 Sirius Viewpoints & Software Modernization 10
Business
Architecture
Application & Data
Architecture
Technical
Architecture
Longer Journey / Greater Impact
Shorter Journey / Lesser Impact
Business Domain
IT Domain
Existing Solution Target Solution
Technical Architecture-Driven
Application/Data Architecture-Driven
Business Architecture-Driven
Source: OMG

11. 02/12/15 SiriusViewpoints & Software Modernization 11
Modernization
New
Implementation
Migration
Manual StandardTool
Model-Based
Generation
COTS

12. 02/12/14 Software ModernizationWorkbench 12
…of COTS users did not achieve all the benefits they had
expected.
Source: Accenture

13. 02/12/15 SiriusViewpoints & Software Modernization 13
Modernization
New
Implementation
Migration
Manual StandardTool
Model-Based
Generation
COTS

14. 02/12/14 Software ModernizationWorkbench 14
Success rate of new implementation / manual migrations
projects.
Source: Gartner

15. 02/12/15 SiriusViewpoints & Software Modernization 15
Modernization
New
Implementation
Migration
Manual StandardTool
Model-Based
Generation
COTS

16. Modernization Process
02/12/15 Sirius Viewpoints & Software Modernization 16
Data Migration
Models (DSLs)
Iterative Migration
Assess
Import and
transform into
models (DSL)
Code Generation
and/or
Business Semantics
Extraction
Transform
into models
Extract
Rules &
Generate
Java
XML
PDF
…
Enterprise
Architecture
Repository

17. Advantages and Benefits of
Model-based Migration
02/12/15 Sirius Viewpoints & Software Modernization 17
Source: itemis
Automation
• Optimization of
Quality/Cost/Time
• Accurately fitting automation
leads to maintainable software
• Short freeze-time
• Parallel development of old
and new system
Target
Architecture
• Full freedom in definition of
architecture
• Consistent implementation
through code generation
• Easier to integrate developers
from the legacy system
Future
Development
• Model-driven software
development
• Adaptations are easier
• Cheaper Maintenance

18. II – Mining Business Rules
02/12/15 Sirius Viewpoints & Software Modernization 1818

19. 02/12/15 SiriusViewpoints & Software Modernization 19

20. 02/12/15 SiriusViewpoints & Software Modernization 20

21. 02/12/15 SiriusViewpoints & Software Modernization 21
• …of source code contains business logic.
• Remaining supports infrastructure-related activities.
Source: Ulrich & Newcomb

22. Respec
Extracting Business Rules
• Extracting business logic from legacy code
to obtain a first-class asset for:
• Architectural assessments and blueprints
• Migration
• Business re-engineering
• and more
02/12/15 Sirius Viewpoints & Software Modernization 22

23. Respec Process & Tool Support
Code
• Possibly
multiple
programming
languages
Business
Logic
• Readable
• Descriptive
• Simplified
• Procedural
Business
Specification
• Basis for new
requirements
• Basis for code
generation
• Rigorous Business Logic mining
method
• Rooted in true operational business
rules
• Prevents “invention” of facts
• Provides traceability through
interlinking
• Supports coverage analysis and
progress monitoring
• Business Logic model and
Specification model …
• Can be augmented with new or
changed requirements
• Provide a precise and detailed basis for
implementation / retargeting
02/12/15 Sirius Viewpoints & Software Modernization 23

24. 02/12/15 SiriusViewpoints & Software Modernization 24

25. Bottom Up / Reverse Engineering
02/12/15 Sirius Viewpoints & Software Modernization 25

26. Business Logic (Editor)
➔ readable
➔ descriptive
➔ simplified
➔ procedural
02/12/15 Sirius Viewpoints & Software Modernization 26

27. Business Logic before & after
raw BLogic (≅ Code) genuine BLogic
➔ Focus on business logic
➔ No technical noise
02/12/15 Sirius Viewpoints & Software Modernization 27

28. BLogic before & after
Genuine BLogic
➔ business terminology
➔ annotated
02/12/15 Sirius Viewpoints & Software Modernization 28

29. Bottom Up / Reverse Engineering
02/12/15 Sirius Viewpoints & Software Modernization 29

30. Specification Composer
02/12/15 Sirius Viewpoints & Software Modernization 30

31. Specification artifacts
• Specification Composer allows to edit specification model,
mainly referencing Business Logic artifacts
• Derived products (from spec model):
• generated specs as PDF or Wiki
• generated viewpoints (diagrams)
• generated input for EA tool/repository
• basis for code generation
02/12/15 Sirius Viewpoints & Software Modernization 31

32. III Viewpoints on
Modernization Artifacts
02/12/15 Sirius Viewpoints & Software Modernization 32

33. Viewpoints
• A software system usually cannot be described with one notation
for all relevant aspects.
• Also, the development process requires different aspects to be
described by different roles at different times, as you want to be
sure to have a clean separation of concerns.
• Hence it is important to identify the set of viewpoints relevant
for describing the different concerns of a system
02/12/15 Sirius Viewpoints & Software Modernization 33

34. Viewpoints
Graphical
Textual
Spreadsheet
Form
...
• Provide notations and
abstractions for viewpoint.
• Choose the best
representation to convey the
concepts you need to express.
• Consider mixed notations
• E.g. text inside diagrams
02/12/15 Sirius Viewpoints & Software Modernization 34

35. Graphical Editors
• Good to express
• Sequence flows / State machines
• Relationships and Dependencies
• Timing / Synchronizations
• ....
• Not good for e.g. expressions
• ... But think of formulas
02/12/15 Sirius Viewpoints & Software Modernization 35

36. Editors (Text)
02/12/15 Sirius Viewpoints & Software Modernization 36
Every model (DSL) has
its own editor, and is
stored as a file, or as
XML.

37. Editors (Forms)
02/12/15 Sirius Viewpoints & Software Modernization 37
Workbench also
supports form-
based editors
Example: business
specification
editor

38. Editors (Graphical)
02/12/15 Sirius Viewpoints & Software Modernization 38
… and graphical editors
Example: component-
architecture diagram

39. Editors (Wireframe Sketches)
02/12/15 Sirius Viewpoints & Software Modernization 39
… and UI editors
Example: wire-
frame sketch for
3270 block
mode terminal
interface

40. Cartography: Impact Analysis
02/12/15 Sirius Viewpoints & Software Modernization 40
Cluster
visualization of
model
dependencies
allows for
impact analysis
and decision-
making w.r.t.
iterative
migration.

41. Viewpoints
• Consider not just the notation
• But also the tooling
• Actions,
• Refactorings,
• Filter,
• Customization,
• Grouping,
• Printing
• ...
02/12/15 Sirius Viewpoints & Software Modernization 41

42. Component Diagram
02/12/15 Sirius Viewpoints & Software Modernization 42

43. Types Overview
02/12/15 Sirius Viewpoints & Software Modernization 43

44. Types Hierarchy
02/12/15 Sirius Viewpoints & Software Modernization 44

45. Dependency Diagrams
02/12/15 Sirius Viewpoints & Software Modernization 45

46. Sequence Diagrams
02/12/15 Sirius Viewpoints & Software Modernization 46

47. 02/12/15 SiriusViewpoints & Software Modernization 47

48. Thank You!
Stéphane Barbey, CTO
stephane.barbey@paranor.ch
02/12/15 Sirius Viewpoints & Software Modernization 48
https://www.linkedin.com/in/barbey
All illustrations used in this presentation are
either owned by the author or licensed under
“CC BY 2.0” or “CC BY SA 2.0”.