The panelists discussed the challenges of transitioning to a software-as-a-service (SaaS) model and solutions for ISVs. Transitioning requires changes across the entire organization, including engineering, operations, support, sales and marketing. Companies must get buy-in for the paradigm shift and consider a hybrid approach. Success requires a commitment to the SaaS model from leadership and addressing potential internal resistance to change.
25. P R O V I D E R S N E E D S Demystifying the Cloud Hardware Framework Application IaaS PaaS SaaS EC2, Azure, Rackspace Force.com, Google App, Long Jump Your own App. Network Architects, Security, Hosting Software Architects, Tested and Proven Architecture Developers, Rapid Development of Functionality
26. Strategical Approach – Reuse Vs. Rewrite SaaS PaaS Is a concept Is a software/technology Defines only the delivery model of your software Defines how your software will be build and delivered Software is delivered over the internet with no setup required at the customer end Software is build on top of the platform and delivered over the internet Allows reusing your content software Mostly requires complete rewrite of the software Can easily support hybrid model (on-demand and on-premise) Will be very expensive to support hybrid model No lock-in on technology/provider Vendor lock-in
27.
28. Maturity Model Factors Factors Level 1 Level 2 Level 3 Level 4 Time Very Low Medium High High Transition Cost Very Low Low Medium Very High Maintenance Efforts Extremely High Medium Low Very Low Scalability Extremely Poor Low Medium High Engineering Skillset NIL Medium High Very High Customer Value Add High Very High N/A N/A Operational Efficiency Very Low Low High Very High