W W W. I T K O. C O M 1 © 2007, iTKO, Inc. | PROPRIETARY / CONFIDENTIAL W W W. I T K O. C O M 1 © 2007, iTKO, Inc. | PROPRIETARY / CONFIDENTIAL Delivering SOA Quality Automation Framework 01 May 2008 Steve Thomas, VP iTKO Government

W W W. I T K O. C O M 2 © 2007, iTKO, Inc. | All rights reserved. U. S. Customs (New E-Gov Border Control Initiative) DRM PRM BRM SRM TRM Acceptance of Cargo StatesIRSFDAJusticeUSDA Look up the license plate of the vehicle. Are there any warrants for the driver? Check to see if the import company Owes taxes, fines, or penalties. If the food properly packaged? How much does a typical truckload of bananas normally weigh? Does the driver fit the profile of any Wanted suspects. What country, what origin? Does not let “x” animals into the country. Know issues and risks. Agency EA Service Component E-Gov Architecture Guidance Federal Enterprise Architecture Conceptual FEA Example – Cross Agency

W W W. I T K O. C O M 3 © 2007, iTKO, Inc. | All rights reserved. For vertical hierarchies within organizations, there is an expected level of shared trust.  Higher level can expect the underlying development team to “build to order” IT functionality for it  Service development team can expect the consumer to leverage the service according to understood business requirements Group Division Organizational Unit Group Division Organizational Unit Group Division Organizational Unit Teams Division Vertical Governance = Piece of Cake

W W W. I T K O. C O M 4 © 2007, iTKO, Inc. | All rights reserved. Across different business units, coordinating the use of a service is difficult.  Service Providers want to establish reuse of services, but they are answerable to different stakeholders  Upstream Consumers of services do not provide clear enough Use Cases of how they will employ services  Therefore teams build redundant functionality Group Division Division 1 Group Division Division 3 Group Division Teams Division 2 Division Group Division Horizontal Service Reuse = Anarchy

W W W. I T K O. C O M 5 © 2007, iTKO, Inc. | All rights reserved. Web Services SOAP Objects.NET Ordering Service CRM Web App States SI provided capabilities IRSFDA USDA Justice RMI Objects Messaging Service Legacy Data Legacy App BI Tools Business Rules File System ESB Web Interface Content Database Data Warehouse Legacy App Financials Mainframe Your App Workflow Services hide complexity

W W W. I T K O. C O M 6 © 2007, iTKO, Inc. | All rights reserved. SOA mandates Continuous improvement/continuous validation: Database Create components Create UI Acceptance Test Deploy App Unit testIntegration New service Database Create UI Database Create UI New service Service changed New service Service retired

W W W. I T K O. C O M 7 © 2007, iTKO, Inc. | All rights reserved. W W W. I T K O. C O M © 2008, Interactive TKO, Inc. | PROPRIETARY / CONFIDENTIAL Increasing rate of change in applications & workflows Increasing Complexity of IT environment High Complexity High Change Low Complexity Low Change Need for Business Agility is Driving Risk in IT Client/server apps Mainframe / Packaged SOA & Composite Apps Web applications Threshold for Failure Complexity x Change = Risk of Failure

W W W. I T K O. C O M 8 © 2007, iTKO, Inc. | All rights reserved. Increasing Number of Services and Components Implemented Risk of Failure Keys to Controlling this Risk: Governance Continuous Validation Virtualization Keys to Controlling this Risk: Governance Continuous Validation Virtualization SOA and integration side effects

W W W. I T K O. C O M 9 © 2007, iTKO, Inc. | All rights reserved. It’s all about Trust Governance needs to provide visibility and enforcement of policy Visibility and enforcement allow service consumers to develop trust of services Trust leads to more frequent reuse and better utility of services Better utility and reuse, along with interoperability, are the base elements that allow services to be loosely coupled Loosely coupled services lead to better Business Agility

W W W. I T K O. C O M 10 © 2007, iTKO, Inc. | All rights reserved. Governance solutions must provide trust & transparency Key function is SOA Policy definition, modeling, and enforcement Three kinds of policy can be automated Structural -- compliance to standards -- ‘the pin-outs’ Behavioral -- honoring functional expectations Performance -- honoring performance / reliability expectations Critical to establish an environment that provides this, often federated across the organization (s) Top level SOA COE built from participants Clearly defined Publish and Consume Processes Visibility to clearly identify root causes via reporting, alerting, dashboards We call this SOA Testing SOA Governance Governance/validation instills trust

