MOBLIMA is an application to computerize the processes of making online booking and purchase of movie tickets, listing of movies and sale reporting. It will be used by the moviegoers and cinema staff.
The entry point of our application is the MoblimaApp.java class. You may build the project and run the MoblimaApp.java class to get started. The .idea directory can be ignored as we developed our application using the IntelliJ IDE.
The Boundary Classes represent the Views, or the user-facing aspect of our application. These classes contain methods that display the options available to users, and handle the requests of users.
The UserUI abstract class serves as the base class in this package, and contain 2 abstract methods that the AdminUI and MovieGoerUI subclasses will implement.
The Controller Classes represent the main logic in our application. These classes contain methods that manipulate the data in our database. These methods are invoked by the Boundary classes when the users perform actions.
The Manager interface serves to ensure that all classes in this package implement the read and write methods that are imperative for database information manipulation.
There exists a single Controller class for each corresponding model class to abide by the Single Responsibility Principle.
Our Model data are stored in this package in .txt flat file format. There exists one .txt file for each Model class in our application. This ensures that changes to one model and its persisted information will not affect others.
Most of our exception handling leverages the built-in Java exception classes. However, we created 3 custom exception classes that provide an additional layer of robust checks to handle erroneous user inputs that might crash our application.
These Classes represent the entity classes in our application that would require informational storage in persisted database.
This project is an assignment for our module deliverables (SC2002/CZ2002) and is not intended for any use outside of this scope.
In the design of this project, we took into consideration the EAIP (Encapsulation, Abstraction, Inheritance, Polymorphism) Principles in OOP as well as the SOLID principles.
These principles, in conjuction with the Model-View-Controller (MVC) framework enabled us to structure our project to achieve loose-coupling and high cohesion.
The quintessential concepts learnt in this course have proved imperative in the design process of this application.
The overview of our architecture is as such:
| Term | Definition |
|---|---|
| Show | The instance of a movie screening at the cinema |
| Movie Type | Type of movie, such as 2D, 3D or Blockbuster |
| Theatre Class | Type of theatre, such as standard or platinum |
| Movie Goer | Customer planning to watch a movie |
| Guest | An unauthenticated Movie Goer that will be prompted to sign up upon ticket booking |
In the design of our application, we made the following assumptions:
- No concurrent access as it is a single-user application.
- Currency is in SGD and inclusive of Goods and Service Tax (GST).
- There is no need for additional security features such as password encryption.
- Payment will always be successful.
- Our application does not interact with external services such as online payment services (VISA, MasterCard, PayLah etc).
- There is no need for validation when purchasing discounted tickets such as Student/Senior Citizen tickets as this will be done upon entry to the theatre.
- Not all MovieGoers will be logged in from the start. (We circumvented this by allowing users to purchase tickets as Guests. After purchasing a ticket, our application will prompt users to create an account.)
- Users will not be allowed to create accounts with identical usernames. This applies to both Admins and MovieGoers. (We implemented a check to enforce this.)
- Admins will not be allowed to create a new Show instance if its show-time conflicts with that of another show in the same theatre in the same cineplex on the same date. (We implemented a check to enforce this.)
- Some holidays fall on different dates every year. Thus, we tagged each Holiday instance to the year it corresponds to for greater clarity (e.g. Chinese New Year 2022).
- All students are of legal age (i.e. students can watch shows irregardless of movie rating)
The following members contributed to the success of this project through their hard work and sleepless nights. In no particular order:
-
Chan Ming Han (Computer Engineering)
-
Wayne Tan Jing Heng (Computer Science)
-
Lim Sui Kiat (Computer Science)
-
Ho Han Yu (Computer Science)
-
Yap Zhe Kai, Nicholas (Computer Science)
Special thanks goes out to Dr Althea Liang for her patience and guidance throughout the course of this project.