PROJECT REQUIREMENTS 1.For this final project, you are required to develop a BookStock System in Java, so that books can be stored in the system for such as their title, price, quantities etc, and the system can be used to support the book stock-keeping purpose as much as possible. Although there are no specific mandatory functionalities required for the BookStock System, as the students are allowed to freely design their system, some of the following features may be incorporated in some ways: New book stocks can be entered. Some stock records can be altered and/or removed. All books can be listed for the title, price, and quantity. Minimal form of search facility is avaliable to find a book. Stock records can be stored externally and reloaded into the system. 2.This project is semi-open in that students are expected to have their own design, and/or additional capacity to enrich their final software product if the students are aiming for the top grades. Such additional features can be anything that would enhance the functionalities and user experience in using such a stock-keeping system in real life. External file or files are also expected to be utilised for storing the stock records. 3.It is up to each student group to decide how to design and implement their BookStock System. 4.The final Project Report must be written to include, among all the other relevant matters, the following aspects. The main functionalities, along with the demonstrating examples and screen shots if pertinent. The design of your user interface and how it impacts on the user experience with your product. How and where you made use of the paradigm of object-oriented programming, if any. The most advanced 3 (or more) Java technical aspects, in your opinion, you have made use of in the development of your BookStock System. Brief conclusion and reflection on your experience in completing this project. We note that your project should aim at top quality as much as possible. Your end-product, the BookStock System, will be judged on the achieved functionalities, the look and feel, the design methodology (e.g. ad hoc versus systematic), and the use of advanced features such as object orientation and exception handling. You should cite your design and technical evidence in your Final Report on the quality of your developed software system.