ICSAN MIS study materials
ICSAN MIS study resources

ICSAN MIS study plan

ICSAN MIS · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Foundations of information systems and their role in organisations & Information systems strategy, governance and alignment with corporate objectives

  • Define each major information system type (TPS, MIS, DSS, EIS, OAS) and state one concrete organisational decision each supports.

  • Map the input-process-output-data-feedback model onto a named organisation you know and identify two failure points in that flow.

  • Explain how IS strategy must cascade from corporate objectives, using at least two alignment models (for example strategic grid and Henderson-Venkatraman-style external/internal alignment logic) in your own words.

  • Draft a one-page argument for why an IS investment should be rejected on strategic-alignment grounds, citing two criteria.

Your checkpoint

A two-page summary sheet containing a system-type comparison table, one alignment model diagram redrawn from memory, and a 200-word alignment critique of a real or hypothetical IS project.

Week 2

Corporate governance, risk management and IT controls & Information systems development, acquisition and project management

  • Distinguish governance from management by assigning five named IT decisions (principle, architecture, infrastructure, investment, prioritisation) to the correct accountable body.

  • Construct a risk register with five IT risks, each scored on likelihood and impact with a stated response (avoid, mitigate, transfer, accept).

  • Classify ten IT controls as preventive, detective or corrective and as general or application controls.

  • Sequence the phases of a structured SDLC and compare it with an agile delivery approach on two dimensions (change tolerance, documentation).

  • Identify three causes of project failure and match each to a specific control or governance mechanism that would have prevented it.

Your checkpoint

A risk-and-controls workbook page: five scored risks, ten classified controls, and a phase-by-phase SDLC table with agile comparison notes.

Week 3

Business applications: ERP, CRM, SCM and enterprise systems & Data management, databases and business intelligence

  • Explain how ERP, CRM and SCM systems differ in primary process focus, master data ownership and typical integration points.

  • Trace one end-to-end order-to-cash process across ERP and CRM, naming the data created at each step.

  • Define the core database concepts (entity, attribute, primary key, foreign key, normalisation to third normal form) and normalise a small unnormalised table yourself.

  • Differentiate OLTP from OLAP workloads and describe how a data warehouse and star schema support business intelligence reporting.

Your checkpoint

A one-page process-and-data map of order-to-cash plus a hand-normalised table carried from unnormalised form to 3NF with keys marked.

Week 4

Corporate governance, risk management and IT controls & Information systems development, acquisition and project management & Data management, databases and business intelligence

  • Re-derive control classifications and risk scoring without notes, then correct any gaps against week 2 material.

  • Produce a project charter outline for a data warehouse initiative including scope, stakeholders, success measures and top three risks.

  • Apply data quality dimensions (accuracy, completeness, timeliness, consistency) to a BI reporting scenario and recommend two remediation actions.

  • Explain segregation of duties in an ERP environment and identify two conflicting role combinations to prohibit.

Your checkpoint

A timed 60-minute closed-book practice paper of 25 mixed questions across domains 3, 4 and 6, scored with a written list of every missed concept.

Week 5

E-business, digital transformation and emerging technologies & Information security, cybersecurity and privacy

  • Categorise e-business models (B2B, B2C, C2C, B2B2C) and match each to a distinct revenue and trust challenge.

  • Explain digital transformation as a change in operating model, not just technology adoption, with two organisational enablers.

  • Describe three emerging technologies (for example cloud computing, RPA, AI/analytics) and state one governance or risk implication of each.

  • Apply the CIA triad to a named system and select one control per property.

  • Outline the phases of incident response and the role of a business continuity and disaster recovery plan, distinguishing RTO from RPO.

Your checkpoint

A two-column table of ten threats against matched controls with CIA property labelled, plus a 150-word incident response walkthrough for one scenario.

Week 6

Information security, cybersecurity and privacy & IT service management, operations and support & Professional ethics, law and regulatory issues in information systems

  • Explain privacy principles (lawful basis, purpose limitation, data minimisation, retention, subject rights) and apply them to a customer analytics use case.

  • Summarise the ITIL-style service lifecycle stages and distinguish incident, problem and change management with one example each.

  • State the professional and ethical obligations of an IS professional in three concrete conflict scenarios (data misuse, pressure to skip controls, undisclosed vendor interest).

  • Identify the main legal and regulatory themes relevant to information systems (data protection, computer misuse, intellectual property, records retention) and note why jurisdiction matters.

Your checkpoint

A one-page ethics-and-law quick reference: five privacy principles, three ITSM definitions, three ethical conflict responses, and four legal themes with one jurisdictional caveat.

Week 7

Foundations of information systems and their role in organisations & Information systems strategy, governance and alignment with corporate objectives & Corporate governance, risk management and IT controls & Information systems development, acquisition and project management & Business applications: ERP, CRM, SCM and enterprise systems

  • Produce condensed recall notes for the five heaviest domains, each limited to one page.

  • Answer 40 mixed practice questions under timed conditions and log every error by domain and by error type (knowledge gap, misread, reasoning slip).

  • Explain aloud, without notes, the linkage between corporate objectives, IS strategy, governance and controls in under three minutes.

  • Re-teach two weak concepts from week 4 and week 5 using a fresh worked example you construct yourself.

Your checkpoint

Five one-page recall sheets plus an error log classifying at least ten mistakes by domain and error type, with a prioritised revision list.

Week 8

Data management, databases and business intelligence & E-business, digital transformation and emerging technologies & Information security, cybersecurity and privacy & IT service management, operations and support & Professional ethics, law and regulatory issues in information systems

  • Complete one full-length timed mock examination covering all ten domains and record the score per domain.

  • Close the top five items on the week 7 error log by rewriting each as a rule or checklist you can apply under pressure.

  • Rehearse scenario-style answers by writing two short structured responses (situation, analysis, recommendation) in exam time limits.

  • Finalise a one-page formula-and-framework sheet covering alignment models, risk scoring, control types, CIA, RTO/RPO and privacy principles.

Your checkpoint

A completed timed mock with a per-domain score breakdown, a closed-out error log, and a single-page framework sheet used during the mock.

Milestones

Week 2: Can classify ten controls and score five risks correctly with notes closed, and can name the five IT governance decisions and their accountable owners.

Week 4: Scores at least 60% on the closed-book 25-question paper across domains 3, 4 and 6, with every missed concept written down.

Week 6: Can state the CIA triad controls, RTO versus RPO, three ITSM definitions and five privacy principles from memory in under ten minutes.

Week 8: Achieves at least 65% overall on the full timed mock with no single domain below 50%, and has closed all top-five error-log items.