ISYS90026 Concepts in Information Systems
ISYS90026 Overview
- University of Melbourne
- S2 2026
- 11 chapters
- Information Technology
ISYS90026 Concepts in Information Systems is a postgraduate, framework-heavy strategy subject in the Master of Information Systems — it studies the effective use of IT by people and organisations ("IT in context"), not the technology itself.
- Assessed by Tutorial participation 10% · Group case 15% · Individual case 25% · Final Exam 50% — Final Exam is a hurdle
- Key terms Information System (vs IT), Systems thinking, Social informatics (Kling), Core competence (Prahalad & Hamel)
- How to prepare Treat ISYS90026 as a framework-application gym, not a memorisation test: for every chapter, learn the framework once…
What you get in the full ISYS90026 Exam Bible
- 11 chapters, 116 pages — every examinable topic, week by week
- 19 original practice questions in the Final Exam format
- 11 worked examples, solved the way ISYS90026 marks
- 19 computed figures, redrawn from the course’s own numbers
- Exam-morning plan for the Final Exam (50%) — what to revise last, where marks are lost
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full exam bible.
How ISYS90026 is assessed
| Component | Weight | Format |
|---|---|---|
| Tutorial participation | 10% | In-class participation, Weeks 2-11 (ILOs 1-7) |
| Group case | 15% | Groups of 3, ~2,500 words case analysis, mid-semester (due Mon Week 7), ILOs 1-7 |
| Individual case | 25% | ~1,500 words individual case analysis, end of semester (due Mon Week 12), ILOs 1-4, 6, 7 |
| Final Exam · hurdle | 50% | One written 2-hour closed-book invigilated exam (10 MCQ + 4 essay sections, 100 marks), exam period |
What other students are asking about ISYS90026
- Where can I find lecture notes or study guides for ISYS90026 at UniMelb?
- The ISYS90026 study guide in AskSia Library covers Concepts in Information Systems in 11 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in ISYS90026, and how much is it worth?
- Yes. In the offering this AskSia Library guide is built from, Final Exam carries 50% of the ISYS90026 mark; the full split is Tutorial participation 10%, Group case 15%, Individual case 25%, Final Exam 50%.
- What does ISYS90026 cover on core competency?
- In AskSia Library's ISYS90026 guide, the Core Competency chapter explains prahalad & Hamel · roots-of-competitiveness · core products · 3 tests · IT-supported competencies.
- What does ISYS90026 cover on competitive advantage?
- In AskSia Library's ISYS90026 guide, the Competitive Advantage chapter explains porter Five Forces · value chain · generic strategies · Porter & Millar information intensity matrix.
- What does ISYS90026 cover on case study analysis and academic writing?
- In AskSia Library's ISYS90026 guide, the Case Study Analysis and Academic Writing chapter explains ellet case method · problem/decision/evaluation cases · argument structure · APA referencing · writing for a general audience.
What ISYS90026 covers
ISYS90026 moves across eleven framework-driven topics, from systems thinking and core competence to competitive advantage, business-IT alignment and maturity, IT governance, sourcing, change management, responsible business and an AI-transformation synthesis — each chapter below drills the same exam skill of mapping a named framework onto an unseen case.
IS Foundations and Systems Thinking
What is Information Systems · IT-in-context · systems thinking · social informatics · roles around the systemWeek 1 sets the premise the whole subject rests on: Information Systems is about the effective use of IT by people and organisations — not the technology itself.
- IS vs IT — IT is the artefact; IS is the socio-technical whole (people + process + data + context)
- IT-in-context — why the same technology succeeds in one firm and fails in another
- Systems thinking — interdependence, feedback loops, boundaries and emergent behaviour
- Leavitt's diamond — People, Structure, Task and Technology are coupled; change one, re-fit the others
- Kling's social informatics — ICTs do not operate in a vacuum; design, use and consequences are context-shaped
- Co-evolution — tech and social practice adapt to each other (not a one-way tech → society street)
Core Competency
Prahalad & Hamel · roots-of-competitiveness · core products · 3 tests · IT-supported competenciesCore competency is ISYS90026's internal strategy lens: a core competence is the collective learning in an organisation — the ability to coordinate diverse skills and integrate multiple technologies — not a product, a patent or a single person.
- Core competence defined — collective learning that coordinates skills and integrates technologies (internal lens, vs Porter's external lens)
- What it is NOT — not a product, a patent, a single technology, or a star employee; it must cross organisational boundaries
- The tree metaphor — roots = competencies → trunk = core products → branches = business units → leaves/fruit = end products
- Core product vs end product — intermediate embodiments (engines, chips, a navigation module) vs what the customer finally buys
- The three tests (MVP) — access to a wide variety of Markets, significant contribution to customer Value, Protected-from-imitation
- The multiplier effect — one competence feeds many products (Canon's competence matrix); investment is leveraged repeatedly
Competitive Advantage
Porter Five Forces · value chain · generic strategies · Porter & Millar information intensity matrixCompetitive advantage is ISYS90026's external lens: a firm's market positioning relative to its rivals, where value means price versus performance.
- External vs internal lens — competitive advantage (how you compete) vs core competence (what you are good at); value = price vs performance
- Three generic strategies — cost leadership, differentiation, focus, set by competitive scope × source of advantage
- Stuck in the middle — why pursuing cost leadership and differentiation industry-wide destroys advantage
- Porter's Five Forces — rivalry (centre) plus new entrants, supplier power, buyer power and substitutes sharing industry profit
- When each force is strong — the specific conditions that erode industry profitability
- Neutralising the forces — how each generic strategy defends against the strongest forces
Case Study Analysis and Academic Writing
Ellet case method · problem/decision/evaluation cases · argument structure · APA referencing · writing for a general audienceThis is the meta-skill chapter behind every mark in ISYS90026 — it is the method used in the group case (15%), the individual case (25%) and all four essay sections of the final exam.
- What a case study is — a simulated business situation giving sufficient but unsorted information (a jigsaw), with no single right answer you must make your own meaning from
- Case analysis as reasoning — act like a detective: build a logical bridge from a vague problem to a concrete solution using theory plus evidence
- Theory as a lens — a framework filters out noise and tells you which facts matter; no single theory explains a whole problem
- Quality over quantity — 'Analytical Alice' (a few relevant frameworks used deeply) beats 'Theory Ted' (cramming fifteen); more theories does not mean deeper analysis
- The three case types — Problem (find the cause), Decision (choose and justify), Evaluation (judge performance) — read the type before you write
- The What / Why / How architecture — position statement, argument, action plan — the spine of every case essay and exam answer
Business-IT Alignment
Strategic Alignment Model · Luftman & Brier · enablers & inhibitors · 12 alignment stepsBusiness-IT alignment is applying IT in harmony with an organisation's strategy, goals and needs — and the exam-critical point is that it is bidirectional co-design with shared risk, not "IT obeying the business".
- Defining alignment — co-design, not obedience; shared accountability and joint risk
- IT value: support activity vs strategic component (Blockbuster vs Netflix; Domino's)
- Strategic Alignment Model (SAM) — four domains on a business/IT × strategy/operations grid
- The two SAM links — strategic fit (vertical) and functional integration (horizontal)
- The four perspectives — strategy execution, technology transformation, competitive potential, service level
- Enablers vs inhibitors (Luftman & Brier) — mirror lists topped by senior-executive support
Business-IT Alignment Maturity
Luftman SAMM · 6 maturity criteria · 5 maturity levels · assessing & improving alignmentWeek 6 moves from how to align IT and business (Chapter 5's Strategic Alignment Model) to how aligned you actually are.
- SAMM — Luftman's (2000) Strategic Alignment Maturity Model: score six criteria, then set one overall level
- Alignment as an evolutionary journey — maturity is climbed a rung at a time and can slip back, never reached in one leap
- The six criteria (C·V·G·P·S·S) — Communications, Value Measurement, Governance, Partnership, Scope & Architecture, Skills
- The five levels — 1 Initial/Ad Hoc → 2 Committed → 3 Established/Focused → 4 Improved/Managed → 5 Optimized
- Value centre vs cost centre — the tell-tale of low vs high maturity (technical metrics vs business outcomes)
- Root cause vs evidence — the exam move: symptoms are evidence; the single failing criterion is the root cause
IT Governance
Weill & Ross · 5 key IT decisions · 6 governance archetypes · governance arrangements matrixWeek 7 opens Theme 3 with Weill & Ross (2005): IT governance is specifying the decision rights and accountability framework that steers desirable behaviour in the use of IT, so that scattered IT choices still add up to the strategy.
- Governance vs management — governance is oversight and decision rights (who decides); management is day-to-day execution (doing the work)
- The three questions — WHAT IT decisions, WHO has the decision right and accountability, HOW it is enforced
- IT Principles — the strategic role of IT and desirable IT behaviours (cost centre vs strategic partner; digital-first)
- IT Architecture vs IT Infrastructure — the standardisation blueprint vs the shared foundational services (the #1 domain mix-up)
- Business Application Needs & IT Investment — specific app requirements, and how much to spend, fund and track value
- The six archetypes — Business Monarchy, IT Monarchy, Federal, IT Duopoly, Feudal, Anarchy (a political metaphor by centralisation)
IT Sourcing and Outsourcing
Cullen sourcing lifecycle · in-house vs outsource vs offshore · critical capabilities · risks & vendor managementIT sourcing is the second half of ISYS90026's Theme 3 (IT Governance & Sourcing): the build-or-buy decision and everything that follows it.
- Build-or-buy — in-house ('build it yourself') vs outsourcing ('buy it from others'); a strategic decision tied to core competence
- The build-or-buy gate — keep core/strategic/sensitive/control-critical work in-house; outsource commodity, mature, non-core work
- Sourcing options spectrum — in-house → onshore (domestic) → offshore (different country) → cloud (XaaS); control falls as you move right
- Offshoring ≠ outsourcing — offshoring is about location, outsourcing about ownership; you can offshore in-house via a captive centre
- The cloud stack — IaaS (rent hardware) vs PaaS (rent the platform) vs SaaS (rent the finished service); differ by who manages which layer
- Drivers & risks — efficiency/focus, strategic agility and tech maturity vs loss of control, security/IP, vendor viability and hidden costs
IT Change Management
Kotter 8-step model · why transformations fail · urgency, coalition, vision · sustaining changeWeek 9 turns from technology to people: change management is people management.
- Change management is people management — the technology is the easy part; getting people to adopt the new way is the hard part
- Mandatory ≠ successful — you can order people to use a system, but you cannot order the change to succeed (compliance is not commitment)
- Why people resist — lack of trust, lack of choice, feeling forced, stress, past failures, helplessness, fear of being judged
- The transition model — reduce the pull of current comforts, emphasise current pains, demonstrate the gains, eliminate the new pains
- Ward & Elvin benefits chain — IS/IT functionality enables business changes → outcomes → benefits → objectives (break any link, no benefit)
- PPTO — an IT change almost always forces organisational change across People, Process, Technology and Organisation
Responsible Business: Ethics, CSR and Sustainability
Porter & Kramer shared value · IS ethics · sustainability/Green IT · DEI in ISTheme 4 asks whether being responsible can be a source of advantage rather than a cost.
- Shared value — Porter & Kramer's core idea: link competitive advantage and CSR so they reinforce each other rather than trade off
- Four weak CSR justifications — moral obligation, sustainability, license to operate and reputation are each insufficient as the primary driver
- Why 'license to operate' is weak — it hands agenda-setting power to external stakeholders whose priorities may not match the firm's strengths
- Responsive vs Strategic CSR — mitigate harm from current activities vs transform value-chain activities for unique advantage (the most-tested split)
- Inside-out vs outside-in linkages — how your activities affect society vs how the competitive context affects you
- The competitive diamond — factor conditions, local demand conditions, related & supporting industries, and context for strategy & rivalry
AI Transformation in Business and Exam Synthesis
practical AI in business (guest) · cross-theme integration · framework-to-case application · exam strategyThis final ISYS90026 topic does two jobs.
- Adopting vs adapting — tools bolted on (minor gains) vs workflows redesigned around AI (real transformation); 78% use gen AI but only 21% redesign a workflow
- Start with the problem, not the technology — why 95% of enterprise AI projects fail and most firms stay stuck exploring
- Three Horizons of AI-enabled work (IFTF) — H1 powerful but limited, H2 rapid advance (agentic, domain models), H3 fundamental transformation
- Five leadership AI mindsets — unaware, paralysed, checkbox, false summit, and the goal: strategic
- The Frontier AI organisation (Harvard) — Foundations → Modern AI-driven IT → back office → front office, on the Process/People/Technology pillars
- How AI threads through the four themes — core competence, competitive advantage (Porter & Millar), alignment, governance/sourcing, change, responsible business
Across the semester you build a toolkit of named frameworks: Prahalad & Hamel core competence, Porter's Five Forces, value chain and generic strategies, Porter & Millar information intensity, Luftman's alignment model and SAMM maturity, Weill & Ross governance archetypes, the Cullen sourcing lifecycle, Kotter's 8-step change model, and Porter & Kramer shared value.
It is a no-math course: the marks live in applying the right framework to an unseen case, not reciting theory. The 50% final exam is a hurdle (you must score at least 50/100 to pass), so the course rewards being able to separate Problem from Root Cause from Evidence and to argue a committed position with case evidence — breadth across all four exam themes beats deep mastery of just one.
Worked example · free
Five Forces, generic strategy and Porter & Millar on an unseen case
- +5Five Forces (name and map all five): Rivalry is rising because the supermarket entered, but it is blunted by PetPantry's differentiation; Threat of new entrants is low because the proprietary pet-health dataset raises entry barriers; Buyer power is lowered because subscribers are locked in by personalised plans; Supplier power is low because many contract manufacturers compete for the work; Threat of substitutes (generic shelf food) is weak because it lacks personalisation.
- +2Synthesise: the structure favours PetPantry because its data moat blunts the two strongest forces — new entrants and rivalry. The copycat's customer losses are the evidence that generic recipes cannot reproduce the matching advantage.
- +2Generic strategy: focused differentiation — a narrow segment (health-conscious pet owners) served with a unique, hard-to-copy offering, not industry-wide cost leadership. Chasing both at once would leave PetPantry "stuck in the middle".
- +4Porter & Millar: IT raises the information intensity of both the product and the value chain; the nutrition-matching algorithm is the barrier to imitation (the rival sees the outcome but not the data or recipe = causal ambiguity); compounding proprietary health data widens the moat over time.
Key terms
- Information System (vs IT)
- IS = IT plus the people, processes and organisational context that put it to use; the discipline studies the socio-technical whole, not the artefact alone. The course's framing premise is "IT in context".
- Systems thinking
- Examining how interrelated parts interact — interdependence, feedback loops, boundaries, emergent behaviour — rather than studying each part in isolation, so designers avoid short-sighted, isolated fixes.
- Social informatics (Kling)
- ICTs do not operate in a vacuum; their design, use and consequences are shaped by human, institutional and social context, and social and technical systems co-evolve.
- Core competence (Prahalad & Hamel)
- The collective learning that lets an organisation coordinate diverse skills and integrate technologies; it must pass three tests — access to many markets, contribution to customer benefit, and difficulty of imitation.
- Generic strategies
- Porter's mutually exclusive routes to advantage — cost leadership, differentiation, or focus; pursuing more than one industry-wide leaves a firm "stuck in the middle".
- Porter's Five Forces
- An industry-structure tool (rivalry, new entrants, supplier power, buyer power, substitutes) that predicts baseline profitability; IT can unfreeze and reshape the forces.
- Value chain
- The architecture of value execution — primary activities (inbound logistics, operations, outbound logistics, marketing & sales, service) plus support activities; managing linkages is a hard-to-imitate advantage.
- Business-IT alignment
- Applying IT in harmony with business strategies and needs through bidirectional co-design with shared accountability — not "IT obeying the business"; value is realised via identification, conversion and realization.
- SAMM (alignment maturity)
- Luftman's Strategic Alignment Maturity Model — six criteria (Communications, Value Measurement, Governance, Partnership, Scope & Architecture, Skills) assessed across five levels from Ad Hoc to Optimized.
- IT governance / decision rights
- Weill & Ross's framework specifying who has decision rights and accountability over five IT decision domains, allocated via six archetypes (e.g. Business Monarchy, Federal, IT Duopoly, Feudal) — governance is oversight, not day-to-day management.
- Outsourcing lifecycle (Cullen)
- A five-phase model — Assess, Evaluate, Contract, Transition, Manage — stressing that you manage the whole cycle, not just the deal; the SLA is enforced in the Manage phase and outsourcing never outsources accountability.
- Shared value & Strategic vs Responsive CSR
- Porter & Kramer: Responsive CSR mitigates harm from current value-chain activities, while Strategic CSR transforms the value chain to reinforce the firm's unique strategy, creating combined social and competitive (shared) value.
ISYS90026 FAQ
How is ISYS90026 assessed?
Four components: tutorial participation (10%), a group case analysis (~2,500 words, 15%, due Week 7), an individual case analysis (~1,500 words, 25%, due Week 12), and a final exam (50%). The majority of the assessment is case discussion and analysis, staged through weekly tutorials.
Is there a final exam, and is it a hurdle?
Yes. The final exam is a 2-hour closed-book, invigilated paper (run via Respondus LockDown Browser) worth 50% and 100 marks, with 10 multiple-choice questions plus 4 essay sections. It is a hurdle: you must score at least 50/100 on the exam to pass the subject, no matter your coursework marks.
What does the exam actually test?
It rewards APPLYING named frameworks to unseen cases, not reciting theory. The four essay sections map to themes — Core Competency & Competitive Advantage, Business-IT Alignment, IT Governance & Sourcing, and Responsible Business — and you are expected to name a framework, define its parts, map them to case evidence, and judge or recommend.
What do students find hardest?
Resisting the urge to summarise the case instead of arguing a committed position, and cleanly separating Problem from Root Cause from Evidence. Close behind are framework discriminations the exam loves to test — core competence vs competitive advantage, Federal vs Feudal governance, Responsive vs Strategic CSR, and getting Kotter's eight steps in order.
How should I prepare?
Memorise each framework, then practise mapping it onto a short case using the What / Why / How structure (position, argument, action plan). Drill the "exam traps" distinctions, do the theme-based practice exams, and because the exam is a hurdle, make sure you can cover all four themes rather than only your strongest one.
Do I need to be good at maths?
No. This is a no-math, framework-heavy strategy subject — the marks come from reasoning about cases with the right framework, not calculation.
Is this page official or affiliated with the University of Melbourne?
No. This is an independent AskSia study resource for students taking ISYS90026; it is not produced, endorsed by, or affiliated with the University of Melbourne. Always confirm assessment details against the official Canvas subject page and current handbook.
Questions students ask in each ISYS90026 chapter
- What is the difference between IS and IT?
- IT is the technical artefact — hardware, software, networks and data. An information system is that technology plus the people, processes and organisational context that put it to use. The whole subject is built on this distinction ("IT in context"), and treating IS = IT is the most common Week 1 mistake. Chapter 01 · IS Foundations and Systems Thinking
- What is the difference between a core competence and a competitive advantage?
- They are complementary lenses on the same firm. A core competence (Prahalad & Hamel) is INTERNAL — what the firm is uniquely good at, built from collective learning. A competitive advantage (Porter, next chapter) is EXTERNAL — how the firm positions itself against rivals in the market. The exam explicitly tests this discrimination, so name which lens you are using and don't mix the vocabularies; a strong answer links them (a competence enables an advantage). Chapter 02 · Core Competency
- What is the difference between competitive advantage and core competence?
- Competitive advantage is the external lens — how a firm positions itself against rivals (cost, differentiation or focus). Core competence is the internal lens — what the firm is uniquely good at. They are two lenses on the same business: a core competence is a source a firm converts into a competitive position. Telling them apart is one of the most-tested exam discriminations. Chapter 03 · Competitive Advantage
- What is this chapter actually about, and why does it matter so much?
- It teaches case study analysis — the method behind the group case (15%), the individual case (25%) and all four exam essay sections. It is the highest-leverage chapter because every other framework is delivered through it: you can know all eleven frameworks and still score a pass if you write a summary instead of an argument. Chapter 04 · Case Study Analysis and Academic Writing
- Is business-IT alignment just IT doing what the business wants?
- No — that is the most common exam trap. Alignment is bidirectional co-design: business needs and technical reality are weighed together with shared accountability and joint risk. IT both supports and helps shape the strategy. Chapter 05 · Business-IT Alignment
- What is Luftman's SAMM?
- The Strategic Alignment Maturity Model (Luftman 2000) is a diagnostic that scores an organisation on six criteria — Communications, Value Measurement, Governance, Partnership, Scope & Architecture and Skills — and places it on a five-level ladder from Initial/Ad Hoc to Optimized, so you can find the weakest dimension and plan the next step up. Chapter 06 · Business-IT Alignment Maturity
- What is the difference between IT governance and IT management?
- Governance is about oversight and decision rights — who has the authority to decide, and who is accountable. Management is about execution — running IT day to day inside those rules. Choosing which laptop model to deploy is management; deciding who is allowed to make that call is governance. Treating governance as "running IT" is the most common framing error in this theme. Chapter 07 · IT Governance
- How do I decide whether to build or buy an IT system?
- Ask whether the system is part of what makes the firm uniquely competitive. Keep it in-house if it is a competitive advantage, is (or feeds) a core competence, handles sensitive or proprietary data, or needs deep specialised domain knowledge. Outsource it if it is standard, commodity, mature off-the-shelf technology outside your core competencies, or if you lack the capital and staff to build it. The rule of thumb is 'focus on what you do best, let specialists handle the rest' — but start small with a non-core service and measure performance first. Chapter 08 · IT Sourcing and Outsourcing
- Why do most IT transformations fail according to Kotter?
- For two reasons. First, the change process is complex and multi-phase, so it is prone to critical errors and skipped steps. Second, fundamental change is strongly resisted by the people it most affects. Kotter's answer is a systematic, ordered approach — his eight steps — because without one, efforts "dissolve into a list of confusing and incompatible projects that lead nowhere". Chapter 09 · IT Change Management
- What is the difference between Responsive and Strategic CSR?
- Responsive CSR is good citizenship that mitigates harm from a firm's current activities — an inside-out, harm-reduction stance. Strategic CSR transforms value-chain activities to reinforce the firm's unique strategy and improves the outside-in competitive context, creating shared value (social benefit plus competitive advantage together). This is the single most-tested distinction in Theme 4, and reversing the two is the classic lost mark. Chapter 10 · Responsible Business: Ethics, CSR and Sustainability
- What is the difference between adopting and adapting AI?
- Adopting means bolting AI tools onto existing work — rolling out a copilot or running a pilot — which yields only minor productivity gains. Adapting means redesigning the workflow around AI so the work itself changes. The exam-critical statistic is the gap: about 78% of organisations use gen AI but only ~21% have actually redesigned a workflow, which is why most see no material earnings impact. Chapter 11 · AI Transformation in Business and Exam Synthesis
How to study for the exam
Treat ISYS90026 as a framework-application gym, not a memorisation test: for every chapter, learn the framework once, then spend most of your time practising the move the exam actually rewards — mapping that framework onto a short, unseen case while explicitly separating the Problem (symptom) from the Root Cause from the Evidence.
Use the What / Why / How discipline on every essay (lead with a committed position, prove it with theory-as-lens plus case facts, close with a symmetric action plan), drill the high-frequency discrimination traps (core competence vs competitive advantage, Federal vs Feudal, Responsive vs Strategic CSR, Kotter ordering), and work the theme-based practice exams under closed-book conditions.
Because the final is a 50/100 hurdle covering all four themes, prioritise reliable breadth across the whole subject over deep mastery of a single favourite topic, and never leave an MCQ blank — there is no penalty for guessing.