working draft enterprise architecture roadmap for business

Working Draft

Enterprise Architecture Roadmap for Business Transformation

Architecture Roadmap and eGov Artifacts

An ICHnet.org perspective on getting from architectures to implementation reality

John Weiler, [email protected] RepresentativeOctober 15, 2002

ICH Architecture Resource Center

2Working Draft from FEAPMO SAWG

Our mission to advance mechanismsthat assure the successful implementation of enterprise

technical solutions aligned to business drivers

“From Architectures …. to Implementation Reality”


The EA Challenge

making sound COTS decisions based on business drivers

Exert from EDS Business Case Analysis: “The leveraging of our efforts with other parties through the formulation of a non-profit

consortium is the most cost effective and efficient way of achieving the goal of interoperability assurance among heterogeneous systems. This ICH capability will augment our capability and provide us much more information about products, standards, and viable enterprise solution

sets than we could ever realize through our own internal efforts.”


The New IT Solution ParadigmCustom Development gives way to COTS Integration

Y e s t e r d a y

Design, Code, Test

• Focus on COTS Integration & Component Assembly

• Architect, Evaluate, & Integrate• Timeframes are 12-24 weeks!• Interoperability not “knowable” in

advance• Rate of change is high and

accelerating

T o d a y

Model, Validate, Integrate

COTS Paradigm shift dictates

EA driven SDLC process

Softwar

e Co

mpo

nent

s

& O

ff the

She

lf Pr

oduc

ts

• Focus is Software Development

• Code everything to spec• Timeframes 12-24 months• Complexity and rate of

change manageable (CMM)• Technology base Stable• Driven by IDEF, UML,

and antiquated EA methods


CIOs Feel...Overwhelmed by offerings?

Ill-equipped to evaluate?Out paced by market?

Interoperable?Over hyped?

• No body of knowledge from which PM can evaluate competing COTS offerings.

• No common EA language to communicate business need to technology.

• No mechanisms for assessing risks, composability or interoperability of COTS solution

• No clear mapping of business drivers to standards or COTS solution offerings. Gap = Risk!

• Current documentation methods do not result in action oriented solution “blueprints”.

PMs lack the tools to make sound COTS acquisition decisions!


ICH Architecture Assurance: Model Align Validate Integrate

Business Drivers

IT Centric EA Effort and Framework

Enterprise Inclusive EA Effort and Framework with internal Alignment, Metrics, Componentization, Normalization, and Objectivity

“Exerprise” Inclusive EA Effort and Framework with ComprehensiveAlignment, Metrics, Componentization, Normalization, and Objectivity

Cost Savings Incremental Improvement

Incremental Improvement


Operational Service Quality

Supportive Incremental Improvement


Operational Alignment

Supportive Incremental Improvement


Business Alignment

Undetermined Incremental Improvement

Substantial Improvement

Validity Undetermined Internal Validity


Adaptability Undetermined Internal Adaptability


• Architecture Driven• Begin with Business Drivers• Mission Aligned• Imbedded Metric• Interoperable• Normative• Non Prescriptive• Action Oriented• Acquisition Ready• Risk Adverse

ICH Common Criteria


ICH Architecture Alignment

BRMCBAApplication Layer 1

InfrastructureLayer M

BRMSRM Appl Service Components Layer 1

InfrastructureService ComponentsLayer N

BRMBRMBusiness Lines

Sub-functions

Con

trib

uti

on

to F

ulfi

llmen

t

Fun

ctio

nal Tra

ceab

ility


ICH Architecture Collaboratory Linking the IT Value Chain

“... the concept of the Interoperability Clearinghouse is sound and vital. Its developing role as an honest broker of all interoperability technologies, no matter what the source, is especially needed. Such efforts should be supported by any organization that wants to stop putting all of its money into maintaining archaic software and obtuse data formats, and instead start focusing on bottom-line issues of productivity and cost-effective use of information technology.” Assessment by Leading FFRDC, 2000


ICH Architecture Resource Center (ARC)EA Collaboratory for the IT Value chain

Establishment of “building codes” for COTS e-solution frameworks using architecture templates Modeling re-usable solution models by industry; finance, e-gov, mfg, healthcare.... based on implementation successesShared COTS Solutions vetting results reduces redundant researche-Directory of interconnecting products, integration services documents “what works” and “what works with what”Architecture Methods, Mentoring, Training, Research, and IV&V to transform the EA processUnbiased Collaboratory promotes information sharing between standards groups, vendors, integrators and enterprise users. Give a little, get a lot!


Architecture Assurance MethodAligning & vetting the inputs & outputs

