Online Library Management System

A Major Project Report Submitted in partial fulfillment of the requirements for the Degree of Master in Computer Application Under Biju Patnaik University of Technology, Rourkela By

Nibha Kumari Subhalaxmi Chaudhury

ROLL # MCA200560825 ROLL # MCA200560849

April – 2008

Under the guidance of

Mrs. Charulata Palai

NATIONAL INSTITUTE OF SCIENCE & TECHNOLOGY Palur Hills, Berhampur, Orissa - 761008, India

ABSTRACT
This project is aimed at developing an online Library Management System (LiMS) for the college library. This is an Intranet based application that can be accessed throughout the campus. This system can be used to search for books/magazines, reserve books, find out who is having a particular book, put in requests to buy a new book etc. This is one integrated system that contains both the user component and the librarian component. There are features like email notifications/reminders, report generators etc in this system.

i

ACKNOWLEDGEMENT
We express our deepest sense of gratitude to our advisor Mrs. Charulata Palai for providing us an opportunity to design a project entitled “Online Library Management System” and guiding us till the completion of this project. We also express our sincere thanks to all the laboratory members of NIST for their continuous support, valuable suggestions and proper guidance without which this project could not have been possible. We would also indebted to Mr. S. B. Neelamani, MCA Project coordinator for giving his valuable time throughout our project. We acknowledge with immense pleasure the sustained interest, encouraging attitude and constant inspiration rendered by Prof. Sangram Mudali, Director, N.I.S.T. His continued drive for better quality in everything that happens at N.I.S.T. and selfless inspiration has always helped us to move ahead. At the nib but not neap tide, we bow our heads in gratitude at the omnipresent Almighty for all his kindness. We still seek his blessings to proceed further.

Nibha Kumari Subhalaxmi Chaudhury

ii

TABLE OF CONTENTS
ABSTRACT................................................................................................................................................i ACKNOWLEDGEMENT.........................................................................................................................ii TABLE OF CONTENTS.........................................................................................................................iii LIST OF FIGURES..................................................................................................................................iv 1. INTRODUCTION ................................................................................................................................5 2. REQUIREMENT ANALYSIS .............................................................................................................6 2.1 Project .............................................................................................................................................6 2.2 Overview Statement.........................................................................................................................6 2.3 Customer..........................................................................................................................................6 2.4 Goal of the Module..........................................................................................................................6 2.5 System Functions.............................................................................................................................6 2.6 System Attributes.............................................................................................................................7 3. ENTITY RELATIONSHIP DIAGRAMS.............................................................................................9 4. DATAFLOW DIAGRAMS.................................................................................................................10 5. LIST OF USE CASES AND SCENARIOS........................................................................................12 6. USE CASE SPECIFICATIONS..........................................................................................................13 7. TECHNICAL DICTIONARY.............................................................................................................22 8. PERSISTENCE DESIGN....................................................................................................................23 9. DATA DICTIONARIES.....................................................................................................................24 10. LIST OF CLASSES ...........................................30 11. CLASS DEFINITIONS ......................................31 12. LIST OF FORMS .............................................................................................................................35 13. FORM DESIGN DETAILS...............................................................................................................38 14. ERROR CODE DESIGN...................................................................................................................47 15. DESIGN OF TEST CASES...............................................................................................................48 16. SCOPE OF IMPROVEMENT...........................................................................................................48 17. CONCLUSION .................................................................................................................................50 REFERENCES .......................................................................................................................................51

iii

