erudine slideshow v3.0
TRANSCRIPT
1© Erudine® 2009
Erudine Behaviour Engine
Software Development Toolkit
2© Erudine® 2009
Agenda
• Business – IT divide• Why development is difficult
• How Erudine solves the issues• Tacit knowledge capture• Agile system development• Legacy cloning
• Where Erudine sits in the enterprise• Project credentials and success stories
3© Erudine® 2009
The Business – IT divideF
unct
iona
lity
Time
New Product
Merger / Acquisition
1.0 1.11.2
1.3
2.02.1
2.2
3.0 3.1
Lost Opportunity Cost
System Business Value
7.2 years
4© Erudine® 2009
Why development is difficult
Mental capacity of developer
Client requirements
System being delivered
5© Erudine® 2009
The ability to understand complexity is limited
Time
Re
qu
irem
en
ts D
eliv
ere
d
Limit of Mental Model
6© Erudine® 2009
Larger projects mean greater communication
Client requirements
System being delivered
Mental capacity of developer
Business Analysts
Designers
Developers
7© Erudine® 2009
Cost of not retaining the mental model
Mental Model
Time
Rel
ease
1
Rel
ease
2
Cost of Change
8© Erudine® 2009
Agenda
• Business – IT divide• Why development is difficult
• How Erudine solves the issues• Tacit knowledge capture• Agile system development• Legacy cloning
• Where Erudine sits in the enterprise• Project credentials and success stories
9© Erudine® 2009
What is “Tacit Knowledge” ?
EXPERT HERE
UNCONSCIOUSLY COMPETENT (TACIT KNOWLEDGE)
CONSCIOUSLY COMPETENT(EXPLICIT KNOWLEDGE)
CONSCIOUSLY INCOMPETENT(COMMON SENSE)
UNCONSCIOUSLY INCOMPETENT(ASSUMPTION)
Knowledge that is:- Highly Personal, Not Easily Visible or Expressible- Usually Requires Joint or Shared Activities to Transmit it
Knowledge that is:- Written Down- Easily Explained
Tra
diti
on
al
Re
qu
irem
en
t C
ap
ture
Eru
din
e B
eh
avi
ou
r E
ng
ine
Re
qu
irem
en
t C
ap
ture
10© Erudine® 2009
Erudine Behaviour Engine
captures system behaviour using a
process similar to the way
we teach children how
to behave
Teaching behaviour
11© Erudine® 2009
The process change: “Teaching not Programming”
USER REQUIREMENTS
BUSINESS ANALYSIS
DETAILED DESIGN MODULE TEST
SYSTEM TEST
USER ACCEPTANCE TESTmonths
weeks
days
CODE & UNIT TEST
ERUDINE REPLACES
minutes
12© Erudine® 2009
Erudine Behaviour Engine
13© Erudine® 2009
Ability to describe real world concepts12
3
Conflict resolution “…but earlier you said…”
Rapid execution of knowledge learned
What is required to teach?
14© Erudine® 2009
What does data look like with Erudine ?
15© Erudine® 2009
What do conclusions look like with Erudine ?
16© Erudine® 2009
What do justifications look like with Erudine ?
The justification is a selected part of the graph
17© Erudine® 2009
Group descriptions - Ontology
18© Erudine® 2009
Conflict Resolution
A change of outcome
Requires a difference to the input
19© Erudine® 2009
Erudine solves the mental modelling issue…
… by automating the capture and conflict resolution that would normally be done by humans. Effectively the system is being ‘taught’ the requirements in the same way a child learns.
20© Erudine® 2009
What are the results of being able to “Teach” ?
Mental Model
Time
Cost of Change
21© Erudine® 2009
Runtime Environment
Outputdata
Inputdata
CONCLUSIONS
CREATE RULES
JUSTIFICATIONS
Inputdata
EXECUTE RULES
OUTPUTS
Training Production
RULES
22© Erudine® 2009
Erudine – How does it work ?
23© Erudine® 2009
Erudine – How does it work ?
24© Erudine® 2009
Erudine – How does it work ?
if A thenif B then
do somethingelse
do nothingendif
elselog error
endif
(A).(B)
(A).NOT(B)
NOT(A)
1 0 0
0 1 0
0 0 1
25© Erudine® 2009
Zero-Order execution performance
0
2
2.5
3
3.5
4
4.5
1000 2000 3000 4000 5000 6000
Tim
es
ms
1.5
Number of Rules
1
0.5
0
26© Erudine® 2009
Zero-Order execution performance
27© Erudine® 2009
Erudine Workflow – Legacy Elimination
PROCESSING SYSTEM Outputdata
Inputdata
CREATES BEHAVIOUR & RESOLVES CLASHES
FINDS A SINGLE DIFFERENCE
HUMAN EXPERT JUSTIFIES WHY RESULTS ARE
DIFFERENT
LEGACY SYSTEM
ERUDINE
LEGACY ELIMINATION CYCLE
BUILD BASIC FRAMEWORK
28© Erudine® 2009
Why use Erudine ?
29© Erudine® 2009
New opportunities – Clone and Evolve
?
New
Clone
Develop and Accept
30© Erudine® 2009
New opportunities – Service Orientation
31© Erudine® 2009
New opportunities – Legacy Recovery
• Package Selection• Selection of “best fit” package• No business distinction• High integration costs• Moderate ongoing costs• Suitable for non-core activities• Medium risk
• Package Selection• Selection of “best fit” package
• No business distinction• High integration costs
• Moderate ongoing costs• Suitable for non-core activities
• Medium risk
• Application re-write• High development costs• Limited lifespan• Reduced ongoing maintenance costs• Suitable for business differentiator• Medium risk
• Status Quo• Little or No development costs• Low immediate risk• High long-term risk• Limited business agility
• Application re-use• Lowered development costs• Lifetime extension• Increased ongoing maintenance• Suitable for short-term gain
Business Value
Cos
t to
the
bus
ines
s
• Application re-write
•High development costs
•Limited lifespan
•Reduced ongoing maintenance costs
•Suitable for business differentiator
•Medium risk
• Status Quo
• Little or No development costs
• Low immediate risk
• High long-term risk
• Limited business agility
• Application re-use•
Lowered development costs
•Lifetime extension
•Increased ongoing maintenance
•Suitable for short-term gain
• Erudine• Low development costs• Never becomes legacy• Greatly reduced maintenance costs• Costs less than package• Benefits of bespoke• Low risk
32© Erudine® 2009
Agenda
• Business – IT divide• Why development is difficult
• How Erudine solves the issues• Tacit knowledge capture• Agile system development• Legacy cloning
• Where Erudine sits in the enterprise• Project credentials and success stories
33© Erudine® 2009
Common Deployment
EBEOrchestration
EBETransformation
EBEOther
Other Service Engine
Other AdapterDB Adapter JMS Adapter
Service Call Routing
Security
Mgmt
QoS/Transactionality
Service Engines
External Interactions
ESB Admin
Other Adapter
34© Erudine® 2009
Erudine Return on Investment
• Requirements Capture• Eternal mental model capture• Tacit knowledge made explicit
• Agility• Rapid prototyping• Exposes behaviour and conflicts
• Legacy Inhibitor• Reverse engineer existing process• Cannot itself become legacy
35© Erudine® 2009
Gartner Magic Quadrant – Business Rules Engines
36© Erudine® 2009
Erudine Behaviour Engine is an
enterprise-grade run time and
integrated development environment that allows systems to
be authored and evolved at a
low cost and reduced risk.
What is Erudine ?
37© Erudine® 2009
Erudine Behaviour Engine delivers…
business agility
What is Erudine ?
38© Erudine® 2009
Erudine Behaviour Engine captures…
system behaviour
What is Erudine ?
39© Erudine® 2009
Or
Situation
Input Output
What
However
Why
Developers Documentation
Traditional Systems Development
40© Erudine® 2009
Therefore
This is how we get an IT system to do the correct thing
Why is separated
Code = Situation & What
So how do we differ when teaching children what to do?
Traditional Systems Development
41© Erudine® 2009
Erudine uniquely integrates the “WHY”
42© Erudine® 2009
Legacy Migration
43© Erudine® 2009
Input Output
EBE
Legacy System
Why
Situ
atio
ns
What it does
Domain Experts
EBE
1 2
Input Outputs
WhatSituations
The legacy system can be retired risk free into an agile EBE environment
Legacy Modernisation
44© Erudine® 2009
Legacy System
Agile Clone
+
Low Risk
EvolveHigh Risk
Erudine Route
New System
Legacy Modernisation
45© Erudine® 2009
Legacy Migration Case Study
46© Erudine® 2009
System Positioning
STAFF TIMESHEETCAPTURE
PAYROLLAPPLICATION
TERMS ANDCONDITIONS
47© Erudine® 2009
Initial Project Estimates
Analysis
Construction
Testing
Project Management
Design
40
160
80
60
80
Total: 420
Estimate EstimateNew
Estimate Actual
Traditional Erudine
48© Erudine® 2009
The traditional effort profile for consecutive tasks
Effort
Time
Analysis and Design (120 days)
Construction (160 days)
Testing (80 days)
8 months
49© Erudine® 2009
Initial Project Estimates
Analysis
Construction
Testing
Project Management
Design
40
160
80
60
80
40
40
0
20
20
Total: 420 120
Estimate EstimateNew
Estimate Actual
Traditional Erudine
50© Erudine® 2009
The effort profile for a Behaviour Recovery process
Effort
Time
Behaviour Recovery (100 days)
(includes Analysis, Design, Construction and Testing)
8 months3 months
51© Erudine® 2009
Behaviour Recovery Process
STAFF TIMESHEETCAPTURE
PAYROLLAPPLICATION
TERMS ANDCONDITIONS
ERUDINEBEHAVIOUR ENGINE
Human Input
52© Erudine® 2009
Behaviour Recovery Metrics
• Existing System• Able to recover over 90% of requirements in 100 man-days
• Recovery of over 1600 individual function points (each with test case)
• Side-effects• Bugs identified
• People “bending the rules” identified
• Conflicts with documentary requirements identified
• Complexity Uncovered• “You would have to lock all of us (the 3 key individuals) in a room for 6 months
solid to get this level of requirement capture from our traditional approach, and we’d probably quit if we were” – Project Resource
53© Erudine® 2009
The traditional complexity to effort ratio
Effort(man-days)
Complexity(function points)
1600+(based on 90% coverage)
(estimated)
40
360
54© Erudine® 2009
Behaviour Recovery vs. Traditional Process
Effort
Time8 months3 months
Revised using Behaviour Capture (x2)
200 man-days
Predicted with true Complexity (x9)
3780 man-days
55© Erudine® 2009
Project Estimates Comparison
Analysis
Construction
Testing
Project Management
Design
40
160
80
60
80
40
40
0
20
20
Total: 420 120
360
1440
720
540
720
120
40
0
20
20
3780 200
Estimate EstimateNew
Estimate Actual
Traditional Erudine
3 people for 6 months
56© Erudine® 2009
Requirements Capture and Validation
57© Erudine® 2009
Faster time to market
58© Erudine® 2009
Decision Support
59© Erudine® 2009
Financial Services
60© Erudine® 2009
Rapid System Development
61© Erudine® 2009
Security Management and Response
62© Erudine® 2009
Simulation and Training
63© Erudine® 2009
System Architects
Software Developers
Business Analysts
Sub Contractors
Central Distribution
Enterprise Usage Report
Monthly Payment
Toolkit Adoption
Innovative Software Distribution
64© Erudine® 2009
Capability Lab
Centre of Excellence
Consultants
Business Developmen
t Forum
Capability Lab
Product Creation Team
Centre of Delivery
Project Bid Team
Erudine Customer
Permanent
Security Cleared
Contractors
Partnerships
Innovation Management
• Visioning of R&D projects
• Funding & visualisation
• Skill-set management
• Rapid product concepts
• Optimised for Innovation
• Optimised for Transactions
Innovation Support Structure
65© Erudine® 2009
RAPID IDEA GENERATION & PROTOTYPING RAPID SALES & MARKET EXPOSURE RAPID CREATION
TRL1
Business Developmen
t Forum
Capability Lab
Sales Acceptance
Customer Interest
Product Developmen
t
Sales
Bids
Projects
Marketing
Insight
Product Innovation
TRL2 TRL3 TRL4 TRL5 TRL6 TRL7
66© Erudine® 2009
COTS Product Creation
67© Erudine® 2009
Thought Leadership
68© Erudine® 2009
“Erudine’s Behaviour Engine offers EADS huge potential in reducing overall development, integration and support costs of complex systems.” Dr Mark Bentall, CTO, EADS Defence and Communications Systems
“Erudine’s unique approach speeds up time to market for new applications and mitigates the risks of changing complex systems.” Jeremy Acklam, Business Development Director, thetrainline.com
“[Erudine’s] non-invasive approach actually minimised the risks of disruption to the existing service while delivering legacy recovery capability far in excess of any traditional process.” Andrew Stevenson, Head of Oracle and CRM, Atos Origin UK
Thought Leaders