Service Oriented Approach to Application Modernization sept 2010

Specialists in Service Oriented
Application Modernization

A Service-Oriented Approach
to Application Modernization

SOA for eGov Conference
September 16, 2010

Dave Mayo (dmayo@everware-cbdi.com)

www.everware-cbdi.com
www.cbdiforum.com

Everware-CBDI Credentials
Worldwide SOA Leadership in Advisory
Reputation Groups & Standards Bodies
Keynote Speakers on
SOA ACT/IAC
CBDI Forum Website: Chair: EA-SIG/Services
over 25,000 subscribers Committee
SOA Methodology in
Sharepoint Lead Role on Practical
SOA Metamodel Guide to Federal SOA
Submission to OMG Federal SOA Community
of Practice: Co-Chair
Authors/Publications Object Management
CBDI Journal (100+ Editions) Group (OMG)
Articles (eg, EA Journal, Co-Chair: GovDTF
Microsoft Journal) Instruct on EA & SOA
White Papers (eg, Federal CIO National Defense U/
Council, IAC, AFEI) EA Program
Books (eg, Service Industry Conferences
Orientation, Information
Public/Private Courses
Modeling)

2 V1.0 0710 www.cbdiforum.com www.everware-cbdi.com © 2010 Everware-CBDI Inc

Topics

How Did We Get Here?
Service Orientation
Model-Driven Development
What is Service-Oriented Application Modernization?
Service Architecture Views
Transition Engineering – Iteration & Releases


What’s wrong with us?!
Despite…
technological advances,
methodological advances,
tons of money being dumped in,
the increasing importance to get it right…
60-70% of large projects fail!

In a word… Complexity
1964 – Introduction of System/360
Dawn of portable code and reuse
Early programs still running today!
Billions of lines of new code
are written every year

We’re buried in code!

How Have We Tried to Solve This?
Modeling to understand the problem and solution
Support communication «Capability»
Goods Handling
«Capability»
Security

Enable analysis prior to build
Evolution of implementation strategies «Capability» «Capability» «Capability»
Food Handling Hazardous Material Hazardous Material

Structured programming… Handling Securilty

Gave way to Object Oriented programming…
Got wrapped in Components with CBD… «Capability»
Hazardous Material
Containment

Now offered up as Services in SOA…in the Cloud.
And, of course, Agile methods.

We’re Really Getting at:
Abstracting – Simplifying and generalizing
Encapsulating – Data and internal design
Modularizing – The architecture into “bite-size” pieces
Loose coupling – Minimizing interdependencies to reduce impacts of change
Separating Concerns – Managing each class of issues independently


Why Service Oriented Architecture?

“Service Oriented Architecture (SOA) is the principles, patterns and policies that
enable application functionality to be provided and requested as services published at
a granularity relevant to the Service Consumer, which are abstracted away from the
implementation using a single, standards-based form of interface.” (CBDI 2003)

SOA Benefits
SOA should provide:
• Structured approach to Business IT
deliver loose coupled, Business Process Assemble Solutions
abstracted information Automation Reduced integration
solutions effort
Standardized business
• Reference architecture for practices Productivity through
– Service Customer Partner reuse of standardized
classification/taxonomy participation Services
– Policy implementation Time to Market Reduced cost and
and governance Improvement in Data and complexity by Portfolio
– Contracts Process Quality Rationalization
– Determining sharing and Consistency Virtualization of IT
generalization at many Reduced Risk resources
levels Virtualization of Business Flexibility or
• Basis for a repeatable resources Specialization
engineering process Consistency across
channels
Multi Channel delivery

CBDI Service Architecture and Engineering™
(CBDI-SAE) [Business
Strategy &
Architecture]
[SO Business Improvement Plan]
[Solution &
Ser vice Execution Metri cs]

[Solution Deployment Authorization/(C ertified) ,
[Project C harter] Solution OLA]
[Business Proces s Exec ution
Metrics]

SO Process
Architecture Software Specification Infor mal Operation
SO Business
* has earlier release
Layer Mandatory Message Sequence Improvement
1 + name : string + text : string
+ name : string SO Business Solution [Solution Imp Des ign,
constrains * + technicalName : string *
+ name : string + sequenceDescription : string [0..1] Tested Software Solution (deployed)]
+ levelNr : int + alias : string [ *] + standardPatternName : string [0..1] Requirements Certification

