Foundations of Information Systems Study Guide and Chapter Summaries – Raisinghani (OpenStax, 2025) BSIT / BBA

Foundations of Information Systems is the OpenStax textbook for a first course in information systems. Mahesh S. Raisinghani led the author team, and OpenStax published the book on March 5, 2025, designing it around the IS2020 curriculum standards. Its 12 chapters move from the components of an information system and data management to databases, systems analysis and design, security and privacy, cloud computing, data analytics, project management, emerging technology, global systems and ethics.

BSIT and BBA students can use it as the course book for Information Systems or Management Information Systems, and it works well as a bridge between the business side and the technology side of a degree. This page adds a plain summary, key points, a tip, a common mistake and two practice questions for every chapter, plus a study plan, so you know what to read first.

Book Overview

Chapter List

Chapter 1: Fundamentals of Information Systems

Difficulty: Easy · Key topics: information system, five components, TPS, MIS, DSS, EIS, ERP, frameworks and standards, IS versus IT, globalization

The chapter starts by defining an information system as a set of connected parts that capture, process, store and share data to support decisions. It names five components, people, data, procedures, hardware and software, and traces the idea back through the printing press, the telegraph and early calculating tools such as the abacus and the Jacquard loom. It then separates the main system types, from transaction processing and management information systems to decision support, executive information and enterprise resource planning systems. The last sections introduce frameworks and standards such as COBIT, ITIL and ISO/IEC 27001, explain how IS differs from IT, and link the field to globalization and emerging technology.

Key Points:

• The five components of an information system are people, data, procedures, hardware and software.
• A system works through environment, input, processing, output, control and feedback.
• The core data operations are capture, processing, storage, retrieval and dissemination.
• The main system types are TPS, MIS, DSS and EIS; an ERP system ties business functions such as accounting, payroll and customer service together.
• IT focuses on building and running hardware, software and networks, while IS also includes the people and processes that use them to meet organizational goals.
• Frameworks named in the chapter include Agile, COBIT, ITIL, Waterfall, Zachman and McKinsey 7-S; standards include ISO/IEC 27001, TOGAF and IS2020.

Memory Tip: Picture a university library. People are the librarians and readers, data is the books, procedures are the borrowing rules, hardware is the shelves and computers, and software is the catalog app. Remove any one and the library stops working.

Common Mistake: Listing only hardware and software as the parts of an information system. People, data and procedures are components too, and exam answers lose marks without them.

Important Questions:

• What are the five components of an information system? People, data, procedures, hardware and software.
• How does information systems differ from information technology? IT concentrates on the hardware, software and networks themselves, while IS also covers the people and processes that use that technology to achieve an organization’s goals.

Chapter 2: Data Management and Information Systems Business Strategies

Difficulty: Medium · Key topics: data governance, information quality, big data, business-IT alignment, digital business models, business process management, digital innovation

Chapter 2 treats data as an asset that an organization must govern. It covers data governance, information quality and the four dimensions of big data, then the planning and decision-making models of Anthony, Simon, and Gorry and Scott Morton. The middle sections ask how IT creates value and how to align it with business strategy, and they list digital business models such as e-commerce, subscription, freemium and marketplace. The chapter closes with business process management and the stages of digital innovation, from initiation to exploitation, plus platform strategies that open a product to outside developers.

Key Points:

• Data governance sets the policies, processes, standards and roles for treating data as an asset.
• Information quality means data that is accurate, complete, consistent and accessible.
• Big data has four dimensions: volume, variety, velocity and veracity.
• Business-IT alignment means integrating IT tightly with strategy; gaps come from different objectives, unrecognized expertise and weak communication.
• Common digital business models are e-commerce, subscription, freemium, affiliate, marketplace, advertising, crowdfunding, sharing economy and digital product.
• Digital innovation moves through initiation, development, implementation and exploitation, though not every step is required or in a fixed order.

Memory Tip: Think of the four Vs as a delivery truck. Volume is how much it carries, variety is how many kinds of goods are inside, velocity is how fast it arrives, and veracity is whether the labels on the boxes are true.

Common Mistake: Defining data quality as accuracy alone. The chapter also lists completeness, consistency and accessibility.

Important Questions:

• What are the four dimensions of big data? Volume, variety, velocity and veracity.
• What is business-IT alignment? Closely integrating IT with an organization’s strategy and goals, so that technology supports what the business is trying to achieve.

