Docstoc

soaxactis

Document Sample
soaxactis Powered By Docstoc
					Legacy to SOA: Issues & Solutions
Sy n tem s A
Ap ca pli tio

lic pp A

tio a

nS tem ys B

Application System C

What exactly is in your programs and data?
Alan Kaplan
President / CTO

Xactis Corporation
Supporting HP, Sun, EDS, and other Prime Contractors

Automation Discovery, Validation and Transformation
Merging Business and Technical Knowledge

Legacy to SOA: What information needs discovery?
Step 1 Step 2
Data

Step 3

Application Information
View and baseline all source code that creates the data element of concern.
Business Rule - Technical Definition: Viewing the entire source code segment that sets the value of a variable of concern, showing all inputs, outputs, and related rules. Establish a baseline to understand the important rules and functionality in existing code. Then monitor / test only the changes.

Database Information
View and baseline the metadata by checking all records that contain the data element of concern.
Data rules (metadata) are inferred from analyzing all records containing the variable of concern -- by data profiling and metadata enhancing with data quality assessment and statistics to identify all issues/ corruption for the variable / data field of concern.

Knowledge & Expertise
The written / spoken language business rule is documented with subject matter expertise.
Explaining the “know-how” – rules & business processes behind the variable / data field of concern, merging views for business & finance managers, with the technical documentation for IT.

Legacy to SOA Who in the company needs discovery?
Tools, Methods and Services are provided for creating and sharing a Rules and Metadata Repository – a knowledge base that will be used by:

Management Business analysts Technical analysts Architects (especially for SOA) Programmers Testers Data specialists IT Governors Auditors (Regulatory Compliance)

Legacy to SOA Why discovery?
Business, Finance, IT and Compliance Departments seek legacy understanding. The ROI is immediate and readily apparent when Enterprise Business Rule and Metadata Repositories serve as a baseline to assist:

Legacy Modernizing, Migrating & Re-Architecting into a Web-enabled Services Framework (SOA) Systems Integration (EAI & EII) with very high data quality Improved Business & Compliance Intelligence Business Continuity from reverse-engineering, documenting information only possessed only by Subject Matter Experts (SME’s) Ease of maintenance/use fewer maintainers/ more uptime Increased quality of testing/fewer testers Audit trail of all software and metadata changes

Legacy to SOA: Automation Discovery & Validation Tools
Source Code Analysis Toolset – Parsing the language to be eliminated or transformed Data Profiling for validating rules that are producing useable information – also for Data Quality Assurance and Remediation Metadata statistics analysis “Data Report Card” for data quality assessment, remediation, and enhancing metadata Rules & Metadata Repository, with:

• • •

Management and Business Analyst views Programming rules from source code Data Rules (Metadata) from data profiling

Code transformation tools – FROM the legacy language and TO the languages involved

Legacy to SOA: Source Code Analysis Toolset

A warehouse of data fields, their rules, attributes and relationships.

Legacy to SOA: Data profiling report of issues
56 Data Quality Issues Identified – Field By Field Listing
Id Subject Status Priority Created Owner Owned Assigned to Assigned Due date Publishable?

2

Record in ZoneSupplier not joinable to ZoneSupplierRange

Opened

Low

19/04/2005 3:03:58 PM

Charles Edwards

19/04/2005 3:03:58 PM

Y

3

Barcode field is unique in BarCode table

Opened

Low

22/04/2005 1:05:47 PM

Charles Edwards

22/04/2005 1:05:47 PM

Y

4

UnitOfTrade mostly unique- what do dups represent?

Opened

High

22/04/2005 1:08:31 PM

Sam Banks

22/04/2005 1:08:31 PM

Y

5

Barcode has many different patterns

Opened

Low

22/04/2005 1:12:35 PM

Alicia Smith

22/04/2005 1:12:35 PM

Y

6

AuditUser has "odd" values.

Opened

High

22/04/2005 1:13:24 PM

Sam Banks

22/04/2005 1:13:24 PM

Y

List of all Entities, PK's, Join Jobs and Issues Summary Report This report summarizes all the Entities, Primary Keys, Join-Jobs, as well as a listing of Issues discovered. This gives an idea of the overall work that was done and the content of further detail reports. There is one detailed report for each entity. In them, details associated with the respective entities are presented. A summary of all illustrations is presented in a single report at the end.

Legacy to SOA: Metadata Enhancer to Decide on Solutions to Problems