....................................................................................3 Librarian’s Entry Form.......................38 Figure 13.....3 Membership SubSystem..............................................................................................15 Request Review.........1 Index Form...........................................................4 Search Form..................................................................40 Figure 13............................9 Change Password Form...............................................................................................................................................................11 Figure 6.........................11 Book Acquisition Form.......................................1 Use Case Diagram.........13 Issue Details Form..................................2 Login Form...........................................................................................................................................................................LIST OF FIGURES Figure 3..................39 Figure 13...............................................4 Acquisition SubSystem ...........................................................................................................................13 Figure 13....................................41 Figure 13............................................................................................................................................................................................................................42 Figure 13........6 Book Return Form............................................11 Figure 4.40 Figure 13...........................................5 Book Issue Form.46 iv ............................1 ER Diagram................................................................................................................................................................................................................................................1 Context Level DFD for Online Library Management System ..............................................................................................................................39 Figure 13............43 Figure 13.....................................41 Figure 13.............10 Figure 4......................2 First Level DFD for Login SubSystem...............................................................................................................................45 Figure 13.....................................43 Figure 13.............45 Figure 13.............................................7 User’s Entry Form..10 Registration Form...................42 Figure 13....................................................10 Figure 4........................................38 Figure 13.........8 Purchase Request Form.....6 Change Password SubSystem............................................................................11 Figure 4....................................9 .......................................................10 Figure 4......................................................................................................................................12 Book Deletion Form....................................................14 Fine Details Form...........

He/She can search books. search for books. Other functions include maintain issue policy. He maintains the different policy required for the OLIMS. and delete operation on books. view fine details and request for purchasing a new book.ONLINE LIBRARY MANAGEMENT SYSTEM 1. view fine details of a particular user and view books issued to a particular user. The user (student/faculty/staff) is the end user. Online Library Management System (OLIMs) as it named is basically an intranet based application for providing usability both to the student and librarian with added security. view books issued to him/her. The main functions of the librarian includes maintenance of books. 5 . INTRODUCTION This project is aimed to aid the Library Management System of any organization in online way. maintain fine policy. Inside maintenance of books he can add. The overall system operator is the librarian. view purchase requests.

12 R1.5 System Functions Ref # R1. This is an Intranet based application that can be accessed throughout the campus.14 R1. REQUIREMENT ANALYSIS 2. 2. It is used to search books. requests to buy a new book.11 R1.1 Project Online Library Management System 2.15 R1. The system should have a link from allthe module to their Evident respective pages. 2. Help.16 Function Category The system should display the links to login into the system Evident It should show the links to three modules of the online library Evident management system Loginas. It should provide facility for all users to choose proper Evident category to login into the system. The system should provide a login form where the userid and Evident password to be entered. Berhampur. 2.ONLINE LIBRARY MANAGEMENT SYSTEM 2. Orissa. 6 .2 Overview Statement The project is aimed at developing an Online Library Management System(OLIMS) for the college library. The system should automatically validate the userid and the Evident password. calculate fines and many other applications.3 Customer National Institute of Science and Technology.13 R1.4 Goal of the Module The project helps in issuing the books online for the college library that is an Intranet based application. About us.

27 R1.29 R1.20 R1. publication and category. The fine details module for the users should be able to display Evident the fine amount of a particular user.17 R1. publication and category. The purchase request module for the users should be able add Evident new requests . The book return module for the librarian should be able to Evident return the books.34 2.18 R1. Evident R1.21 R1. The book acquisition module for the librarian should be able to Evident add new books to the library.28 R1.32 R1. The book issue module for the librarian should be able to issue Evident the books. The system should be able to accept the purchase request Evident made by the users.ONLINE LIBRARY MANAGEMENT SYSTEM R1. author.6 System Attributes Attribute Detail and Boundary Constraint 7 .19 R1. The issue details module for the users should be able to Evident display the issued details of a particular user. The change password module for the users should be able to change the password.31 R1.23 R1.24 R1.25 R1. The book information module for the librarian should be able Evident to display the detail information of all the books present in the library. The request review module for the librarian should be able to Evident display all the requests made by the users. All the modules should display information according to the Evident category of user who has logged in. title.30 R1.26 The system should ask for sign up to new users. Evident It should provide the registration form for new users to be Evident signed up. The book search module for the librarian should be able to Evident search books through bookid. The change password module for the librarian should be able Evident to change the password.33 R1. author. title. The system should have a help screen to help the users. The book deletion module for the librarian should be able to Evident delete books from the library.22 R1. The book search module for the users should be able to search Evident books through bookid.

JavaScript P-III or above. HTML.40 Gb Hard disk Intranet based application 8 . Apache server.ONLINE LIBRARY MANAGEMENT SYSTEM Software Hardware Network Oracle(9i).128 MB RAM or above.JSP.

