Service Oriented Approach to Application Modernization sept 2010

Specialists in Service Oriented

Application Modernization

www.everware-cbdi.comwww.cbdiforum.com

A Service-Oriented Approach to Application Modernization

SOA for eGov ConferenceSeptember 16, 2010

Dave Mayo ([email protected])

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

Everware-CBDI CredentialsWorldwide SOA Reputation

� Keynote Speakers on SOA

� CBDI Forum Website: over 25,000 subscribers

� SOA Methodology in Sharepoint

� SOA Metamodel Submission to OMG

Leadership in Advisory Groups & Standards Bodies

� ACT/IAC� Chair: EA-SIG/Services

Committee

� Lead Role on Practical Guide to Federal SOA

� Federal SOA Community of Practice : Co-Chair

� Object Management Group (OMG)� Co-Chair: GovDTF

� Instruct on EA & SOA� National Defense U/

EA Program

� Industry Conferences

� Public/Private Courses

Authors/Publications� CBDI Journal (100+ Editions)� Articles (eg, EA Journal,

Microsoft Journal)� White Papers (eg, Federal CIO

Council, IAC, AFEI)� Books (eg, Service

Orientation, Information Modeling)


Topics

� How Did We Get Here?� Service Orientation� Model-Driven Development � Application Modernization� 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

� Enable analysis prior to build

� Evolution of implementation strategies� Structured programming…

� Gave way to Object Oriented programming…� Got wrapped in Components with CBD…

� Now offered up as Services in SOA…in the Cloud.

� And, of course, Agile methods.

«Capability»Goods Handling

«Capability»Food Handling

«Capabi lity»Hazardous Material

Securilty

«Capability»Hazardous Material

Containment

«Capabi lity»Security

«Capabil ity»Hazardous Material

Handling

� 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

6 © 2010 Everware-CBDI IncV1.0 0710 www.cbdiforum.com www.everware-cbdi.com6

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 should provide:

• Structured approach to deliver loose coupled, abstracted information solutions

• Reference architecture for

– Service classification/taxonomy

– Policy implementation and governance

– Contracts

– Determining sharing and generalization at many levels

• Basis for a repeatable engineering process

Business

� Business Process

Automation

� Standardized business

practices

� Customer Partner

participation

� Time to Market

� Improvement in Data and

Process Quality

� Consistency

� Reduced Risk

� Virtualization of Business

resources

� Consistency across

channels

� Multi Channel delivery

SOA Benefits

IT

� Assemble Solutions

� Reduced integration

effort

� Productivity through

reuse of standardized

Services

� Reduced cost and

complexity by Portfolio

Rationalization

� Virtualization of IT

resources

� Flexibility or

Specialization


CBDI Service Architecture and Engineering™(CBDI-SAE)

Software Specification

+ name : string

+ technicalName : string

+ alias : str ing [ *]+ versionNr : int

+ revisionNr : int

+ issueNr : int

Service Specification

+ isInfrastructureService : bool...

+ responsibilities : str ing+ purpose : string

+ commodityLevel : enum

+ standardization Support : string+ customizationSupport : string

+ targetConsumers : str ing

+ visibility : enum+ stability : str ing

+ hasRunTimeInstances : boolean

+ otherInfo : string

has earlier release*

*

Interface or

Port Type

+ name

defines

1..*

1Operation Specification

+ name : string

+ style : enum

+ transmission : enum

+ inputMessage : string+ outputMessage : string

+ errorMessage : string

+ isTransactional : boolean+ coordinationBy : enum

/offers

1..*

1

groups

1..*

1

Endpoint

+ name : string+ networkAddress : string

+ WSDL binding name : string

has alternative

1..*

1

Endpoint Operation

+ name : string

supports 1..*

1

bound to

1..*

1

Protocol

+ name : enum

+ versionNr : enum

bound to

1

*

Informal Operation

+ text : string

+ name : string

offers

*

Compliance Item

+ identifier : string

+ definition : string+ category : eum

+ notes : string

Service State

+ name : stringhas nested*

0..1

currently exists in

1

*

