Skip to main content
CBE NEXUS · UNDERGRADUATE INFORMATION SYSTEMS · CHAPTER 1

Foundations of Information Systems and Digital Organisations

Undergraduate textbook notes · Systems thinking · Organisational processes · Data · Digital value

Learning outcomes: Define information systems and distinguish data, information and knowledge; explain system components and architecture; analyse organisational processes; compare major information-system types; and evaluate how digital capabilities create value and introduce risk.

Introduction

Information systems are central to contemporary organisations. They connect people, processes, data and technology to support operations, coordination, decisions and services. This chapter establishes the concepts needed for later study of databases, systems analysis, networks, cybersecurity, enterprise platforms, analytics and digital transformation.

1. Meaning, scope and evolution of information systems

An information system (IS) is an organised combination of people, processes, data and technology that collects, processes, stores and distributes information to support operations, coordination, control, analysis and decision-making. It is not simply a computer or software application. A payroll system, for example, depends on employee records, pay rules, approval procedures, staff responsibilities, computing infrastructure and controls. If any component is poorly designed, the overall system may produce inaccurate results or fail to meet organisational needs. Information systems therefore have both technical and social dimensions.

Information systems have evolved from manual ledgers and paper-based filing to transaction-processing systems, databases, enterprise platforms, cloud services, mobile applications, analytics and AI-enabled systems. Each generation has changed the speed, scale and reach of organisational information processing. Modern organisations operate across networks of suppliers, customers, regulators and partners. Digital platforms enable transactions and collaboration across geographical boundaries, but also create dependencies on connectivity, data quality, cybersecurity, vendors and governance. Understanding this evolution helps analysts distinguish a temporary technology trend from a lasting organisational capability.

The scope of information systems includes business applications, infrastructure, data management, cybersecurity, systems analysis, digital strategy, user experience, governance and organisational change. Information systems professionals translate organisational needs into reliable services and help organisations use technology responsibly. Their work may involve requirements analysis, configuration, integration, testing, service support, data analysis, project delivery and risk management. The discipline draws on computing, management, economics, behavioural science, law and design because information systems affect how people work and how organisations create value.

Figure 1. Core components of an information system
PEOPLE + PROCESSES + DATA + TECHNOLOGY
↓
COLLECT → PROCESS → STORE → DISTRIBUTE INFORMATION
↖ FEEDBACK AND CONTROL ↙

2. Data, information, knowledge and organisational value

Data are recorded observations or symbols that have not necessarily been interpreted. Information is data processed and organised so that it has meaning for a particular purpose. Knowledge involves understanding, experience and judgement used to interpret information and guide action. A list of daily sales transactions is data; a report showing sales by product and region is information; a manager's understanding of why a product performs differently across regions is knowledge. The distinctions are contextual: information useful to one decision-maker may be irrelevant or incomplete for another.

Information quality is commonly assessed through accuracy, completeness, consistency, timeliness, relevance, validity, accessibility and uniqueness. These dimensions can conflict. Real-time information may be less thoroughly validated than a carefully reconciled monthly report. Highly detailed data may be difficult to interpret, while an aggregated summary may conceal important differences. Organisations should define quality requirements according to the decision and risk involved. Data governance assigns responsibilities for definitions, ownership, quality rules, access, retention and acceptable use.

Information creates value when it improves a process or decision sufficiently to justify the costs and risks of collecting, maintaining and using it. Value may arise through lower transaction costs, faster service, reduced errors, improved customer experience, better resource allocation or new products. Technology expenditure alone does not guarantee benefits. The organisation must redesign processes, train users, maintain data quality and measure whether the expected outcomes occur. A useful business case identifies the baseline, expected benefits, implementation costs, dependencies, risks and method for evaluating realised value.

3. Components and architecture of information systems

A useful systems model identifies input, processing, output, feedback and control. Inputs may include customer orders, sensor readings or staff records. Processing validates, transforms, calculates or combines the inputs. Outputs include confirmations, reports, dashboards and decisions. Feedback provides information about system performance or results, while control establishes rules and corrective action. The model helps analysts trace how information moves through a process and identify where errors, delays or unauthorised changes may occur.

Technology components include hardware, software, networks, databases, cloud services and interfaces. People include users, managers, administrators, developers, suppliers and customers. Processes define how work is performed, approved and monitored. Data represent the objects and events the organisation needs to understand. These components are interdependent. A technically available application may fail if users cannot access it, if the process is unclear, if data definitions conflict or if responsibilities are not assigned. Architecture must therefore address business, application, data and technology perspectives together.

An information systems architecture describes the major components of an organisation's systems and how they relate. It may include business capabilities, applications, data flows, integration interfaces, infrastructure, identity services and security controls. Architecture principles support consistency and guide investment decisions. Examples include using standard interfaces, minimising unnecessary duplication, protecting sensitive data, designing for resilience and preferring reusable services where appropriate. Architecture is not merely a diagram: it is a set of decisions, constraints and standards that guide the evolution of the digital environment.