Chapter 3: Database Management Systems

Difficulty: Medium · Key topics: DBMS, structured and unstructured data, relational database, NoSQL, data warehouse, data lake, conceptual, logical and physical design, normalization, mobile and cloud databases

This chapter explains how organizations store and manage data in a database management system. It sorts data into structured, semistructured and unstructured types and compares relational databases, NoSQL stores, data warehouses and data lakes. It then walks through design in three stages, conceptual, logical and physical, and shows why normalization and careful design matter in settings such as e-commerce and electronic health records. The final section links databases to mobile apps and cloud database services, including testing and the copying of data across locations so that services survive hardware failures.

Key Points:

• A DBMS stores, manages and processes data while keeping it organized, accessible and secure.
• Data can be structured, semistructured or unstructured, and each kind needs different tools.
• The database types compared are relational, NoSQL, data warehouse and data lake.
• Design moves from conceptual to logical to physical, aiming to reduce redundancy and meet normalization requirements.
• Testing covers unit, integration, system and user acceptance levels, and documentation and maintenance follow.
• Cloud databases let developers focus on app features, and providers replicate data across geographic locations to prevent loss.

Memory Tip: Compare the three design stages with building a house. Conceptual design is the sketch of what the family needs, logical design is the architect’s blueprint, and physical design is the actual construction on one specific plot, which is a specific DBMS.

Common Mistake: Mixing up logical and physical design. Logical design describes the structure without choosing a product, while physical design sets the database up on a particular DBMS.

Important Questions:

• What are the three stages of database design? Conceptual, logical and physical design.
• Why do mobile apps and cloud databases go together? Apps depend on databases for user profiles, messages and product details, and a cloud database scales easily and removes storage management, so developers can concentrate on the app.

Chapter 4: Systems Analysis, Design, and Development

Difficulty: Medium · Key topics: SDLC, Agile, user requirements, user stories, data flow diagrams, prototypes, peer-to-peer and client/server, user-centered design, accessibility

Chapter 4 follows the work of a systems analyst. It explains systems analysis and design, the system development life cycle and Agile, then shows how to define a business problem and capture user requirements with flowcharts, user stories and similar tools. The technical design section covers logical and physical design, the data life cycle, prototypes, input and output, and enterprise network architectures such as peer-to-peer and client/server. The last section turns to user-centered design, mobile app design and accessibility standards for websites.

Key Points:

• The SDLC stages are analysis, design, development, testing, deployment and maintenance.
• Agile is iterative: it delivers small, usable work packages and copes with changing requirements.
• Incomplete or incorrect requirements cause delays and extra cost, so upfront work saves resources.
• System design covers data design, interface design and process design.
• Prototypes catch problems early, involve users and reduce rework.
• Peer-to-peer and client/server are the two most common network architectures.
• User-centered design is iterative and puts the user’s experience and feedback at the center.

Memory Tip: Map the SDLC onto building a house: analysis is what the family needs, design is the plan, development is construction, testing is the inspection, deployment is moving in and maintenance is the repairs afterwards.

Common Mistake: Rushing past requirements to start building. The chapter stresses that wrong or missing requirements are the most expensive mistakes to fix later.

Important Questions:

• What are the stages of the system development life cycle? Analysis, design, development, testing, deployment and maintenance.
• How does Agile differ from a step-by-step approach? Agile works iteratively in short cycles such as sprints, delivering small usable pieces and adjusting to changing requirements instead of fixing everything upfront.

Chapter 5: Information Systems Security Risk Management

Difficulty: Hard · Key topics: CIA triad, firewall, VLAN, IDS and IPS, encryption, malware, social engineering, DDoS, penetration testing, GDPR, ISRM, CISO, certifications

Chapter 5 begins with network security: routers, switches and VLANs, firewalls and intrusion detection and prevention systems, and the confidentiality, integrity and availability triad. It then lists common threats, including malware, social engineering, insider threats and DDoS attacks, and the defenses against them, such as patching, penetration testing, vulnerability assessments and ethical hacking. A section on information security risk management combines risk identification, controls, incident response, recovery and continuous monitoring, using COBIT5 and NIST guidance. The chapter ends with the CISO role and the certifications that open security careers.

Key Points:

• The CIA triad is confidentiality, integrity and availability, supported by authentication and authorization.
• A router with a firewall can block unauthorized access, and switches can isolate traffic into VLANs.
• Common threats are malware, social engineering, insider threats, DDoS attacks and software or hardware flaws.
• Penetration testing and vulnerability assessments reveal weaknesses before attackers exploit them.
• An ISRM strategy combines risk identification, protective measures, incident response, recovery and continuous monitoring.
• Regulations such as GDPR and CCPA protect consumers, and COBIT5 and NIST offer structured guidance.
• The CISO sets the overall security strategy; CISSP, CISM, CEH and Security+ are among the certifications named.

Memory Tip: Remember the CIA triad as locked, unaltered, reachable. Confidentiality keeps data locked away from the wrong people, integrity keeps it unaltered, and availability keeps it reachable when needed.

Common Mistake: Believing that one control, such as a firewall or antivirus, is enough. The chapter opens with the idea that several layers of protection are needed.

Important Questions:

• What does the CIA triad stand for? Confidentiality, integrity and availability, the three core goals of information security.
• Why do organizations run penetration tests and vulnerability assessments? To find weaknesses in systems and networks so they can be fixed before attackers exploit them.

Chapter 6: Enterprise Security, Data Privacy, and Risk Management

Difficulty: Medium · Key topics: data privacy, data security, third-party risk, IoT vulnerabilities, ISO/IEC 27001, GDPR, audit, gap analysis, compliance, Privacy by Design

This chapter moves from technical defenses to the enterprise view of privacy and security. It argues that protecting data is a strategic business concern, not only an IT task, and it shows how third parties such as cloud providers add risk. It covers the new weaknesses of web applications and IoT devices, then global standards and frameworks such as ISO/IEC 27001, ISO/IEC 27701 and the NIST Privacy Framework. The final section walks through preparing for GDPR compliance with audits, gap analysis, policy changes and employee training.

Key Points:

• Privacy and security are strategic business concerns, not just IT issues, and need sustained investment.
• Third parties such as cloud providers and analytics firms add risk, so regular audits and clear handling agreements are needed.
• IoT and mobile technologies have created significant new vulnerabilities; defense combines preventive and reactive measures.
• ISO/IEC 27001 sets requirements for an information security management system.
• COBIT 2019, ISO/IEC 27701 and the NIST Privacy Framework are widely recognized frameworks.
• GDPR compliance is continuous: legal review, staff training, automated monitoring, audits and clear communication with users.

Memory Tip: The least privilege principle works like a hotel key card. It opens your own room and the gym, not every door in the building, and staff should only get the access their job needs.

Common Mistake: Treating GDPR compliance as a one-time project. The chapter ends on policy reviews, monitoring and audits that never really stop.

Important Questions:

• What is ISO/IEC 27001? A key international standard that sets requirements for information security management systems.
• Why does an organization carry out a gap analysis? To see where its current practices fall short of regulations or best practices and where data may be exposed.

Chapter 7: Cloud Computing and Managing the Cloud Infrastructure

Difficulty: Medium · Key topics: on-premise, virtualization, IaaS, PaaS, SaaS, public, private and hybrid cloud, pricing, SDN, migration, SLA

Chapter 7 contrasts on-premise systems, run by an organization’s own staff, with cloud computing delivered over the internet. It explains virtualization, scalability and elasticity, then the IaaS, PaaS and SaaS service models, the community, private, public and hybrid deployment models, and usage-based pricing. Later sections cover enabling technologies such as software-defined networking and storage-area networks, how to plan a secure migration with NIST and the CIA triad, and how to decide whether to build, buy or lease cloud applications. It ends with the social and industry effects of the cloud.

Key Points:

• On-premise systems are run by the organization’s own IS staff; cloud services are reached over the internet from any device and location.
• Virtualization is what makes cloud resources scalable and elastic.
• The service models are IaaS, PaaS and SaaS; the deployment models are community, private, public and hybrid.
• Cloud pricing is usage-based, and costs should be compared with on-premise options before signing contracts.
• Software-defined networking, virtualization and storage-area networks supply many cloud capabilities.
• Security must be planned before, during and after migration, using frameworks such as NIST and the CIA triad.

Memory Tip: Think of pizza. IaaS rents you the kitchen, PaaS gives you the kitchen with the oven and tools set up so you only cook, and SaaS is ordering the finished pizza.

Common Mistake: Assuming the cloud is always cheaper. The chapter tells organizations to compare costs with on-premise options first.

Important Questions:

• What is the difference between IaaS, PaaS and SaaS? IaaS rents computing infrastructure, PaaS provides a platform for building and running applications, and SaaS delivers finished software over the internet.
• What are the four cloud deployment models? Community, private, public and hybrid cloud.

Chapter 8: Data Analytics and Modeling

Difficulty: Medium · Key topics: analytics process, big data sources, business intelligence, dashboards, regression, decision trees, clustering, web analytics, bounce rate, SEO

This chapter shows how raw data becomes a business decision. It traces analytics from version 1.0 to 3.0, lists where big data comes from and walks through the analytics process, from defining the problem to acting on the results. It then covers business intelligence, dashboards and reports, and three techniques for better decisions: regression, decision trees and clustering. The last section is about web analytics, including page tagging, log file analysis, cookies, bounce rate and the role of SEO. Ethics and privacy come up in several places.

Key Points:

• Analytics has passed through three eras, Analytics 1.0 to 3.0, and the current era applies traditional analytics to big data.
• Big data comes from web scraping, sensors, social media, data marketplaces and APIs, and internal sources.
• The analytics process runs from defining the problem to preparing data, analyzing it, interpreting results and acting on them.
• BI reporting turns raw data into insight through dashboards, reports and visualizations.
• Regression relates a dependent variable to independent ones, decision trees split data by the most important attribute, and clustering groups similar data points.
• Web analytics gathers data through page tagging, log file analysis, JavaScript events and cookies.

Memory Tip: Regression predicts a number from other variables, a decision tree asks a chain of yes or no questions to split the data, and clustering simply groups similar items together.

Common Mistake: Mixing up regression and clustering. Regression models a relationship between variables, while clustering groups similar data points by shared features.

Important Questions:

• What are the steps of the business analytics process? Define the problem, prepare the data, analyze it statistically, interpret the results and act on them.
• What does bounce rate tell a website owner? It shows the share of visitors who leave after viewing one page, a sign that the page or the traffic source may need improving.

Chapter 9: Information Systems Project Management

Difficulty: Easy · Key topics: PMBOK, Agile, PRINCE2, project life cycle, work breakdown structure, risk register, scope creep, scrum, Kanban, project manager

Chapter 9 introduces project management for information systems. It explains the goal of delivering on time, within budget and within scope, compares the PMBOK, Agile and PRINCE2 methodologies, and distinguishes predictive, adaptive and incremental approaches. It then follows the five stages of a project, from initiation to closure, and shows how a work breakdown structure and a risk assessment support the plan. The last section is a career focus on project management roles, degrees and certifications.

Key Points:

• Project management keeps a project within schedule, budget and scope while protecting quality and limiting risk.
• PMBOK is sequential, waterfall-style; Agile and PRINCE2 are the other documented methodologies.
• Development approaches are predictive, adaptive and incremental.
• The five stages are initiation, planning, execution, monitoring and control, and closure.
• A work breakdown structure lists tasks, dependencies, timelines and required resources.
• Risk work means identifying risks, evaluating them, assigning owners and choosing mitigation strategies.

Memory Tip: Say the five stages as start, plan, do, watch, finish: initiation, planning, execution, monitoring and control, closure.

Common Mistake: Treating monitoring and control as the last step. Closure ends a project, and monitoring and control runs alongside execution.

Important Questions:

• What are the five stages of a project? Initiation, planning, execution, monitoring and control, and closure.
• What is a work breakdown structure used for? It breaks a project into tasks and shows their dependencies, timelines and required resources.

Chapter 10: Emerging Technologies and Frontiers of Information Systems

Difficulty: Easy · Key topics: emerging technology, blockchain, AI, machine learning, generative AI, AR, VR, quantum computing, IS frontiers, research process

This chapter defines emerging technologies as new or fast-evolving hardware and software that use data in new ways, and it names their typical traits: novelty, rapid growth and the power to disrupt. Blockchain, AI, augmented reality and virtual reality are the examples, with machine learning, generative AI and quantum computing among the key terms. The second section looks at the frontiers of information systems, such as combining AI with analytics for real-time decisions. The last section shows the effect on society and the economy and describes how research moves from an idea to the market.

Key Points:

• Emerging technologies include both brand-new inventions and existing technologies that are evolving.
• Typical traits are novelty, rapid progress and the potential to disrupt existing practices.
• Blockchain, AI, AR and VR are the chapter’s real-world examples.
• IS frontiers are the latest research areas, applications and technologies likely to strongly affect the field.
• Combining frontiers with other technologies, such as AI with data analytics, can process large data volumes in real time.
• Each technology brings its own opportunities, challenges and risks, so each should be assessed individually.

Memory Tip: For any new technology, ask three questions in order: what opportunity does it offer, what challenge does it create, and what risk does it carry?

Common Mistake: Thinking an emerging technology must be a brand-new invention. The chapter includes existing technologies that are still evolving.

Important Questions:

• What are the typical characteristics of emerging technologies? Novelty, rapid progress and the potential to disrupt existing practices.
• What are information systems frontiers? The latest developments in the field, including new research areas, innovative applications and emerging technologies likely to strongly affect information systems.

Chapter 11: Global Information Systems

Difficulty: Easy · Key topics: global information system, e-business models, global strategy, SMART objectives, logistics, supply chain, risk, culture, global teams

Chapter 11 looks at information systems that work across borders, starting with the example of Dubai’s smart-city programs. It explains how global systems standardize practices, centralize data management and support spatial analysis, and how to build one in phases. It then covers e-business models, global strategy with SMART objectives, global logistics and supply chain management, and risk. The final section shows how personal and organizational culture affect technology adoption and how global IS teams and cross-functional organizations work together.

Key Points:

• Global information systems standardize business practices, centralize data management and integrate operations across locations.
• Building one involves defining needs and objectives, choosing and designing technology, phased rollout, training, monitoring and feedback.
• A global strategy needs market analysis, SMART objectives, planned actions, resources and a diverse team.
• Global supply chain management covers the flow of goods, information and money across borders.
• Personal and organizational culture shape how willing people are to adopt a system.
• Culturally appropriate design uses user research, clear language and customizable features.

Memory Tip: SMART objectives are specific, measurable, achievable, relevant and time-bound. Test any goal you write in an exam answer against those five words.

Common Mistake: Assuming a system that works in one country can simply be copied to another. The chapter shows that culture affects how a system is designed, adopted and used.

Important Questions:

• Why do organizations build global information systems? To standardize practices, centralize data and integrate operations across locations, which improves consistency, decision-making, efficiency and innovation.
• How does culture affect information systems? Personal and organizational culture shape how people see technology and whether they adopt it, so teams must study cultural differences when developing and implementing a system.

Chapter 12: Ethics, Sustainability, and Social Issues in Information Systems

Difficulty: Medium · Key topics: utilitarianism, deontology, virtue ethics, systems thinking, green IS, sustainability, CSR, intellectual property, AI ethics, algorithmic bias, health informatics

The last chapter asks how information systems can be used responsibly. It introduces three ethical theories, utilitarianism, deontology and virtue ethics, along with systems thinking, sustainability, green and lean IS and corporate social responsibility. It then explains the four forms of intellectual property: copyrights, patents, trade secrets and trademarks. The final two sections cover the ethics of AI and machine learning, including algorithmic bias, explainability and human oversight, and the ethics of health informatics, including patient consent and privacy.

Key Points:

• Utilitarianism judges consequences, deontology judges the action itself and virtue ethics judges the actor’s character.
• Sustainability covers environmental stewardship, economic viability and social welfare; green IS cuts ecological impact and lean IS removes waste.
• The three Ps, people, planet and profit, can guide corporate social responsibility in IS.
• The four forms of intellectual property are copyrights, patents, trade secrets and trademarks, each with different requirements and duration.
• Algorithmic bias is handled with diverse datasets, audits, minority oversampling and human monitoring.
• In health informatics, patient consent, de-identification, encryption and access controls protect sensitive data.

Memory Tip: Remember the three ethical theories as outcome, rule and person. Utilitarianism asks about the outcome, deontology asks which rule or duty applies, and virtue ethics asks what a good person would do.

Common Mistake: Treating all intellectual property as one thing. Copyright, patent, trade secret and trademark law protect different things under different requirements.

Important Questions:

• What are the three pillars of sustainability in information systems? Environmental stewardship, economic viability and social welfare.
• How can organizations reduce algorithmic bias? By using diverse datasets, running audits, oversampling minority groups and keeping humans in the loop to monitor results.

How to Study This Book

Foundations of Information Systems has 12 chapters, and this page gives one block for each. The preface does not group the chapters into parts, so this page keeps the book’s own order. The book is an introduction to the whole field, designed around the IS2020 curriculum standards, so expect breadth rather than depth. Each chapter has a list of key terms and a section-by-section summary, which makes revision easier than in most textbooks.