Note: Model does not support concurrent substates. Probably

needs to

Service

Information

Model

Pre Post Condit ion Pair


+ precondition : string

+ postcondition

*

1

behavior defined by

Service Classification

+ name : string

+ meaning : str ing

+ code : str ing

belongs to

*

*

Service Classification Group

+ singleValuedMembership : boolean

+ mandatoryMembership : boolean+ name : str ing

member of

1

*

Business Objective

+ definition : str ing

supported by

* *

Architecture

Layer

+ name : string

+ levelNr : intconstrains

1

*

Service Definition

Language File contains

1..*0..1

Organizat ion

+ name : string

+ isLegalEntity : booleandefines

*

1...

Employee

+ name : string

+ id : str ing

employs

*

1

Service Owner

+ type : emum

acts as

*

1 responsible for

1..*0..2

Service Level Agreement

+ fileName

concerns this

1..**

is consumer in

*

*

is provider in

*

*

maintains data defined by

Message Specification

+ role+ encodingForm

+ structure

sent to or from

1..*

1..*

Business Type

+ name

+ definition*

consists of0..1

Mandatory Message Sequence

+ sequenceDescription : string [0..1]

+ standardPatternName : string [0..1]

required to execute

1

1..*involves executing

1..*

*

Compliance Level

+ areaName : enum

+ name : string

Compliance Level Deviatioin

Item


+ role : enum

+ definition : string+ category : string...

conforms to

*

*applies to

*

*

1..*

1..*

comprised of

subject to

*

1

overiddenBy

*

1

subject to

1

*

SAE Meta Model

Business

View

Service Perspective

Ser

vice

Cat

alog

Logical Specification of Software Services

Service = Service Specification

Service = Software Service Impl.

Service Packaging into Automation Units

Deployment of Automation Units

Service = Run-Time Software Service

Business Service = Services offered by Organizational Units

Business Service, Context for Software Services

Sample Artifacts

Specification

Implementation

Deployment

Infrastructure

e.g. Network Layout, ESB

Infrastructure Service = Run-Time Platform

Logical Network Services

Physical Network

Automation Unit Specification

Service Platform Design Specification

SO Business Plan

Service Implementation Architecture

Service Deployment Architecture

Service Specification Architecture

Tech

nica

l A

rchi

tect

ure


Ser

vice

Lev

el A

gree

men

t

SO Business Model

Service Implementation

SO

Sec

urity

Arc

hite

ctur

e

Ser

vice

Por

tfolio

Pla

n SO Reference Architecture

PROJECT & SYSTEMOUTCOMES

SERVICEOUTCOMES

BUSINESSOUTCOMES

SE

RV

ICE

AR

CH

ITE

CT

UR

E &

EN

GIN

EE

RIN

G

PR

OC

ES

S

LEA

DE

RS

HIP

& G

OV

ER

NA

NC

E

SO

A P

ER

FO

RM

AN

CE

MANAGEMENTCAPABILITY

ARCHITECTURALCAPABILITY

PROCESS / LIFECYCLECAPABILITY

INFRASTRUCTURECAPABILITY

PEOPLE &ORGANIZATION

enablers results

SOA Maturity & Excellence

SO Process

CoordinatedArchitecture Scope

SolutionAssembly/Implementation

Solution Design,Specification& Coordination

SO BusinessRequirementsPlanning

LegacyTransitionPlanning

ServiceImplementation

Solution/ServiceDeployment

Solution/ServicePlatform Design& Installation

Con

sum

eP

rovi

deE

nabl

e

[BusinessStrategy &Architecture]

[SOAAdoptionPlan]

[IT inventor y]

[IT Strateg y& Architec ture]

[Solution Project Justification,

Project Requirements

[DeployedSer vices,

Ser viceDiscover yArtifacts,

Ser viceAccessProcs]

[Guidelines (e.g. ITIL)]

[IT Strateg y& Architec ture]

[Legacy Tr ansition Plan]

[Project C harter]

[Ser viceDescriptions(part of Pr oject Ser vice Plan/SPP)]

[Tested AU Units]

[Ser vice D eploymentInstructions,

Tested AU Units]

[Solution Architec ture, C omponent Descriptions, Sol ution D esign Scope]

SO BusinessImprovement

[SOA ReferenceFramewor k]

[Ser vice Platfor m Design,

Tested Ser vice Pl atfor m,

Installed Ser vice Platfor m]

SolutionCertification

[Solution Imp Des ign,

Tested Software Solution (deployed)]

Solution Provisioning

Service OrientedArchitecture& Design

Solution/ServicesPlatformArchitecture

[Solution/Ser vicesPlatfor mArchitecture]

[Project Ser vice Architec ture/SPP,

SO Securi ty Arch]

[Business Models ,

Business Case for SOA,

SO Business Des ign,

Business SolutionRequirements]

SolutionArchitecture & Design

[Ser vice Specs,

Usage SLA]

[Solution DeploymentInstructions, Tested Software Solution]

[Solution Deployment Authorizat ion/(C ertified) ,

Solution OLA]

Solution/ServiceOperations &Measurement

[Solution &Ser vice Execution Metri cs]

[Deployed SoftwareSolution]

[SO Business Improvement Plan]

[BusinessResults]

SOA Adoption Plan

Governance & Management FrameworkMan

age

[Project Ser vice Plan/ SPP Frag ment (approved)]

ServiceCertification

Service Provisioning

Service Design,Specification &Coordination

[Ser vice Specs (approved) ,

AU Descri ptions (approved)]

[ Ser vices (published)]

[Business Process Execution Metrics]

[ SPP, SO Security Archi tecture][Project Ser vice Plan]

[SolutionDesign, Solution Test Pl ans, Component Specs

Ser vice R equirementsSPP Frag ment

[InstalledSer vice Pl atfor m]

[Ser vice D eployment Authorizat ion/Ser vices ( certified) , Ser vice OLA]

[(Ser viceCatalog (updated) ]]

SOA Governance

SOA Policy Hierarchy

SO

A G

overnance Process

SO

A G

over

nanc

e M

atur

ity

SOA Governance Infrastructure

SOA Governance Organization

Service Life CyclePlanned

Specified

Certified

Published

Operational

Retired

Being Provisioned

Provisioned

Archived

CBDI-SAETM SOA Reference Framework

Model

SOA Principles

Service Life CycleSOA Meta Model

Glossary

Architecture

Business

Deployment

Patterns

Policy

Techniques

SOA Views

Organization

Roles & Structure

Funding Models

Project Profiles

Models

Deliverables

SOA Best Practice

Process

Enable

Consume

Manage

Provide

TechnologyS

tandardsImplementation

Specification


CBDI-SAE Process Model

SolutionAssembly/

Implementation

BusinessModeling


BusinessImprovement

SolutionArchitecture &

Design

Legacy to ServiceReengineering

SolutionProvisioning

ServiceProvisioning

Solution/ServiceDeployment

Solution/ServicePlatform Design

& InstallationEnable

Solution/ServicePlatform

Architecture

Solution/Service Operations & Management

Modernization Change Management

SOA Quality ManagementManage

SOA Delivery Management

Consume

Provide

Information Architecture

Service OrientedArchitecture

& Design

ApplicationModernization

Planning

Legacy Application Reengineering

SOA Governance

SOA Adoption & Excellence

Knowledge Discovery


Model Driven Development

StartEvent1 Meets standards for enli stm ent, appoi ntm ent or induction?

enl ist with M EPS?

appli cant not quali fied for enli stm ent/accession

appli cant not enli sted wi th MEPS

shipping requested?

enlistee

quali fi ed not enl isted

shipper

«BusinessProcess»1 applicant qualification

«BusinessProcess»1 applicant qualification

Applicant chooses notto enli st

«BusinessProcess»2 enl istment

«BusinessProcess»2 enl istment

Applicant chooses notto enli st

«BusinessProce...3 shipping

«BusinessProce...3 shipping

no

yes

no

yes

no, waiver granted

yes

Application & Service Models

Business Process Models

Metadata Models

Message Mgt

«Business Type»Region

«Business T ype»Faci lity

+ name: string

«Business Type»Armed Serv ice

«Business T ype»Reception/Training

Center

«Busi ness T ype»Duty Station

«Business T ype»Party

+ name

«Business T ype»Role

«Business T ype»Organization

«Business T ype»Person

+ gender: Gender+ dob: date+ ssn: stri ng+ uniqueIdenti fi er+ phone numbers+ fi rstName: stri ng+ mi ddl eName: string+ lastName: stri ng+ mari talStatus: MaritalStatus+ pri or mi litary service+ pri vileges+ preferences+ raci al Category: RacialCategory+ ethnicCategory: Ethni cCategory+ dependents: int+ rel igiousPreference: string+ educat ion: Education

«Business T ype»Location

+ street: string+ city: string+ county: string+ zipCode: stri ng+ name

Parties and Facilities

«enumerat ion»Gender

mal e fem al e other

«enumerati on»MaritalStatus

married single divorced

«enumerat ion»RacialCategory

ameri canIndi anOrAlaskaNat ive asi an blackOrAfricanAmeri can nati veHawaii anOrOtherPaci ficIslander white decli neT oRespond

«enum eration»EthnicCategory

decli neT oRespond hispanicOrLatino nonHi spani cOrLati no

«Business T ype»ForeignLanguageSki ll

+ l anguage: stri ng+ f irst: boolean

*

residesat

*

1plays

*

incl udes

1

have

*

*is locatedat

1

*

bel ongs to

1

*

+placeOfBi rth

1

1

hasLanguage

*

• Routing• Mediation• Translation• Etc.

•Source code•Executables•Test Harness•Documentation

Workflow /OrchestrationControl

Business RulesLogic

Virtualized Data Access

Infrastructure /ESB Configuration

UML BPMN

BPELJava, C#, XSD,WSDL

UML, SBVR

DDL,XBRL, OCL

UML,OWL/RDF

DDL,SQL,SPARQL

Business Rule Models

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.


Model Driven Architecture & SOA

CIM - Computation Independent Model

PIM - Platform Independent Model

PSM - Platform Specific Model

PSI - Platform Specific Implementation

Service Perspective

Business View

Capability ModelBusiness Process ModelBusiness Type ModelEvent Response Model

Execution View

Java Implementation FilesOracle DDLWSDL Files

Implementation & Deployment

View

Service Implementation ModelService Data ModelService Deployment ModelService Platform Model

Specification View

Service Specification ModelUse Case ModelService Information Model

MDA Perspective(OMG)


MDA Supports Technology Independence (“Future Proofing”)

CIM

PIM

Java PSM

Java PSI

.Net PSM

.Net PSI

WSDL PSM

WSDL PSI

� Model Consistency� Model Reuse� Portability� Simplify Integration/Assembly� Eases Technology Upgrades



To Improve:

� Consistency� Standards� Governance/Policy Enforcement� Master Data Management� Interoperability

� Effectiveness� Customer Focus� Business Support � Business Intelligence� Quality of Service

� Efficiency� IT Consolidation� Process/Operations

Optimization� Resource Utilization

� Agility (Organizational & IT)� Mergers & Acquisition� Competitive Pressures� Regulatory & Statutory

Compliance� Innovation� Technology Obsolescence

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.


What is the core of Application Modernization?

AS-IS TO-BE

Transition

Understanding current implementation

Detailing new implementation

Managing the transition

Supporting new business requirements

mapping


Forrester (2009) Top Reasons for Modernization

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

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.


CBDI-SAE Application Modernization Framework

Delivery Management

Information Architecture

Business Case Analysis

Transition Strategy

BusinessArchitecture

Tra

nsiti

onal

A

rchi

tect

ure

1

Tra

nsiti

onal

A

rchi

tect

ure

2

Tra

nsiti

onal

A

rchi

tect

ure

3

Tra

nsiti

onal

A

rchi

tect

ure

nTo-BeAs-Is

Kno

wle

dge

Dis

cove

ry

Rapid D

eliverySequence Planning

SpecificationArchitecture

ImplementationArchitecture

Technology Architecture

DeploymentArchitecture


Application Modernization Options

Current Environment

Legacy Applications

Rehost Open Re-architect Retire Develop Acquire

Target Environment

IndependentLegacy

Application

WrappedLegacy

TransactionsServices

COTSApplication


Application Rearchitecting - Services

Preparation

Existing Systems using proprietary delivery

technology with single integrated database

Business process embedded in existing application.

Constrains process and implementation flexibility

Stage 2

Selective Componentization

Increased implementation flexibility whilst maintaining

stability of services

Stage 1

Surround existing systems with Service Architecture

Business Driven Service Architecture enabling more

flexible use of existing assets in new business

processes

Internal dependencies still remain

Stage 3

Optimally componentized implementation

Opportunities for resource virtualization

Dependencies all via Services


Approach Determines Type/Level of Activity

Implementation Architecture

Implementation

Deployment ArchitectureTechnology Architecture

Service Specification Architecture


<<component>>

<<component>>Internal

Architecture

<<component>>If, then, else


<<database>>

<<message>>

<<module>>If, then, else

<<module>>

<<module>>

Logi

cal

Phy

sica

l

<<Application>>

<<Application>>

Application Architecture

<<database>>

<<database>>table, column

AS-IS Business Model(including Capabilities)

TO-BE Business Model

Replace (Build)Replace (Buy)

RationalizeRe-skin

Re-processService Facade

Service EnableRecode

Restructure

Arc

hite

ctur

e R

ecov

ery

Architecture-based D

evelopment

Re-platformRe-host

New Deployment Architecture


Core/Context Influences Modernization Approach

Core Activities --engage your resources

Context Activities --disengage resources

Mission CriticalActivities --Primary purpose of the organization

SupportingActivities --not the main lineof business

DIFFERENTIATE STANDARDIZE

OUTSOURCEEXPERIMENT

ApproachReplace (Build)

Service FacadeRationalize

Replace (Buy)

Re-skin

Offload

e.g. experiment with social

networks, mobile devices

e.g. to enable virtualization and

cloud

(based on concepts developed by Geoffrey Moore)


What is Service Oriented Application Modernization?

Micro –

Single

Application

(Push)

Data

Virtualization

Security

Management

Model

Driven

Development

Business

Process

Mgt

Business

Rules

Mgt

SOA

Macro –

Multiple

Apps

(Pull)

Enterprise

Architecture

Portfolio

Mgt

Transition

Engineering

Investment

Planning

(CPIC)


Contextual Framework Relationships

Enterprise Architecture

e.g. FEAF

Legacy TransformationApproach

Architecture

Function

Code

Deploy

Service Oriented Architecture

Provides the TO-BE

Provides the overall context

Provides the overall context

AS-IS TO-BE

Transition

mapping

Business Requirements


Obtain Executive

Buy-In andSupport

Establish Management

Structureand Control

Define anArchitectureProcess

and Approach

DevelopBaseline

EnterpriseArchitecture

DevelopTarget


Develop theSequencing Plan

Usethe


Maintain theEnterprise

Architecture

Obtain Executive

Buy-In andSupport

Establish Management

Structureand Control

Define anArchitectureProcess

and Approach

DevelopBaseline


DevelopTarget


Develop theSequencing Plan

Usethe


Maintain theEnterprise

Architecture


Service Architecture

Business Model(Capability

Dependencies)


Model


Model

ServiceDeploymentEnvironment

Implemented by

Supported by

Operates within

Service Architecture Views

Business requirements view

External (consumer’s) view

Internal (developer’s) view

Runtime platform

*

*

1

*

*

*

Legacy Environment

LegacyApplications *

*


Deriving the Service Architecture Views

Implementation View

Process Services(orchestration layer)

ProductLifecycleServices

Core Business Services(the backbone layer)

Products Service

Sales Process Services

Solution Layer(UI, dialog

management)

« component »Products Life

Cycle Component

« component »Sales ProcessComponent

« aggregator »Products

Component

Customers Service

OrdersService

«component»Sales

Component

Underlying Services(not so easy to use)

Products InManufacturing Sys

Products InInventory Sys

«legacy»Manufacturing

System

«wrapper»ProductsAPI2

Wrapper«legacy»InventorySystem

Utility Services(high reuse layer)

AddressFormatting Service

«external»

Undefined

indicates an embedded data store

OrderingApplication

BillingApplication

Product LifeCycle System

Service Specification View

315

Process Services(orchestration layer)

ProductLifecycleServices

Core Business Services(“backbone” layer)

Customers Service

OrdersService

Products Service

Sales Process Services

Solution Layer(UI, dialog

management)

Utility Services(high reuse layer)Address Formatting

Service

Underlying Services(not so easy to use)

Products inManufacturing

SystemProducts in

Inventory System

OrderingApplication

BillingApplication

Product LifeCycle System

Capability Dependency View

Inventory

Management

Manufacturing

Accounting

PurchasingReceiving

Shipping

Business Process View

Sta rtEvent1 Meets standards for e nli stmen t, app ointme nt or i nducti on?

enli st wi th MEPS?

appl icant not qual ifi ed for enl istment/accession

ap pli cant no t en li sted wi th MEPS

shipping requeste d?

enli stee

q uali fi ed not enl isted

shipper

«Bus iness Process»1 applicant qualification

«Bus iness Process»1 applicant qualification

Appl ica nt choo ses notto enl ist

«BusinessProcess»2 enlistment

«BusinessProcess»2 enlistment

Appl ica nt choo ses notto enl ist

«Bus inessProce...3 shipping

«Bus inessProce...3 shipping

no

yes

no

yes

no, waiver granted

yes

Deployment View

338

a: Client PC

Internet Explorer

SOAP over HTTP

an: ExternalHost

Address Formatting Service

SOAP over JMS

HTTP

RMI

: Application Server

: EJB Container

: Oracle DBMS

JDBC

Sales ComponentProducts

Component

InventoryDBSales DB

: Mainframe

: TP Monitor

: DB2 DBMS

Manufacturing

System

ManufacturingDB

: Orchestration Server

: BPEL Engine

ProductsLifeCycle Compt

SalesProcessComponent

a: Web Server{opSys = WindowsNT}{webSvr = Apache}{nrDeployed = 4}

: Servlet EngineOrdering and Billing AppsProduct LC System

: SOAP EngineProducts LC ServiceSales Process

ServiceProducts ServiceOrders ServiceCustomers ServiceProductsFromManufProductsFromInvnty

Protocol Adapter

Inventory System

Technology View

20

UI

Security

Provision/Host

ABC

Service Consumer

Messaging

Transport

Messaging

Mediation Transform Route

BCA

Encrypt Authe nticate

DecryptSign

Fire wall

Permissions

)@d F9&

ServiceOrche stration )@d F9&

