HKIE Professional Assessment - Information Discipline study materials
HKIE Professional Assessment - Information Discipline study resources

HKIE Professional Assessment - Information Discipline study plan

HKIE Professional Assessment - Information Discipline · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Information Discipline (content domains not enumerated in source)

  • Map the full Information Discipline syllabus into a personal topic inventory, tagging each item as familiar, shaky, or unknown

  • Draft a one-page summary of the discipline's scope and how it differs from the other HKIE disciplines, written from memory and then corrected

  • List the governing ordinances, regulations and codes that recur across the discipline and note which body issues each

  • Set up a spaced-repetition deck seeded with 40 terms drawn from your topic inventory

Your checkpoint

A dated topic inventory spreadsheet with every syllabus item tagged and a count of known versus unknown items

Week 2

Information Discipline (content domains not enumerated in source)

  • Explain, in writing, the professional and ethical duties an engineer owes to the public, employer and profession

  • Compare the roles of the engineer, the contractor and the client across a typical project lifecycle

  • Identify the statutory and contractual routes for reporting unsafe or non-compliant work

  • Summarise the disciplinary and registration framework that applies to engineers in Hong Kong

Your checkpoint

A 600-word briefing note on professional conduct and statutory duties, cross-checked against at least three primary sources

Week 3

Information Discipline (content domains not enumerated in source)

  • Trace the information lifecycle from requirements capture through design, build, operate and decommission

  • Describe how requirements are elicited, recorded and verified, and where traceability is lost in practice

  • Distinguish functional from non-functional requirements and give three engineering examples of each

  • Sketch a data or information flow for a small system, marking each handover between parties

Your checkpoint

A one-page information lifecycle diagram with a 300-word commentary on where handover risk concentrates

Week 4

Information Discipline (content domains not enumerated in source)

  • Explain the purpose and structure of a quality management system and how it is audited

  • Describe configuration and change control, including baselines, versioning and approval routes

  • Outline the main information-security principles (confidentiality, integrity, availability) and how they map to controls

  • Summarise the data-protection obligations that attach to personal data held by an engineering organisation

Your checkpoint

A two-page comparison table of quality, configuration and security controls, each with its purpose and an audit question

Week 5

Information Discipline (content domains not enumerated in source)

  • Describe how risk is identified, assessed, treated and monitored across an engineering project

  • Explain the role of standards and codes of practice in setting acceptable engineering practice

  • Outline the main procurement and contract models and the information obligations each creates

  • Summarise the interface between engineering delivery and the wider construction or operations programme

Your checkpoint

A risk register for a hypothetical project with at least ten entries, each with a treatment and an owner

Week 6

Information Discipline (content domains not enumerated in source)

  • Explain how emerging technology (automation, data analytics, connected systems) changes information practice

  • Describe the assurance and verification steps needed before relying on automated or model-based outputs

  • Outline the sustainability and whole-life considerations that bear on information decisions

  • Draft a short argument for or against adopting a new technology in a regulated engineering setting

Your checkpoint

A 500-word position paper on one emerging technology, with three assurance questions a reviewer should ask

Week 7

Information Discipline (content domains not enumerated in source)

  • Rehearse structuring a written answer to a scenario question under time pressure

  • Practise extracting the actual question from a long scenario and stating assumptions explicitly

  • Self-mark two practice answers against the syllabus and log every gap found

  • Convert each logged gap into a revision action with a date

Your checkpoint

Two timed practice answers plus a gap log where every entry has a scheduled revision action

Week 8

Information Discipline (content domains not enumerated in source)

  • Consolidate weak areas identified in the gap log, closing at least 80 per cent of them

  • Recite the key statutes, codes and bodies from memory without prompts

  • Complete a full mock under exam conditions and mark it honestly

  • Write a one-page pre-exam checklist covering timing, structure and common traps

Your checkpoint

A marked mock result with a one-page checklist and a closed-gap count

Milestones

Week 2: Can state the engineer's core professional duties and the relevant statutory framework from memory, with no more than two errors

Week 4: Can explain the information lifecycle, quality management, configuration control and security principles without notes

Week 6: Can construct a defensible risk register and justify each treatment in one sentence

Week 8: Mock score is consistent with a comfortable pass and the gap log is largely closed