Consume
+ versionNr : int [Business [Solution Project Justific ation,
Planning

SAE Meta Model
*
* involves executing
Results]
+ revisionNr : int offers 1..* Project Requirements

+ issueNr : int
Message
Service Business Type Specification [Solution Architec ture, C omponent
Solution Provisioning
Or ganizat ion 0..1 consists of [Solution [Solution Deployment
maintains data defined by Infor mation Descriptions, Sol ution D esign Scope] Design, Solution Test Pl ans, Instructions, Tested Software Solution]
1... + name [Business Models , Component Spec s
+ name : string Model * + role
defines + definition
+ isLegalEntity : boolean + encodingForm Business Case for SOA,
Business Objective supported by
Service Specification + structure SO Business Des ign,
Solution Solution Design, Solution
* + definition : string * * required to execute Business Solution
Architecture & Design Specification Assembly/
+ isInfrastructureService : bool... Requirements]
* * 1
+ responsibilities : string 1..* & Coordination Implementation
+ purpose : string 1 1..* 1..* sent to or from
+ commodityLevel : enum 1 /offers [Project Ser vice Plan/ SPP Frag ment
employs Operation Specification (approved)]
+ standardization Support : string
1 1..*
+ customizationSupport : string + name : string
+ targetConsumers : string [Ser vice Specs,
* defines + style : enum [ Ser vices (publis hed)]
+ visibility : enum + transmission : enum
Ser vice R equirements Usage SLA]
SPP Frag ment
1 acts as + stability : string + inputMessage : string [SOA
Employee Service Owner responsible for Interface or 1 groups Adoption
+ hasRunTimeInstances : boolean + outputMessage : string
[(Ser vice [Ser vice D eployment Authorization/
* + type : emum Port Type Plan] Catalog (updated) ]] Ser vices ( certified) , Ser vice OLA]
+ name : string 0..2 1..* + otherInfo : string 1..* 1..* + errorMessage : string
+ id : string + name + isTransactional : boolean
+ coordinationBy : enum [Deployed
is provider in Service Definition Ser vices,
Language File contains 1 Service Oriented
Protocol Ser vice
is consumer in
0..1 1..* Architecture Service Discover y
* 1 Artifacts,
concerns this + name : enum 1 1 Certification
* * 1..*
+ versionNr : enum & Design [Tested AU Units] Ser vice
Access
1
1 applies to Procs]
* * * has alternative

Provide
Service Level behavior defined by subject to
Agreement conforms to bound to Service Provisioning

CBDI-SAETM
bound to [Ser vice

SOA Reference Framework
* Descriptions
+ fileName currently exists in * * (part of Pr oject Ser vice Plan/SPP)]
belongs to * [ SPP, SO Security Archi tecture]
[Project Ser vice Plan] [Ser vice Specs (approved) ,
Pre Post Condit ion Pair
*
Compliance Level
*
1..* Service Design, AU Descri ptions (approved)]
1
+ areaName : enum Endpoint
+ identifier : string 1..* Specification &
+ precondition : string
* Service State Service Classification + name : string
+ postcondition Endpoint
Coordination
has nested + name : string
+ name : string + name : string Operation [IT Strateg y
1..* + networkAddress : string & Architec ture]
+ meaning : string 1
+ WSDL binding name : string + name : string
0..1 + code : string
supports 1..* Legacy Service
[Legacy Tr ansition Plan]
* comprised of Transition
Implementation
Note: Model does not support Planning
concurrent substates. Probably member of *
1..*
needs to subject to
Compliance Level Deviatioin
Coordinated
Compliance Item * [Ser vice D eployment
1 Item [SOA Reference
Architecture Scope

Model Process
Framewor k] Instructions,

Service Classification Group + identifier : string 1 overiddenBy + identifier : string
Tested AU Units]
[IT inventor y]
+ definition : string
+ singleValuedMembership : boolean + category : eum * + role : enum
+ mandatoryMembership : boolean + definition : string
+ notes : string + category : string
+ name : string ...

[Solution/
Ser vices
Solution/Services Platfor m Solution/Service [Installed
Architecture] Ser vice Pl atfor m] Solution/Service
Platform Platform Design
Deployment

Manage
Architecture & Installation

Enable
[Project Ser vice Architec ture/SPP,

SOA Principles Glossary SO Securi ty Arch]

[IT Strateg y
& Architec ture]
[Ser vice Platfor m Design,
Tested Ser vice Pl atfor m,
Installed Ser vice Platfor m]
[Guidelines (e.g. ITIL)]
[Deployed Software
Solution]

Solution/Service
Operations &
Measurement

Manage
Service Life Cycle SOA Meta Model Service Life Cycle Consume SOA Adoption Plan
Governance & Management Framework

Planned Provide
Specified Architecture
SOA Governance
Enable SOA Governance
Being Provisioned Organization
SOA Views SOA Best Practice

SOA Governance Process

SOA Governance Maturity
Provisioned SOA Policy Hierarchy
Business Policy
Models
Deliverables
Techniques
Patterns
Standards
Certified
Organization
Published
Specification
Operational Roles & Structure
Implementation
Retired

Deployment Project Profiles
Archived

Technology Funding Models SOA Governance Infrastructure
Sample Artifacts Service Perspective
Vie
w Business Service, Context for Software
SO Business Plan Services
Business
Business Service =
SO Business Model Services offered by
Organizational Units

Logical Specification of Software
Specification Service Specification Services enablers results
Architecture
MANAGEMENT
Service CAPABILITY PROJECT &
Specification SYSTEM

SERVICE ARCHITECTURE & ENGINEERING
Service = Service Specification

Implementati
Service Implementation
Architecture
Service Packaging into Automation Units
ARCHITECTURAL
OUTCOMES
SOA
Service Level Agreement

on Automation Unit
CAPABILITY

SO Reference
Service Portfolio Plan

Maturity &
Specification
LEADERSHIP & GOVERNANCE

Service
Service Catalog

Implementation Service = Software Service Impl. PROCESS / LIFECYCLE SERVICE
Deployment of Automation Units CAPABILITY OUTCOMES
Deployment
Service Deployment

Architecture Excellence

SOA PERFORMANCE
Architecture
SO Security Architecture

Service Platform Design
Specification
INFRASTRUCTURE
Service = Run-Time Software Service CAPABILITY

PROCESS
e.g. Network Layout, ESB
Infrastruct Logical Network Services BUSINESS
Architecture
Technical

ure OUTCOMES
PEOPLE &
Physical Network Infrastructure Service = ORGANIZATION
Run-Time Platform


CBDI-SAE Process Model

Business
Improvement

Consume Solution
Provisioning
Solution Solution
Business
Architecture & Assembly/
Modeling
Design Implementation
Legacy Application
Reengineering
Application
Knowledge
Modernization
Discovery
Planning
Legacy to Service
Reengineering
Service Oriented Service
Provide Architecture Implementation
& Design Service
Provisioning

Information Architecture

Solution/Service Solution/Service Solution/Service
Solution/Service
Enable Platform Platform Design Operations &
Deployment
Architecture & Installation Management

SOA Adoption & Excellence
SOA Governance

Manage SOA Quality Management

SOA Delivery Management
Modernization Change Management


Model Driven Development

Model Driven Development: Software delivery approach where specification models and other
abstract artifacts are created to describe the structure and behavior of a system or module. The models
are either executed directly or transformed into implementation code or environment control.

Application & Business Business Rule Metadata Message Mgt
Service Models Process Models Models Models

yes
«BusinessProcess»
2 enl istm ent
yes

shipping
«BusinessProce...
3 shippi ng

shipper Parties and
Facilities
+placeOf Bi rth

1
«Business T ype»
Location
«Business Type»
• Routing
requested? resides + st reet : st ring bel ongs to Regi on
«Business T ype»

Mediation
enl ist wit h at + cit y: string
M EPS? Party * *
yes + count y: string * 1

•
no + name incl udes + zipCode: st ri ng
+ name
no, waiver grant ed Applic ant
enlistee 1
chooses not 1 is located
to enli st plays * «enumerat ion»
* at
* Raci alCategory
«Busi nessProcess» «Business T ype»
1 appli cant qual ifi cati on «Business T ype» Faci lity ameri canI ndi anO rAlaskaNat ive
«Business T ype» «Business T ype»
Person have asi an
Role Organizati on + name: string
StartEvent1 Meet s standards for quali fi ed not enl ist ed blackO rAfricanAmeri can
hasLanguage + gender: G ender 1 *
nati veHawaii anO rO therPaci ficI slander
enli stm ent, appoi ntm ent or + dob: date
1 + white
induct ion? ssn: stri ng
+ uniqueI denti fi er decli neT oRespond
*
+ phone numbers

Translation
«Business T ype» + fi rst Name: st ri ng
ForeignLanguageSki ll + mi ddl eName: string «enumerat ion» «enumerati on»

•
«Business T ype» «Busi ness T ype» G ender MaritalStatus
+ last Name: st ri ng «Business Type»
+ l anguage: stri ng Recepti on/Tr ai ning Duty Station
no + mari talStatus: Marit alSt atus Arm ed Serv ice
+ f irst: boolean Center mal e married
+ pri or mi lit ary service f em al e single
+ pri vileges other divorced
+ preferences
appli cant not
appli cant not + raci al Category: RacialCategory
enli sted wi th «enum eration»
quali fied for + ethnicCat egory: Et hni cCategory
enli stm ent /accession MEPS EthnicCategory
+ dependent s: int
+ rel igiousPreference: string
decli neT oRespond
+ educat ion: Education
hispanicO rLatino
nonHi spani cO rLati no

• Etc.

BPMN UML, UML,
UML
SBVR OWL/
RDF

Java, C#, DDL,
XSD, BPEL XBRL, DDL,SQL,
WSDL OCL SPARQL
• Source code Virtualized
Workflow / Business Rules Infrastructure /
• Executables
Orchestration Logic Data Access ESB
• Test Harness
• Documentation
Control Configuration


Model Driven Architecture & SOA
MDA Perspective Service Perspective
(OMG)
Capability Model
CIM - Computation Business Business Process Model
Independent Model View Business Type Model
Event Response Model

Service Specification Model
PIM - Platform Specification Use Case Model
Independent Model View Service Information Model

Implementation Service Implementation Model
PSM - Platform Service Data Model
Specific Model & Deployment Service Deployment Model
View Service Platform Model

Java Implementation Files
PSI - Platform Specific Execution Oracle DDL
Implementation View WSDL Files


MDA Supports Technology Independence
(“Future Proofing”)

Model Consistency
Model Reuse CIM
Portability
Simplify Integration/Assembly
Eases Technology Upgrades
PIM

Java .Net WSDL
PSM PSM PSM

Java .Net WSDL
PSI PSI PSI



Application Modernization: Rationalize one or more applications (at the presentation, code or data
layer) to improve business support, technology usage and lifecycle and run-time delivery processes.

To Improve:

Consistency Efficiency
Standards
IT Consolidation
Governance/Policy Enforcement
Master Data Management Process/Operations
Interoperability Optimization
Effectiveness Resource Utilization
Customer Focus Agility (Organizational & IT)
Business Support Mergers & Acquisition
Business Intelligence Competitive Pressures
Quality of Service Regulatory & Statutory
Compliance
Innovation
Technology Obsolescence


What is the core of Application Modernization?

Supporting new business requirements

mapping

Transition

AS-IS Managing the transition TO-BE
Understanding current Detailing new
implementation implementation


Forrester (2009) Top Reasons for Modernization

IT leaders survey:
59% place modernization as the top software issue
49% will consolidate or rationalize enterprise applications

1.

2.

3.

4.

5.

6.

7.

8.

Source: Application Modernization and Migration Trends, Forrester Consulting, November, 2009.


CBDI-SAE Application Modernization Framework

Business

Architecture n
Architecture 1

Architecture 2

Architecture 3
Architecture Knowledge Discovery

Rapid Delivery
Specification
Architecture
Implementation Sequence Planning
Architecture

Transitional
Transitional

Transitional

Transitional
Deployment
Architecture
Technology
Architecture As-Is To-Be

Transition Strategy
Business Case Analysis
Information Architecture
Delivery Management


Application Modernization Options

Current Environment

Legacy Applications

Rehost Open Re- Retire Develop Acquire
architect

Independent Wrapped
COTS
Legacy Legacy Services
Application
Application Transactions

Target Environment


Application Rearchitecting - Services

Preparation Stage 1 Stage 2 Stage 3

Existing Systems using
proprietary delivery Surround existing systems Optimally componentized
Selective Componentization
technology with single with Service Architecture implementation
integrated database

Business Driven Service
Business process embedded
Architecture enabling more Increased implementation
in existing application. Opportunities for resource
flexible use of existing flexibility whilst maintaining
Constrains process and virtualization
assets in new business stability of services
implementation flexibility
processes

Internal dependencies still Dependencies all via
remain Services


Approach Determines Type/Level of Activity
AS-IS Business Model TO-BE Business Model
(including Capabilities)

Service Specification
Application Architecture Architecture
Service
<<Application>>
Replace (Build) Specification

Architecture-based Development
<<Application>> Architecture Recovery Replace (Buy)

Implementation Internal
Architecture <<component>> Architecture
<<module>> Rationalize
Re-skin <<component>
Logical

<<module>>
Re-process >
Service Facade Service
<<database>> Implementation
Architecture
Implementation
Physical

<<component>>
<<module>> Service Enable If, then, else <<database>>
If, then, else
Recode
Restructure <<message>>
<<database>>
table, column

Deployment Architecture Re-platform New Deployment
Technology Architecture Re-host Architecture


Core/Context Influences Modernization Approach

(based on concepts developed by
Replace (Build) Approach
Geoffrey Moore)

Core Activities -- Context Activities --
engage your resources disengage resources

Mission Critical
Activities -- Replace (Buy)
DIFFERENTIATE STANDARDIZE
Primary purpose
of the organization

Service Facade
Rationalize
Supporting
Activities --
not the main line EXPERIMENT OUTSOURCE
Offload
of business

e.g. experiment e.g. to enable
with social virtualization and
networks, mobile cloud
devices Re-skin

What is
Service Oriented Application Modernization?

Business
Enterprise
Process
Architecture
Mgt
Model Portfolio
SOA
Driven
Mgt
Development

Micro – Macro –
Data Single Multiple
Virtualization Application Apps
(Push) (Pull)

Investment
Security Planning Transition
Management (CPIC) Engineering
Business
Rules
Mgt


Contextual Framework Relationships

Provides the overall
context

Enterprise Architecture Service Oriented
Business Requirements
Obtain
Executive
Architecture
Maintain the Buy-In and
Enterprise Support
Establish
Architecture Management
Structure
and Control mapping
Use
the
Enterprise
Define an
Architecture Architecture
Process
and Approach Transition
Develop the
Sequencing Plan

Develop
Develop
Baseline
Enterprise
AS-IS TO-BE
Target Architecture
Enterprise
Architecture

e.g. FEAF

Architecture

Function
Code
Provides the Deploy
Provides
overall the TO-BE
context
Legacy
Transformation
Approach

Service Architecture Views

Legacy Service
Environment Architecture
Business Model
Legacy *
(Capability
Applications * Dependencies) Business requirements view
*
Supported by
*
Service
Specification External (consumer’s) view
Model

*
Implemented by
*
Service
Implementation Internal (developer’s) view
Model

*
Operates within
1

Service Runtime platform
Deployment
Environment


Deriving the Service Architecture Views

Business Drivers Business Process Service Registry
• Vision/Mission View
yes «Bus inessProce...

• Strategies
3 shipping

shi pper

«BusinessProcess»
yes 2 enlistment shi pping
requeste d?
enli st wi th
MEPS? yes
no

• Objective1
no, waiver granted Appl ica nt
enli stee
choo ses not
to enl ist

Service
«Bus iness Process»
1 applicant qualification

Sta rtEvent1 M eets standards for q uali fi ed not enl isted
e nli stmen t, app ointme nt or
i nducti on?

• Objective2 appl icant not
qual ifi ed for
enl istm ent/accession
no

ap pli cant no t
en li sted wi th
M EPS
Registry/
• Objective3 Repository

Req’d capabilities
defined in

Capability Dependency Service Implementation Deployment View
View Specification View View a: Client PC

In ternet Explorer
an: ExternalHost

Address
Formattin g Service

Product Life Ordering Billing
Solution Layer Solution Layer
Product Life Ordering Billing
Cycle System Application Application (UI, dialog (UI, dialog
Manufacturing Cycle System Application Application HTTP SOAP over
management) management) HTTP

a: Web Server
Product : Application Server : Mainframe
Sales {opSys = Win dowsNT}
Produ ct Lifecycle
Process {webSvr = Apach e}
Services Inven tory System
Lifecycle Process Services « component »
Services Process Services {nrDeployed = 4}
Services « component »
Sales Process Services (orchestration layer) (orchestration layer)
Inventory Products Life Sales Process : T P Monitor
Cycle Component : EJB Container Protocol Adapter
Management Component
Shipping : Servlet Engine Manu facturing
Sales Compon en t
Products Produ cts Orderin g and Billin g System
Service Componen t Apps
Orders Core Business Services « aggregator » Orders
Customers
Core Business Services Product LC System
Service (the backbone layer)
Service (“backbone” layer) Products
«component»
Service : Orchestration
Cu stomers Service Component
Sales
Server
Products Service : SOAP Engine
Component RMI
Purchasing Products LC Service
Receiving Sales Process : BPEL En gine
«external» JDBC Service
Utility Services Address Utility Services Produ ctsLife
Address Formatting Products Service
(high reuse layer) Formatting Service Undefined (high reuse layer) Cycle Compt : DB2 DBMS
Service : Oracle DBMS Orders Service
Inven toryDB Customers Service SalesProcess
Products In Products In Manu facturing
Sales DB ProductsFromManuf Compon en t
Products in Manufacturing Sys Inventory Sys DB
ProductsFromInvnty
Man ufacturing Underlying Services «legacy» «wrapper»
Products in
(not so easy to use) Manufacturing ProductsAPI2
Underlying Services
Accounting System Inventory System
«legacy»
System Wrapper Inventory (not so easy to use) SOAP over JMS
System 338
315 indicates an embedded data store

Realized by Implemented by Deployed to

Business Type Legacy Technology View
View Discovery
Parties and
+placeOfBi rth
Facilities «Busi ness T ype»
1
Location
«Business T ype» UI
resi des + street: stri ng bel ongs to Region
«Busi ness T ype» Process Management Manageme nt Governance Registry/
at
Party * * + city: string
+ county: stri ng * 1 Directory
+ nam e i ncludes + zipCode: string
+ name

1
1 i s located
pl ays * «enumerati on»
* at Service
* RacialCategory
«Busi ness T ype» Orche stration )@d F9&
«Business Ty pe» Facility am eri canIndi anOrAlaskaNati ve
Person «Busi ness T ype» «Business T ype»
Organization have asi an
Role + name: string
hasLanguage + gender: Gender bl ackOrAfri canAmerican
1 *
+ dob: date nativeHawaii anOrOtherPac ificIsl ander
1 + white
ssn: string
decl ineT oRespond
* + uniqueIdentifier Mediation Transform
+ phone numbers Route
«Business T ype» + fi rstName: string
ForeignLanguageSkill + mi ddl eName: stri ng «enum eration» «enumerati on»
+ lastName: string «Business T ype» «Busi ness T ype» Gender MaritalStatus
+ language: stri ng «Busi ness Ty pe» Reception/Training Duty Station
+ marital Status: MaritalStatus Armed Serv ice m ale marri ed Messaging
+ fi rst: boolean Center
+ pri or m il itary servi ce femal e singl e )@d Messaging F9&
+ pri vil eges other divorced
+ preferences
+ raci alCategory: Rac ial Category Transport
+ ethnic Category : Ethni cCategory «enum eration»
+ dependents: int EthnicCategory
Security Policy Descr-
+ rel igiousPreference: stri ng decl ineT oRespond Authe nticate Fire wall SLA
+ educati on: Education Encrypt iption
hi spanic OrLati no
nonHispanicOrLati no Sign Permissions Decrypt