1 ER Diagram 9 . ENTITY RELATIONSHIP DIAGRAMS empid maili d name Librarian returndat e empid addres s 1 issuedate i s s u e d b y y name bookid i s s u e d b y phoneno empi d nam e deptnam e N N bookca t authorna meme price issued to studid bookstatus password N Book issued to Faculty M M maili d deptnam e issued to Staff M maili d N bookna me edition addres s phoneno maili d phoneno batc h M Student nam e branch addres s phoneno mailid Figure 3.ONLINE LIBRARY MANAGEMENT SYSTEM 3.

ONLINE LIBRARY MANAGEMENT SYSTEM 4.1 Form Valid User Invalid Userid Or Password User Entry Form Figure 4.1 Context Level DFD for Online Library Management System Librarian Librarian Entry Faculty/ Staff/ Student Login SubSystem 1.0 Book Search Registration Purchase Request Purchase Request Reveiw Book Acquisition Issue Details Change Password Fine Details Figure 4.2 First Level DFD for Login SubSystem 10 . DATAFLOW DIAGRAMS Login Book Information Book Transaction Online Library Management System 1.

2 Valid data MEMBERSHIP EMPLOYEE Valid data STUDENT Figure 4.3 Book Figure 4.3 Membership SubSystem Valid data data Librarian Invalid data Acquisition Subsystem 1.4 Acquisition SubSystem Faculty / Staff / Student Userid Password Change Password SubSystem 1.6 Change Password SubSystem 11 .ONLINE LIBRARY MANAGEMENT SYSTEM Valid data Valid data Userid.4 Valid data Login Invalid data Figure 4. Password LOGIN Faculty / Staff / Student Memberid Memberdate Invalid data Membershi p SubSystem 1.

View fine details 12 . Scenario #3.2 (normal) Use Case #2/ MAINTAIN BOOK This is used to maintain the book details.2 (normal) Issue a book Return a book Use Case #4/ MAINTAIN PURCHASE REQUEST This use case is used to maintain purchase request details. Scenario #4.1 (normal) Scenario #4.2 (normal) Scenario #2.3 (normal) Acquire new book. Scenario #2.1 (normal) Use Case #6/SEARCH This is used to search the books.1 (normal) Scenario #3.1 (normal) Scenario #1.1 (normal) Search.ONLINE LIBRARY MANAGEMENT SYSTEM 5.. LIST OF USE CASES AND SCENARIOS Use Case #1/MAINTAIN USER DATA This use case is used to maintain the user details like user category. Scenario #1. Scenario #6.2 (normal) Accept purchase request View purchase request Use Case #5/MAINTAIN FINE DETAILS This use case is used for displaying the fine details of a user.1 (normal) Scenario #2. userid and password. Delete book Books Issued LoginAs user Add new user Use Case #3/MAINTAIN TRANSACTION This is used to maintain the transaction of books. Scenario #5.

1 Use Case Diagram 13 .ONLINE LIBRARY MANAGEMENT SYSTEM 6. USE CASE SPECIFICATIONS Online Library Management system Maintain Userdata Maintain Books Librarian Maintain Transaction Maintain Purchase Request User Maintain Fine Details Search Figure 6.

R1.33 Typical Course of Action Scenario #1. Scenario #1.19. Staff.15. Line 2: Empty or wrong password indicate error and displays the error message along with the “BACK” button. Student This use case is used to login the userid and password and also to create an account for the new user. Faculty.14. R1. R1. R1. The system then checks for the validity of the userid and password from the data base. R1. Primary R1.1(normal) LoginAs user Use Case #1/MAINTAIN THE USER DATA Actor Action System Response 1 User types the userid in the login 2 screen The user then types in the password 3 assigned to him and clicks on “submit”.11.24.17.1(normal) Typical Course of Action 14 Add new user Use Case #1/MAINTAIN THE USER DATA . Alternate Course: Line 1: Empty or wrong userid indicate error and displays the error message along with the “BACK” button.18. if it is correct then the user page is displayed for student.ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #1 Maintain User Data Module #/Name Actors Purpose Overview Type Cross reference Online Library Management System Librarian.16. R1. R1. guest and teacher user and librarian page for the librarian.13. R1. R1. The userid and the password of the user have to be entered. R1.12.

