Introduction
Requirement
Aim
This assignment is intended to assess your skills in understanding and interpreting a moderately complex problem, designing a solution to the problem, and implementing the design using principles of correct syntax, layout, and program structure, more importantly, the collaboration skills in team work. The objectives are to produce a program that:
Follows the specifications accurately.
All designs and plans have been well reported.
Implements programming principles covered in the course i.e. is well structured, demonstrates meaningful object decomposition and re-use, is reasonably efficient and uses GUI controls appropriately.
Has been thoroughly tested as demonstrated by the test plan.
References are appropriate.
Obeys the Unitec programming standards.
Instructions
It is your responsibility to clarify any unclear aspect of the assignment with your lecturer.
The works is designed as an individual assignment
On Jan 13th you must give a presentation to demonstrate your submitted program. Demonstrations are compulsory, or your assignment will be not marked.
This assignment must be your own work.
You are given program specifications. Study these carefully and create an initial design (object class diagrams, screens, method summaries describing complex logic) to solve the problem. The design must enforce the principles of object-oriented program design.
You must then convert your design into a Java program. Your final program must compile correctly using the Eclipse IDE as configured in CSIT Labs. Your final programs should be error free and well laid out, using the Java code conventions of the textbook.
You are required to prepare Checkpoints in a Test Plan and use it for testing your program.
Submission
Design review
All entity classes showing instance variables and methods. Sketches of the screens and a workflow plan. These can be rough drafts, hand drawn is accepted.
Assignment completion
Presentation
It is 10 min presentation, which will include demonstration:
oof your program design
oyour working program
oand discussion your main steps in this project
Be prepared to answer any questions about your design solution, programs, testing
Softcopy:
Combine all your documents (source code, report incl. design, plans, screen shots and test plan) into a Windows compressed (zipped) file
Rename the file with your name and student id, e.g. john_1450890.zip
Submit a zipped file electronically to Moodle before 12.55 p.m on Jan 30th
Assignment Description
Scenario
“Parallel South 37th” movie theatre is asking you to develop a prototype for selling its tickets. The porpoise is to handle the basic activity of selling tickets for the film shows. The expected protoype should allow the clerks on the movie theatre to sell tickets, define movies and showtimes for every movie, update information on showtimes, search movies to see show times. It should be able to generate reports on a particular movie. The system will store information safely on files. Even though this is just a prototype system, they expect you to deliver a system that is user-friendly and error free.
Some important specs:
-The system is intended for one complex with five cinemas
-Each cinema has 100 seats
-Allocated in 10 seat rows (A to J) and 10 seats in each row
-Each cinema, each day may have 0 to 5 shows a day.
Specifications
Movie registration: The first procedure is to register movies. The system should be able to register new movies. The system must validate input (movie name, movie ID, starting date, ending date). Movie ID should be unique and not empty. After passing the validation, the system should store the movie id, movie name, starting date and ending date in a CSV format as shown below
101, Rogue One, 15/12/2016, 14/01/2016
Show time registration: The user will add one show at a time. The system must validate all data. It should be saved on a CSV file, it will include: Show ID, Movie ID, Cinema, Date, Time and Ticket price. Show ID should be unique and not empty.
Example: (a show, on cinema 1, 15/12/2016 at 10:00 am)
1001, 101, 1, 15/12/2016, 10:00, 20
Ticket allocation: The user may sell a ticket for a movie show. Records on file will contain: Transaction ID, Show ID, Row, Seat. One record for each sold ticket. The system must validate all data. It should be saved on a CSV file. Transaction ID should be unique and not empty.
Example: (one ticket sold for show 10001, ticket on B5)
10001, 1001, B, 5
The user would be able to perform. the next operations:
Add a movie
Add a show
Search show times
The user should be able to search through the shows using the movie ID or movie name to show showtimes.
Update and Delete movies
The user should be able to search through the movies using the movie ID or movie name and update movie information or delete a movie. You may not delete a movie if there is at least one ticket sold for at least one show of that movie.
Update and Delete show times
The user should be able to search through the shows using the movie ID or movie name and update show times, delete one show time or delete every show time for that movie. You may not delete a show if there is at least one ticket sold.
Sell a ticket.
The user may sell one ticket at a time. It will ask for row and seat, check if it is available. If it is, a sell can be made.
Refound a flight
A user may refound a sold ticket. It should delete the record on the sold ticket files
Display all movies
Display all showtimes for a movie for a day
Generate a report for a specific show
List all seats allocated
Compute the total earned by that show.
Generate a report for a specific movie
Compute the total earned by that movie.