Aligning Existing IT Architecture with SOA A Phased

Aligning Existing IT Architecture with SOA: ------ A Phased Transition Strategy to MDA SOA William M. Ulrich Tactical Strategy Group, Inc. tsginc@cruzio. com www. systemtransformation. com Copyright © Tactical Strategy Group, Inc. 2006

Overview of Session l Why existing architectures must be transformed to deliver on SOA promise l Transition strategy definition l Functional decomposition & gap analysis l Data definition rationalization, target mapping & redesign l Business l Phased 2 logic extraction, mapping & reuse deactivation of existing architecture Copyright © Tactical Strategy Group, Inc. 2006

State of Data & Application Architectures l Implementation logic coupled with business logic l Redundant, inconsistent & fragmented data & functional definitions l Systems are not aligned around servicesdriven focus l Poorly aligned systems typically caused by poorly aligned data 3 Copyright © Tactical Strategy Group, Inc. 2006

Existing Architectures: Segregated into Stovepipes with Significant Cross-Functional Redundancy Existing Organizational Governance Structures Existing Business Processes Existing Data & System Architectures 4 Copyright © Tactical Strategy Group, Inc. 2006

Existing Architectures are Not Service-Based l Numerous systems run in batch mode l Online modules tend to be multi-functional l Logic & data has highly intertwined dependencies across stovepipe environments l Redundant data & functionality is rampant l IT cannot just wrap an online transaction and call it a service 5 Copyright © Tactical Strategy Group, Inc. 2006

Application Architecture: A Slave to Data Architecture Persistent data is fragmented, redundant & misaligned l Data defined inconsistently, redundantly l Data contained in archaic, ill-defined structures l Applications are intertwined with and basically slaves to data architecture l Services architecture must be built on reliable data foundation l 6 Copyright © Tactical Strategy Group, Inc. 2006

Sample Cross-Section of Existing IT Architecture VSAM User Spreadsheets Procurement Tracking Payments Order Processing DB 2 Sales A/R Agency Billing Agency DB 2 Billing System Special Order Processing VSAM Tracking Accounts Receivable (A/R) IMS Distribution Agency VSAM Standard Inventory Specialty Items VSAM Payments DB 2 IMS Proposal Redundant functions & data, convoluted architecture not conducive to SOA 7 Copyright © Tactical Strategy Group, Inc. 2006

Defining End-State Architecture Relies on Data & Functional Views Data architecture designed around market & business-driven requirements Order Data Common Order Modules Submodules Customer Data Common Customer Mgmt. Modules Submodules Inventory Data Common Inventory Mgmt. Modules Submodules Common Distribution Modules Submodules Applications decompose into single function modules (i. e. services) 8 Copyright © Tactical Strategy Group, Inc. 2006

Existing Systems Transformation Strategy is Target Dependent l Code-based target SOA: Retains & reuses business logic in code-based implementations l Relies on source code refactoring & modularization l l Model driven target SOA: Requires business rule extraction, transformation & reuse in model driven target l Limited refactoring supports phased deactivation l l 9 This discussion focuses on model driven SOA target Copyright © Tactical Strategy Group, Inc. 2006

Transformation Roadmap to MDA SOA l Establish target SOA framework l 10 (e. g. MDA, code-based, rules engines, etc. ) l Establish transformation process & tool support l Establish scope & initial transition strategy l Decompose current architecture l Use current-to-target mapping to refine transition strategy l Further decompose existing systems data and application functionality l Apply refactoring options to support phased legacy deactivation Copyright © Tactical Strategy Group, Inc. 2006

Setting SOA Transition Project Scope l Broad-based approach: l Requires cross-functional assessment l Examines multiple interrelated applications l Narrow approach: l Bypasses cross-functional mapping & decomposition l May ignore redundant functionality across stovepipe environments l Scope is based on breadth of desired functionality to be reused 11 Copyright © Tactical Strategy Group, Inc. 2006

Broad-Based Assessment – Enterprise Level Functional GAP Analysis Current Applications Current Functions Target Functions Application A 5 FUNCTION 1 FUNCTION A Application B 4 FUNCTION 2 Application B 1 FUNCTION 3 FUNCTION C FUNCTION 4 FUNCTION D FUNCTION 5 FUNCTION E User System X 12 No Map FUNCTION B Copyright © Tactical Strategy Group, Inc. 2006

