drAssignment Directions

Now that you've written the logic and unit testing for the Library Management System $($LMS$)$Project$,$ it's time to make it user$-$friendly!

For this assignment, you will add a GUI to your LMS$.$Your GUI should allow the user to implement every function that is provided in the project description.$$You may choose which GUI elements you want to use to do this, including text boxes, radio buttons, tables, combo boxes, etc. $$Allow your creativity to shape your design, with simplicity being the key requirement rather than excessive intricacy. $$Your GUI must be functional but does not have to be ornately designed unless you want to$.$Extra points will be awarded if your GUI goes above and beyond with an immaculate layout.$$Otherwise$,$ your GUI must be clear, concise, and simple to use, while executing all functions of the LMS properly.

There are many options for creating a GUI for your LMS application.$$My recommendation is to use the GUI builder within IntelliJ.$$

Another option is to use JavaFX.$$Resources for both of these tools are provided on the resource page for this module.$$Ultimately$,$ the method you use to implement your GUI is up to you, so long as it is written in Java and interfaces with your LMS application according to the project directions. $$You may need to do your own additional research in order to implement your GUI using the method of your choice.

Your GUI should execute the following tasks:

Ask the user for a file name, and receive it from the user.$$Open the file supplied by the user, and add each book to the LMS database.$$Display an error message if the file was not found.

Print the database to the screen.

Ask the user for a barcode number to remove.$$Receive the barcode, remove the corresponding book from the database, and print a confirmation message that the book was deleted.$$Display an error message if the barcode was not found.

Ask the user for a title number to remove.$$Receive the title, remove the corresponding book from the database, and print a confirmation message that the book was deleted. Display an error message if the title was not found.

Ask the user for a title to check out. Check out the book, and print a confirmation message.$$Display an error message if the book is already checked out.

Ask the user for a title to check in$.$Check in the book, and print a confirmation message.

Don't forget to add an Exit button so that users can leave the GUI when finished!

Coding Comments

Your code must be sufficiently commented.$$The following should have a comment:

Every class should have a multi$-$line comment that includes the following:

Your name, course, and dateThe class nameA brief explanation of the function of this specific class, as it relates to the overall program objective.$$The class that contains your main method should clearly explain the overall program objective or problem description

Every method should have a multi$-$line comment that includes the following:

the method namea brief explanation of the method's purposethe arguments of the methodthe return value of the method

Getters, setters, and constructors do not need a detailed comment.

Keep in mind that some comments are unnecessary.$$Comments on conditional statements, loops, and arithmetic calculations are generally not needed if the comment simply explains what the next line of code does.$$A comment may be needed if we need to understand why the next line of code was written the way it was.$$

For examples related to writing comments, check this page.