Provision/Host
BCA
ABC

Service Consumer Service
Provider
20


Capability Dependencies
Business Capability: The competence, ability and capacity to
perform a specific function of value to a certain level of maturity.

Hire & Retain
Quality Staff

Manage
Compensation
Recruiting

Position
Provide Management
Benefits Manage
Careers

Provide
Healthcare
Provide Income
Security Provide
Provide Professional
Training & Development
Educat.


Layered Service (Specification) Architecture

Process Driven
Order
Solution Model Process Services Fulfillment
Service

Function Driven Capability Services

Capability Model Logistics Service

Data Centric Core
Orders Service
Business
Domain Model Products
Services
Service
Bottom Up
Underlying
Current Systems
Model Services Accounts
Receivable API
Design Driven
Utility
Reuse Model Address Reformatting Service
Services
Units of Measure


Service Implementation Architecture

Automation
Unit:
Software
Component
or
Wrapped
Legacy
Transaction


a: Client PC
an: ExternalHost
Deployment
Internet Explorer Address
Architecture Formatting Service

Shows where Automation
Units are installed HTTP SOAP over
HTTP

a: Web Server
Application Server Mainframe
{opSys = WindowsNT}
Inventory System {webSvr = Apache}
{nrDeployed = 4}
Protocol Adapter TP Monitor
EJB Container
Servlet Engine Manufacturing
Sales Component
Products Ordering and Billing System
Component Apps
Product LC System
Orchestration
Server
RMI
SOAP Engine
Products LC Service
Sales Process BPEL Engine
JDBC Service
ProductsLife
Products Service
Cycle Compt DB2 DBMS
Oracle DBMS Orders Service
Customers Service SalesProcess
InventoryDB Manufacturing
ProductsFromManuf Component
Sales DB DB
ProductsFromInvnty

