Mind Map by , created over 5 years ago

Mind Map on SaaS, created by wisaalbehardien on 05/21/2014.

Tags No tags specified
Created by wisaalbehardien over 5 years ago
Saulo Aizprúa
Saulo Aizprúa
French -> small but important words for GCSE
Chemistry (C3)
Amy Lashkari
Writing successful GCSE English essays
Sarah Holmes
A Cloud Definition
Bio Final Exam Melinda Winter
Jaidha Rosenblat
SaaS интернет-магазин
Vyacheslav Malch
Modern UI
yuvraj singh
1 Definition
1.1 software hosted, managed and maintained by a cloud service provider
1.2 made accessible to consumers over the internet on demand
1.3 configurable resources are offered: storage, networking capabilities, server usage, applications
1.4 service accessed through the browser
1.5 consumer unable to manage or alter underlying software but rather use it as is and when needed
2 Types of SaaS enterprise Software
2.1 BI and Analytics
2.1.1 SaaS BI delivers BI tools such as dashboards to consolidate key facts about business for easy consumption
2.1.2 consumers are encouraged to view business critical info during the course of normal browsing
2.2 CRM
2.2.1 provide business solution in cost effective maner
2.2.2 Salesforce.com has created a SaaS CRM product
2.2.3 allows company to focus on their core functions
2.3 ERP
2.3.1 allows the rental of ERP or use of ERP for a period of time
3 SaaS Infrastructure
3.1 application layer
3.1.1 manages all application services offered to the consumer
3.1.2 direct interaction with user
3.1.3 responsible for providing services
3.2 service management layer
3.2.1 provides requirements to users per application requirements
3.2.2 a functional module
3.2.3 performs specific tasks per role of user as governed by specific business roles
3.3 Business Layer
3.3.1 made up of business components and rules that operate on the SaaS service and its components
3.3.2 built to allow readily changed to suit business needs
3.3.3 independent of functional modules of service
3.4 Data Layer
3.4.1 metadata management layer bridge between business layer and DML
3.4.2 data management layer (DML) used to store and record data flowing in and out of SaaS service
3.5 Platform Layer
3.5.1 mapping and scheduling policies for the translation of consumers Quality of Service (QoS) requirements
3.6 Infrastructure Layer
3.6.1 allocates virtual machines to consumers requests
4 Multi-tenant architecture
4.1 structure whereby a single instance of software is made up of many consumers (tenants) on a one to many structure
4.2 consumers sharing the same application and database
4.3 allows provider to reach economy of scale
4.4 allows increased utilization of hardware resources and improved ease of maintenance during deployments
5 Web Services
5.1 a software system designed to support interoperable machine to machine interaction over a network
5.2 provides a standard mechanism for applications to publish and subscribe software services over the internet allowing for SaaS applications to be accessible
6 SaaS governance and core competency
6.1 Provider management
6.1.1 service level agreement (SLA) governs quality and availability of service provides support for consumers components the parties the consumer the provider third parties SLA parameters metrics on how the service parameters are measured Service level objectives set of formal expressions that describe conditions and actions which need to be performed by each party when condition is met
6.1.2 provider needs to be able to mitigate threats to consumer
6.2 security management
6.2.1 security structure would be in charge of: identifying and aggregating security compliancy and privacy issues, and solutions and processes that would positively impact the organisation
6.2.2 can either positively or negatively impact the adoption of SaaS
6.2.3 SLA parameters need to mention security measures
6.3 Standard Management
6.3.1 providers need to have a set of standards
6.3.2 interoperability
6.3.3 portability
6.3.4 security for the services
6.3.5 values need to be aligned
6.3.6 need to be alignment in terms of software requirements
6.4 Information Management
6.4.1 need to have correct management of information
6.4.2 release dates
6.4.3 technical integration
6.4.4 budgeting allocation
6.4.5 system administration
7 Pricing Models
7.1 pay per use
7.1.1 charged according to number of units used and each unit is charged at a fixed price
7.1.2 small consumers who lack capital
7.1.3 acts as an operating cost
7.1.4 allows consumer to test and evaluate the software to see if it meets needs
7.1.5 difficult to estimate
7.2 software rental
7.2.1 provider and consumer negotiate subscription fee to use software
7.2.2 decided on the amount of time software is used, number of users using, the company size, the functionality being used
7.2.3 user pays irrespective of whether they use it or not
7.3 fixed price
7.3.1 pay a fixed rate for a certain number of hours of software usage per month
7.3.2 allows for definite cost
7.4 revenue percentage
7.4.1 for consumers selling products and services
7.4.2 to collect a percentage of revenue rather than flat fee
7.4.3 percentage depends on size of business and nature of industry in which business operates
7.5 hybrid
7.5.1 allows combination of paying models
7.5.2 more direct and flexible relationship between usage and cost
7.5.3 difficult to estimate future costs as it allows consumers to rent some aspects of software without worrying about amount of units used
8 Advantages
8.1 lower costs
8.2 higher level of service
8.3 convenient and scalable
8.4 flexibility
8.5 higher security and lower risk
9 Disadvantages
9.1 financial
9.2 lack of customisation flexibility
9.3 limited integration and transition
9.4 issues specific to developing countries
9.5 data security and integrity
9.6 network security
9.7 business continuity and service availablity
9.8 data confidentiality and auditability
9.9 vendor and data lock in
9.10 compliance
9.11 organisational change
10 Management Issues
10.1 Finance
10.1.1 choose correct pricing model to suit needs
10.1.2 implementation costs
10.1.3 benefit of elasticity and transference of risk outweighs the costs
10.2 Risk management
10.2.1 SLA agreement to mitigate costs
10.2.2 encrypt storage
10.2.3 firewalls
10.2.4 virtual local area network
10.2.5 countries have laws under which data is governed
10.2.6 transfer risk of overprovisioing
10.2.7 transfer risk of under provisioning
10.3 Customer Retention
10.4 application selection
10.4.1 functional fit
10.4.2 flexibility and adatability
10.4.3 reliability
10.4.4 scability
10.4.5 fulfilment of organisational needs
10.4.6 process improvement over existing systems
10.5 Vendor selection
10.5.1 reputation
10.5.2 vision and strategy
10.5.3 financial position
10.5.4 reliability
10.5.5 ability to meet future needs
10.5.6 service quality of implementation
10.5.7 security and privacy
10.5.8 implementation time
10.5.9 resonsiveness and support
10.6 Firewall
10.6.1 firewall stops all incoming traffic
11 SaaS vendors
11.1 Salesforce.com
11.2 Microsoft
11.3 Oracle
11.4 SAP
11.5 Netsuite

Media attachments