Manageme nt

SLA

Service

Provider

Registry/

Directory

Process Management

Descr-

iption

Governance

Policy

Req’d capabilities defined in

Realized by Implemented by Deployed to

Business Drivers• Vision/Mission• Strategies

• Objective1 • Objective2• Objective3

Business Type View

«Business Type»Region

«Business Type»Facil ity

+ name: string

«Business Type»Armed Serv ice

«Business Type»Reception/Training

Center

«Business Type»Duty Station

«Business Type»Party

+ name

«Business Type»Role

«Business Type»Organization

«Business Type»Person

+ gender: Gender+ dob: date+ ssn: string+ uniqueIdentif ier+ phone numbers+ fi rstName: string+ middleName: stri ng+ lastName: string+ maritalStatus: MaritalStatus+ pri or m il itary servi ce+ pri vil eges+ preferences+ raci alCategory: RacialCategory+ ethnicCategory: Ethni cCategory+ dependents: int+ rel igiousPreference: stri ng+ educati on: Education

«Business Type»Location

+ street: stri ng+ city: string+ county: stri ng+ zipCode: string+ name

Parties and Facilities

«enumeration»Gender

male female other

«enumerati on»MaritalStatus

marri ed singl e divorced

«enumerati on»RacialCategory

ameri canIndianOrAlaskaNati ve asi an bl ackOrAfri canAmerican nativeHawaii anOrOtherPacif icIsl ander white decl ineToRespond

