MIS 301 Extra Credit Study Guide

Chapter 9 review page covering cloud computing, SaaS, IaaS, PaaS, AWS, total cost of ownership, cloud business models, entry barriers, enterprise benefits, and the risks of hosted software.

Chapter 9: Software as a Service and Cloud Computing

What Chapter 9 is mainly about

Chapter 9 explains how cloud computing changes the economics of software and infrastructure by shifting firms away from owning and maintaining everything themselves. It focuses on SaaS as the most common cloud model, compares SaaS, PaaS, and IaaS, and shows why companies move to the cloud for speed, scale, and lower upfront costs, while still facing risks related to vendors, control, performance, security, and switching costs.

Main takeaway: Cloud computing is not just a technical shift. It is a business model shift from owning to renting, from large upfront costs to ongoing operating costs, and from maximum control to a tradeoff between convenience, scalability, and dependence on outside providers.

What this page includes

  • Precise Chapter 9 vocabulary
  • Explanations from the textbook and slides
  • A scenario-based 5-question quiz
  • Visible chapter citations and works cited

How to study with it

  • Know the difference between SaaS, PaaS, and IaaS
  • Understand the tradeoff between control and convenience
  • Learn why TCO matters more than sticker price
  • Connect cloud benefits to entry barriers and strategy

Chapter 9 Vocabulary

Cloud Computing The delivery of computing resources such as hardware, storage, software, and processing power over the internet instead of running everything locally.
Citation: Chapter 9 review guide and SaaS slides
Software as a Service (SaaS) A model in which software is delivered over the internet and managed by a third-party provider, so users access the software without installing or maintaining it locally.
Citation: Chapter 9 review guide; SaaS slides
Platform as a Service (PaaS) A cloud model in which a provider manages most of the technology stack while customers build and manage their own applications on top of it.
Citation: “IT Can Be Better to Outsource Tech Stack Management” slide
Infrastructure as a Service (IaaS) A cloud model in which a provider rents out computing infrastructure such as servers, storage, and networking, while customers manage more of the stack themselves.
Citation: Chapter 9 review guide; outsourcing tech stack slide
Amazon Web Services (AWS) Amazon’s cloud platform that provides infrastructure, storage, databases, analytics, AI tools, and many other services over the internet.
Citation: Chapter 9 review guide, AWS products section
Service Level Agreement (SLA) A contract that defines the service standards a provider promises, such as uptime, reliability, support, and performance.
Citation: Chapter 9 review guide, vocabulary section
Consumerization of Technology The trend in which easy-to-use consumer tools influence what users expect from business software and enterprise systems.
Citation: Chapter 9 review guide, vocabulary section
Hosted Software Software that runs on remote servers rather than directly on the user’s own machine, requiring network access to use.
Citation: “What Kind of Software Is It?” slide
Local Software Software that runs directly on the user’s own machine and does not require a network connection just to execute.
Citation: “What Kind of Software Is It?” slide
Subscription Model A pricing approach in which customers pay recurring fees over time rather than buying a perpetual license once.
Citation: SaaS provider business model slide
Freemium Model A business model in which basic service is free, while premium features or upgraded versions require payment.
Citation: SaaS provider business model slide
Vendor Lock-In Dependence on a specific provider that makes switching difficult, costly, or disruptive.
Citation: Chapter 9 review guide and SaaS risks slide
Switching Costs The time, effort, money, retraining, migration work, and compatibility loss a firm faces when moving from one provider or system to another.
Citation: SaaS risks slide and TCO logic
Total Cost of Ownership (TCO) The full cost of a system over time, including implementation, deployment, training, support, integration, strategic updates, and recovery from failures or changes.
Citation: TCO over time slide; components of TCO slide
CAPEX Capital expenditure. Large upfront spending on owned assets such as servers, software licenses, and infrastructure.
Citation: Chapter 9 review guide, cost structure section
OPEX Operating expenditure. Ongoing recurring costs such as subscriptions, usage fees, and service payments.
Citation: Chapter 9 review guide, cost structure section
Distributed Computing Computing in which data and processing are spread across multiple machines or servers rather than being handled by one local system.
Citation: Chapter 9 review guide, key points section
Scalability The ability to expand or reduce computing resources quickly in response to changing demand.
Citation: Cloud computing benefits slides and Chapter 9 review guide
Latency The delay involved in transmitting data and receiving a response from a remote system, which can make cloud software feel slower or less responsive.
Citation: SaaS risks slide; online Excel latency slide
On-Premise Software Traditional software and infrastructure that a firm installs, owns, and manages within its own facilities rather than renting from a cloud provider.
Citation: TCO over time slide and winners comparison slide

Key Concepts and Explanations

1. Cloud computing changes the business model of software

One of the biggest ideas in Chapter 9 is that cloud computing is not only about where code runs. It changes how software is sold, updated, financed, and managed. Instead of buying and maintaining everything internally, firms can rent access to software or infrastructure and pay over time. This changes both the cost structure and the speed of deployment.

2. SaaS trades control for convenience

SaaS is the easiest cloud model to adopt because the provider manages almost everything, including the software itself. That reduces maintenance, speeds deployment, and supports remote access. However, it also means the customer gives up some control over features, customization, performance, and long-term dependence on the vendor.