Start with Chapters 1 and 2. Chapter 1 gives you the vocabulary used in every other chapter: the five components, the system types and the difference between IS and IT. Chapter 2 is the business half of the course, with data governance, the four Vs of big data, digital business models and business process management. These two chapters map to the first weeks of a typical Management Information Systems course.

Chapters 3 and 4 are the technical core. Read Chapter 3 on databases before Chapter 4, because the data design and entity relationship diagrams in systems analysis make more sense once you know tables, keys and normalization. For exams, learn the three design stages (conceptual, logical, physical) and the stages of the SDLC in order.

Chapters 5 and 6 are the security pair, and Chapter 5 is the hardest chapter in the book because it packs in networking and cryptography terms. Read Chapter 5 first, and make a one-line table of each threat and its defense. Chapter 6 then shows how privacy, standards and compliance work at enterprise level, with GDPR as the worked example. Chapter 7 on the cloud builds on both, because its migration section applies the CIA triad.

Chapters 8 and 9 suit BBA students especially: analytics and decision-making in Chapter 8, and project planning, risk and the work breakdown structure in Chapter 9. Chapters 10 to 12 are the lightest on technical detail. Chapter 10 on emerging technology and Chapter 11 on global systems are mostly reading, and Chapter 12 on ethics gives you the theories and IP vocabulary used in essay questions.

Every chapter ends with Key Terms, a Summary, Check Your Understanding questions, multiple-choice Review Questions and Application Questions. Chapter 12, for example, has 17 review questions, 9 check-your-understanding questions and 6 application questions. According to the preface, the Answer Key at the back of the book covers about half of the Review Questions, and the Instructor Answer Guide covers all of them but needs a verified instructor account, so attempt each question on paper first.

Know what the book does not do. It is not a programming course; SQL appears in Chapter 3 as a key term but is not taught. The legal material, such as intellectual property and CCPA, is mostly about the United States and Europe, so add Pakistani examples and local law when you write exam answers. Technology chapters, especially Chapters 7 and 10, will date as products change, so treat the concepts as the lasting part.

Used In These Programs

This book is used for the Information Systems course (often called Management Information Systems) in: BS Information Technology · BBA. Browse all Information Systems books or all Computer Science books.

Who Should Read This

Foundations of Information Systems is written for first-course students: BSIT and BBA students in an introduction to information systems or MIS course, and students of related programs such as BS Computer Science, BS Software Engineering and BS Data Science who want to see how technology serves a business. It suits business students who need the technology vocabulary and IT students who need the business side. It is not a deep technical text, so for databases, networks or programming you will need a specialist book.

When a chapter makes you want more depth, pair it with another free book. The Concepts of Information Technology covers the hardware and software basics behind Chapter 1, Database Management System goes further than Chapter 3, and Computer Networking: Principles, Protocols and Practice explains the networks behind Chapters 5 and 7.

Applicable Universities

This book is useful for students at Pakistani universities offering BS Information Technology, BBA and related programs, including Punjab University, Virtual University, COMSATS, FAST, UET, NUST, and other HEC-recognized institutions.

Official Copy of Foundations of Information Systems

Foundations of Information Systems is free from its official publisher, OpenStax. Click the button below to open the official OpenStax book page, where you can download the complete PDF or read every chapter online in your browser.

FAQs

Related Books

• The Concepts of Information Technology (the hardware, software and IT basics behind Chapter 1)
• Database Management System (a deeper look at the database design of Chapter 3)
• Computer Networking: Principles, Protocols and Practice (the networks behind the security and cloud chapters)
• Operating Systems and Networks (the systems software that every information system runs on)

Foundations of Information Systems gives BSIT and BBA students a free, complete first look at how organizations use data, technology and people together, from databases and security to the cloud and ethics. Browse more Computer Science books or all University Books.

Foundations of Information Systems, by Mahesh S. Raisinghani (senior contributing author) and contributing authors Amal Alhosban, Dax Bradley, Wade Chumney, Nicole Dhanraj, Sherita Freeman, James Gibbs, Sean Petty, Karen Srba, Ayushi Tandon and Michael MacLeod. OpenStax, Rice University, 2025. Free under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International licence (CC BY-NC-SA 4.0). Access for free at https://openstax.org/details/books/foundations-information-systems