SOAP over JMS

CBDI-SAE Transition Engineering Process
Business Architecture
Define Future Define Business
Performance
Operating Improvement
Management
Concept Increments

Service Architecture Release Planning
Project Planning
Service
Capability
Portfolio Detailed
Analysis
Planning Release Release
Architecture & Planning
Scheduling

Data
Application Management
Legacy/Source
Modernization Release
Analysis
Planning Deployment

Development
&
Configuration Implementation
Legacy Transition Planning Management


Transition Engineering:
Release Planning Architecture

Release 1 Release 2 Release 3 Release 4
(t + 3 mo) (t + 6 mo) (t + 9 mo) (t + 12 mo)

C1 C1 C3 C1 C3 C1 C3 C4 Capabilities
C2 C2 C2a C2a View

S1 S1 S3 S1 S3 S1 S3 S4 Service
Specification
S2 S2 S2a S2a
View

Automation
LT1 LT1 SC3 SC1 SC3 SC1 SC3 SC4 Units (Legacy
LT2 LT2 SC2 Sc2
Trx / SW
Components)

P1/ P1/ P2/ P2/ P2/ P4/ Deployment
MF MF Lin Lin Lin Win Platform


Evolutionary Implementation of Capabilities

Releases (Transition States)

Capability Category (Human Resources) 3 mo. 6 mo. 9 mo. 1 yr. 15 mo. 18 mo. Legend

Manage Positive Identification Red = No Capability

Manage Recruiting Blue = Prototype

Manage Online Background Investigations Yellow = Partial
Green = Ready for
Manage Retention Review & Certification
Manage Medical Benefits

Manage Income Security

Manage Training & Education

Manage Annual Review Process

Manage EEO

Manage Compensation
Manage Access to Position Management
System

Manage Exit Processing


We need Things Why can’t They’re not Why don’t Because Why
Why do we adapt
to deliver we need have adaptable. we make we don’t don’t we
the new changed. what we things have have
it fast? have?
system adaptable? time. time?
fast. Specialists in Service Oriented Application Modernization

CBDI Journal 1997

Thank you.
Dave Mayo
dmayo@everware-cbdi.com

www.cbdiforum.com www.everware-cbdi.com

Service Oriented Approach to Application Modernization sept 2010

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Service Oriented Approach to Application Modernization sept 2010 (20)

Recently uploaded (20)

Service Oriented Approach to Application Modernization sept 2010