Figure 2. Systems architecture perspectives
BUSINESS NEEDS ↔ BUSINESS PROCESSES
APPLICATIONS ↔ DATA AND INTEGRATION
TECHNOLOGY INFRASTRUCTURE ↔ SECURITY AND GOVERNANCE

4. Information systems in organisations and business processes

Business processes are connected activities that transform inputs into outputs for an internal or external customer. Examples include order-to-cash, procure-to-pay, recruit-to-retire and incident-to-resolution. Information systems support these processes by recording events, routing tasks, enforcing rules, providing status visibility and connecting departments. A process view prevents organisations from optimising one department while creating delays or errors elsewhere. Analysts should understand the end-to-end flow, hand-offs, decision points, exceptions and performance measures before recommending technology.

Functional systems may support finance, human resources, marketing, operations, procurement and customer service. However, organisational work often crosses these boundaries. A customer order may affect sales, inventory, credit control, warehouse operations, delivery and accounting. When departments use isolated systems, the organisation may experience duplicate entry, inconsistent customer records and delayed reporting. Integration and shared data definitions can improve coordination, but they require governance and careful management of dependencies.

Process analysis distinguishes the current state (as-is) from a proposed future state (to-be). Analysts document activities, roles, inputs, outputs, rules, systems and exceptions. They identify bottlenecks, unnecessary approvals, rework, control gaps and opportunities for automation. Process redesign should not simply digitise every existing step. It should question whether activities are necessary, whether responsibilities are clear and whether the redesigned process improves outcomes without weakening accountability or excluding users.

5. Transaction processing systems

Transaction processing systems (TPS) capture and process routine business events such as sales, payments, bookings, stock movements, attendance and payroll transactions. They are often operationally critical because many organisational processes depend on accurate, timely transaction records. A TPS may process transactions in batches or online as events occur. Batch processing can be efficient for scheduled tasks such as payroll, while online transaction processing is important where users need immediate confirmation, such as ticket booking or retail payment.

Transaction processing must preserve data integrity. A transaction should be complete, valid and recorded consistently, even when several operations are involved. Database transactions are often discussed through ACID properties: atomicity, consistency, isolation and durability. Atomicity means that a transaction succeeds as a whole or is rolled back; consistency preserves defined rules; isolation limits interference between concurrent transactions; durability ensures committed changes persist. These properties help prevent partial updates, lost changes and inconsistent records.

TPS controls include authentication, authorisation, validation, duplicate detection, audit trails, reconciliations, exception handling and backup. For example, a payment workflow should verify the amount and account, prevent unauthorised access, record the transaction reference and provide a reliable outcome to the user. Error messages should be useful without exposing sensitive system details. Operational monitoring should detect unusual failure rates, queue backlogs and processing delays. Because TPS data often feed management reports, poor transaction controls can propagate errors throughout the organisation.

6. Management information and decision support systems

Management information systems (MIS) transform operational data into structured reports that help managers monitor performance, compare results with plans and coordinate resources. Reports may be periodic, exception-based, summary or detailed. A useful report answers a defined management question and presents measures consistently. Too many reports can create information overload, while poorly defined indicators can encourage decisions based on misleading comparisons. Managers should understand the source, calculation, time period and limitations of every important measure.

Decision support systems (DSS) help analyse problems that may be semi-structured or require comparison of alternatives. They can include models, simulations, scenario analysis, optimisation and interactive queries. A budgeting model might show how changes in price, demand or costs affect projected profit. A transport model might compare routes under different capacity constraints. A DSS supports judgement; it does not automatically make the decision correct. Assumptions, data quality and model limitations must be visible to decision-makers.

Executive information systems and dashboards provide high-level indicators for strategic monitoring. Good dashboards use a limited set of meaningful measures, clear definitions, appropriate visual scales and drill-down capability. They should distinguish leading indicators that may signal future performance from lagging indicators that record past outcomes. A dashboard is not a substitute for investigation. When an indicator changes, managers should examine causes, data quality, context and unintended incentives before taking action.

7. Enterprise systems and organisational integration

Enterprise systems integrate information and processes across organisational functions. Enterprise resource planning (ERP) systems commonly connect finance, procurement, inventory, production, projects and human resources through shared data and workflows. Customer relationship management (CRM) systems support customer information, sales activities, marketing and service. Supply chain management systems coordinate demand, sourcing, inventory, logistics and supplier relationships. These categories overlap and may be delivered as modules within a wider platform.

Integration can reduce duplicate data entry and improve visibility, but enterprise implementation is difficult. Organisations must decide whether to adopt standard software processes or customise the platform to existing practices. Excessive customisation increases cost and makes upgrades harder; excessive standardisation may force an organisation to abandon a genuine competitive capability or regulatory requirement. Data migration, process redesign, role changes, training and executive sponsorship are major determinants of success.

Enterprise implementation should begin with business objectives and process ownership rather than a product demonstration alone. A phased approach may reduce risk, while a single major deployment may offer faster integration but concentrate disruption. Configuration, testing, user acceptance, migration rehearsal, cutover planning and post-implementation support are essential. Benefits should be measured after go-live because a system can be technically operational while users continue to rely on spreadsheets or workarounds.