W W W. I T K O. C O M 11 © 2007, iTKO, Inc. | All rights reserved. Complete Testing Every heterogeneous layer of architecture Test UI verify in system of record Reuse functional test for performance testing Collaborative Testing Test early Not just dev, analysts and QA should verify processes Continuously Test Regress on existing functionality Add testing of new services to existing testing workflows Complete single component  all technologies Continuous Phased tests  constant testing Collaborative Dev/QA test silos  everyone tests, every phase “Three C’s” of Automated SOA Governance

W W W. I T K O. C O M 12 © 2007, iTKO, Inc. | All rights reserved. Presentation Layer Service/Process Layer Integration Layer Data/ Applications web UI Swing UI web 2.0 UI CORBAJ2EEWeb ServiceBPM ESB Java Web Service RMICustomBatch Feeds LegacyCustom Apps Database File SystemPackaged Apps Complete SOA Test Map - Simplified

W W W. I T K O. C O M 13 © 2007, iTKO, Inc. | All rights reserved. SOA and Web Services (or JBOWS) OASIS - SOA does not equal Web Services Web services can be used to implement SOA (SOA is NOT “JBOWS”) Web Services protocols do not ensure the overall system is SOA CPMO’s may start by testing at web services level But only 10-20% of SOA tests produced are web services tests! Web Services testing is to SOA what UI Testing used to be to traditional Application Testing SS SOA

W W W. I T K O. C O M 14 © 2007, iTKO, Inc. | All rights reserved. Web front-end Swing App Processing Web App CORBA App ESB Process App A Process App B Additional Apps Now & Future Database App Server EJB, WS, POJO Problem may not appear for end users Problems will not appear in XML from SOAP Error in message layer Development tested…… Failed in Operation!

W W W. I T K O. C O M 15 © 2007, iTKO, Inc. | All rights reserved. Service-Oriented Virtualization Definition: Service-Oriented Virtualization (SOV) is the IT strategy of simulating the real-world behavior of software assets that comprise an SOA application, thereby decoupling development and testing teams from dependency on deployed Services and their underlying implementation layers.

W W W. I T K O. C O M 16 © 2007, iTKO, Inc. | All rights reserved. SOA Testing without SOV LISA Testing LISA Testing UDDI registry SOAP request Service1 SAP Database Mainframe Application under test JDBC CICS

W W W. I T K O. C O M 17 © 2007, iTKO, Inc. | All rights reserved. Contention for Shared Resources Live services are not always available for dev & testing Administrators control or prohibit access to prevent overload and downtime Multiple dev & test teams create scheduling conflicts for access to key systems Traditional Dev & QA = Centralized Control, Longer Cycles Dev team Mainframe Client test team SOA Development = Constrained by Access Dev & Test teams Mainframe IT Ops control Live or Synthetic Transactions

W W W. I T K O. C O M 18 © 2007, iTKO, Inc. | All rights reserved. Some improvement, but dependencies on finished services still limit agility downtime Dependencies in Development Cycles Team1 Team2 Integration Team/QA3 Completed Tested Delivered Functionality PROJECT TEAM Define Conventional “Waterfall” development cycle… Attempt to break up SOA development to distributed teams Delivered Functionality DevelopTestIntegrateDeploy Dependency

W W W. I T K O. C O M 19 © 2007, iTKO, Inc. | All rights reserved. Virtual Service Environment Virtual Services Environment Testing UDDI registry Service1 SAP Database Mainframe Application under test JDBC CICS VS1’DB1’ MF1’ SOAP request

W W W. I T K O. C O M 20 © 2007, iTKO, Inc. | All rights reserved. W W W. I T K O. C O M © 2008, Interactive TKO, Inc. | PROPRIETARY / CONFIDENTIAL Cost Savings with VSE Conventional Environment Hardware Software Support & Maintenance Hardware Virtualization Service Oriented Virtualization w/ VSE Hardware Software Support & Maintenance Hardware Software Support & Maintenance

W W W. I T K O. C O M 21 © 2007, iTKO, Inc. | All rights reserved. Production Staging Continuous SOA Governance Platform Test Bed Dev Build Test Bed Dev Build ProductComponent QA/QE Production Pre-production Component/ Service Teams Development ProductComponent Continuous Validation Continuous Regression Testing Continuous Integration = Continuous Testing

W W W. I T K O. C O M 22 © 2007, iTKO, Inc. | All rights reserved. Framework for Automated Governance Enforcement Testing Service Oriented Virtualization Continuous Validation

W W W. I T K O. C O M 23 © 2007, iTKO, Inc. | All rights reserved. W W W. I T K O. C O M © 2008, Interactive TKO, Inc. | PROPRIETARY / CONFIDENTIAL Thank you for your interest Grab a white paper!: “Service-Oriented Virtualization (SOV): Breaking the Barriers of Dependency on Physical Infrastructures” For more info on LISA’s SOA Testing, Validation & Virtualization capabilities: URL: Request an evaluation Blog: