1. Ontology-Driven Digital Enterprise
Taming Complexity and Bridging the Business-IT Gap with ODASE®
Flexibility, Quality and Lower TCO for Business-Critical Enterprise Software
January 2014

2. 1. Business-IT Gap and Complexity!
Today
What?
How?
Business and IT spend lots of time, energy and money clarifying what
each other means while IT struggles with complexity2 (Business x IT)
What?
How?
The Business problem is precisely defined and drives the implementation
© 2014 Mission Critical IT
2

3. MCit
IT
Business Ontology
• Concise (100s statements, not millions LOC)
• “Robots” generate code from the ontology
• Testable and explainable, not a black box
• 10 to 20 times less code to write
• Standards (W3C Semantic Web)
• Dramatic impact: cost, flexibility, quality
●
●
●
●
© 2014 Mission Critical IT
Separate Business from Implementation
Business & IT share the same semantic model
Programming is fully automated for the Business Logic
More flexible, more reusable, less technical debt
3

4. 2. Development Process – Modeling
3
Data
(Legacy or New)
© 2014 Mission Critical IT
OD A
SE
Informal Processes
OD A
2'
SE
Informal Rules
Ontology
=
Model+Rules
SE
2
Requirements
OD A
1
Ontology
=
Model
Ontology
=
Model+Rules+Process
Ontology
Tested, Explained
Validated, Improved
4

5. Development Process – Programming
7
6
5
1
2
3
4
2
Business rules and processes are added to the ontology
3
The ontology is tested, explained, validated, improved
4
A Business API is automatically generated in Java or C#
5
IT programs, using that API, what's not in that model*
6
Generic engines (reasoners, process, stores...) are reused
7
Agile iterations to adjust/improve: 1  2  3  4  5  6  7
*
© 2014 Mission Critical IT
IT
Requirements are modeled as an ontology
Business
1
Business & IT
and should not be in the model (UI, middleware, integration...) using their standards
5

6. Dramatic Impact
 CQFT – Cost, Quality, Flexibility, Time
Ontology
At the source
© 2014 Mission Critical IT
Classical
x 20 < Cost < x 150
6

7. 3. High Velocity Real Life Applications
 Insurance – Product Factory and Rating Engine (Paris)
Ontology
© 2014 Mission Critical IT
7

8. Quality (Insurance, Paris)
© 2014 Mission Critical IT
8

9. 4. Legacy Modernization – Railways
 Traffic Management (Artemis)
–
Modernization
•
2 MLOC Forte  Java or C#
•
–
Change language
Change architecture
client-server  Event Driven SOA
Application
•
at least 20 messages/s
•
–
Real-time
Complex
infrastructure, schedules, trains, events
Ontology-driven modernization (pilot)
•
Only specification
program with 130,000 LOC (Forte)
•
To be migrated in
20 days
Done: Deadline, Functionnality, Performance, Flexibility
© 2014 Mission Critical IT
9

10. Application UI
Complexity under control
© 2014 Mission Critical IT
10

11. Metric
 Existing code
–
130,000 LOC (Forte)
–
Cocomo : 398 person-months, 24 months, 17 FTE
 Ontology-driven
–
Ontology
Concepts
87
Properties
163
Rules
–
Very concise
Program
65
Hand-Written
UI (SWING)
4,623
130,000 LOC replaced by
87 concepts + 65 rules
4,623 Java LOC
(Only the View and Control; the Model is the ontology)
–
Effort
140 pd (person-day)
50% Ontology creation
25% Java programming
25% Data migration, infrastructure...
© 2014 Mission Critical IT
11

12. 5. Conclusions & Benefits
 Language of the Business
–
–
Declarative, expresses Business Knowledge, using formal logic
standards
–
For the very long term (as mathematics)
–
New logic will not invalidate existing logic
 Language of IT
–
Languages of today (Java, C#) and tomorrow (new code generator)
–
Ontology is an up-to-date asset: no need to restart from scratch
Business = Ontology
IT = Platform + Architecture + Integration
Application = Business + IT
© 2014 Mission Critical IT
12

13. Benefits
Business
© 2014 Mission Critical IT
IT
13

14. Annex – MCit ODASE®
4
1
2
3
ODASE (Ontology Driven Architecture and Services Engineering) = MCit tools and platform
1
Business Ontology defining 100% of the Business Logic
•
OWL for concepts, properties, axioms, instances
•
RDF for data represented universally as triples (subject, predicate, object)
•
Business Rules in extended SWRL (Semantic Web Rule Language)
•
Declarative Workflows expressed in OWL and SWRL
2
ODASE Workbench = Model checker (test, explanations, verification)
3
ODASE Hedwig = Code generators for Java, C# (and future languages)
4
ODASE Platform = All-in-One (reasoners, stores, workflow engines...)
© 2014 Mission Critical IT
14

15. Annex – The Tools and Platform
Application
Tests and Explanation
O
H DA
ed S
w E
ig
lication
eC
Lif
O
D
Vi A
zO SE
n
W OD
or A
kb SE
en
ch
Any Ontology Editor
O
Pl D
at AS
fo E
rm
le
l
lA
pp
yc
Fu
Ex
am
pl
e
:P
ro
té
g
é
Model (concepts, rules, processes)
IT
Documentation
Business
Documentation
© 2014 Mission Critical IT
O
H DA
ed S
w E
ig
Robot
15