3. Cloud reduces some entry barriers and increases competition

Before cloud computing, a new firm often needed major upfront investments in servers, software, data centers, and technical staff. Cloud services reduce those barriers by letting firms rent powerful infrastructure and software as needed. That makes it easier for startups to launch, which increases competition and forces incumbents to keep innovating.

4. TCO matters more than just the purchase price

Chapter 9 makes clear that the real cost of software is much bigger than the initial price tag. Requirements analysis, site preparation, licenses, implementation, training, operational support, failures, upgrades, and future strategic changes all affect the true cost. SaaS often lowers upfront and support costs, but firms still need to analyze the full long-term picture.

5. SaaS benefits providers as well as customers

SaaS helps providers because they manage one hosted version instead of supporting many separate local installations. It becomes easier to deploy fixes, add enhancements, roll out updates, and reduce piracy because customers do not possess full local copies of the software in the traditional sense.

6. Cloud is powerful, but not risk-free

Dependence on a single vendor, latency, internet reliability, security concerns, legal issues with off-site data, incomplete features compared with desktop software, and the possibility of vendor failure are all major risks. That is why many firms move cautiously, especially with mission-critical systems and highly customized business processes.

Good Chapter 9 study habit: do not memorize cloud as simply "software on the internet." Ask what part of the stack is being outsourced, what the firm gains, what the firm gives up, and whether the real long-term cost and risk profile actually improves.

Cloud Models, Cost Structure, and Why Firms Do Not Move Everything

Chapter 9 compares SaaS, PaaS, and IaaS and asks why cloud can be attractive without being automatically best for every situation.

1. SaaS outsources almost the whole stack
In SaaS, somebody else manages everything, including the application itself. This is why SaaS is often easiest for users and fastest for deployment.
2. PaaS and IaaS offer more control, but more responsibility
With PaaS, firms usually manage their own applications while renting the rest of the platform. With IaaS, they rent infrastructure and must manage even more of the software stack themselves.
3. Cloud shifts CAPEX toward OPEX
Instead of paying large upfront capital costs for servers, licenses, and infrastructure, firms often move toward recurring subscription or usage-based payments over time.
4. Remote access and scale are major strengths
Cloud systems support remote work, availability from many locations, and rapid scaling up or down as demand changes. This can be especially valuable for growing firms or unpredictable workloads.
5. Not everything belongs in the cloud
Firms may keep some systems on-premise because of unique business processes, regulatory limits, perceived security issues, missing cloud features, latency concerns, or the difficulty of migrating highly complex systems.
Important: the chapter does not say cloud always wins. It says managers should compare benefits, risks, TCO, fit with business processes, and strategic dependence before deciding which layer of the stack to outsource.

Chapter 9 Quiz

These questions are scenario-based and designed to feel closer to actual MIS test questions.

1. A startup chooses AWS instead of buying its own servers because it wants to launch quickly, avoid large upfront hardware purchases, and expand capacity only if customer demand grows. Which Chapter 9 idea best explains why this choice is attractive?

2. A firm adopts a hosted spreadsheet platform because employees can access it anywhere, but later discovers that one advanced feature used in critical financial modeling is missing from the online version. Which Chapter 9 lesson does this most directly illustrate?

3. A software company prefers SaaS over traditional licensed software because it wants all users on the same current version, wants to push updates easily, and wants piracy to be less of a problem. Which answer best fits Chapter 9?

4. A company compares a locally installed system with a SaaS alternative. The SaaS option looks more expensive month-to-month, but the local system would also require consultants, deployment work, user training, downtime during transition, support staff, and future upgrade projects. Which Chapter 9 concept best explains what the firm needs to evaluate?

5. A hospital considers moving a mission-critical system to the cloud, but leaders worry about dependence on one vendor, legal responsibility for off-site data, internet reliability, and the difficulty of recovering if the provider fails. Which Chapter 9 conclusion best fits?

Answer Key and Explanations

Question 1

Correct answer: A

This is one of the core benefits of cloud computing in Chapter 9. Renting infrastructure lets startups avoid huge capital expenditures, move faster, and scale resources when demand changes. B is false because cloud can actually increase competition. C is too absolute. D is wrong because financial analysis still matters a great deal.

Question 2

Correct answer: B

Chapter 9 specifically points out that SaaS products can be very convenient and accessible while still lacking some features of traditional desktop software. This is a classic tradeoff. A is incorrect. C is also incorrect because cloud dependence can create lock-in. D is too narrow because latency and responsiveness matter in business software too.

Question 3

Correct answer: A

SaaS helps providers because they manage one hosted version instead of many scattered local installations. That makes it easier to deploy fixes, control updates, and reduce piracy. B and D are false, and C gets the incentives backward.

Question 4

Correct answer: B

Total cost of ownership is exactly about looking beyond the sticker price. Implementation, consultants, training, support, downtime, and future upgrades are all part of the real cost. That is why managers should compare full long-term costs rather than just upfront prices or monthly subscription fees.

Question 5

Correct answer: B

The chapter does not claim that cloud is always the right answer. It argues that firms should evaluate cloud carefully, especially for mission-critical systems. Vendor dependence, security, legal compliance, latency, and provider failure are real concerns that require cautious planning.

Works Cited