Dave Connelly, President and CEO of the Open Applications Group, says, "We are looking forward to the contributions of the Interoperability Clearinghouse as a partner in our efforts to dramatically improve software integration for customers Internet eCommerce and other projects."


COTS Assessment Frameworkcompliance with OMB guidance

Architecture Roles

Validation Points

Respond toBusinessChange

Investment Process /Architecture ProjectAssessment Framework

1

AssessBusiness

Alignment

2

AssessBusiness Case

Proposal

AssessTechnologyCompliance

Target ITApp.Port /

Infra.Initiatives

Aligned per IT Strategy

AlignmentScorecard

(SELECT)

DevelopBusiness

Case

ComplianceAssessment

5

(SELECT)

ProjectInitialization

Assess Waiver/Exception Request

EnterpriseDesign

Patterns

Acceptable Alignment

Acceptable

Compliance

UnacceptableConformance

Unacceptable Alignment

Unacceptable

Compliance

Proposed Concept

Report

TRMStandards

4

EvaluateArchitectureCompliance

IRBReport

Audit Reports

(EVALUATE)Evaluation

Disapproved

3

(CONTROL)• Define• Build• Implement• Operate


ProductMfg.

Integrator

IT Standards

Drivers

Standards ProfileTwo Phase Commit�Relational Constructs�Row Level Locking�Referential Integrity�ODBC Interface�SQL Interface�IDL Interface

Vetted Product Spec- Two Phase Commit�Relational Constructs�Row Level Locking�Referential Integrity�ODBC Interface�SQL Interface�JDBC Interface�Triggers�OLE DB Interface�Multiphase converter

Solution ProfileScale, IndustrySolution SuiteProduct A Product B v6.1Product C v2Platform S

ICH Architecture Assurance Method aligns SDLC viewsBusiness drivers, Standards, COTS Specs & Integration Needs

BRM Biz ProcessInfrastructure NeedsBus. DriversExternal InfluencesPolicyStrategic PlansLegacy IntegrationAs-is EA

Normalized Lexicon�Distributed Org�Mobile Force�non-fixed locations�secure communications�concurrent updates�complex data types�unstructured data�central data collection�Open Systems

Solution Architecture

Stake Holders

ICH AAM


85%

Evidence Sources

Str

en

gth

of

Evid

en

ce

50%

25%

Bi-directional

vendor claim

Functional/conformanc

etesting

Implementation

successes

Integrationtesting

Strength of Evidence = Risk MetricsDue diligence on features/functions reduces risk

Risk75% $ & time


ICH

Confidence

Level

Resources (cost & time)

Trade Studies

Testing Alone

Traditional approach

ICH advantage

High

Low

RiskDelta

Cost/timeDelta

ICH Method: The BenefitSharing results reduces time, cost, and risks


COTS RepositoryCornerstone of Portfolio Mgt

“propagation of intellectual capital that can assist in E-Government transformation” FEAPMO.gov

OFFICE OF THE SECRETARY OF DEFENSE, DEPUTY CIO: "Since the value of the ICH to our programs increases rapidly

through results sharing, we encourage the defense community and IT industry to participate directly in the public service

initiative in terms of sponsorship and lessons learned"


Example: OnLine Documents


Example 2: Technology Area Criteria Selection


Example 2: Technology Area Criteria Management


Example 2: Technology Area Viewing


Shared COTS Research: Eliminating Redundant Study efforts saves $$$$


Validation Process Flows

“As one of the leading advocates of open systems and interoperability, the OMG believes that the Interoperability

Clearinghouse initiative will help users realize the benefits from our combined efforts”. OMG, Bill Hoffman, President


ISV Product Entry WorkflowWorkflow engine validates vendor entries

ProductData Sheet

CompositeFeatures

Add NewFeatures

NewProduct/StandardProfiles

Technology Class Profile

DocumentedFeatures

SelectExistingFeatures

EstablishXML

URL Links

CreateUML

Template

ConformanceTemplates

Work Flow Manager.

StandardsDirectory

ProductDirectory

StandardSpecification

ValidateNew

Features

COTSValidation


Functional Validation Process

VendorStatements

Work Flow Manager.

Stds Conform.Statement

Interop.Statement

FunctionalStatement

Conformance Testing

FunctionalTesting

InteroperabilityTesting

TestingResults

Attach toProductProfile

VendorConcurs

60 DaysPass?

Yes

No

VendorCorrection

No

Yes

UpdateProduct

Directory

Sendto 3rdParties

3rd PartyProduct

StatementSendMessage to Subscribers

InteropValidation


Interoperability Validation ProcessIndustry validates Vendor Interworking Statements

SelectProducts

Tested

