TK Study

Software Engineering › Key terms › Y12 SE Project › Gantt chart

Gantt chart

Diagram Key terms bank Y12 SE Project Diagrams and tools

Also listed as: Gantt chart (specification)

Definition

Gantt chart Y12 SE Project Diagram

A bar chart showing tasks against time, with start and end dates, duration and dependencies; used to schedule and track a project.

Example: Testing cannot start until coding finishes.

Found in: syllabus, course specifications, school notes, past SDD papers.

Gantt chart (specification) Diagrams and tools Diagram

Shows tasks on an estimated timeline with self-explanatory names, estimated time, dependent tasks, dates and milestones; can allocate resources and show percentage completion, and is updated with actual v estimated times.

Example: Design (1 wk) then Build (2 wk), dependent on Design.

Found in: syllabus, course specifications, school notes, past SDD papers.

Short version to memorise (key terms bank)

Tasks against time with dependencies and milestones.

Where it is used in the test

Syllabus area: Y12 SE Project Diagrams and tools.

Question types it can appear in

Where it has appeared in the paper

The Software Engineering Project (Part D). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Other questions that mention it

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

Diagram: “A bar chart showing tasks against time, with start and end dates, duration and dependencies; used to schedule and track a project.” Then apply it: Testing cannot start until coding finishes.

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Command words used with it

From the linked past questions
  • Describe: Provide characteristics and features. (2022 Software Design and Development HSC Q27 (10 marks): Modelling and design (IPO, data structure, Gantt))
  • Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (2024 Software Design and Development HSC Q25 (4 marks): Documentation)

Technique for the question types

What the marking guidelines and feedback say

2022 Software Design and Development HSC Q27 (10 marks): Modelling and design (IPO, data structure, Gantt)

Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).

2024 Software Design and Development HSC Q25 (4 marks): Documentation

Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Project management · Collaboration tools · Social and ethical issues in project work · Communication issues · Quality assurance · Modelling tools · Back-end engineering contribution · Class diagram · Class diagram inheritance and multiplicity · Entity relationship diagram (ERD) · Storyboard · Decision tree · Data dictionary · Process diary (log book)