DATA2001 · Data Science, Big Data and Data Variety
Exam Review and Synthesis
Week 13 synthesises the whole unit for the 50% final exam that covers all content (Weeks 1-13): the ER/SQL foundations, Python analysis, scalable analytics and indexing, and the full data-variety arc from scraping and APIs to spatial, time-series, text and image data. This chapter gives a high-yield recap, a cross-model worked example, and a revision plan into the University of Sydney formal examination period.
What this chapter covers
- 01Foundations recap: ER modelling and keys, ER-to-relational mapping, the relational model
- 02SQL recap: SELECT-JOIN-GROUP BY-HAVING, set operations and subqueries, the six-step evaluation order
- 03Analysis recap: Pandas cleaning, summary statistics with the right divisor, precision/recall/F1
- 04Scaling recap: memory hierarchy and I/O, index selection, partitioning and sharding
- 05Data-variety recap: scraping/DOM, REST APIs and JSON/JSONB, PostGIS and the ::geography cast, point-vs-sequence time-series, TF-IDF, image thresholding
- 06Cross-model synthesis: choosing the right data model and tool for a task; filtering expressed in SQL, Pandas and NumPy
- 07Exam strategy: pace by marks, show formulas, sanity-check units and answers; a STUVAC revision plan
A weighted mean from assessment-component weightings
- +1Weighted-mean formula. x-bar_w = (w1·x1 + w2·x2 + w3·x3) ÷ (w1 + w2 + w3), with the marks as values and the component weightings as weights.
- +1Numerator. 20·70 + 30·85 + 50·60 = 1400 + 2550 + 3000 = 6950.
- +1Denominator and result. Total weight = 20 + 30 + 50 = 100, so x-bar_w = 6950 ÷ 100 = 69.5.
- +1Compare with the plain mean. The unweighted mean is (70 + 85 + 60) ÷ 3 = 215 ÷ 3 ≈ 71.67. The weighted mean (69.5) is lower because the 60 mark carries the largest weight (50%), pulling the average down — weighting changes which values dominate.
Key terms
- Weighted mean
- x-bar_w = (sum of weight × value) ÷ (sum of weights). Used whenever items count unequally — credit-weighted marks (as in a WAM), reliability-weighted sensor readings, or class-weighted metrics.
- Clause evaluation order
- The conceptual order in which SQL processes a query: FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY. Knowing it tells you which clause a condition belongs in and why WHERE cannot reference an aggregate.
- Data model choice
- Matching a task to a representation and tool: relational/SQL for structured tabular data, JSON/JSONB and APIs for semi-structured web data, PostGIS for spatial, temporal storage for time series, and vectorisation (TF-IDF / feature vectors) for text and images.
- Filtering, three ways (recap)
- Keeping rows that meet a condition appears as SQL WHERE, Pandas df.query(...) or a Boolean mask, and NumPy array[array > x] — one idea across the unit's three main tools.
- Semi-structured thread (recap)
- HTML (scraping), XML/JSON (APIs) and JSONB (storage) are all self-describing, schema-flexible formats — a single unifying concept spanning Weeks 6-7 that the final likes to test across topics.
- Vectorisation thread (recap)
- Turning content into vectors so 'similar' means 'nearby': TF-IDF vectors with cosine similarity for text, and image feature vectors for similarity search. The same idea closes the data-variety arc.
Exam Review and Synthesis FAQ
What does the DATA2001 final exam cover and how is it structured?
The final is worth 50% and covers all unit content, Weeks 1-13 — ER/SQL foundations, Python analysis, scalable analytics and indexing, and the whole data-variety arc. The exact duration, section structure, mark allocation and open/closed-book status are not published in the available course materials, so confirm them on Canvas and the unit outline (for reference the in-semester midterm was a 50-minute pen-and-paper MCQ + short-answer quiz on Weeks 4-8). Because it spans everything, revise breadth-first.
How should I revise for a whole-unit final?
Cover breadth before depth: make sure you can start every topic, then deepen the ones you find hardest. Build a one-page map grouping the unit as Foundations (ER/SQL/relational), Scaling (storage/index/partition) and Data Variety (web/spatial/time-series/text/image), and under each note the key facts and the one small calculation that tends to appear. Rehearse the recurring calculations — a SQL GROUP BY/HAVING, summary statistics with the right divisor, precision/recall/F1, a bounding box, TF-IDF, a threshold mask — under time pressure. Do not neglect the early ER/SQL material just because the midterm skipped it; the final includes it.
Which cross-topic themes are worth revising together?
Three threads unify the unit. Filtering is the same idea in SQL (WHERE), Pandas (.query / masks) and NumPy (Boolean indexing). The semi-structured thread links HTML scraping, JSON/XML APIs and JSONB storage. The vectorisation thread links TF-IDF cosine similarity for text with image feature vectors. Indexing (Week 5) and spatial GiST indexing (Week 8) share the 'separate structure that avoids a full scan' theme. Revising these together helps with the cross-topic questions the final favours.
Can AI help me revise for the DATA2001 final?
Yes, as a revision partner. Sia can quiz you across all thirteen weeks, set timed mixed problems, and walk through any calculation — SQL, statistics, spatial, TF-IDF, thresholding — one step at a time, checking your working. Use it to find and close your weak spots. It does not sit the graded exam for you, and the University of Sydney academic-integrity policy applies to the exam itself.
Exam move
Plan backwards from the 50% final, which covers everything. First, cover breadth: for each of the thirteen chapters be able to start every topic and state its one high-yield fact and calculation, then use STUVAC to deepen your weakest areas. Rehearse the recurring computations under time pressure — a GROUP BY/HAVING query, mean/variance with the correct divisor, precision/recall/F1, a bounding box with the ::geography note, TF-IDF, and a threshold mask — because these are the marks you can bank. Revise the three unifying threads (filtering three ways, the semi-structured thread, the vectorisation thread) so cross-topic questions feel familiar, and revisit the Week 1-3 ER/SQL foundations that the midterm did not test. Pace by marks in the exam, show your formula before substituting, and sanity-check every answer's units and range. Ask Sia to run timed full-unit mocks and mark them; confirm the exam date, room, duration and open/closed-book status on Canvas and the University of Sydney exam timetable — the final sits in the Semester 1, 2027 formal examination period, around June 2027.
Working through Exam Review and Synthesis in DATA2001? Sia is AskSia’s AI Data Science tutor — ask any DATA2001 Exam Review and Synthesis question and get a clear, step-by-step explanation grounded in how DATA2001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.