transforming openedge business applicationsmedia.progress.com/exchange/2014/collateral/... · •...
TRANSCRIPT
Transforming OpenEdge Business
Applications
Progress “Fluid” Framework
© 2013 Progress Software Corporation. All rights reserved. 2
What’s Hot Out There....
IT Trends that are driving business growth.
Cloud-based application (SaaS) and platform services (PaaS)
Mobile devices
Demand for new business functions, quicker
New UI Technology
Business growth: more members / partners / insurers / hospitals...
© 2013 Progress Software Corporation. All rights reserved. 3
Platform Transformation
What does this mean?
Business Functions must be isolated and reusable
Provide Business Functions as Services
Allow for multiple User Interfaces
Ability to deploy the application in the Cloud
Legacy applications must be re-architected and refactored to be OERA
compliant.
But “If it ain't broke, ….”; Good! It means you have a good app to start with!
© 2013 Progress Software Corporation. All rights reserved. 4
Platform Transformation
How?
“Preserve and Extend” Not “Rip and Replace”
Less costly and less risky
Capitalize on the application’s strengths
Address the application’s limitations
Work can co-exist with legacy application
© 2013 Progress Software Corporation. All rights reserved. 5
Re-architect and Refactor legacy style applications based on OERA
Business Rules isolated
Service Oriented
Multi-tenant ready
Deploy in the Cloud
Multiple User Interfaces and Mobile access
Corticon business rules to create dynamic, customized logic
Platform Transformation
S e r v i c e s I n t e r f a c e
Data Access Services
Save Data Load Data
Business Services
Save
Data
Validate
Data
Load
Data
Common
Functions
User Interface 3rd Party
Application
3rd Party
Application
Infr
astr
uctu
re S
erv
ice
s Service
Manager
Security
Manager
Connection
Manager
State
Manager
Data Sources - Multi-tenant
Cloud - On-premise - Hybrid
© 2013 Progress Software Corporation. All rights reserved. 6
Fluid Framework - Demonstration
From
To
© 2013 Progress Software Corporation. All rights reserved. 7
Data Access Services
Database
Business Services
Infr
astr
uctu
re S
erv
ices Services Interface
Service
Manager
Security
Manager
Connection
Manager
State
Manager Activity
Data Access
SaveData
LoadData
GetResults
Customer
Activity
Business Rules
SaveData
LoadData
GetResults
Activity Validator
Common Library
Validate Rep
Library
Data Access
Validate Rep
Salesrep
SaveData
LoadData
GetResults
Validate
Validate Rep
Activity Presenter
LoadData Validate Rep
Fluid Framework - SOA
© 2013 Progress Software Corporation. All rights reserved. 8
Fluid Framework - Integration
Make Business Functions available as
services
Publish as web services
Data Access Services
Business Services
Save
Data
Validate
Data
Load
Data
S e r v i c e s I n t e r f a c e
Save Data Load Data
Data Sources - Multi-tenant
Cloud - On-premise - Hybrid
© 2013 Progress Software Corporation. All rights reserved. 9
Fluid Framework – Multiple User Interfaces
Data Access Services
Business Services
Save
Data
Validate
Data
Load
Data
S e r v i c e s I n t e r f a c e
Save Data Load Data
Data Sources - Multi-tenant
Cloud - On-premise - Hybrid
© 2013 Progress Software Corporation. All rights reserved. 10
Fluid Framework - Corticon
Rules Engine
Move appropriate Business Rules to Corticon
Services WS Call
Business maintains IP
Greater Flexibility
Code free changes
What if functionality
Stand alone testing
Data Access Services
Business Services
Save
Data
Validate
Data
Load
Data
S e r v i c e s I n t e r f a c e
Save Data Load Data
Data Sources - Multi-tenant
Cloud - On-premise - Hybrid
© 2013 Progress Software Corporation. All rights reserved. 11
Fluid Framework
Consistent management of all the components of the application, maximize code reuse and achieve
complete separation of UI from the Business Services.
Provides the structure and framework for building an OERA application
Contains the components and services that manage the communication between the OERA
layers
Contains flexible, extensible common infrastructure services such as Security, State and
Connection Managers
Focuses on isolation of business functionality to maximise code reuse
Manages the communication with the UI and external applications with an efficient and
technology agnostic mechanism
Achieves complete separation of UI from Business services
Can co-exist with current legacy application
It is built using OOABL and takes advantage of the best of the 4GL and OO paradigms
© 2013 Progress Software Corporation. All rights reserved. 12
Platform Transformation- Benefits
Isolate Business logic
• Protect IP
• Multiple User Interfaces, Any device, Any platform, Any cloud
SOA
• Easier maintenance through promoting code and function reuse
• Combine services into new, composite applications
• Allow access to business functions across platforms
• Respond quicker and more cost-effectively to a changing market
Corticon – Business Rules Management
• Business develops IP with greater flexibility
• Code free changes
• “What if ..” functionality
• Stand alone testing of rules
© 2013 Progress Software Corporation. All rights reserved. 13
Consultant:
• In-depth look at Framework - Lift the
covers
• Demonstrate capabilities and
methodologies
• Technical Q&A
• Agree scope of POC
Approach
Business Release 3.0
Business Release 2.0 • Modernisation drivers
• Modernisation approach
• Demonstration of capability
• Overview of Framework
Client:
• Overview of application
• Outline of development team and
capability
• Objectives
Business/Consultant:
• Capture/Validate Key Business
Drivers
• Capture Key Attributes of Current
Application
• Capture Tactical & Consequential
Pains
• Capture High-Level Desires, Future
Plans, & Requirements
Discovery:
• Capture working snapshot of
application
• Development team structure and
methodologies
• Application strengths and
weaknesses
• Confirm scope of prototype
Prototype:
• Working sample activity
• Demonstrate modernised
architecture
• Full source code for analysis and
testing
Analysis:
• Analysis of code base
• Help create estimate of effort for
modernisation
• Define possible modernisation
strategies
• On-site training and mentoring
• Collaborative build and release aligned
with business priorities
• Short release cycles
Awareness 0.0 Discovery 0.1
2 days
POC 0.5
20 days
Business Release 1.0