Show CurrentProduct

Connections &Functions

Confirm Connections

ExistingLinks

?

Create newConnection &

Component

Vendor Interop.Submissions

Confirm Product

Functions

DetermineLevel of Effort

& Interop.

CreateProduct

C4ISRAttrib.

UpdateIC


Results from the ICH Process: Interoperable Web-Based Solution Architectures

Test Env. (Mercury Intl.)

NT 4.0WS

Application Libs (C, DLL, MFC)

Security Service (PKI X.509)

IDL StubRMI Runtime

Win 32 Subsystem | NT Device Drivers

J2EE Web Services

EJB

Comms (TCP/IP) SSL

IDE Runtime (Javascript, PB, C++, JDK)

Java JITC

Directory Svrs.X.500, or

DNS,DHCP

J2EE /Web Services

Systems Management Server(Patrol)

Certificate Validation

Win 32 Subsystem - NT Device Drivers

Comms (TCP/IP)/ SSL

CDS ServiceBackup

Network Mgt.(Open View)

Apha orPentium-ProNT 4.0Server

Application Client

Systems Server

Alpha,PentiumProNT 4.0Server

Application & System Runtime Modules

Security Service (PKI Certificate)

Directory Svrs.

X.500,DNS, DHCP,LDAP (v1.22)CDS

EJB Server (or CORBA Server)

TP Mntr.(Encina++)

Win 32 Subsystem - NT Device Drivers

Comms (TCP/IP) SSL

Time Servicer

JDBC API Client (Connection Client)

Compilers (Java JITC)

Application Server

or API

EJB Module

RDBMS Server

SQL Proxy Server (Connection Server)

HP, Sun, orIBM Unix

or AlphaNT 40Server Posix Subsystem (Native or NT), Drivers

Comms (TCP/IP) SSL

ebXML Server

Database Server

JDBC Driver OCI/INET XA Lib.(Encina)

RDBMS API (ODBC or JDBC)

ebXML API

HP, Sun, orIBM Unix

or AlphaNT 40Server Posix Subsystem (Native or NT), Drivers

Comms (TCP/IP) SSL

Web Services

WEB Server

ODBC Driver (Intersolve) OCI/INET

RMI/IIOP

MFI/Gateway

Browser, Native GUI


Case StudiesApplied Architectonics

“The ICH repository data and analysis methodologies was very helpful in supporting a quick turn around for [Information Assurance] section of COTS security products. Highly detailed ICH technology domain and product evaluation data comprised over 60% of this urgently needed [architecture] report”. GCPR, Program Manager, Northrop Grumman/PRC


Challenge: develop enterprise architecture for patient record integration

Applied ICH Architecture Immersion Program Developed architecture validation criteria to GCPR Program

Office Developed product selection guidelines for Prime Contractor Applied ICH Architecture Assurance Method

Outcomes Enabled award based on unambiguous design specs Augmented UML/MDA to address legacy and COTS capabilities Ensured viability of chosen technologies

Met HIPPA requirements Met security requirements Provided integration framework for web

infrastructure Assured implementation success

Case Study: World Largest Healthcare Project


Challenge: Select enterprise web infrastructure to integrate stovepipe applications

Applied ICH Solutions Validation Program Performed architecture baseline assessment Provided guidance and selection support for Web-app

server, VPN, portal, last-mile wireless connectivity

Outcomes Validated requirements against marketplace

offerings Improved confidence in technology decisions

Delayed VPN implementation Purchased Web application server, database,

and media products Deployed system without a hitch

Significantly reduced time/cost to implementation

Case Study: World Largest Media Company


Case Study: World Largest Intelligence Agency

Challenge: means of integrating diverse communities via the web

Applied Architecture Validation Program Developed common criteria for emerging portal

market Evaluated selection of Enterprise Portal for pilot

project Developed impact analysis on enterprise architecture Maintained view of evolving marketplace

Outcomes Enhanced and normalized portal selection criteria Identified key features/functional areas for testing Applied commercial best practices for successful

production rollout Improved understanding and alignment of technology to

problem domain


Conclusion: The ICH Method is;

Industry Developed, Government Approved, Business Driven, Standards-based, Collaborative COTS Selection Process ………...on GSA Schedule!

“...to help the 24 Presidential Priority E-Gov Initiatives and Federal Agencies with activities surrounding the technical and solution design of their e-Gov initiatives. ” Mark Forman


www.ICHnet.org703 768 0400

[email protected]

Need Help?

working draft enterprise architecture roadmap for business

Documents

business alignment

architecture methods

ich architecture assurance

architecture templates

cots solution offerings

business need

business drivers mission

architecture assurance