8. Database systems and data management foundations

A database is an organised collection of related data managed to support storage, retrieval, updating and control. A database management system (DBMS) provides facilities for defining structures, querying records, enforcing constraints, controlling concurrent access, managing transactions and recovering from failures. Relational databases organise information into tables with rows and columns. A row represents a record and a column represents an attribute. Keys identify records and establish relationships between tables.

Good database design begins with understanding entities, attributes, relationships and business rules. An entity might be Student, Course, Lecturer or Enrolment. A primary key uniquely identifies each row; a foreign key references a related record. Entity-relationship diagrams show entities and cardinality, such as one-to-many or many-to-many relationships. A many-to-many relationship is commonly represented through an associative table. Clear naming, data types, constraints and documentation improve maintainability.

Normalisation reduces unnecessary duplication and update anomalies by organising data according to dependencies. First normal form requires atomic values and no repeating groups; second normal form addresses partial dependency on a composite key; third normal form removes inappropriate transitive dependencies. Normalisation is a design tool, not an end in itself: some analytical or high-performance systems may use controlled denormalisation. Data governance also covers metadata, master data, reference data, retention, lineage, quality and lawful access.

Figure 3. Relational database relationship
STUDENT (StudentID, Name)
1 ─────
M ENROLMENT (StudentID, CourseID, Date)
M ───── 1
COURSE (CourseID, Title)

9. Networks, internet and digital communication

Computer networks connect devices so that they can exchange data and share resources. A network includes end devices, transmission media, switches, routers, wireless access points, addressing, protocols and security controls. Local area networks connect devices within a limited site, while wide area networks connect geographically separated locations. The internet is a global network of interconnected networks that use common protocols. Organisational systems depend on reliable connectivity for communication, cloud services, remote work and digital transactions.

Protocols define how communication occurs. The TCP/IP model provides a practical way to understand layered networking. IP addressing supports delivery between networks; TCP provides reliable ordered transport; UDP offers lower-overhead datagram delivery where application requirements permit; DNS maps domain names to network addresses; HTTP and HTTPS support web communication. Encryption in HTTPS helps protect data in transit, although it does not guarantee that a website or endpoint is trustworthy.

Network design considers bandwidth, latency, availability, capacity, segmentation, redundancy and monitoring. Bandwidth describes potential data transfer capacity; latency describes delay. A video meeting may be sensitive to latency and jitter, while a large file transfer may depend more on throughput. Network segmentation can limit the spread of compromise and separate guest, operational and sensitive environments. Organisations should monitor performance, maintain configurations and plan for outages and provider dependencies.

10. Cloud computing and modern infrastructure

Cloud computing provides on-demand access to shared computing resources such as servers, storage, databases, networking and software. Common service models include Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS). IaaS provides configurable infrastructure; PaaS provides a managed environment for building and deploying applications; SaaS delivers a ready-to-use application. Responsibility for configuration, security and maintenance varies across the service model and provider.

Deployment models include public, private, hybrid and community cloud arrangements. Public cloud services can offer elasticity and global reach, while private environments may provide greater control for particular requirements. Hybrid arrangements combine environments but introduce integration, identity, networking and governance complexity. Cloud migration should be based on workload suitability, data sensitivity, performance, cost, resilience, legal obligations and exit options rather than an assumption that cloud is always cheaper.

Cloud governance includes identity and access management, encryption, logging, configuration management, backup, cost monitoring, vendor risk and disaster recovery. Shared responsibility means that the provider secures aspects of the service while the customer remains responsible for many settings, identities, data and applications. Misconfigured storage or excessive permissions can expose information even when the underlying cloud infrastructure is secure. Organisations should test recovery procedures and understand how to retrieve data or migrate away from a provider.

11. Cybersecurity, privacy and information risk

Cybersecurity protects the confidentiality, integrity and availability of information systems. Confidentiality means information is accessible only to authorised parties; integrity concerns accuracy and protection against unauthorised alteration; availability means systems and information are accessible when needed. Threats include phishing, credential theft, malware, ransomware, insider misuse, software vulnerabilities, denial-of-service attacks, supply-chain compromise and physical loss. Risk depends on threats, vulnerabilities, exposure, impact and the effectiveness of controls.

Security is a continuous management responsibility rather than a single product purchase. Common controls include multi-factor authentication, least privilege, secure configuration, patching, endpoint protection, network segmentation, encryption, backups, logging, staff awareness and incident response. Administrative controls include policies, training, supplier review and access approval. Physical controls protect facilities, devices and media. Controls should be selected according to risk and tested to ensure that they work in practice.

Privacy concerns the appropriate collection, use, sharing, retention and deletion of personal information. Organisations should identify a lawful and transparent purpose, minimise data collection, restrict access, maintain accuracy and explain relevant uses. Privacy impact assessments can help identify risks before a new system or data-sharing arrangement is introduced. Security and privacy are related but distinct: a securely stored dataset can still be used unfairly or for a purpose people did not reasonably expect.

12. Systems analysis and requirements engineering

