Must-have

• Analytics attached to each course;

  • No of visits

• API to calculate the

  • “Most Popular Course” — most visits(?),

  • “Highest Rated Course Per Term” — highest rating per term,

  • “Most Liked Review” — most upvoted review,

  • “People’s Choice” — highest enjoyability rating,

  • “Industry Award” — highest usefulness rating,

  • “WAM Booster” — highest manageability;

• A Unilectives Wrapped interface.

Nice-to-have

• Additional statistics collected by analytics, e.g. clicks around the page, time spent, etc.

Not-in-scope

Analytics

Analytics is complicated. We have 2 choices:

• (1) Use Google Analytics (Free);

• (2) Create the logic ourselves using middlewares.

Specs TBC once we decide.

API

The API route(s) must compute the aforementioned statistics (highest traffic, highest overall rating, etc). Each API route should produce a String; either the relevant courseCode or reviewID.

The logic should include

• (1) Querying from the database / getting the analytics data;

• (2) Processing this data.

Note we are following the controller-service-repository architecture already in use. See backend/src/controllers and ctrl click through the endpoints.

Interface / Design

The design has two components: (1) the page itself; and (2) the integration of the page into the main page.

• The page should be something similar to previous year’s draft. Consult UI/UX or directors for TBD final hi-fi design.

• At your discretion. Ideas: via a link in the navbar + a closeable pop-up dialogue in the bottom-right of the screen.

Term 2 Week 3 - Week 9 (26th of July)

• Everything Done

Landing

Christine

Navbar

Urja

Most popular course [most views]

Adrian

Highest rated course per term

Alice

People's choice [most enjoyable]

Kevin

Industry award [most useful]

Falco

Most liked review

Tom

Wam booster [most manageable]

Summary