Add the user details 15 .ONLINE LIBRARY MANAGEMENT SYSTEM Actor Action System Response 1 Enter the new user details to be 2 added Click SUBMIT to add the user 3 details Alternate Course: Line 1: Invalid userid indicates error message with “BACK” button.

2(normal) Delete book Use Case #2/ MAINTAIN BOOK Actor Action System Response 1 The Librarian clicks on the book 2 deletion in the Librarian home page. . The Librarian fills the fields like 3 bookid and the cause of deletion and then click “submit”. 1. Librarian should keep detail information of the books Primary R1. Alternate Course: Line 1: Invalid bookid details indicate error Scenario #2. Alternate Course: Line 2: Invalid bookid details indicate error Scenario #2.34. R1.23.1(normal) Acquire new book Use Case #2/ MAINTAIN BOOK Actor Action 1 Select the category under which the 2 book to be added Enter the book details System Response 3 System then verifies the information in the various fields and if correct then displays the success message.24.35 Typical Course of Action Scenario #2. R1.21.ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #2 Maintain Book Module #/Name Actors Purpose Overview Type Cross reference Online Library Management System Librarian To maintain the book information.. 16 System then verifies the information in the fields and if correct then displays the success message. R1.3(normal) Books Issued Use Case #2/ MAINTAIN BOOK Actor Action System Response 1 Enter the userid to view the issued 2 Displays the books issued.25. R1.

ONLINE LIBRARY MANAGEMENT SYSTEM book. 17 . Alternate Course: Line 1: Invalid userid details indicate error.

Librarian can issue a book to the users Secondary R1.31 Typical Course of Action Scenario #3.bookid and return 2 System should cancel the issued date Alternate Course: Line 1:Invalid userid and bookid indicate error.bookid.ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #3 Maintain Transaction Module #/Name Actors Purpose Overview Type Cross reference Online Library Management System Librarian Used for issuing and canceling book to user. 18 .title.30. Scenario #3.issue 2 System should issue the book to the date and return dateto issue Alternate Course: Line 1:Invalid bookid and userid indicate error.1(normal) Issue a book Use Case #3/MAINTAIN TRANSACTION Actor Action System Response 1 Enter the userid .2(normal) Return an issued book Use Case #3/MAINTAIN TRANSACTION Actor Action System Response 1 Enter the userid.R1. book user.

23.Faculty. Alternate Course: Line 1: Invalid userid indicate error Scenario #4. 1.Staff.2(normal) View purchase request Use Case #4/ MAINTAIN PURCHASE REQUEST Actor Action 1 Ask for the request details.staff and student can add purchase request .1(normal) Accept purchase request Use Case #4/ MAINTAIN PURCHASE REQUEST Actor Action System Response 1 Enter the userid and the purchase 2 System verifies the userid and if request .25. Secondary R1. 1.32 Typical Course of Action Scenario #4.ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #4 Maintain Purchase Request Module #/Name Actors Purpose Overview Type Cross reference Online Library Management System Librarian. correct then adds the request with a success message. Librarian can view purchase request details and Faculty. Alternate Course: Line 1: Invalid userid indicate error System Response 2 Displays the purchase request. Use Case #5 Maintain fine details Module #/Name Online Library Management System 19 . Student Used for adding / viewing the purchase request details.

22 Typical Course of Action Scenario #5.ONLINE LIBRARY MANAGEMENT SYSTEM Actors Purpose Overview Type Cross reference Librarian.Student Used for viewing the fine details. Alternate Course: Line 1: Invalid userid indicate error details 20 .1(normal) View fine details Use Case #5/MAINTAIN FINE DETAILS Actor Action System Response 1 Enter the userid to request for the 2 System should display the fine fine details.Staff. Secondary R1.faculty. User can view the fine details.

Secondary R1. Staff. Student Used for searching books.28 Typical Course of Action Scenario #6. 21 . Faculty.20.1(normal) Search Use Case #6SEARCH Actor Action 1 User select the search category System Response 2 Display the search output.ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #6 Maintain Search Module #/Name Actors Purpose Overview Type Cross reference Online Library Management System Librarian. Able to search according to search category.R1.