Analyze all data field issues and enhance the metadata – semi-automated.

Legacy to SOA: Data Report Card
Data quality statistics to review and risk assess

Generates Data Quality statistics showing the percentages of tables and fields for which various types of metadata and rules have been defined. This may indicate data corruption and where additional effort may be required to more completely define the data rules, as indicated here by red shading.

Legacy to SOA: Customer Rules & Metadata - Documented and Compared

Which rule should be analyzed/migrated/rewritten and which rule should be discarded?

Legacy to SOA: Rules & Metadata Repository™ - Processes

Business Analyst / Compliance Views

Legacy to SOA: Rules & Metadata Repository™ - Business Rules

Business Analyst / Compliance Views

Legacy to SOA: Auto Re-Architecting Overview

BEFORE Inflexible / Monolithic Legacy Systems for Mission Critical Operations
(Insufficient documentation restricts implementing competitive changes)

Legacy to SOA: Auto Re-Architecting Overview

BEFORE Inflexible / Monolithic Legacy Systems for Mission Critical Operations
(Insufficient documentation restricts implementing competitive changes)

DURING Business Rule & Process Extracting
Auto Re-Architecting on the Mainframe or in Java / J2EE or C# / .NET

Legacy to SOA: Auto Re-Architecting Overview

BEFORE Inflexible / Monolithic Legacy Systems for Mission Critical Operations
(Insufficient documentation restricts implementing competitive changes)

AFTER SOA Service-Oriented Architecture and Web-Enabled User Functionality

DURING Business Rule & Process Extracting
Auto Re-Architecting on the Mainframe or in Java / J2EE or C# / .NET

Legacy to SOA: The SOA Architecture for Online & Batch Processes

Access Layer Process Layer Service Layer Resource Layer

On the Mainframe or transformed into Java / J2EE or C# / .NET
SOA Architecture for Online Processes
Extracted Rules & Processes are used to Quickly Program the Rules / Workflow Engine
Enterprise Rules / Workflow Engine GUI To Change Workflow, Processes & Rules

Legacy to SOA: Auto Re-Architecting

Online Process A Object

Online Process B Object

Online Process C Object

On the Mainframe or transformed into Java / J2EE or C# / .NET
SOA Architecture for Online Processes
Extracted Rules & Processes are used to Quickly Program the Rules / Workflow Engine
Enterprise Rules / Workflow Engine GUI To Change Workflow, Processes & Rules

Legacy to SOA: Auto Re-Architecting

Online Process A Object
Analyzing Module

Online Process B Object

Online Process C Object
Reporting Module

XML Data File

XML
Transformed Batch Processes become Loosely Coupled Modules invoked by XML files controlled by the Rules / Workflow Engine

XML

Sub-Process Module A

Sub-Process Module B

XML

XML

Example: SOA Architecture for High Performance Batch Processes

Legacy to SOA: Suggested Re-Architecting Process
Source Code Reverse Engineering Data Field Analyst Toolset Rule & Process Documentation Manual Validation Data Migration & Quality Analysis Data Analysis Suite DQ and Data Migration Analyses Rules Repository Library for Business Rules and Data Properties Take Decisions About: 1) What to Clean Up & Re-factor or Transform 2) What to Generate in the Rules Engine 3) What to Rewrite Re-write All Other Functionality Parameter Settings Layer for New Requirements & Customers Re-factoring, etc. Other functionality added Generate Online Processes and Parameter layer Using: Oracle Rules, iLog, Blaze, Pega, etc. Design SOA Implementation Both the Application and Data Architecture & Framework Access, Process, Service and Resource Layers SOA Architectural Implementation Access, Process, Service and Resource Layers For All System Functionality

Transform Some or Most Batch Processes Java & C# Transformation of Loosely Coupled Service Modules i.e. Analyzing, Billing & Reporting

Full Implementation and Integration Access, Process, Service & Resource i.e. Layers for Analyzing, Billing and Reporting

Additional Implementations Separate / Parallel Initiative to be Merged

Legacy to SOA: Contact Information
Xactis Corporation
1 North Brook Drive Short Hills, NJ 07078 www.xactiscorp.com akaplan@xactiscorp.com 973-218-0133 Voice 973-218-0134 Fax


				
DOCUMENT INFO
Shared By:
Categories:
Tags: White, Paper
Stats:
views:22
posted:4/17/2008
language:English
pages:20