COMP 2613 Assignment 2
The assignment will continue on from assignment 1, and also building on the labs and reinforce the concepts and features of the java framework we’ve learned in weeks seven through ten. You’ll be adding data persistence and a graphical user interface for the Games Information System (GIS).
At the core of this application is your assignment 1 and labs. The assignment is a consolidation and extension of the requirements for the labs.
The design of GIS must follow good object-oriented principles and practices.
Your code must compile and the jar file must run. Compile-time warnings are considered errors and must be eliminated from your code by using appropriate annotation tags.
The main class must be named Gis, and the jar file containing your runnable code must be named <student#>Gis.jar, i.e. A00123456Gis.jar.
As in assignment 1, all activity must be logged to a text file named <student#>Gis.log, i.e. A00123456Gis.log.
Exceptions must be handled such that no stack traces are displayed in the console, but as mentioned above, a message will be logged explaining the cause of the error.
In the second half of COMP 2613 the topics are database, multithreading, graphical user, database, model-view-controller and other design patterns, and network programming. This assignment will touch on many of these.
Remove the printing of the reports to the console and to a text report that we had in assignment 1.
Similar to your labs, the first time GIS is run, the data will be read from personas.dat, players.dat, games.dat, and scores.dat. The data will be stored into four separate tables in a local (derby) database – you can create additional tables if you need them. If collections are used, they are only used to temporarily store datasets. A separate Database class is used to manage the connection to the database. For each of the tables a separate DAO class is required; the DAO classes will contain the table creation, and create, read, update, and delete methods. To re-test the data loading functionality, you will delete the external database files and restart your application.
The application contains a graphical user interface, which will be displayed when the user runs GIS. The UI will always be displayed even if there are errors loading the data. Errors will be written to the application log files and will be messaged to the user in the form of a simple dialog box.
The follow menu must be implemented: