Information Discipline: Professional Engineering Judgement in Information Systems
The Information Discipline covers the professional practice of information engineering: software and systems, data, networks, cybersecurity, service delivery and the management of digital change. The HKIE Professional Assessment tests whether you can exercise independent engineering judgement in that space, explain trade-offs, and accept professional accountability - not whether you can quote product features. Because the source does not enumerate sub-domains, prepare for cross-cutting questions that start from a realistic project or operational problem.
What assessors look for
- Requirements and traceability: functional needs, constraints, acceptance criteria and evidence that design decisions link back to stakeholder requirements.
- Architecture and non-functional behaviour: availability, performance, scalability, maintainability, interoperability and total cost of ownership; explain why one option beats another.
- Security, privacy and risk: data classification, least privilege, secure development, incident response, and Hong Kong obligations such as the Personal Data (Privacy) Ordinance.
- Delivery and operation: phased rollout, migration, rollback, change control, testing, observability, service continuity and measurable benefits.
- Professional conduct: honest reporting, conflict-of-interest handling, IP and licensing awareness, safety and environmental considerations, and clear communication to technical and non-technical audiences.
Worked example
A clinic asks you to replace a paper appointment system. A weak answer lists a database and a mobile app. A professional answer first classifies patient data, defines availability and recovery targets, and sets acceptance criteria for booking accuracy and waiting time. It compares build versus buy against integration effort, vendor lock-in and support cost; specifies role-based access and audit logging; plans a pilot with rollback; and defines post-launch measures. The reasoning shows traceability from clinical need to design, risk treatment and operational readiness.
Traps that cost marks
- Describing tools or vendors instead of engineering decisions and trade-offs.
- Treating security, privacy and maintainability as afterthoughts.
- Claiming benefits without baseline, metric or verification method.
- Omitting transition, rollback and operational ownership.
- Presenting team output as personal competence without stating your decisions.