Opulentus Prime Library Management System: Slumdog Elite Team J.C. Edwards Deepak Yadav Naveen Chandra
Opulentus Prime Library Management System: Slumdog Elite Team J.C. Edwards Deepak Yadav Naveen Chandra
Opulentus Prime Library Management System: Slumdog Elite Team J.C. Edwards Deepak Yadav Naveen Chandra
J.C. Edwards
Deepak Yadav
Naveen Chandra
Introduction
This document provides a thorough design of the system. This is an online library, when
users search for books, the system will output which library branches have the books, and
which branch is the nearest to user's home address. Search function allows both users and
librarians to search by title, rating, category, author, publisher, ISBN, language, branch,
keywords. The system also allows browsing by the same parameters.
There is a feedback system where the users can give a rating and comments to the
book after they have returned it.
Software architecture
1.1 Programming platform: - We used java language as front hand support and JavaScript,
HTML as scripting languages. Thus our software is system-independent and can be run
in both MS Windows and UNIX system.
1.2 Database: - MySQL is used as backhand database support. Connection to the database
is made by JDBC interface. Database tables are created using SQL queries. The runtime
SQL will be sent to database and the query result will be sent back to application by
JDBC connection.
T_Transaction
transctionID : VARCHAR(255)
T_Student studentID : VARCHAR(255)
studentID : VARCHAR(255) callNo : VARCHAR(255)
name : VARCHAR(255) <<Non-Identifying>> checkOutDate : TIMESTAMP <<Non-Identifying>> T_Book
street : VARCHAR(255) checkInDate : TIMESTAMP callNo : VARCHAR(255)
1 0..* fines : DOUBLE(64)
city : VARCHAR(255) ISBN : VARCHAR(255)
zipCode : VARCHAR(255) COL_0 : VARCHAR(255) title : VARCHAR(255)
state : VARCHAR(255) COL_1 : VARCHAR(255) 0..* 1 author : VARCHAR(255)
phoneNo : VARCHAR(255) status : VARCHAR(255)
lateFeeTotal : DOUBLE(64) <<PK>> PK_T_Transactio1()
<<FK>> FK_T_Transactio1() <<PK>> PK_T_Book2()
<<PK>> PK_T_Student0() <<FK>> FK_T_Transactio0()
<<Index>> TC_T_Transactio3()
<<Index>> TC_T_Transactio1()
T_MyList
callNo : VARCHAR(255)
<<PK>> PK_T_MyList3()
Use case view: -
1.4 Actors: -
Librarian: - A librarian can add, delete and update book status and search from the
database. A user can borrow, return books, reserve books and search for books. He
can also renew his loan period. If a book is overdue, the user will be fined a certain
amount each day over the due. If a book is reported lost, the user will pay the full
cost of the book.
User: - The users are categorized into member and non member. Members can get
books delivered to their home address, and they can request for the library to order
books they do not have. The library also has a collection of multimedia items such as
DVDs and games, and only members can borrow these items.
Library System
Reserve book(s)
Borrow book(s)
Librarian
Login system
Browse library
Non-Member
Use Case Scenarios-
Scenario1-
Scenario2-
Scenario3
Scenario4
Scenario5
Scenario6
2. Class Diagrams: - A class has a name, list of attributes and list of operations. The classes
used in this library management system are book, member, non-member and librarian. A
member class is further classified in different categories namely student, staff and paid
membership for who are not the part of institution. Paid membership is of two types, general
membership and professional membership. A non-member is the one who is not registered
with the library management system.
Student
studentID : String
name : String
street : String
city : String
zipCode : String
state : String
phoneNo : String
lateFeeTotal : Double
borrowedBook : Integer
Return book:-
Order book:-
UI Mockups