Systems analysis investigates a problem or opportunity and determines what an information system must achieve. Requirements engineering includes elicitation, analysis, specification, validation, prioritisation and management of requirements. Stakeholders may include users, customers, managers, regulators, support teams, suppliers and people indirectly affected by the system. Their needs can conflict. An analyst must make assumptions visible, resolve ambiguity and ensure that the system's intended outcomes are understood.

Functional requirements describe what the system should do, such as create an order, calculate a fee or approve a request. Non-functional requirements describe qualities and constraints such as performance, availability, usability, security, accessibility, maintainability, interoperability and compliance. A requirement should be clear, necessary, testable, traceable and feasible. Vague statements such as 'the system must be user-friendly' should be converted into observable acceptance criteria.

Elicitation methods include interviews, workshops, observation, document analysis, surveys, interface prototyping and process modelling. Use cases describe interactions between an actor and a system to achieve a goal. User stories express a need from a user's perspective and may be paired with acceptance criteria. Requirements validation checks whether the documented needs reflect stakeholder intent and whether they can be tested. Change control prevents uncontrolled scope expansion while allowing justified adaptation.

Figure 4. Requirements engineering cycle
ELICIT → ANALYSE → SPECIFY → VALIDATE
↑ CHANGE CONTROL AND TRACEABILITY ↓

13. Systems development life cycle and delivery methods

The systems development life cycle (SDLC) describes stages through which an information system is planned, analysed, designed, built or configured, tested, deployed and maintained. Traditional sequential approaches define stages and approvals in advance. Iterative and incremental approaches deliver parts of a system, learn from feedback and refine subsequent releases. Agile methods emphasise collaboration, working increments, adaptation and continuous feedback. No approach is universally best; complexity, uncertainty, regulation, dependencies and organisational readiness influence selection.

Design translates requirements into architecture, data structures, interfaces, security controls and component specifications. Development may involve coding, configuration, integration or procurement of a packaged solution. Testing should occur at multiple levels: unit testing checks components; integration testing checks interactions; system testing examines the complete solution; acceptance testing checks whether business needs are met. Non-functional testing may examine load, resilience, accessibility, security and recovery.

Deployment planning includes migration, user communication, training, cutover, rollback, support and monitoring. Maintenance includes correcting defects, adapting to changes, improving performance and managing vulnerabilities. Technical debt arises when short-term shortcuts create future maintenance cost or risk. Good delivery practices document decisions, automate repeatable tests where practical, control versions and ensure that operational teams can support the system after project completion.

14. User experience, accessibility and human-computer interaction

Human-computer interaction (HCI) studies how people interact with digital systems and how interfaces can support effective, safe and satisfying use. User experience (UX) includes usability, accessibility, usefulness, trust, emotional response and the wider experience before, during and after interaction. A technically correct system may still fail if users cannot understand its navigation, interpret errors or complete essential tasks. Design should begin with users and their contexts rather than with the preferences of the development team.

Usability is often evaluated through effectiveness, efficiency and satisfaction in a specified context. Common methods include observation, task-based testing, interviews, surveys, analytics and heuristic evaluation. A usability test should define representative tasks and participants, observe where difficulty occurs and distinguish interface problems from inadequate training or system performance. Small interface changes can have significant effects on error rates and completion time, but improvements should be verified with users.

Accessibility aims to make systems usable by people with diverse sensory, physical, cognitive and language needs. Good practice includes keyboard operation, readable contrast, captions, text alternatives, clear focus indicators, scalable text, meaningful labels and compatibility with assistive technologies. Accessibility is not merely a compliance checklist. It is part of inclusive service design and should be considered from the earliest requirements stage, tested with diverse users and maintained as content and interfaces change.

15. Information systems governance and professional ethics

IT governance establishes decision rights, accountability and oversight for the use of information technology. It connects technology investment with organisational strategy, risk appetite, performance and stakeholder responsibilities. Governance clarifies who approves investment, who owns data, who accepts risk, who sets architecture standards and who monitors service performance. Without clear accountability, technology decisions may become fragmented and security or compliance responsibilities may be neglected.

Policies and standards translate governance decisions into expected practice. Areas include acceptable use, access control, data classification, retention, incident response, supplier management, software acquisition, change management and business continuity. Internal audit and assurance assess whether controls are designed appropriately and operate as intended. Compliance should be embedded in normal processes rather than treated as a last-minute document exercise.

Information systems professionals face ethical questions involving privacy, surveillance, algorithmic bias, accessibility, intellectual property, conflicts of interest, environmental impact and unequal access. A system can be lawful yet still cause avoidable harm. Professionals should identify affected groups, examine who benefits and who bears risk, disclose limitations and escalate serious concerns through appropriate channels. Competence includes knowing when specialist legal, security, privacy or accessibility advice is required.

16. Digital transformation, innovation and organisational change

Digital transformation is the coordinated use of digital capabilities to change how an organisation operates, delivers value and relates to stakeholders. It is broader than installing a new application. Transformation may involve redesigning services, changing decision rights, developing new business models, integrating data, automating tasks and building new capabilities. The desired outcome should be stated in organisational terms, such as shorter service time, improved reliability or a new customer experience.

Innovation can be incremental, improving an existing process, or more radical, creating a substantially different product or operating model. Digital platforms, application programming interfaces, mobile services, analytics, automation and AI can enable new services. However, technical possibility does not establish business value. Organisations should test assumptions with users, assess feasibility and risk, run controlled pilots where suitable and measure results against a baseline. Innovation governance should allow experimentation without ignoring security, privacy or operational safety.

Change management addresses the human and organisational effects of transformation. People may resist because of uncertainty, loss of control, workload, poor communication, inadequate skills or legitimate concerns about the proposed design. Effective change includes stakeholder engagement, visible leadership, training, support, feedback and realistic transition planning. Organisations should monitor adoption and workarounds after deployment. A transformation is sustainable when new practices are embedded in responsibilities, measures, culture and ongoing improvement.

17. Data analytics, business intelligence and artificial intelligence

Business intelligence (BI) converts organisational data into reports, dashboards and analysis that support monitoring and decisions. Analytics may be descriptive (what happened), diagnostic (why it happened), predictive (what may happen) or prescriptive (what action may be useful). These categories describe different analytical purposes rather than a guarantee of increasing accuracy. Predictive models estimate patterns from data and can fail when conditions change or training data do not represent the population where the model is used.

Data pipelines collect, clean, transform and move data from operational sources into analytical environments. Data warehouses are commonly designed for structured reporting across integrated sources; data lakes may store diverse raw or semi-structured data; lakehouse architectures combine aspects of both. Extract-transform-load and extract-load-transform processes prepare data for use. Metadata, lineage, access control and quality checks are essential because analytical errors can originate long before a model is fitted.

Artificial intelligence and machine learning can support classification, forecasting, recommendation, language processing and automation. Their use raises questions about bias, explainability, accountability, privacy, security and human oversight. A model trained on historical decisions may reproduce past discrimination. Performance should be evaluated across relevant groups and operating conditions, not only by one aggregate accuracy figure. High-impact decisions require appropriate governance, meaningful human review, appeal mechanisms and monitoring for model drift.

18. Information systems projects, risk and service management

Information systems projects deliver a defined change within constraints of scope, time, cost, quality, resources and risk. Project management includes initiation, planning, execution, monitoring and closure. A project charter identifies purpose, objectives, sponsor, boundaries and authority. Stakeholder analysis identifies people who can influence or are affected by the work. A work breakdown structure decomposes deliverables into manageable work packages, while schedules and budgets provide a basis for control.

Risk management identifies uncertain events that could affect project objectives. Risks should be described in terms of cause, event and consequence, assessed for likelihood and impact, assigned an owner and given a response. Responses may include avoidance, mitigation, transfer or acceptance. A risk register should be reviewed throughout delivery. Common information systems risks include unclear requirements, integration failure, poor data quality, supplier delay, security vulnerabilities, insufficient user adoption and unrealistic benefits assumptions.

IT service management focuses on delivering and supporting reliable technology services. Incident management restores service after disruption; problem management investigates underlying causes; change enablement controls modifications; service request management handles standard user requests; configuration management maintains information about service components. Service-level objectives should reflect business needs. Continual improvement uses performance data and user feedback to identify changes that improve reliability, cost, security and experience.

19. Business continuity, resilience and disaster recovery

Business continuity is the organisation's ability to continue delivering critical products and services during disruption. Disaster recovery focuses on restoring technology systems and data after a major incident. A business impact analysis identifies critical activities, dependencies, maximum tolerable disruption and the consequences of downtime. It helps prioritise recovery rather than treating every system as equally urgent.

Recovery time objective (RTO) is the target time within which a service should be restored. Recovery point objective (RPO) is the maximum targeted period of data loss measured in time. A service with a short RPO may require frequent replication or backups; a short RTO may require standby infrastructure and tested failover. These targets have cost implications and should be based on business impact rather than arbitrary technical preferences.

Resilience requires more than backups. Organisations should consider redundant infrastructure, alternative communications, supplier dependencies, cyber incident response, staff roles, physical risks and manual workarounds. Backups must be protected from compromise and restoration must be tested. Exercises reveal gaps in plans and clarify decision authority. After an incident, a learning-focused review should identify root causes, response strengths and corrective actions without hiding accountability.

Figure 5. Business continuity recovery targets
DISRUPTION → RESPONSE → RESTORE SERVICE
RTO = target restoration time
RPO = acceptable data-loss interval

20. E-commerce, digital platforms and electronic payments

E-commerce involves buying, selling or exchanging products and services through electronic networks. Business models include business-to-consumer, business-to-business, consumer-to-consumer and direct-to-consumer arrangements. Digital platforms connect multiple participant groups and may create network effects when value increases as more users or providers participate. Platform success depends on trust, service quality, discoverability, reliable transactions, dispute handling and fair rules.

An e-commerce system commonly includes product catalogues, search, customer accounts, shopping carts, order management, inventory, payment integration, delivery tracking, customer support and analytics. Each step creates data and operational dependencies. Payment workflows must handle authorisation, confirmation, failure, refunds, reconciliation and fraud controls. A user interface should communicate the status of a transaction clearly and avoid claiming success before the payment provider confirms it.

