flowchart TD
GAME[GAME] --- d1(("d"))
d1 --- SINGLEPLAYER[SINGLEPLAYER]
d1 --- MULTIPLAYER[MULTIPLAYER]
GAME --- d2(("d"))
d2 --- WINNABLE[WINNABLE]
d2 --- NONWIN["NON-WIN"]
NONWIN ---|"1 PrequelTo"| SEQUEL{SEQUEL}
SEQUEL ---|"1 SequelTo"| NONWIN
Name(["Name"]) --- GAME
Year(["Year"]) --- GAME
Language(["Language"]) --- GAME
Description(["Description"]) --- GAME
Console(["Console"]) --- GAME
Characters(["Characters"]) --- SINGLEPLAYER
MinPlayers(["MinPlayers"]) --- MULTIPLAYER
MaxPlayers(["MaxPlayers"]) --- MULTIPLAYER
Purpose(["Purpose"]) --- NONWIN
Practical 1: Course Tools
Introduces the two tools used throughout the course: diagrams.net (draw.io) for building ER diagrams, and Gradescope for submitting assessment. This practical itself is not assessable — it’s onboarding practice before Assignment 1. The semester plan lists it as the first practical, Intro to Course Tools, run in teaching week 2 (infs1200).
Nothing on this page (the Always a Gamer UoD, the diagram, or the task breakdown) has been verified against a published version, so treat it as a working reconstruction.
Task 1 — Recreate the “Always a Gamer” diagram in draw.io
UoD: a fictional gaming company’s GAME entity (Name, Year, Language, Description, Console) specialises two separate, disjoint (d) ways:
- How it’s played:
SINGLEPLAYER(Characters) orMULTIPLAYER(MinPlayers,MaxPlayers). - Whether it can be won:
WINNABLE, orNON-WIN(Purpose).
NON-WIN games also have a recursive SEQUEL relationship to other NON-WIN games (roles PrequelTo/SequelTo, 1:1).
Recreate this EER diagram yourself in draw.io. The mechanics worth finding first are the shape palette, connecting an entity to a relationship diamond, and exporting the finished drawing as an image.
The four subclasses above are drawn as plain rectangles, exactly like GAME itself. Subclass-hood is carried by the edge into the d circle, never by the box outline — a double-line box means weak entity, which is a different idea entirely. See er-diagram-notation for the full symbol table and the Mermaid shape mapping this note follows.
Task 2 — Using the ER diagram
Question 1 — Identifying entities
Which entity type is the superclass that every other entity type in this diagram specialises from (directly or indirectly)?
GAME is the superclass. Its two disjoint specialisations are SINGLEPLAYER/MULTIPLAYER (one d-circle) and WINNABLE/NON-WIN (a separate d-circle) — four subclasses total, all ultimately specialising GAME.
Task 2.2 — Exporting the diagram
Export the finished diagram from draw.io as an image and attach it to the practical’s Gradescope submission — no fixed “right answer” here, it just confirms the export step works.
Task 3 — Submitting via Gradescope
Submit via the Gradescope link on the course Blackboard site. Not assessable — purely to confirm your Gradescope account is set up correctly ahead of Assignment 1.