Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Mission Driven  Cloud Computing Solution Design Kevin Jackson Engineering Fellow [email_address] NJVC, LLC
Cloud Computing.  Not a Panacea Lower Gain From Clouds Higher Gain From Clouds Lower Pain To Cloud Delivery Higher Pain To...
Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model for Interoperability Assessment <ul><li>Four to...
Sample Functional Capability Profile Narrower Scope Broader Scope Mission Requirement Solution Capability X X Capability C...
Technical Feasibility Dimensions Value Dimension Smaller Risk Larger Risk Inter-System Time Binding to Achieve Capability ...
Domain Dependent Values Cloud Computing SCOPE Model Management Coupling What is the degree of coupling between operational...
Mission Driven  Cloud Computing Solutions SCOPE MODEL General Net-readiness Capability/Domain Dependent Capability/Domain ...
Upcoming SlideShare
Loading in …5
×

Kevin Jackson - DoDIIS Worldwide 2010

1,252 views

Published on

Overview of SCOPE analysis for cloud computing

Published in: Technology
  • Be the first to comment

Kevin Jackson - DoDIIS Worldwide 2010

  1. 1. Mission Driven Cloud Computing Solution Design Kevin Jackson Engineering Fellow [email_address] NJVC, LLC
  2. 2. Cloud Computing. Not a Panacea Lower Gain From Clouds Higher Gain From Clouds Lower Pain To Cloud Delivery Higher Pain To Cloud Delivery Collabora -tion Transactional Content SME ERP LE ERP On-Line Storage Web2.0 Application Dev’t. DB Migration Projects Data Archive Situational Apps Web Scale Analytics [Enterprise Data] Dep’t. BI Applica-tion Test US Situational Awareness European Situational Awareness US has more network bandwidth available in the battlefield, therefore higher gain from using external cloud Courtesy IBM “ DB-Centric” Architecture “ Content-Centric” Architecture “ Loosely Coupled” Architecture Storage and Data Integration Architecture
  3. 3. Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model for Interoperability Assessment <ul><li>Four top-level categories of dimensions: </li></ul><ul><ul><li>Net-Readiness: </li></ul></ul><ul><ul><ul><li>Ability to deliver capability in a network context. </li></ul></ul></ul><ul><ul><li>Capability/Domain-Independent Scope: </li></ul></ul><ul><ul><ul><li>The range of scope or context supported. </li></ul></ul></ul><ul><ul><li>Capability/Domain-Dependent Scope </li></ul></ul><ul><ul><ul><li>The nature, quantity, quality, speed, etc., of capability provided to meet operational needs. </li></ul></ul></ul><ul><ul><li>Technical/Economic Feasibility </li></ul></ul><ul><ul><ul><li>The feasibility or risk associated with providing capability. </li></ul></ul></ul>SCOPE quantitatively and qualitatively measures how well a system can operate in a network centric environment. The addition of cloud computing domain specific dimensions and metrics provides a means for directly mapping mission requirements to cloud computing capabilities.
  4. 4. Sample Functional Capability Profile Narrower Scope Broader Scope Mission Requirement Solution Capability X X Capability C6 C1 C2 C3 C4 C5 C6 C7 C8 Requirements Capabilities Capability/Domain Independent Technical/Economic Feasibility
  5. 5. Technical Feasibility Dimensions Value Dimension Smaller Risk Larger Risk Inter-System Time Binding to Achieve Capability Strategic Tactical Transactional Real Time Run-Time Computing Resources Needed <1% of existing system resources 1-10% 10-50% >50% of existing system resources Service Mgmt. Resources Needed Negligible Within Current Net Service Capacity Within Planned Net Service Capacity Beyond Planned Net Service Capacity Net Resources Needed (FD) Negligible Within Current Net Capacity Within Planned Net Capacity Beyond Planned Net Capacity Interface Development Complexity <1% of system size 1-10% 10-50% >50% of system size Technology Readiness Level For Net Use TRL Levels 8-9 TRL Levels 6-7 TRL Levels 4-5 TRL Levels 1-3
  6. 6. Domain Dependent Values Cloud Computing SCOPE Model Management Coupling What is the degree of coupling between operational responsibility and execution resource ownership for: Network Resources   Computing Platform resources   Data resources   Service resources   What is the degree of coupling between relationship management and consequence management Range of Services What is the dynamic range of services associated with: Platform scalability   Storage scalability   Network access scalability/Network entity reach   Types of applications supported   Types of coupling to the physical environment   Types of coupling to the political/social environment Network Infrastructure Capacity What is the network infrastructure capacity between cloud provider and consumer? LAN Bandwidths   WAN Bandwidths and latencies   Mobile network Bandwidths and latencies   Dedicated communication links (point to point)   Low bandwidth and intermittent links   Asymmetric network links Platform Types   What execution platform types are provided by the cloud? Domain Specificity What is the degree of domain-specificity of the cloud-based services offered?   Data portability   Service Level interoperability   Levels of privacy/security/anonymity   Levels of redundancy and/or physical dispersion   Speed of allocation of resources   Level of management visibility/control
  7. 7. Mission Driven Cloud Computing Solutions SCOPE MODEL General Net-readiness Capability/Domain Dependent Capability/Domain Independent Technical/Economic Feasibility

×