Digital commerce raises concerns about privacy, consumer protection, identity fraud, accessibility, misleading interfaces, cross-border taxation and platform dependence. Organisations should explain prices and terms, protect payment-related data, provide clear complaint routes and comply with relevant law. Security should be designed into the transaction lifecycle. Conversion optimisation must not rely on deceptive patterns such as hidden fees, false urgency or confusing cancellation processes.

21. Information systems in public services, education and healthcare

Public-sector information systems support identity services, taxation, licensing, records, benefits, procurement, public communication and service delivery. They can improve coordination and access, but errors may affect rights, livelihoods or eligibility for essential services. Public systems require transparency, accountability, accessibility, robust identity controls, clear appeal routes and careful handling of sensitive data. Digital-by-default services should retain appropriate alternatives for people who cannot use them.

Education information systems may manage enrolment, learning content, assessment, attendance, communication and institutional administration. They should support teachers and learners rather than reduce education to data entry or surveillance. Learning analytics can identify patterns that may warrant support, but predictions should not be treated as fixed judgements about a learner's potential. Data access should be proportionate, and children require particular attention to privacy and safeguarding.

Healthcare information systems may support electronic health records, appointments, laboratory results, prescribing, billing, telehealth and public health surveillance. Interoperability can improve continuity of care, but data exchange must preserve accuracy, confidentiality and appropriate access. Incorrect records can create clinical risk. Systems should support professional workflows, audit access and provide safe downtime procedures. High-stakes applications require clinical governance, testing and human accountability.

22. Information systems strategy and competitive advantage

Information systems strategy explains how digital capabilities support organisational goals. Strategic alignment requires understanding the organisation's mission, customers, processes, capabilities and competitive environment. Technology choices should be assessed for their contribution to differentiation, cost efficiency, responsiveness, innovation, risk reduction and service quality. A technology investment that does not address a strategic need may consume resources without producing sustainable value.

Competitive advantage may arise when systems enable capabilities that are valuable, difficult to imitate, well organised and aligned with market needs. However, software can often be purchased by competitors. Advantage may depend more on distinctive data, process knowledge, trusted relationships, organisational learning and the ability to adapt. Outsourcing or cloud adoption may improve efficiency but can also create dependence on vendors and reduce internal capability if knowledge transfer is neglected.

Strategic planning should include an application portfolio, architecture roadmap, investment priorities, risk assessment, skills plan and benefits realisation. Systems should be reviewed for duplication, technical debt, resilience and changing business relevance. Governance must balance standardisation with local needs. Strategy is not a static document: it should be revised as customer expectations, technology, regulation and organisational priorities change.

23. Vendor management, procurement and outsourcing

Organisations acquire information systems through internal development, commercial products, cloud subscriptions, managed services or combinations of these approaches. Procurement should begin with a clear statement of need and requirements, not a predetermined product. Evaluation criteria may include functional fit, security, privacy, accessibility, interoperability, support, supplier viability, total cost of ownership and exit arrangements. Demonstrations should use realistic scenarios and involve actual users.

Vendor due diligence examines financial stability, technical capability, service history, subcontractors, data locations, security assurance, incident notification, business continuity and compliance obligations. Contracts should define service levels, responsibilities, data ownership, permitted use, confidentiality, audit rights, breach response, change control, termination and data return or deletion. Legal and procurement specialists should review high-risk arrangements. A low subscription price may conceal implementation, integration, training, storage, support and exit costs.

Outsourcing does not transfer all accountability. The organisation remains responsible for deciding whether the service is appropriate, controlling access, monitoring performance and protecting stakeholders. Concentration risk can arise when many critical services depend on one provider. Exit planning should identify data formats, migration support, transition time, service continuity and the feasibility of switching. Vendor relationships require ongoing monitoring rather than a one-time approval.

24. Systems implementation, testing and organisational adoption

Implementation converts a designed solution into an operating service. It includes configuration, integration, data migration, security setup, training, user acceptance, cutover and support. Migration is particularly risky because source data may contain duplicates, inconsistent formats, missing fields or outdated records. Data cleansing rules should be agreed with business owners, and migration should be rehearsed using representative data before production cutover.

Testing verifies whether the system meets functional and non-functional requirements. Test cases should include normal use, boundary conditions, invalid inputs, permissions, concurrent activity, failure recovery and accessibility. Defects should be prioritised by severity and impact. User acceptance testing allows representative users to assess whether real tasks can be completed. Acceptance criteria should be agreed in advance to avoid subjective decisions at the end of a project.

Adoption depends on whether the system is useful, understandable, trusted and supported. Training should be role-specific and available at the time users need it. Feedback channels should allow staff to report problems and suggest improvements. Managers should monitor workarounds, help-desk requests, process completion and user experience. A successful go-live is a beginning: support, maintenance and benefits review determine whether the system becomes an effective organisational capability.

25. Professional roles, skills and career development

