Upload
shanon-taylor
View
213
Download
0
Embed Size (px)
Citation preview
© 2006-2007Lockheed Martin Corporation, All Rights Reserved
INFORMATION SYSTEMS & GLOBAL SERVICES
11
Applying Predictive Metrics for Service Oriented Architecture (SOA)
Applying Predictive Metrics for Service Oriented Architecture (SOA)
Phil Magrogan CTO, ITS-ESE Program
Lockheed Martin
Fourth Service-Oriented Architecture for E-Government ConferenceOctober 1-2, 2007
Carlos C. Amaro, Ph.D.IS&GS SOA Initiative
Lockheed Martin
Min-Gu LeeTechnology Architect
Lockheed Martin
INFORMATION SYSTEMS & GLOBAL SERVICES
22
ValuesValues
Question1. What did you find useful and not useful in the metrics? Useful to recognize the need for:
• SOA maturity model and checklist (focus on technology but including SOA Governance for organization and management)
• To provide guidance for improving an organization's SOA ability• SOA technology roadmap (especially for the post pilot SOA
project)• To guide development and support for the latest technologies
applicable to SOA
Useful • Based on inexpensive and none time consuming field data • To see the current status/health
• Concise form with color coding (Red/Yellow/Green)
Not useful format to share with other stakeholders
INFORMATION SYSTEMS & GLOBAL SERVICES
33
SOA Maturity Model Checklist: SOA Maturity Model Checklist: Improving An Organization's SOA AbilityImproving An Organization's SOA Ability
Maturity Levels Maturity Checklist *
1. Ad hoc Services
Well-defined and documented Services WSDL for all Web services SOAP or other standard protocols
2. Architected Services
SOA Service Center (Architecture) SOA Architecture SOA Maturity Model SOA Roadmap UDDI Runtime Management Enterprise Service Bus Enterprise Infrastructural Services Metrics for re-use of Services
3. A. Business ServicesB. Information Services
SOA Service Center (Methodology) SOA Governance Model Enterprise Business Services Enterprise Information Services Business Process Work-flow WS-BPEL
4. Measured Business Services
SOA Service Center (Scorecard) Business Process Management Business Activity Monitoring Event-driven Services
5. Optimized Business Services Business Rules dynamically change based on Event-driven Services Services are dynamically provisioned
* This checklist is presented on US EPA Service Oriented Architecture Service Center Plan, Version 1.1, 40-BP-PLN-0043, September 27, 2006. This checklist is originally based on and derives inspiration from Lockheed Martin SOA Reference Architecture, March 2005. & A New SOA Maturity Model, 2005 published by Sonic Software Corporation, AmberPoint Inc., BearingPoint Inc., Systinet Corporation.
When your answer for the question 4.1c (Effort to
change process Orchestration) is RED, you may need to have a plan to
improve your organization’s SOA maturity level.
INFORMATION SYSTEMS & GLOBAL SERVICES
44
Lockheed Martin’s Lockheed Martin’s Predictive Metrics InitiativesPredictive Metrics Initiatives
SOA-Initiative (SOA-I) SOA-I launched by Information Systems & Global Services (IS&GS) in
2006 to provide integrated, productized, repeatable SOA methodology and expertise to customer programs
Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) interoperability assessment model
A model/framework that defines characteristics for assessing how a set of systems support SCOPE over a network.
Can be used to assess “as-is” or “to-be” Developed by Lockheed Martin in 2005 and is currently evolving into an
industry standard under the Network-Centric Operations Industry Consortium™ (NCOIC).
SCOPE Model SOA Extensions Define extensions to the SCOPE model that describe key SOA-relevant
characteristics SOA Extensions will enable the assessment of current and planned SOA
capabilities and environments
INFORMATION SYSTEMS & GLOBAL SERVICES
55
ImprovementsImprovements
Question 2. What areas, if any, did we miss and how might we address them based on characteristics of the technology being used and product characteristics? Evaluating interface effort is too restrictive
• Effort (0-16 hours) required to use data and services from other organizations participating in the SOA
• It may take more than 16 hours to define an external interface• It may not be possible to segregate data interface design from
other design activity• It does not map well to agile development which may implement
the interface over several iterations
INFORMATION SYSTEMS & GLOBAL SERVICES
66
UsagesUsages
Question 3. How might a Chief Architect or Program manager use them most effectively? Most effective when used in conjunction with a
SOA technology roadmap and maturity model/checklist
INFORMATION SYSTEMS & GLOBAL SERVICES
77
SuggestionsSuggestions
Question4. What changes would you suggest? Educate the reader how to add or remove the
evaluating factor without degrading the value of the metric
Map to • A Software Development Life Cycle (SDLC)• Technology roadmap and maturity model
Provide • A summary with color coding for reporting• More sophisticated metrics for the power user• Background of statistical techniques and their validation
INFORMATION SYSTEMS & GLOBAL SERVICES
88
SOA Technology in Detail (Backup) SOA Technology in Detail (Backup)
UDDI Registry Publishing Runtime discovery
Design Time Repository Metadata and metadata
relationship management Life cycle management Contract management Design-time policy
management
Runtime Management Auto Discovery Service network visualization Runtime policy management Measuring and monitoring Service level management Active management Exception management
Testing and Validation Security ESB
Transformation Routing
Orchestration BPEL