«enumeration»EthnicCategory

decl ineToRespond hi spanicOrLati no nonHispanicOrLati no

«Business Type»ForeignLanguageSkill

+ language: stri ng+ fi rst: boolean

*

resi desat

*

1plays

*

i ncludes

1

have

*

*i s locatedat

1

*

belongs to

1

*

+placeOfBi rth

1

1

hasLanguage

*

Service Registry

Legacy Discovery

ServiceRegistry/

Repository


Capability Dependencies

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

Hire & RetainQuality Staff

PositionManagementManage

Careers

ManageCompensation

Provide Training &

Educat.

Recruiting

Provide Benefits

ProvideHealthcare

Provide IncomeSecurity Provide

ProfessionalDevelopment


Layered Service (Specification) Architecture

Solution Model

Domain Model

Current Systems Model

Process Driven

Data Centric

Bottom Up

Order FulfillmentService

ProductsService

Orders Service

Process Services

Core Business Services

Underlying Services

Utility Services

Address Reformatting Service

AccountsReceivable API

Capability Model

Function Driven

Logistics Service

Capability Services

Reuse Model

Design Driven

Units of Measure



Automation Unit:

�Software Component or

�Wrapped Legacy Transaction


Deployment Architecture

a: Client PC

Internet Explorer

SOAP over HTTP