Information systems graduates may work as business analysts, systems analysts, application support specialists, database administrators, data analysts, IT project coordinators, service managers, cybersecurity analysts, ERP consultants, product specialists or technology officers. Job titles and responsibilities vary between organisations. Some roles require advanced technical certification, regulated responsibilities or substantial experience. Graduates should compare actual job descriptions with their competencies rather than assuming that a degree automatically qualifies them for every specialist position.

Core capabilities include systems thinking, requirements analysis, process modelling, database concepts, networking, security awareness, communication, documentation, problem-solving and teamwork. Technical skills may include SQL, scripting, software configuration, cloud concepts, analytics tools and testing methods. Equally important are stakeholder interviewing, explaining trade-offs, managing expectations and translating technical issues into business language. Professional growth involves combining technical depth with organisational understanding.

Career development should be evidence-based. Students can build a portfolio containing documented projects, process models, database designs, dashboards, requirements specifications, test plans and reflective case studies, provided no confidential data is disclosed. Practical work should be reproducible and clearly identify the student's contribution. Continuing learning is essential because platforms, threats, standards and professional practices change rapidly.

26. Research methods and evaluation in information systems

Information systems research examines technology, people, organisations and their interactions. Research questions may concern adoption, usability, implementation success, system quality, digital inclusion, security behaviour, data governance or organisational outcomes. The research approach should fit the question. Surveys can examine perceptions across a sample; interviews explore experiences; case studies investigate systems in context; experiments compare interface or intervention conditions; design science develops and evaluates an artefact.

Evaluation should distinguish technical performance from organisational outcomes. A system may meet uptime targets but fail to improve service quality. Measures can include task completion, error rates, response time, user satisfaction, adoption, process cycle time, cost, accessibility, security incidents and realised benefits. Baselines and clear definitions are essential. A before-and-after comparison may be influenced by other changes, so causal claims should be cautious unless the design supports them.

Ethical and responsible research includes informed consent, privacy, data minimisation, secure storage and transparent reporting. Researchers should avoid collecting unnecessary personal information or exposing organisational vulnerabilities. Where systems contain sensitive records, approval and access controls are essential. Evaluation findings should include limitations, unintended consequences and differences across user groups. A system should not be declared successful solely because it was delivered on schedule or within budget.

27. Emerging technologies and the future of information systems

Emerging technologies include generative AI, machine learning, Internet of Things devices, edge computing, blockchain, robotics, extended reality and advanced automation. Their significance depends on the problem being addressed and the maturity of the technology. Internet-connected sensors can provide real-time operational data, while edge computing processes information closer to where it is generated. Distributed ledgers can support shared records in some contexts, but they do not automatically guarantee truth, privacy or efficient governance.

Generative AI can assist with drafting, coding, summarisation, search and interaction with information systems. Risks include inaccurate output, confidential data leakage, intellectual property concerns, bias, prompt injection and overreliance. Organisations should define approved use cases, assess vendors, protect data, validate outputs and retain human accountability. AI-generated content should not be treated as verified simply because it is fluent. High-impact uses require stronger testing, monitoring and appeal arrangements.

Future-ready information systems professionals need adaptable foundations rather than dependence on one tool. They should understand data, networks, security, architecture, human factors, governance and organisational change. Continuous learning should include technical practice and critical evaluation of social consequences. Sustainability also matters: digital systems consume energy and materials, generate electronic waste and depend on global supply chains. Responsible design considers lifecycle impacts, accessibility and long-term maintainability.

28. Integrated case study: digitising a service organisation

Consider a regional training institution that manages applications, enrolment, fees, class schedules, assessment and learner support through disconnected spreadsheets and paper forms. Staff re-enter the same information, learners receive inconsistent updates and managers cannot obtain a reliable view of enrolment or outstanding payments. A technology-first response might purchase an enterprise platform immediately. A systems approach first maps the current process, identifies data owners, consults learners and staff, reviews legal obligations and establishes measurable objectives.

A proposed solution could include a secure learner information system, role-based access, online application forms, payment-provider integration, timetable management, assessment records and management reporting. Requirements should cover usability, accessibility, language, mobile connectivity, privacy, availability and data export. The institution should assess whether a packaged system can meet needs through configuration, and avoid unnecessary customisation. Data cleansing, migration rehearsals, staff training and support must be planned.

Success measures might include reduced application processing time, fewer duplicate records, improved payment reconciliation, accessible learner communication and higher user satisfaction. The institution should monitor service failures, security events, support demand and differences in access between learner groups. A phased rollout may reduce disruption, with feedback informing later releases. The case demonstrates that information systems success depends on people, processes, data, technology and governance operating together.

Structured university examination questions and model answers

For strong examination responses, define key terms, explain how components interact, use an organisational example and evaluate benefits, limitations and risks.

1. Define an information system.

Model answer: An organised combination of people, processes, data and technology that collects, processes, stores and distributes information to support operations, coordination, control and decision-making.

2. Differentiate data, information and knowledge.

Model answer: Data are recorded observations; information is data organised to have meaning; knowledge is understanding and judgement used to interpret information and guide action.

3. Identify five dimensions of information quality.

