70 likes | 142 Views
Predictive Metrics for Service Oriented Architecture (SOA). John Salasin, Ph.D. Visiting Researcher National Institute of Standards and Technology. The MITRE Corporation 29 August, 2007. SOA Predictive Metrics Basic Premises (1).
E N D
Predictive Metrics for Service Oriented Architecture (SOA) John Salasin, Ph.D. Visiting Researcher National Institute of Standards and Technology The MITRE Corporation 29 August, 2007
SOA Predictive Metrics Basic Premises (1) • System development / evolution is defined by a series of models (Models are the “global invariants” of development.) • Back of the envelope sketches • Architecture / Design • Running System (fully elaborated model) • “Predictive metrics” are based on measuring model features to identify potential future problems
SOA Predictive Metrics Basic Premises (2) • SOA is a system
SOA Predictive Metrics Basic Premises (3) • System development / evolution is defined by a series of models (Models are the “global invariants” of development.) • Back of the envelope sketches • Architecture / Design • Running System (fully elaborated model) • “Predictive metrics” are based on measuring model features to identify potential future problems • We want to assess system based on measures of technology and its application.
SOA Predictive Metrics Categories of Metrics • Ease with which a system can be modified or expanded. • Extent to which the system provides all functionality required. • Factors that facilitate the adoption of a system across an enterprise. • Capability of the organization responsible for an enterprise to specify, monitor and enforce all policies • Measurement instrument at: http://www.antd.nist.gov/~salasin/SOAMetrics/
SOA Predictive Metrics Status • Pilot testing for clarity, data avalability, predictive power (“Retrospective Longitudinal Study”) • Working in cooperation with the Federal CIO Council’s EA Task Force, Services Subcommittee.
Near-term changes • Measures of adaptability (e.g., change in orchestration, addition of new service) • Currently: Change in effort (time) to make change • Proposed: Tools/languages available to make change, e.g.: 1: Easy to use graphical interface or 2-3 script statements (a couple of minutes) 2: 5-10 script (declarative) statements (10 - 20 minutes) 3: 3/4 GL (e.g. Java, C#) programming (>> 20 minutes) • Addition of information technology support to Governance. E.g., to • A Map relationships and dependencies among assets and planned assets to conduct impact analyses. • A Execute a registration process to alert users to new assets and status changes. • A Support the development process by tracking which assets are proposed, funded, completed, released. • A Interact with lifecycle and configuration management processes to automatically discover the actual services. • A Detect and track business and IT exceptions, problems, failures. • Rating scale” • Automatic data extraction or easy to use graphical interface or 2-3 script statements (a couple of minutes) • 5-10 script (declarative) statements (10 - 20 minutes) • 3/4 GL (e.g. Java, C#) programming (>> 20 minutes)