an: ExternalHost

Address Formatting Service

SOAP over JMS

HTTP

RMI

Application Server

EJB Container

Oracle DBMS

JDBC

Sales ComponentProducts

Component

InventoryDBSales DB

Mainframe

TP Monitor

DB2 DBMS

Manufacturing System

ManufacturingDB

Orchestration Server

BPEL Engine

ProductsLifeCycle Compt

SalesProcessComponent

a: Web Server{opSys = WindowsNT}{webSvr = Apache}{nrDeployed = 4}

Servlet EngineOrdering and Billing AppsProduct LC System

SOAP EngineProducts LC ServiceSales Process

ServiceProducts ServiceOrders ServiceCustomers ServiceProductsFromManufProductsFromInvnty

Protocol Adapter

Inventory System

Shows where Automation Units are installed


Legacy Transition Planning

Service Architecture

Capability Analysis

ServicePortfolioPlanning

ApplicationModernization

Planning

Legacy/SourceAnalysis

Release Planning

ReleaseArchitecture &

Scheduling

ImplementationManagement

Data Management

Project Planning

Detailed ReleasePlanning

Development &

Configuration

Release Deployment

Business ArchitectureDefine Future

Operating Concept

Performance Management

Define Business Improvement Increments

CBDI-SAE Transition Engineering Process


Release 1(t + 3 mo)

Release 2(t + 6 mo)

S1 S1 S3

C1 C1 C3

LT1

P1/ MF

SC3LT1

P1/ MF

P2/ Lin

S1

C1

SC1

P2/ Lin

S4

C4

SC4

P4/ Win

Release 3(t + 9 mo)

Release 4(t + 12 mo)

CapabilitiesView

Service SpecificationView

Automation Units (Legacy Trx / SW Components)

Deployment Platform

Transition Engineering:Release Planning Architecture

S2

LT2

C2

S2

LT2

C2

S1 S3

C1 C3

SC3SC1

P2/ Lin

S2a

SC2

C2a

S3

C3

SC3

S2a

Sc2

C2a


Evolutionary Implementation of Capabilities

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

Manage Retention � � � � � �Green = Ready for 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 � � � � � �

Releases (Transition States)

Specialists in Service Oriented Application Modernization

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

Dave [email protected]

Thank you.

We need to deliver the new system fast.

Why do we need it fast?

Things have changed.

Why can’t we adapt what we have?

They’re not adaptable.

Why don’t we make things adaptable?

Because we don’t have time.

Why don’t we have time?

CBDI Journal 1997

Service Oriented Approach to Application Modernization sept 2010

Technology

Transcript of Service Oriented Approach to Application Modernization sept 2010