A GUI program development in Java and user manual - Object Oriented Programming
- or -
Post a project like this2528
£100(approx. $125)
- Posted:
- Proposals: 2
- Remote
- #1537905
- Awarded
Description
Experience Level: Intermediate
General information for the business: Assignment
Kind of development: New program from scratch
Objective: Automation of library management system has been studied over the years by many
stakeholders. The main purpose of such system is to mechanise library housekeeping
operations predominantly by computerization. In this coursework you will create a ‘prototype’
library management application to focus on basic operations in a library like adding new books,
new members, searching books and members and facility to borrow and return books; and
updating information about books and members. The application should store all the information
about books and members in a persistent storage e.g. files.
A partial implementation of a prototype library management system will be made available in the
Moodle. The prototype is implemented as an eclipse project. This prototype contains the menus
for different functionalities (e.g. add, view, issue and delete books; add, view and delete
members). However, in terms of functionalities, the prototype allows only to add books to the
system and view the stored books. The prototype uses text file as its backend storage to store
the information of books. This file is named as books.txt and it can be found inside the data
folder of the eclipse project. The different information of a book (e.g. ISBN, title, author etc.) is
stored as a single line in the text file, where each information is separated by double colon (i.e.
::). For example, the following book information,
ISBN: 1234-654
Title: Introduction to Java
Author: Smith Owen
Publisher: Penguin
Publication Date: Nov 2015
Can be stored as the line shown below,
1234-654::Introduction to Java::Smith Owen::Penguin::Nov 2015
Description of requirements/functionality: The application must implement all the following:
Add new books to the system. System should store at least the following information for
each book: ISBN, Title, Author, Publisher, Publication Date and Availability (i.e. if the
book is available or issued to someone.)
Add new members to the system. System should store at least the following information
for each member: ID, Name, Number of Books Borrowed, and Phone Number.
View all the books stored in the system.
View all the members stored in the system.
Issue books to members. When a book is issued to a member the status of the book
should be updated in the book view. Also the members view should display that a book
has been issued for the member.
Return issued books. When a member returns a book the status of the returned book
should be updated in the book view. Also the members list should display that a book
has been returned by the member.
Save the status of the system to the backend storage (e.g. file storage) at any time. Also
when the system is closed it should update its backend storage, such that the system
can load the up to date status at the next start.
The system should consider the ISBN of a book as unique and should not allow to store
duplicate ISBN.
The system should consider the ID of a member as unique and should not allow to store
duplicate ID.
Delete existing books from the system. When a book is deleted, it should not appear in
the books view.
Delete Existing members from the system. When a member is deleted, it should not
appear in the members view.
Add new admin user.
Search books. Searching should be based on different information of a book, e.g. ISBN,
Title, Author etc. System should display the found book or should display a message if
no book found. Display book cover image when a book is found.
Search members. Searching should be based on different information of a member, e.g.
ID, Name, and Phone Number. System should display the found member or should
display an information if no member found.
Impose a limit on the maximum number of books that a member can borrow and use
that during issuing books for a member.
The system should generate return (due) date when issuing a book. The system takes
the current date from the operating system to generate the return date (e.g. within two
weeks) and adds the return date in the record of the book.
Display all the borrowed books sorted by due dates.
The system should have option to calculate charges (e.g. 50p for each day) for overdue
books and records the charge in the members’ record.
Members with overdue books should be flagged using (colour/mark), and this should
appear on the members list
Admin should be able to update books and members records.
I have attached a Library zip file which already has menus and other stuff inside, use this to help start you off.
P.s. can you add enough comments to understand the code and also create a Manual describes detail
usage scenarios for all
the features.
Specific technologies required: Java Eclipse
OS requirements: Windows
Extra notes:
Kind of development: New program from scratch
Objective: Automation of library management system has been studied over the years by many
stakeholders. The main purpose of such system is to mechanise library housekeeping
operations predominantly by computerization. In this coursework you will create a ‘prototype’
library management application to focus on basic operations in a library like adding new books,
new members, searching books and members and facility to borrow and return books; and
updating information about books and members. The application should store all the information
about books and members in a persistent storage e.g. files.
A partial implementation of a prototype library management system will be made available in the
Moodle. The prototype is implemented as an eclipse project. This prototype contains the menus
for different functionalities (e.g. add, view, issue and delete books; add, view and delete
members). However, in terms of functionalities, the prototype allows only to add books to the
system and view the stored books. The prototype uses text file as its backend storage to store
the information of books. This file is named as books.txt and it can be found inside the data
folder of the eclipse project. The different information of a book (e.g. ISBN, title, author etc.) is
stored as a single line in the text file, where each information is separated by double colon (i.e.
::). For example, the following book information,
ISBN: 1234-654
Title: Introduction to Java
Author: Smith Owen
Publisher: Penguin
Publication Date: Nov 2015
Can be stored as the line shown below,
1234-654::Introduction to Java::Smith Owen::Penguin::Nov 2015
Description of requirements/functionality: The application must implement all the following:
Add new books to the system. System should store at least the following information for
each book: ISBN, Title, Author, Publisher, Publication Date and Availability (i.e. if the
book is available or issued to someone.)
Add new members to the system. System should store at least the following information
for each member: ID, Name, Number of Books Borrowed, and Phone Number.
View all the books stored in the system.
View all the members stored in the system.
Issue books to members. When a book is issued to a member the status of the book
should be updated in the book view. Also the members view should display that a book
has been issued for the member.
Return issued books. When a member returns a book the status of the returned book
should be updated in the book view. Also the members list should display that a book
has been returned by the member.
Save the status of the system to the backend storage (e.g. file storage) at any time. Also
when the system is closed it should update its backend storage, such that the system
can load the up to date status at the next start.
The system should consider the ISBN of a book as unique and should not allow to store
duplicate ISBN.
The system should consider the ID of a member as unique and should not allow to store
duplicate ID.
Delete existing books from the system. When a book is deleted, it should not appear in
the books view.
Delete Existing members from the system. When a member is deleted, it should not
appear in the members view.
Add new admin user.
Search books. Searching should be based on different information of a book, e.g. ISBN,
Title, Author etc. System should display the found book or should display a message if
no book found. Display book cover image when a book is found.
Search members. Searching should be based on different information of a member, e.g.
ID, Name, and Phone Number. System should display the found member or should
display an information if no member found.
Impose a limit on the maximum number of books that a member can borrow and use
that during issuing books for a member.
The system should generate return (due) date when issuing a book. The system takes
the current date from the operating system to generate the return date (e.g. within two
weeks) and adds the return date in the record of the book.
Display all the borrowed books sorted by due dates.
The system should have option to calculate charges (e.g. 50p for each day) for overdue
books and records the charge in the members’ record.
Members with overdue books should be flagged using (colour/mark), and this should
appear on the members list
Admin should be able to update books and members records.
I have attached a Library zip file which already has menus and other stuff inside, use this to help start you off.
P.s. can you add enough comments to understand the code and also create a Manual describes detail
usage scenarios for all
the features.
Specific technologies required: Java Eclipse
OS requirements: Windows
Extra notes:
Adam H.
100% (2)Projects Completed
2
Freelancers worked with
2
Projects awarded
25%
Last project
26 Apr 2017
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies