The full module text consolidating all lessons on producing an HCI development report, which learners read straight through as the primary reading for documenting a design project from user needs to final prototype evaluation.
Topics
This module covers 7 topics. Open a topic to see its subtopics.
Module Content
24 items.
-
-
A lesson defining the HCI Development Report as a formal document recording every project stage, contrasting it with informal lab notebooks or journals and explaining its professional audience and traceability role.
-
A lesson on requirements documentation, covering how to capture findings from the research and planning phase so that user needs, defined behaviours, and constraints form a verifiable foundation for later design decisions.
-
A lesson on design process documentation, explaining how to record decisions, experiments, and iterations as transparent, evidence-based reasoning for stakeholders and evaluators rather than as bureaucratic paperwork.
-
A lesson on evaluation documentation, showing how to report usability testing methods, findings, and the traceable chain from observed user behaviour to resulting design changes.
-
A lesson on final implementation documentation, guiding learners to write an honest capstone record of what was built, the rationale behind it, and how faithfully it matches the original requirements and prototypes.
-
A lesson on documenting group collaboration, covering how to record planning, task division, negotiation, review, and reflection so individual contributions and teamwork processes are made visible.
-
A lesson on report structure, referencing, and presentation, teaching learners to organise a professional HCI report into a coherent evidence-based narrative with proper citation and polished formatting.
-
Introduces what an HCI Development Report is, why it differs from informal documentation, and how learners should approach creating a formal structured record of their design project from user needs through to prototype evaluation.
-
Explains how to capture and document user needs, functional and non-functional requirements, and design constraints, giving learners a guide to building the research and planning foundation that underpins all subsequent design decisions.
-
Covers how to record design decisions, experiments, and iterative changes throughout a project, helping learners create a transparent, evidence-based account of how and why their design evolved over time.
-
Describes how to formally document usability evaluations, including methods used, findings gathered, and how results influenced design revisions, enabling learners to demonstrate that their design choices were grounded in observed user behaviour.
-
Explains how to write the closing section of an HCI project report by documenting what was built, how faithfully it reflects earlier design intentions, and honestly accounting for any gaps between planned and delivered outcomes.
-
Covers how to record team members' individual contributions, collaborative processes, decision-making, and reflections in group projects, helping learners and instructors assess both collective output and each person's role.
-
Guides learners on how to organise a professional HCI report with a coherent structure, apply correct academic referencing, and present the document to communicate a clear, evidence-backed design narrative to evaluators.
-
Guides learners on how to organise a professional HCI report with a coherent structure, apply correct academic referencing, and present the document to communicate a clear, evidence-backed design narrative to evaluators.
-
A reading that defines the HCI development report as a structured, selective record spanning requirements through evaluation, explaining its purpose, audience, and the kinds of evidence and design rationale it must contain, used by learners as the conceptual foundation before drafting their own project report.
-
A reading on requirements documentation that covers deriving functional and non-functional requirements from user research — who the users are, their goals, and current problems — and recording the rationale behind each, used by learners as a guide when writing the requirements section of their project report.
-
A reading on documenting the design process, covering idea generation, sketches and low-fidelity prototypes, design rationale, higher-fidelity versions, and how designs changed across iterations, used by learners to assemble a design section that explains reasoning rather than just displaying screens.
-
A reading on evaluation documentation explaining how to record usability methods, participants or evaluators, tasks and setting, findings with supporting evidence and severity ratings, and the design iterations those findings triggered, used by learners to make their evaluation work verifiable in the report.
-
A reading on final implementation documentation covering how to describe the delivered interface — screens, components, navigation, and key interactions — along with implementation decisions, trade-offs, and known limitations, used by learners when writing the section that accounts for what was actually built.
-
A reading on documenting group collaboration that addresses recording individual contributions, how decisions were made collectively, and how the team managed the project, used by student teams to demonstrate process quality alongside design quality in a group report.
-
A reading on report structure, referencing, and presentation covering the standard section sequence (introduction, method, findings, discussion), citation practices, and visual presentation conventions that make a report readable to an outside audience, used by learners when organizing and polishing their final submission.
-
A consolidated single-page compilation of all topics in the module, from the introduction to development reporting through requirements, design process, evaluation, implementation, collaboration, and report presentation, useful for review or as a printable reference while drafting a full project report.