Broad-Based Data Architecture Analysis: Existing-Data-to-Business-Data Mapping Target Data Subject Areas & Entities HR Data Order Processing Data Inventory Data Customer Management Data Supply Chain Management Data Existing system-to-target data mapping highlights redundancies, inconsistencies and fragmentation within current data architecture. Copyright © Tactical Strategy Group, Inc. 2006 13

Refine Transition Plan Based on Broad. Based Assessment Findings Existing applications & data definitions Produce packing list Ship order Individual Project Scope • Extract business rules & data definitions • Rationalize/consolidate data & logic as needed • Migrate/merge extracted logic & data definitions into applicable models • Selectively deactivate legacy functionality Drop ship from remote warehouse Shipping Clerk Insured Employee Object From object data model Register Claim Trigger Employee makes a claim Decrement FGI Trigger Daily claim review process Approve Claim Precondition Register claim Source: Martin/Odell Sample models Individual projects are established to capture, reconcile, migrate & deploy functionality within model driven, services oriented architecture 14 Copyright © Tactical Strategy Group, Inc. 2006

Target Data Architecture Mapping CURRENT SYSTEM TARGET SYSTEM Interviews Legacy Data Records & Elements Current System Models Existing Documentation 15 Interviews Identify Unique & Redundant Entities Retained by Target Mapping Top-Down Analysis Entities by System Entities Not Mapped Current-to-target data mapping extracts bottom-up data usage to create or validate target data models. Copyright © Tactical Strategy Group, Inc. 2006

Bottom-up Data Definition Analysis, Rationalization, Redesign & Reuse Top-down, business data model • Data grouping analysis system-wide record, segment & table definitions • Analysts selectively review results to augment top-down data models Yearly Pay Gross Pay Net Pay Selected Data Groups 16 Copyright © Tactical Strategy Group, Inc. 2006

Targeted Functional GAP Analysis Current Programs Current Functions Target Functions PROGRAM 1 FUNCTION A PROGRAM 2 FUNCTION 2 PROGRAM 3 FUNCTION C FUNCTION 4 FUNCTION D FUNCTION 5 FUNCTION E MANUAL No Map FUNCTION B Program-to-function mapping helps determine level of existing functional reuse within target architecture. 17 Copyright © Tactical Strategy Group, Inc. 2006

Business Rule Derivation: Multi-Phased Discipline 18 l Logic Capture: Process of capturing logic blocks that serve as business rule candidates l Logic Filtering: Eliminating non-business logic l Logic Packaging: Putting logic into a context that makes sense to business and design analysts l Rule Analysis: Categorizing, leveraging and reusing captured business rules Copyright © Tactical Strategy Group, Inc. 2006

Extracted, Categorized & Packaged Business Rule Candidate System / Application Name: Accounting / Accounts Receivable Program Name: PGREG 117 Paragraph Name: REGION-VALIDATION Data Element Search Argument: Element = REGION-CODE Logic: IF REGION-CODE NOT = ZERO AND ACCOUNTING-CLEARANCE NOT = ZERO ADD WS-VALIDATION-AMT (WRK-SUB) TO RGN-TOTAL (IE-REGION). 19 Copyright © Tactical Strategy Group, Inc. 2006

Phased Deactivation Strategy l Modularization & deactivation of existing logic, modules and/or sub-systems l Phased reconciliation & deactivation of redundant functionality l May involve parallel processing during transition 20 Copyright © Tactical Strategy Group, Inc. 2006

In Summary… SOA is goes beyond basic wrapping options l Strategy driven by target architecture paradigm & requirements l Functional mapping & reuse occurs at several levels that include: l Enterprise level vs. more subset of applications l Data vs. application functionality l Functional decomposition vs. business rule capture l l Transition strategy should include: Redundancy identification & consolidation l Phased deactivation of legacy artifacts l 21 Copyright © Tactical Strategy Group, Inc. 2006

Aligning Existing IT Architecture with SOA: ------ A Phased Transition Strategy to MDA SOA William M. Ulrich Tactical Strategy Group, Inc. tsginc@cruzio. com www. systemtransformation. com Copyright © Tactical Strategy Group, Inc. 2006