POO-TV

This is a simplified implementation of a movie streaming platform backend with functionalities such as register, login, logout, watch, buy and appreciate movies, subscribe to notifications about certain genres and access to new movie recommendations.

Version 1

Packages

• pages/

  • Page - an abstract class that shapes a generic page; it is used to implement the Visitor design pattern (for Logger and Action classes), so that pages are the visitable objects;
  • HomepageAuth, HomepageUnauth, LoginPage, LogoutPage, Movies, RegisterPage, SeeDetails and Upgrades - classes that extends Page and contains the implementations of methods from this abstract class; these classes are made in accordance with Singleton design pattern, so they can be instanced only one time, because there is only one page of each type;

• actions/

  • Action - an abstract class that shapes a generic action; it contains abstract methods execute for each type of page; each page implements a method called makeAction which calls this function, so actions are the visitors objects;
  • a class for every type of action that exists in POO-TV; these classes extends Action, and contains implementation of execute for every type of page;
  • ActionFactory - a Singleton class that is used to create Actions; this class has a method that creates object of type Action based on an object of class Actioninput; so, there is implemented the Factory pattern;

• input/

  • contains input clases that are used to map the JSON format input files;

• entities/

  • User - a class that shapes a user that do stuff on POO-TV; it retains the authentification infos, called Credentials which are stored in another class from this package, and informations about purchased, watched, liked and rated movies; this class offers implementation for methods used to buy tokens, to purchase movies, to upgrade account, etc.;
  • Credentials;
  • Movie - a class that shapes a movie existent on POO-TV; it contains informations about actors, genres, number of likes and ratings, average rating;
  • ILogger - an interface that is used to implement something like the Visitor pattern for printing the ouput; it defines methods that print something in case of succesfully done actions on pages HomepageAuth, Movies and SeeDetails;
  • Logger - a class that implements the interface above; it offers implementation for print methods for each of those pages; this class is also a Singleton class, because there must be only one Logger; this class also has a method to print in case of Error;
  • POOTVCore - a class that is the core of this application; it contains the registered users, the current user, the existing movies and the current movies to be displayed (on page Movie); this class is also a Singleton one;

• strategies/

  • FilterStrategy - interface that shapes a generic strategy to use in action Filter; a class that implements this interface must offer implementation for a method filter; it is used to implement Strategy design pattern;
  • ActorsFilter, DurationSort, GenreFilter and RatingSort - classes that implements this interface;

General implementation

In main method, all pages are intitialized, POOTVCore and Logger are initialized. Next HomepageNeauth is set as current page and current user is null. Next, for every action, the current page calls method makeAction.

Version 2

Below I only noted what I added and modified to implement the functionalities required in the 2nd stage of the project.

Added classes

• in package actions/

  • SubscribeAction - a class that implements interface Action; it is made to implement the subscribe feature;
  • BackAction - a class that implements the option to go back to the previous page;
  • AddMovieAction and DeleteMovieAction - classes that implement the database features: add and remove movies;

• in package entities/

  • Notification - a class that shapes a notification that will appear for a user;
  • State - a class that shapes the state of this application at some time: the page and the current movie; it is used to implement the Back feature;
  • RecommendationManager - a utility class that is used to make the recommendations for premium users;

Modifications

• in package input/

  • I modified ActionInput class to deal with the new fields from JSON files that are used for the new features;

• in package entities/

  • User - I added some fields to implement the new features: an arraylist for notifications, an arraylist for subscriptions and a hashmap for liked genres;
  • Movie - I modified the ratings field to a hashmap, so that user can modify his rating for a movie;
  • ILogger - I modified this interface so that it doesn't contain a required method for page HomepageAuth, because there will be no output when Back is made to this page;
  • Logger - I added two methods: printLogin, to be used when a login or register action is made, and printRecommendation to implement the recommendation feature;
  • POOTVCore - I added an arraylist of States to implement a pages history for the Back feature;

Actions package diagram
Pages package diagram
Strategies package diagram
Logger diagram