Академический Документы
Профессиональный Документы
Культура Документы
Jeff Simpson
Federal SOA Architect
An opening thought
Charles Darwin
SOA Quality Assurance Testing Problem
SOA is …
SOA is …(seriously)
Reuse
Agility No. These are
emergent attributes or
Efficiency
properties, not the
Loosely-Coupled definition
Sharing
What is SOA?
I’m not sure what this is really it. Nor do I know anyone else who has a
really good answer.
“The Nexus between politics and operations”
Comprised of Policies, Procedures and Metrics
Service Lifecycle
Governance Tools:
UDDI Registry
Metadata Repository
WebServices Management (SOA Software [BlueTitan], AmberPoint, etc.)
Traditional Enterprise Management Systems (Tivoli, HP OpenView, BPM Patrol, etc.)
Governance usually optimized for one of several outcomes:
Reuse – The Cornerstone of Reuse is Communication
Agility
Positive Financial Outcome
Sharing
SOA Governance is just beginning to mature
“Draconian”, “Autocratic”, “Oligarchy” or “Facist” Governance does not work well in large
organizations
Understanding how to govern operations as large as NCOW is unclear
Usual System Testing
Development Environment
Continuous Integration
Unit and Integration Testing
QA Environment
Protected environment
Scale Testing
Hardware identical to Production Environment
Separate network
Production Environment
Same as QA Environment
Handles multiple Security Enclaves (NIPR, SIPR, JWICS)
Issues with Net-Centric SOA Testing
It impossible to perform traditional QA testing a Net-Centric
Environment
Producer Friction
Producer Accreditation and Certification
Producing “Composite” Services
Consumer Friction
Usage friction – adding hurdles to utilizing shared data and services
Vetting consumers in various degrees
Root-case analysis problems with provided composite services
Responsibility of Service Providers
jsimpson@bea.com