Model answer: Accuracy, completeness, consistency, timeliness, relevance, validity, accessibility and uniqueness are common dimensions.

4. Explain the input-process-output-feedback model.

Model answer: Inputs enter a system, processing transforms them, outputs provide results, feedback reports performance and control guides corrective action.

5. What is enterprise architecture?

Model answer: A description of the organisation's business capabilities, applications, data, technology and their relationships, guided by principles and standards.

6. Distinguish batch and online transaction processing.

Model answer: Batch processing handles accumulated transactions at scheduled intervals; online processing records and responds to transactions as they occur.

7. Explain the ACID properties.

Model answer: Atomicity, consistency, isolation and durability protect the completeness and reliability of database transactions.

8. What is a decision support system?

Model answer: An interactive system using data and analytical models to help decision-makers examine alternatives and semi-structured problems.

9. State two benefits and two challenges of ERP.

Model answer: Benefits include integrated processes and shared data; challenges include cost, data migration, process change, customisation and user adoption.

10. Define a primary key and a foreign key.

Model answer: A primary key uniquely identifies a row; a foreign key references a key in another table to represent a relationship.

11. What is database normalisation?

Model answer: A process of organising relational data to reduce unnecessary duplication and update anomalies through appropriate table structures and dependencies.

12. Differentiate bandwidth and latency.

Model answer: Bandwidth is the potential data transfer capacity; latency is the time delay in communication.

13. Compare IaaS, PaaS and SaaS.

Model answer: IaaS provides computing infrastructure, PaaS provides a managed application development/deployment platform, and SaaS provides a ready-to-use application.

14. Explain the CIA triad.

Model answer: Confidentiality restricts access to authorised parties, integrity protects accuracy and authorised changes, and availability ensures access when required.

15. Differentiate privacy and security.

Model answer: Security protects systems and information against threats; privacy governs appropriate collection, use, sharing and retention of personal information.

16. Distinguish functional and non-functional requirements.

Model answer: Functional requirements specify system behaviours; non-functional requirements specify quality attributes and constraints such as performance, security and accessibility.

17. What is user acceptance testing?

Model answer: Testing by representative users to determine whether the system meets agreed business needs and acceptance criteria.

18. Explain the purpose of HCI.

Model answer: Human-computer interaction studies how people interact with technology and how systems can be designed for effective, safe and usable interaction.

19. What is IT governance?

Model answer: The structures and processes that establish decision rights, accountability and oversight for organisational technology use and investment.

20. Define digital transformation.

Model answer: The coordinated use of digital capabilities to change organisational operations, services, business models and stakeholder relationships.

21. Differentiate descriptive and predictive analytics.

Model answer: Descriptive analytics summarises what has happened; predictive analytics estimates what may happen using patterns in data.

22. Why can an AI model reproduce discrimination?

Model answer: Historical data or design choices may encode unequal treatment or under-represent groups, causing biased predictions or outcomes.

23. What is an RTO and an RPO?

Model answer: Recovery time objective is the target time to restore a service; recovery point objective is the maximum targeted period of data loss.

24. Identify key stages in an information systems project.

Model answer: Initiation, planning, requirements, design, build or configuration, testing, deployment, monitoring and closure are common stages.

25. Why is vendor exit planning important?

Model answer: It reduces lock-in risk and helps ensure that data, services and operations can be migrated or recovered when a contract ends or a provider fails.

26. What should an e-commerce payment workflow communicate?

Model answer: It should clearly show pending, confirmed, failed or refunded status and rely on verified provider responses rather than assuming a payment succeeded.

27. Why are public-sector information systems especially sensitive?

Model answer: Errors may affect rights, eligibility and access to essential services, so transparency, accountability, privacy and appeal mechanisms are important.

28. How can an organisation evaluate whether a new system creates value?

Model answer: Compare outcomes with a baseline using measures such as cycle time, error rates, cost, service quality, adoption, accessibility and realised benefits.

29. Name two research methods used in information systems.

Model answer: Surveys, interviews, case studies, experiments, observation and design-science research are examples.

30. Explain why a systems approach is necessary for digital transformation.

Model answer: Outcomes depend on people, processes, data, technology and governance together; changing software alone may leave underlying problems unresolved.

Chapter synthesis and revision guide

Information systems should be understood as socio-technical arrangements rather than isolated software. Their effectiveness depends on the alignment of people, processes, data, technology and governance. Data becomes useful information through appropriate processing and interpretation, while organisational knowledge combines information with experience and judgement. Information quality and responsible data management are essential to reliable decisions.

Operational systems record transactions; management information systems provide structured reporting; decision support systems help examine alternatives; and enterprise platforms integrate processes across functions. Databases, networks and cloud services provide important technical foundations, while cybersecurity, privacy, accessibility and governance protect organisational and stakeholder interests.

Revision sequence: definitions and evolution → data and information quality → system components and architecture → business processes → transaction processing → management and decision support → enterprise systems → databases → networks and cloud → cybersecurity and privacy → analysis and development → HCI and governance → analytics and AI → projects and resilience → digital strategy and professional practice.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.