Metodologia Soa En Ingles

SOA Test Methodology
Abstract
Service-Oriented Architecture (SOA) promises significant benefits to today's organizations. Abstract Successfully delivering SOA benefits, especially Business Agility and Component Reuse, will be dependant on the Test Approach that your organization adopts to implement your SOA. This white paper will provide a comprehensive guidance on best practices for testingSOA Solutions. This document includes a review of the following topics that will need to be addressed to ensure a successful SOA implementation:
l more testing effort will be required at the service level and not at the system level Why

l Why

Security testing moves from an end of project activity to one that spans the entire project life cycle

l A SOA Test team will not only require adetailed technical understanding of your SOA, but they

must be experts of domains within your business
l Test Approach demands an appropriate tool strategy SOA

www.thbs.com/soa

Table of Contents
1 INTRODUCTION 1.1 SERVICE-ORIENTED ARCHITECTURE OVERVIEW 1.1.1 What is SOA 1.1.2 SOA Benefits & Implementation Principles 1.1.3 Key Terms of Service-Oriented Architecture 1.1.4 Test Model 1.1.5SOA Governance SOA TEST METHODOLOGY 2.1 TRADITIONAL TEST APPROACH 2.1.1 Revised Test Approach for SOA 2.2 SOA TEST APPROACH 2.2.1 Purpose 2.2.2 How Do You Test SOA Architecture? 2.2.3 Governance Testing 2.2.4 Service-component-level Testing 2.2.5 Service-level Testing 2.2.6 Integration-level Testing 2.2.7 Process/Orchestration-level Testing 2.2.8 System-level Testing 2.2.9 Security Testing 2.3DELIVERABLES BASED ON DISCIPLINES AND KEY DOCUMENTATION 2.3.1 Test Phases and Test Types 2.3.2 Functional Testing 2.3.3 Performance 2.3.4 Security 2.3.5 Interoperability 2.3.6 Backward Compatibility 2.3.7 Compliance REGRESSION STRATEGY SECURITY TESTING USER ACCEPTANCE TESTING RISK BASED TESTING OFFSHORE ONSITE MODEL TEST TOOLS AND USAGE 8.1 COMMERCIAL PRODUCTS 8.1.1 Green Hat GH Tester 8.1.2 Mercury8.1.3 Parasoft SOAtest 8.1.4 AdventNet QEngine 8.1.5 Borland SilkPerfomer SOA edition 8.1.6 LISA WS – Testing 8.2 OPEN SOURCE PRODUCTS 8.2.1 SOAP UI 8.2.2 PushToTest TESTMAKER CONCLUSION 3 4 4 4 5 6 7 8 8 9 9 9 10 11 11 12 12 12 13 13 13 13 14 14 14 14 15 15 16 16 17 17 18 19 19 19 19 19 19 20 20 20 20 20 20
2 2007 Torry Harris Business Solutions, All Rights Reserved

2

3 4 5 6 7 8

9

1.Introduction
'To SOA or not to SOA' is not the question anymore. It is 'When to SOA?' With the maturity in SOA Implementations and realization of the associated benefits and challenges, increasingly Enterprises are including SOA Adoption in their Road Map. Service-Oriented Architecture, or SOA, enables IT departments to make the transition from an application-centric view of the world to aprocess-centric view. Today, IT departments have the freedom to combine business services from multiple applications to deliver true end-to-end support for business processes. And, because the integration mechanism of SOA (usually Web Services) enables loosely coupled integration, IT departments can upgrade or change applications without impacting other applications. Though SOA is being increasinglyimplemented both as green field (top down) and legacy modernization (bottom up), there is a clear lack of testing methodologies designed specifically for SOA applications. New approaches and methodologies are necessary to verify and validate applications based on SOA concepts. Why is SOA testing different? The answer has many dimensions, but the bottom line is agility and flexibility. Yes, whatmakes SOA a very attractive, business friendly IT paradigm is the same reason why a different testing approach is required in SOA Implementations. When it comes to testing SOA applications, one has to look beyond functionality and performance (load) testing. SOA testing requires testing of interfaces and services that might bring together diverse systems and platforms, along with other performance...