Topic 6 · Case Study & Reporting  ›  Week 13

Final Test & Final Preparation

The busiest week of the semester. The Final Test (30%) is held now, and everything for Week 14 — report and presentation — has to be finished alongside it.

● Final Test this week — 30%

A practical test covering Chapter 2 and Power BI. Marked out of 70 and worth 30% of your course grade; the passing mark is 14/70. Date, time, venue and what to bring are confirmed in class.

This week you will…

  • Know the format and scope of the Final Test, and revise efficiently.
  • Finish and proofread the case-study report.
  • Rehearse the presentation against the clock.
  • Have everything ready to submit in Week 14.

13.1  What the paper looks like

Three sections. Most of the marks are in the practical work — this is a test of what you can build, not what you can recite.

SectionTypeMarksWhat it asks
AMultiple choice10Concepts from Chapters 1–2: good tables, chart choice, colour, what Power BI is for.
BShort answer10Short, clear written answers with examples — comparing chart types, spotting problems in a bad visual.
CPractical tasks50Case studies with real datasets: build charts to a specification, then interpret them.
Total70Worth 30% of the course · pass mark 14
● Section C is 71% of the paper

Fifty of the seventy marks come from building and explaining visuals. Revise by opening the software and building charts, not by rereading slides.

13.2  How Section C is usually structured

Expect several case studies, each following the same shape:

  1. A short business scenario and a stated objective.
  2. Instructions to construct a specific chart with exact formatting — a centred title, legend in a named position, data labels showing value and percentage.
  3. A question asking you to read the chart and explain what it shows — usually worth 2 marks.
● Both halves are marked

Building a beautiful chart and skipping the explanation loses marks, and so does the reverse. Always write the sentence — which category is largest, what the percentage is, what the trend means.

Follow formatting instructions literally. If the paper says “legend positioned top-right, stacked, bold, size 14”, every one of those is a mark you either earn or don't. Read the requirement twice, then check your chart against it before moving on.

13.3  Revision map

Go back to the weeks, not to a summary. Each row links straight to the lesson.

ReviseFromWhy it's testable
Exploratory vs explanatory analysisWeek 1Section A concepts.
Features of a good table; tables vs figuresWeek 2Appears in Section A and B almost every time.
Chart choice — tables, points, linesWeek 3“Which chart is most suitable for…”
Bars, histogram, boxplot, geospatialWeek 4Section B comparisons: histogram vs boxplot, line vs bar.
Cautious elements — too many colours, 3-D, pies with many slicesWeek 4The classic Section B case study: “what's wrong with this pie chart?”
Power BI: import, Power Query, formatting visualsWeek 9Section C, every question.
Line, bar, clustered/stacked, histogram, boxplot, maps in Power BIWeek 10Section C — the chart you're asked to build.
Dashboards, slicers, cross-filteringWeek 11Longer Section C tasks.

13.4  On the day

  1. Check Power BI Desktop works on the machine you'll use — before the test, not during it.
  2. Read all three sections first and budget your time by marks: Section C deserves most of it.
  3. Answer in the booklet provided, arranged in order.
  4. For every chart: build it, format it to spec, then write the interpretation sentence.
  5. Save your completed work as a PDF named FullName_StudentID.pdf for submission.
  6. Bring nothing unauthorised into the room.
● The filename is part of the instructions

Past papers specify FullName_StudentID.pdf exactly. Get it right — a file your lecturer can't identify is a problem you don't want on results day.

13.5  Finishing the report

The full checklist lives on the project page. These are the things that most often cost marks in the final days.

CheckWhy
Write the Abstract last, as one past-tense paragraphIt summarises a finished paper. No citations, no figures, no abbreviations.
Every figure and table is referred to in the textAnything not referred to should be removed — that's the rule in the guidelines.
No raw software screenshots pasted in without explanationSummarise results in words, using figures to illustrate.
Tables and figures are complementary, never duplicating each otherSame information twice reads as padding.
Conclusion is one paragraph, tied to the objectives, with limitationsDirectly on the rubric.
3–5 references in APA 7th, matching the in-text citationsSee the reference examples.
Prescribed template, single spacing, 10 pages maximumFormat is a graded criterion.
All members' names and IDs on the coverAnd every name should belong to someone who contributed.
Read it aloud once. It is the fastest way to catch the grammar and flow problems that cost you marks under “Overall report presentation”.

13.6  Rehearsing the presentation

Half the presentation rubric is delivery, creativity and teamwork — none of which improve by adding another chart. They improve by rehearsing.

  1. Run it with a timer. Fifteen minutes is the maximum; aim for thirteen.
  2. Every member speaks. Decide who covers what and practise the handovers — they're where groups look unprepared.
  3. Rehearse the slicer moment. Click it live, out loud: “overall it looks like this — but filter to here, and…”
  4. Practise your chart justifications — one sentence each, said aloud, not read.
  5. Test the technology on the actual setup: screen share, cable, internet.
  6. Record a backup video in case the live version fails.
  7. Get a fresh perspective — present to someone outside your group and ask what they took away.
● Check your public link works

Your presentation must be delivered publicly and the link submitted. Open it in a private browser window before you submit — a link only you can open counts as not submitted.

13.7  Ready for Week 14?

Report

  • All seven sections written.
  • Within 10 pages, on the template.
  • Proofread by someone who didn't write it.
  • Exported to PDF, named correctly.

Presentation

  • Dashboard finished and interactive.
  • Timed under 15 minutes.
  • Every member has their part.
  • Public link tested; backup recorded.
● Session 2 recap

Abstract last. Every figure referenced. Rehearse with a timer and hand over cleanly. Test the link before you need it.

Week 14 →