4. 2. 22 . User: One who intends to use this software Invalid user: One who does not have a valid userid and password to access the system Valid user: One who does have a valid userid and password to access the system . Login: The event through which the user gains access to the system. 3. TECHNICAL DICTIONARY 1.ONLINE LIBRARY MANAGEMENT SYSTEM 7. 6. 5. Librarian: One who manages the whole Online Library Management System Input validation: The checking of details entered by the user at the interface level.

edition. bookstatus. [T#6/Booktransaction] This table stores information about of transaction details stores bookid. phoneno. location. author. userid. [T#2/Student] This table stores information about the students includes studid. address. [T#4/Membership] This table stores information about all the members of the library includes memid. mailed. suggestion. acquisitioned. phoneno. edition. PERSISTENCE DESIGN [T#1/Login] This table stores the information about the User login includes category. returndate. password. dateofjoin. desig. issuedate. publishername. requestdate. acquisitiondate. memname. ename. [T#3/Employee] This table stores information about the employees (Faculty and Staff) includes empid. bookcat. title. deptname. mailed. memid. branch. tilte.ONLINE LIBRARY MANAGEMENT SYSTEM 8. studname. [T#5/Book] This table stores all the details of book includes bookid. 23 . batch. contactadd. [T#7/Purchaserequest] This table contains information of book request details stores memid. authorname. memdate. price. pages. memtype.

Userid Y String It stores the userid which is primary key in this table. DATA DICTIONARIES Table#/Name Module#/Name Project Name Description Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 1/LOGIN 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of user login Master userid Nibha kumari. Table#/Name Module#/Name Project Name Description Type 2/STUDENT 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of student Master 24 . Y String String 3.ONLINE LIBRARY MANAGEMENT SYSTEM 9. Subhalaxmi Chaudhury Charulata Palai NA 9 10 20 1. 2. Password Y It stores the password entered by the user. Category It stores the category of the user.

branch Y It stores the branch entered by the student. 4. Subhalaxmi Chaudhury Charulata Palai NA 9 30 20 4 100 15 50 1. studid Y String It stores the student id which is primary key in this table. phoneno Y Number It stores the phoneno entered by the student. 2. 7.ONLINE LIBRARY MANAGEMENT SYSTEM Key(s) Initial Size Growth Rate Designed by Checked by Modifications studid Nibha kumari. 5. String 25 . mailid Y It stores the mailed entered by the student. 6. batch Y It stores the batch entered by the student. address Y String It stores the address entered by the student. studname It stores the name of the student. Y String String Number 3.

deptname Y String It stores the department name entered by the employee. Subhalaxmi Chaudhury Charulata Palai NA 9 30 15 30 8 100 11 50 1. phoneno Y Number It stores the phone number entered by the employee. mailid Y String It stores the mailid entered by the employee. ename It stores the name of the employee. 5. 4. contactadd Y String It stores the date of join entered by the employee. 26 . 8. empid Y String It stores the employee id which is primary key in this table. desig Y String It stores the designation (faculty/staff) entered by the employee. Y String 3. 7. 6. dateofjoin Y Date It stores the date of join entered by the employee.ONLINE LIBRARY MANAGEMENT SYSTEM Table#/Name Module#/Name Project Name Description Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 3/EMPLOYEE 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of employee Master empid Nibha kumari. 2.

Subhalaxmi Chaudhury Charulata Palai NA 9 30 10 8 1. 4. memdate Y Date It stores the membership date entered by the member. memid Y String It stores the member id which is reffered from login table. 2. memtype Y String It stores the member type entered by the member.ONLINE LIBRARY MANAGEMENT SYSTEM Table#/Name Module#/Name Project Name Description Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 4/MEMBERSHIP 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of membership Master memid Nibha kumari. memname It stores the name of the member. Table#/Name Module#/Name Project Name Description Type 5/BOOK 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of membership Master 27 . Y String 3.

Subhalaxmi Chaudhury Charulata Palai NA Y Y Y Y Y Y Y Y Y Y Y Y String String String Date String String Number String String Number Number Date 7 20 50 30 30 5 5 5 13 7. It stores the availability status of a particular book. Table#/Name Module#/Name Project Name Description Type Key(s) 6/BOOKTRANSACTION 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of transaction Transaction memid 28 . of pages in a book. 5. 10. It stores the date on which the book has been acquired. bookid bookcat title authorname bookid Nibha kumari.2 10 8 It stores the book id which is primary key in this table. It stores the author name of the book. 11. It stores the no. 2. It stores the edition of the book. Publishername edition pages location bookstatus price acquisitionid acquisitiondate It stores publisher name of the book.ONLINE LIBRARY MANAGEMENT SYSTEM Key(s) Initial Size Growth Rate Designed by Checked by Modifications 1. 8. It stores the acquisition id of a book. 4. 7. It stores the price of a book. 3. 9. 6. It stores name of the book. It stores the book in a particular location. It stores the book category. 12.

5. 2. duedate It stores the due date. issuedate It stores the issue date. 3. fineamt It stores the total fine amount. 6. bookid Y String It stores the book id which is reffered from the book table. Y Y Y Y Date Date Date Number 29 . memid Y String It stores the member id which is referred from the membership table.ONLINE LIBRARY MANAGEMENT SYSTEM Initial Size Growth Rate Designed by Checked by Modifications Nibha kumari. Subhalaxmi Chaudhury Charulata Palai NA 9 7 8 8 8 4 1. returndate It stores the return date. 4.

10. 5. 4. Sting String String 6. LIST OF CLASSES Class # 1/ clsLoginDetails Class # 2/ clsStudentDetails Class # 3/ clsEmployeeDetails Class # 4/ clsMemberDetails 30 .. 2. Subhalaxmi Chaudhury Charulata Palai NA 9 50 30 5 100 8 1. author Y It stores the author name of the book. suggestion Y It stores the user suggestion for the book. requestdate Y Date It stores the date on which a request for a book has been made. edition Y It stores the edition of the requested book. title Y String It stores the book name which has to be brought.ONLINE LIBRARY MANAGEMENT SYSTEM Table#/Name Module#/Name Project Name Description Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 7/PURCHASEREQUEST 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of purchase request Transaction memid Nibha kumari. 3. memid Y String It stores the member id which is referred from the membership table.

CLASS DEFINITIONS Class#1 Attribute category userid M/P P P Data Type String String 31 clsLoginDetails Description/Prototype It stores the user category It stores user id .ONLINE LIBRARY MANAGEMENT SYSTEM Class # 5/ clsBookDetails Class # 6/ clsBookTransactionDetails Class # 7/ clsPurchaseRequest 11.

of employee It stores the mailid of employee Class#4 clsMembershipDetails Attribute memid memname memtype memdate Class#5 M/P P P P P Data Type String String String Date Description/Prototype It stores the membership id It stores the name of member It stores the membership type It stores the membership date clsBookdetails Attribute bookid M/P P Data Type String Description/Prototype It stores the book id in the table 32 .ONLINE LIBRARY MANAGEMENT SYSTEM password Class#2 Attribute studid studname branch batch address Phoneno Mailed Class#3 Attribute empid ename desig deptname dateofjoin conaddress phoneno mailed P String It stores password clsStudentDetails M/P P P P P P P P Data Type String String String Number String Number String Description/Prototype It stores the student id It stores the name of student It stores the branch name It stores the batch of student It stores the address of student It stores the phoneno.of student It stores the mailid of student clsEmployeeDetails M/P P P P P P P P P Data Type String String String String Date String Number String Description/Prototype It stores the employee id It stores the name of employee It stores the designation of employee It stores the department name of employee It stores the date of join of employee It stores the contact address of employee It stores the phoneno.

ONLINE LIBRARY MANAGEMENT SYSTEM bookcat title authorname publishername edition pages location bookstatus price acquisitionid acquisitiondate P P P P P P P P P P P String String String String String Number String String Number Number Date It stores the book category It stores the book name It stores the author name It stores the publisher name It stores the edition It stores the no. of pages in a book It stores the location of a particular book It stores the availability status of a book It stores the price of the book It stores the acquisition id It stores the date on which the has been acquired 33 .

ONLINE LIBRARY MANAGEMENT SYSTEM Class#6 clsBookTransactionDetails Attribute memid bookid issuedate duedate returndate fineamt Class#7 M/P P P P P P P Data Type String String Date Date Date Number Description/Prototype It stores the member id in the table It stores the book id It stores the date of issue It stores the due date of return It stores the date on which the book has returned It stores the total fine amount clsPurchaseRequestDetails Attribute memid title author edition suggestion requestdate M/P P P P P P P Data Type String String String String String Date Description/Prototype It stores the member id in the table It stores the book name It stores the author name It stores the edition It stores the suggestion for the requested book It stores the date on which a request has been made 34 .

[F# 4/Help] It contains the help page for the users. book issue.change password for the librarian. book deletion. [F#9/BookAcquisition] This form is used for adding book details. book search. [F# 5/Login] Authorized user can enter in to the system through valid userid and password. [F#7/BookInformation] This form displays the details of all the books. book return. [F# 2/LoginAs] It contains the user category to select to enter in to the login form. category. [F# 3/AboutUs] It contains the information about the developer group. [F#8/ Book Search] It is used for searching the books according to the bookid. LIST OF FORMS [F# 1/Index] It is the home page which contains three buttons loginas. 35 . author. request review. title.aboutus and help for all type of users. book acquisition. publication as required.ONLINE LIBRARY MANAGEMENT SYSTEM 12. [F#6/Librarian] This form contains eight buttons such as book information.

[F#19/ChangePasswordConfirm] This form is used for giving a message that change password is confirm. [F#16/ BookReturned] This form is used for giving a message that a book has been returned successfully. [F#14/BookIssued ] This form is used for giving a message that a book has been issued successfully [F#15/ BookReturn] This form contains one button called book id so that specified user’s book will be returned . [F#17/RequestReview] This is the form is used for viewing the purchase requests made by the users. issued details. [F#11/ BookDeletion] This page is used for deleting a specific book details by giving the book id. [F#12/ BookDeleted] This form is used for giving a message that a book has been deleted successfully [F#13/BookIssue ] This is the form contains two buttons for entering member id and book id. change password for the users. [F#20/User] This form contains eight buttons such as book search.ONLINE LIBRARY MANAGEMENT SYSTEM [F#10/ BookAdded] This form is used for giving a message that a book has been added successfully. [F#18/ChangePassword] This is the form is used for changing the password both by the librarian and user. purchase request. fine details. 36 .

userid. Title. and email id. contact address. date of joining. [F#22/FineDetails] This form is used for viewing the total fine amount of a specific user by entering the user id . [F#23/PurchaseRequest] This is the form is used to send the purchase requests by giving user id. author. [F#24/PurchaseRequestConfirm] This form is used for giving a message that a purchase request has been sent successfully.ONLINE LIBRARY MANAGEMENT SYSTEM [F#21/IssuedDetails] This is the form is used for viewing the issue details of a specific user by entering the user id. 37 .batch. phone no. suggestion and date of request. edition. membership date. branch. [F#25/Refistration] This form is used to add new user to the system by entering name. membership type. confirm password. password.dept name.

FORM DESIGN DETAILS Index form Figure 13.ONLINE LIBRARY MANAGEMENT SYSTEM 13. About Us And Help. Login Form Figure 13.2 Login Form 38 .1 Index Form This form is the index form used for all the users which contains LoginAs.

4 Search Form 39 .ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to enter in to the system by entering the userid and password. issuing book.3 Librarian’s Entry Form This form is librarian’s entry form contains eight buttons used for viewing book details searching the books. Librarian’s entry form Figure 13. deleting book details. acquiring new book. returning book and viewing purchase requests. Search Figure 13.

author. Book Return Figure 13.5 Book Issue Form This form is used for issuing a book by giving userid so that book will be issued in his/her id. title.ONLINE LIBRARY MANAGEMENT SYSTEM This form is used for searching the books according to bookid. publisher and category Book Issue Figure 13.6 Book Return Form 40 .

books issued used for viewing the books issued.7 User’s Entry Form This form is user’s entry form containing five buttons searching the books.ONLINE LIBRARY MANAGEMENT SYSTEM This form is used for returning book by entering the bookid .8 Purchase Request Form 41 . viewing the fine details and request for purchase of a book. User’s entry form Figure 13. Purchase Request Figure 13.

password.ONLINE LIBRARY MANAGEMENT SYSTEM This form is used for purchase of a new book by entering the user id. Change Password Figure 13. new password and confirm password.10 Registration Form 42 . Registration Figure 13.9 Change Password Form This form is used to change the password by entering user id .

12 Book Deletion Form 43 . Book Deletion Figure 13.11 Book Acquisition Form This form is used to add new books to the library.ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to add new user by registering them. Book Acquisition Figure 13.

44 .ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to delete book information from the system.

13 Issue Details Form This form is used to view the issue details of a specific user by entering the user id.ONLINE LIBRARY MANAGEMENT SYSTEM Issue Details Figure 13.14 Fine Details Form This form is used to view the total fine amount of a specific user by entering the user id. Fine Details Figure 13. 45 .

46 .15 Request Review This form is used to review the requests made by the users by the librarian.ONLINE LIBRARY MANAGEMENT SYSTEM Request Review Figure 13.

Error # 1 2 3 4 5 6 7 8 9 10 11 12 13 Error Description Invalid loginid Or password ERROR: Same Book id ERROR: Book id already present ERROR: User id already present ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field ERROR: Missing Field Name of Form Login Book Transaction Book Acquisition Registration Purchase Request Registration Book Acquisition Book Issue Book Return Issue Details Fine Details Change Password Search 47 . ERROR CODE DESIGN These are the anticipated errors and the accompanying messages.ONLINE LIBRARY MANAGEMENT SYSTEM 14.

1 To leave the user id field empty & submit ERROR: Missing Field ERROR:Missing Field ERROR: Missing Field.Book Acquisition: Book Acquisition Form 3. SCOPE OF IMPROVEMENT This project has a scope for improvement in the following areas • Currently the OLIMS allows applicants to issue books one by one. Purchase Request: Purchase Request Form 6.2 Enter without filling any field and submit ERROR: Missing Field 4. Login: Login Form 1.Book Transaction : Book Transaction Form 2.2 Enter without filling any field and submit 5. Login form disposed. 3. 48 .2 Enter a zero length password 1.1 To leave the user id field empty & submit 8. DESIGN OF TEST CASES Test Test Expected Response Case # 1. 4.1 To send a request without filling any field 6. Issue Details: Issue Details Form 7.1 Enter a zero length user id 1.Registration: Registration Form 4. 2.1 Enter already present book id for new ERROR: Same book id book. Fine Details: Fine Details Form 8.2 To leave some field empty and submit 7. ERROR: Missing Field. 16.1 Enter same book id for more than one ERROR:Same book id 2. ERROR: Missing Field.It can be bettered by allowing for multiple books simultaneously.3 Enter correct login name and password Enter Your Userid Enter Your Password User logged into system.2 transaction.1 To search without any search criteria 6.1 Enter already present member id for new ERROR: Same member id member. Enter Book Transaction without filling ERROR:Missing Field member id 3. Search: Book Search Form 5. ERROR: Missing Field.ONLINE LIBRARY MANAGEMENT SYSTEM 15.

49 .ONLINE LIBRARY MANAGEMENT SYSTEM • user. • One improvement for allowing the administrator to send email notifications to Another improvement for reserving a particular book borrowed by others currently and cancelling the reservation made earlier for a particular book.

Thus it puts an option for all categories of users to have the transaction details with added security features. which reduces the complexities arised in the “Manual Library System “ .This Intranet based application will provide facilities to different kinds of users.ONLINE LIBRARY MANAGEMENT SYSTEM 17. CONCLUSION This Online Library Management System will provide an automated s/w for the college library to search the books online . This integrated system allows both the user component and librarian component to work independently 50 .

51 .ONLINE LIBRARY MANAGEMENT SYSTEM REFERENCES [1] NTCS Project Documentation.

Sign up to vote on this title
UsefulNot useful