Reference no: EM132671597

PROJECT REQUIREMENTS

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 the book title, ISBN number, authors, price, quantities etc, and system can be used to support the book stock-keeping purpose as much as possible. Although there a no specific mandatory functionalities required for the BookStock System, as students are allowed to freely design their system, some of the following features may be incorporated in some ways:

o New book stocks can be entered.
o Some stock records can be altered and/or removed.
o All books can be listed for the ISBN, title, authors, price, and quantity.
o Minimal form of search facility is avaliable to find or sort books.
o Stock records can be stored externally and reloaded into the system.

We also expect that the system will be largely menu-driven and the navigation among the book record: should also be possible, perhaps through additional options on the main menu, or on a submenu when displaying a particular book detail, somewhat similar to
• Current book
• Next book
• Previous book

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 system 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. For example, the book search could be based jointly on multiple aspects, and the returned search results could be exactly those which satisfy the search criteria, or could be non-exact in that the records matching more closely with the search criteria will be listed earlier.

3. External file or files are also expected to be utilised for storing the stock records. In particular, when the BookStock System starts, it should first load the existing records from the data file/s which should contain sufficient number of book records. For those who are having difficulties in implementing such data files, it is highly recommended that they initialise enough book records directly within their Java program so that they don't have to repeatedly enter those records when testing or demonstrating their programs.

4. It is up to each student group to decide how to design and implement their BookStock System.

5. Students should not utilise any of the Java GUI components nor any form of database servers for their project, as these are not within the scope of this unit However, if anyone does wish to illustrate extra book images, he is welcome to do so, but only just for the image display. Also feel free to make use of the following illustrating sample Java code DisagyPics.zip in this regard.

6. The final Project Report must be written to include, among all the other relevant matters, the following aspects.
o The main functionalities, along with the demonstrating examples and screen shots if pertinent.
o The design of your user interface and how it impacts on the user experience with your software book.
o How and where you made use of the paradigm of object-oriented programming, if any.
o The most advanced 3 (or more) Java technical aspects, in your opinion, you have made use of in the development of your BookStock System.
o 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.