Cloud Perspectives Steven Woodward CFPS, CSQA steve@cloud-perspectives.com 613-823-7573 www.cloud-perspectives.com
Introduction Models and Standards Categories and Context Function Point Scenarios Hints Final Considerations Copyright Cloud Perspectives 2015 All rights reserved 2
IFPUG Cross Contributions & Collaboration NIST National Institute of Standards for Technology OMG CSCC (Object Management Group) TM Forum QuEST Forum Cloud Security Alliance IEEE Many others! Copyright Cloud Perspectives 2015 All rights reserved 3
Hosting: External or Internal Three Service Models -Software as a Service (SaaS) - Platform as a Service (PaaS) - Infrastructure as a Service (IaaS) Four Deployment Models -Private cloud -Community cloud -Public cloud -Hybrid cloud Five Essential Characteristics -On demand self-service -Broad network access -Resource pooling -Rapid elasticity -Measured service Copyright Cloud Perspectives 2015 All rights reserved 4
Copyright Cloud Perspectives 2015 All rights reserved 5
Review objectives & goals Use other reference architectures and cloud eco-system models to generate discussions Business application boundaries Middleware boundary approaches IaaS and PaaS can be initiated by a user or machine (even a higher level service SaaS for example) Copyright Cloud Perspectives 2015 All rights reserved 6
User Layer User Function Partner Function Administration Function Cross-Layer Functions Access Layer Services Layer Endpoint Function SaaS/ CaaS IaaS PaaS Inter Cloud Function Service Orchestration Management Security & Privacy Cloud Operational Function NaaS Cloud Availability Function Resources Layer Resource Orchestration Pooling and Virtualization Physical Resources Monitoring & SLA Copyright Cloud Perspectives 2015 All rights reserved 7
User Layer User Function Partner Function Administration Function Cross-Layer Functions Access Layer Services Layer Endpoint Function SaaS/ CaaS IaaS PaaS Inter Cloud Function Service Orchestration Management Security & Privacy Cloud Operational Function NaaS Cloud Availability Function Resources Layer Resource Orchestration Pooling and Virtualization Physical Resources Monitoring & SLA Copyright Cloud Perspectives 2015 All rights reserved 8
Copyright Cloud Perspectives 2015 All rights reserved 9
Goals/Objectives Application Boundaries Potential Middleware Boundaries Other Trust Boundaries Additional Attributes and Context Interpretations and Special Extensions Categorization and Analysis Communication of Results Effective Leveraging of FP Data Learn and Refine Copyright Cloud Perspectives 2015 All rights reserved 10
Copyright Cloud Perspectives 2015 All rights reserved 11
Kill weeds Progress: Disperse 1.5 litres Duration.75 hour Front & Back Yard Copyright Cloud Perspectives 2015 All rights reserved 12
Disappointing Analysis: Wife put path/grass killer into the weed killer container I used the wrong spray Context and categorization are keys to realizing success, otherwise it could cause more harm than good. Copyright Cloud Perspectives 2015 All rights reserved 13
One Product Can Cross Services Business Facing Functions SaaS Development Platform Functions Service Facing Functions PaaS Infrastructure/ Resource Functions IaaS $200/ FP $800/ FP $60/ FP Copyright Cloud Perspectives 2015 All rights reserved 14
Create, View Customer Create Pay Product Customer can make a purchase Dynamically request more storage due to customer purchases made Customer requests more storage due to product information Copyright Cloud Perspectives 2015 All rights reserved 15
Create Customer Create Pay Product View Customer Pay Friend Application Boundary Customer SaaS Product Copyright Cloud Perspectives 2015 All rights reserved 16
1) All DETs within the cloud solution are meaningful to the business and stakeholders 2) Some DETs within the cloud solution product are not meaningful to the business and stakeholders 3) DETs can be defined by the user/ administrator 4) DETs can be defined by the user/ administrator, but are pre-configured as part of the solution Copyright Cloud Perspectives 2015 All rights reserved 17
1) All DETs meaningful 2) Some DETs meaningful DET Interpretation Count all DETS Count only meaningful DETs 3) Admin Defined Count DETs meaningful to the business 4) Supplied Configured with Admin Available Count DETs supplied and configured to satisfy business requirements Rationale Meaningful If it s not of value don t count it Counting from business perspective, not how it is implemented Counting from business perspective, not how it is implemented End Business User Perspective Copyright Cloud Perspectives 2015 All rights reserved 18
1) All DETs meaningful 2) Some DETs meaningful 3) Admin Defined 4) Supplied Configured with Admin Available DET Interpretation Count all DETS Count only meaningful DETs Count functionality for defining DETs (those are then treated as repeating ) Count DETs supplied and configured to satisfy business requirements Rationale Meaningful If it s not of value don t count it Counting functionality to define business DETs, not each DET configured Those DETs that were pre-configured by the supplier are recognizable DETs, meaningful to the consumer Technical Team Evaluating Solution Functions Copyright Cloud Perspectives 2015 All rights reserved 19
Consider Objectives Using FPA for Project Estimates? Using FPA to Clarify Business Functions? Using FPA for Outsourcing? Using FPA for Maintenance? Using FPA to help generate test plans? Using FPA to price and make payments based on software functionality provided Copyright Cloud Perspectives 2015 All rights reserved 20
Business requires that the product add function is available from an end user desktop windows device, plus from ios (Apple), Blackberry and Windows mobile devices. The cloud PaaS product from where the SaaS is generated, uses a code once deploy multiple devices, based on selection of media Copyright Cloud Perspectives 2015 All rights reserved 21
Business Perspectives Product Add EI Windows desk Product Add EI Windows mobile Product Add EI Blackberry mobile Product Add EI ios mobile Technical Perspective Product Add Copyright Cloud Perspectives 2015 All rights reserved 22
Function Design Code Deploy Test Product Add - Windows Product Add Mobile Windows Product Add - Blackberry Product Add - ios common common common s/b unique common common common s/b unique common common common s/b unique common common common s/b unique Copyright Cloud Perspectives 2015 All rights reserved 23
How much unique functionality needs to be coded? How much functionality needs to be tested? Can FPA be used to answer these questions and provide valuable insights/perspectives? Is it better to not use functional size measures? Copyright Cloud Perspectives 2015 All rights reserved 24
Business requires that the product add function is available from an end user desktop windows device, plus from ios (Apple), Blackberry and Windows mobile devices. The cloud PaaS product from where the SaaS is generated has the flexibility to design and utilize mobile device features to optimize user experience. Code multiple - deploy multiple. Copyright Cloud Perspectives 2015 All rights reserved 25
Business Perspectives Product Add EI Windows desk Product Add EI Windows mobile Product Add EI Blackberry mobile Product Add EI ios mobile Technical Perspective Product Add EI Windows desk Product Add EI Windows mobile Product Add EI Blackberry mobile Product Add EI ios mobile Copyright Cloud Perspectives 2015 All rights reserved 26
Function Design Code Deploy Test Product Add - Windows Product Add Mobile Windows Product Add - Blackberry unique unique unique unique unique unique unique unique unique unique unique unique Product Add - ios unique unique unique unique Copyright Cloud Perspectives 2015 All rights reserved 27
How much unique functionality needs to be coded? How much functionality needs to be tested? Can FPA be used to answer these questions and provide valuable insights/perspectives? Is it better to not use functional size measures? Copyright Cloud Perspectives 2015 All rights reserved 28
Business Perspectives Product Add Technical Perspective Product Add Could be valid too! Examples? Early Requirements No concerns regarding mobile devices, no testing planned Benchmarks local interpretation guidelines Copyright Cloud Perspectives 2015 All rights reserved 29
Consistency is required Comparative and trend analysis Potentially may need to reset or identify other categories/classifications Copyright Cloud Perspectives 2015 All rights reserved 30
Consumer Facing SaaS - EI Customer Makes a Purchase EI Services Layer SaaS PaaS SaaS Carrier Network Carrier Network Carrier Network API Validate Credit Card API Map Location Copyright Cloud Perspectives 2015 All rights reserved 31
Services Layer SaaS PaaS Carrier Network Middleware PaaS API s Carrier Network API PaaS - EO API Validate Credit Card Carrier Network API PaaS - EO API Map Location Copyright Cloud Perspectives 2015 All rights reserved 32
API IaaS EI Middleware End Consumer Makes a Purchase (EI) Based on a trigger, automatically requests additional storage to be provisioned using an IaaS service if needed Services Layer SaaS PaaS Service Orchestration IaaS IaaS NaaS Resources Layer Resource Orchestration Pooling and Virtualization Physical Resources Copyright Cloud Perspectives 2015 All rights reserved 33
Consumer Facing IaaS - EI Customer Requests More Storage (EI) Based on a customer request, additional storage is provisioned using an IaaS service Services Layer SaaS PaaS Service Orchestration IaaS IaaS NaaS Resources Layer Resource Orchestration Pooling and Virtualization Physical Resources Copyright Cloud Perspectives 2015 All rights reserved 34
Although the data (ILFs & EIFs) are physically stored within physical resources, they can be logically categorized within the Service Models (IaaS, PaaS, SaaS) SaaS Customer Product Purchases PaaS HTML Button Code? or-optional RET of Product? IaaS Infrastructure Allocations NaaS Copyright Cloud Perspectives 2015 All rights reserved 35
Use industry frameworks to gain perspectives Need context of what why and decisions Boundaries and accountability are key Count using the IFPUG rules and whitepapers such as middleware Categorizations of functionality help provide context (customized, configured, Service Models, etc) Logical data perspectives vs physical Copyright Cloud Perspectives 2015 All rights reserved 36
Use IFPUG method as a framework Categorized productivity and performance baselines for pricing Use measurement well, not rigidly local guidelines & extensions Cloud impacts pricing and costing Still learning, it s new! (no golden answer) Preparation and planning enables the most appropriate categorizations such that benefits are realized vs causing even more harm Copyright Cloud Perspectives 2015 All rights reserved 37
Basic framework remains valid and is actually part of most Enterprise Architecture models Boundaries Data Functions IFPUG Copyright Cloud Perspectives 2015 All rights reserved 38
Based upon user recognizable functionality using IFPUG! Goal - Reduce Costs of ICT Development, Maintenance and Time-to-Value 16 Month traditional development (time to value) schedule reduced to 60 days Total Cost of Ownership (development, enhancements & maintenance) for 10 year period reduced from $4 million to just over $1million http://www.prontoforms.com/att/res/downloads/prontoforms- WhitePaper-Buy-vs-Build.pdf Copyright Cloud Perspectives 2015 All rights reserved 39
Want to participate & get involved? steve@cloud-perspectives.com Copyright Cloud Perspectives 2015 All rights reserved 40