Library System: Pay fines function
Pay fines function in Library system is a method used to ensure the timely returning of the borrowed library item by the borrowers. This is an enforcement mechanism designed to ensure that library books are returned within a certain period of time. Fines are usually assessed for only a few days or months, until a pre-set limit is reached.
•To improve availability of library items.
•Improve Facilities by fine.
•Increase borrower loyalty
•Attract new customers
•Reduce the chance of unreturned items.
•Automating the process of Library.
•To make process faster by automating the tedious and mistake prone process.
•To incorporate diverse rules of any Library.
•To reduce the room for errors by substituting manual work by computerizing process.
•Design and implement a fully automated system. Based on the user-requirement, a proper design need to be drawn out carefully. Then the system will be implemented.
•To improve the security.
•To enable simple interfaces.
•To view instant reports.
•To avoid the inconsistency in human calculation.
•saving the time of Library staff, students and staff.
Requirements gathering with client:
During the last few weeks, I searched about the requirements of the user on the Internet. I interviewed some librarian also and various borrowers who want to use system and I received a good response from all of them. It gone through some existing students and staffs and I got some good ideas .Internet is also prove to be helpful in my research. Internet will provide access to existing features and these features will we studied carefully and will be embedded in this project along with its unique and new features to make this project a success.
For collecting user requirements, interviews, onsite observation and questionnaires are one of the most common techniques for gathering the essential information regarding the system
Use case diagrams graphically depict the interaction between the system and users. In other words, they graphically describe who will use the system and in what ways the user expected to interact with the system.
A Use case is a behaviorally related sequence of steps (a scenario), both automated and manual, for the purpose of completing a single business task.
The following use case diagrams represent the interaction between user and system. This system is mainly intended for one type of user (refer figure-1). Some time it is really difficult to predict user will perform what function. There has been used only one actor as a user.
|Version||Librarian can edit the student, staff and other actors records.|
|Goal||Present a menu for Librarian to access the various function of the issue items.|
|Summary||The students, staff, others borrows a items from the system.|
|Actors||students, staff, others, Librarian|
|Pre-conditions||The students, staff, others have no old debts to the system|
|Trigger||ITS officer selects edit student, staff, others records option|
|Basic course of event||The Librarian scans the borrower’s barcode to check the fine status.|
The Librarian renews the loan Item.
The Librarian issues the Item.
|Post-Conditions||The students, staff, others have successfully borrowed the items|
|Business Rules||For borrowing items and renewing loans, fine amount should not exceed $25|
|Notes||The students, staff, others chooses an items that is not already lent and that s/he does not own. The Librarian assigns the students, staff, others as the borrower of that item and also states a deadline for returning the items.|