----------------------- Page 1----------------------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 April 2008 Under the guidance of Mrs. Charulata Palai ----------------------- Page 2----------------------NATIONAL INSTITUTE OF SCIENCE & TECHNOLOGY Palur Hills, Berhampur, Ori a - 761008, India ROLL # MCA200560825 ROLL # MCA200560849

----------------------- Page 3----------------------ABSTRACT This project is aimed at developing an online Library Management System (LiMS) f or the college library. t can be accessed This is an Intranet based application tha

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 an d the librarian eminders, component. report There are features like email notifications/r

generators etc in this system. i ----------------------- Page 4----------------------ACKNOWLEDGEMENT We express our deepest sense of gratitude to our advisor Mrs. Charulata Palai fo r

providing us an opportunity to design a project entitled Online Library Managemen t System and guiding us till the completion of this project. We also express our sincere thanks to all the laboratory members of NIST for the ir 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 givin g his valuable time throughout our project. We acknowledge with immense pleasure the sustained interest, encouraging attitud e and constant inspiration rendered by Prof. Sangram Mudali, Director, N.I.S.T. Hi s continued drive for better quality in everything that happens at N.I.S.T. and se lfless 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 ----------------------- Page 5----------------------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 .............. ............................. 11. CLASS DEFINITIONS .................... 12. LIST OF FORMS 31 30 .................. ............. ................................................................................ ................................ 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 ----------------------- Page 6----------------------LIST OF FIGURES Figure 3.1 ER Diagram........................................................... ...................................................................9 ................................................................................ ................................................................................ ..10 Figure 4.1 Context Level DFD for Online Library Management System .............. ................................10 Figure 4.2 First Level DFD for Login SubSystem.................................. .................................................10 Figure 4.3 Membership SubSystem................................................. ........................................................11 Figure 4.4 Acquisition SubSystem ............................................... ...........................................................11 Figure 4.6 Change Password SubSystem............................................ .....................................................11 Figure 6.1 Use Case Diagram..................................................... .............................................................13 Figure 13.1 Index Form..........................................................

.................................................................38 Figure 13.2 Login Form.......................................................... .................................................................38 Figure 13.3 Librarians Entry Form................................................ .........................................................39 Figure 13.4 Search Form......................................................... .................................................................39 Figure 13.5 Book Issue Form..................................................... ..............................................................40 Figure 13.6 Book Return Form.................................................... ............................................................40 Figure 13.7 Users Entry Form..................................................... ...........................................................41 Figure 13.8 Purchase Request Form............................................... .........................................................41 Figure 13.9 Change Password Form................................................ ........................................................42 Figure 13.10 Registration Form.................................................. .............................................................42 Figure 13.11 Book Acquisition Form.............................................. ........................................................43 Figure 13.12 Book Deletion Form................................................. ..........................................................43 Figure 13.13 Issue Details Form................................................. .............................................................45 Figure 13.14 Fine Details Form.................................................. .............................................................45 Figure 13.15 Request Review..................................................... .............................................................46 i ----------------------- Page 7----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 1. INTRODUCTION This project is aimed to aid the Library Management System of any organizati on in online way. Online Library Management System (OLIMs) as it named is basical ly an intranet based application for providing usability both to the student and l ibrarian with added security. The overall system operator is the librarian. He maintains the different pol icy required for the OLIMS. The main functions of the librarian includes maintenance of b ooks. on Inside maintenance on books. Other of books he can add, and delete operati

functions include maintain issue policy, maintain fine policy, view purchase

requests, search for books, view fine details of a particular user and view books issu ed to a particular user. The user (student/faculty/staff) is the end user. He/She can search books, v iew books issued to him/her, view fine details and request for purchasing a new book. 5 ----------------------- Page 8----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 2. REQUIREMENT ANALYSIS 2.1 Project Online Library Management System 2.2 Overview Statement The project is aimed at developing an Online Library Management System(OLIMS ) for the college library. This is an Intranet based application that can be a ccessed throughout the campus. 2.3 Customer National Institute of Science and Technology, Berhampur, Orissa. 2.4 Goal of the Module The project helps in issuing the books online for the college library that i s an Intranet based application. It is used to search books, requests to buy a new book, c alculate fines and many other applications. 2.5 System Functions Ref # Category R1.11 Evident R1.12 Evident Function The system should display the links to login into the system It should show the links to three modules of the online library management system Loginas, Help, About us.

R1.13 Evident

The system should have a link from allthe module to their

respective pages. R1.14 It should provide proper Evident R1.15 Evident R1.16 Evident

facility

for

all

users

to

choose

category to login into the system. The system should provide a login form where the userid and password to be entered. The system should automatically validate the userid and the password. 6

----------------------- Page 9----------------------ONLINE LIBRARY MANAGEMENT SYSTEM R1.17 The system should ask for sign up to new users. Evident R1.18 It should provide the registration form for new users to be Evident R1.19 signed up. All the modules should display information according to the Evident category of user who has logged in. The book search module for the users should be able to search Evident

R1.20

books through bookid, title, author, publication and category. R1.21 The issue details module for the users should b able to Evident R1.22 display the issued details of a particular user. The fine details module for the users should be able to display Evident the fine amount of a particular user. The purchase request module for the users should be able add Evident new requests . The change password module for the users should be able to change the password. The system should be able to accept Evident the purchase request

R1.23

R1.24 R1.25

R1.26

made by the users. The book information module for the librarian should be able Evident to display the detail information of all the books present in

R1.27

the library. The book acquisition module for the librarian should be able to Evident add new books to the library. The book search module for the librarian should be able to Evident search books through bookid, title, author, publicati

R1.28

on

and R1.29 category. The book deletion module for the librarian should be able to Evident delete books from the library. The book issue module for the librarian should be able to issue Evident the books. The book return module for the librarian should be able to Evident return the books. The request review module for the librarian should be able to Evident display all the requests made by the users. The change password module for the librarian should be able Evident to change the password. The system should have a help screen to help the users. Evident

R1.30

R1.31

R1.32

R1.33

R1.34

2.6 System Attributes Attribute Detail and Boundary Constraint 7 ----------------------- Page 10----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Software Hardware Network Oracle(9i),JSP, Apache server, HTML, JavaScript P-III or above,128 MB RAM or above,40 Gb Hard disk Intranet based application 8 ----------------------- Page 11----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 3. ENTITY RELATIONSHIP DIAGRAMS em pid

maili name d Libra rian returndat 1 issuedate e deptnam empid e addres empi s i s s u e d b y phoneno d bookid nam password name bookstatus e N N N issued issued maili Faculty to d M M M bookca t edition maili d addres authorna s meme bookna phoneno deptnam maili N to Book Staff i s s u e d b y y

me e phoneno price issued to batc h studid M nam Student branch e addres mailid s phoneno

Figure 3.1 ER Diagr am 9 ----------------------- Page 12----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 4. DATAFLOW DIAGRAMS Login Book Information Book Transaction Book Search Onli ne Libra ry Registration anagement System Purchase Request M

1.0 Purchase Request

Reveiw

Issue Details Book Acquisition Change Password Fine Details Figure 4.1 Context Level DFD for Online Library Management System Librarian Librarian Entry Faculty Form Staff Valid User Student Invalid Userid User Entry Or Form Password Figure 4.2 First Level DFD for Login SubSystem SubSystem 1.1 Login

10 ----------------------- Page 13----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Valid data Valid data Faculty rshi Staff MEMBERSHIP p Valid data Student LOGIN Userid, Password Membe

SubSy stem 1.2 Memberid Memberdate EMPLOYEE Invalid data Valid data STUDENT Figure 4.3 Membership SubSystem Valid data data Librarian Invalid Book data Figure 4.4 Acquisition SubSystem Userid Valid data Password nge Faculty sword Staff Student SubSy stem 1.4 Login Invalid data Figure 4.6 Change Password SubSystem 11 ----------------------- Page 14----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 5. LIST OF USE CASES AND SCENARIOS Use Case #1/MAINTAIN USER DATA Pas Cha Acquisition Subsystem 1.3

This use case is used to maintain the user rid and password. Scenario #1.1 (normal) Scenario #1.2 (normal)

details like user category, use

LoginAs user Add new user

Use Case #2/ MAINTAIN BOOK This is used to maintain the book details. Scenario #2.1 (normal) Scenario #2.2 (normal) Scenario #2.3 (normal) Use Case #3/MAINTAIN TRANSACTION This is used to maintain the transaction of books. Scenario #3.1 (normal) Scenario #3.2 (normal) Issue a book Return a book Acquire new book. Delete book Books Issued

Use Case #4/ MAINTAIN PURCHASE REQUEST This use case is used to maintain purchase request details. Scenario #4.1 (normal) Scenario #4.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. Scenario #5.1 (normal) Use Case #6/SEARCH This is used to search the books.. Scenario #6.1 (normal) Search. 12 ----------------------- Page 15----------------------ONLINE LIBRARY MANAGEMENT SYSTEM View fine details

6. USE CASE SPECIFICATIONS Online Library Management system Maintain Userdata Maintain Books Librarian Maintain Transaction Maintain User Purchase Request Maintain Fine Details Search Figure 6.1 Use Case Diagram 13 ----------------------- Page 16----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #1 in User Data Module #/Name Actors Purpose word and also Overview entered. Type Cross reference , R1.17, R1.18, Mainta Online Library Management System Librarian, Faculty, Staff, Student This use case is used to login the userid and pass to create an account for the new user. The userid and the password of the user have to be Primary R1.11, R1.12, R1.13, R1.14, R1.15, R1.16

R1.19, R1.24, R1.33 Typical Course of Action Scenario #1.1(normal) LoginAs user Use Case #1/MAINTAIN THE USER DA TA

Actor Action User types

the

userid

in

the

System Response login 3 The system then

2 checks

screen The user then types in the password for the to him and clicks on

assigned and password submit. is correct s displayed for

validity of the userid from the data base, if it then the user page i

student, guest and tea cher user and librarian page for the librarian. Alternate Course: Line 1: Empty or wrong userid indicate error and displays the error messag e along with the BACK button. Line 2: Empty or wrong password indicate error and displays the error messag e along with the BACK button. Scenario #1.1(normal) Add new user Use Case #1/MAINTAIN THE USER DA TA Typical Course of Action 14 ----------------------- Page 17----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 1 2 Actor Action Enter the added Click details Alternate Course: Line 1: Invalid userid indicates error message with BACK button. SUBMIT new to user add details the to user System Response be 3 Add the user details

15 ----------------------- Page 18----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #2 Maintain Book Module #/Name Actors Purpose Overview oks Type Cross reference Typical Course of Action Scenario #2.1(normal) uire new book IN BOOK 1 Actor Action Select the category under which the System Response Acq Use Case #2/ MAINTA Primary R1.21, 1.23, R1.24, R1.25, R1.34, R1.35 Online Library Management System Librarian To maintain the book information. Librarian should keep detail information of the bo

book to be added 2 Enter the book details he information and if correct

System then verifies t in the various fields then displays the suc

cess message. Alternate Course: Line 1: Invalid bookid details indicate error Scenario #2.2(normal) Delete book Use Case #2/ MAINTA IN BOOK 1 2 Actor Action The Librarian System Response clicks on the book like 3 System then verifies in the fields an

deletion in the Librarian home page. The Librarian fills the fields the information d if bookid and the cause of deletion and correct then then click submit..

displays the success messa

ge. Alternate Course: Line 2: Invalid bookid details indicate error Scenario #2.3(normal) Books Issued Use Case #2/ MAINTAI N BOOK Actor Action 1 Enter the userid to view the issued ued. 16 ----------------------- Page 19----------------------ONLINE LIBRARY MANAGEMENT SYSTEM book. Alternate Course: Line 1: Invalid userid details indicate error. 17 ----------------------- Page 20----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #3 ransaction Module #/Name Actors Purpose Overview Type Cross reference Typical Course of Action Scenario #3.1(normal) Issue a book Use Case #3/MAINTAIN TRANSACTIO N Actor Action 1 Enter the e book to the userid System Response ,bookid,title,issue 2 System should issue th user. Maintain T Online Library Management System Librarian Used for issuing and canceling book to user. Librarian can issue a book to the users Secondary R1.30,R1.31 System Response 2 Displays the books iss

date and return dateto issue Alternate Course:

Line 1:Invalid bookid and userid indicate error. Scenario #3.2(normal) issued book N Actor Action 1 Enter the the issued date Alternate Course: Line 1:Invalid userid and bookid indicate error. 18 ----------------------- Page 21----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #4 ase Request Module #/Name Actors Purpose ails. Overview culty,staff Type Cross reference Typical Course of Action Scenario #4.1(normal) hase request EST Actor Action 1 Enter the userid userid and if and the System Response purchase 2 System verifies th Accept purc Use Case #4/ MAINTAIN PURCHASE REQU Maintain Purch Online Library Management System Librarian,Faculty,Staff, Student Used for adding / viewing the purchase request det Librarian can view purchase request details and Fa and student can add purchase request . Secondary R1.23, 1.25, 1.32 userid,bookid and System Response return 2 System should book cance Return an Use Case #3/MAINTAIN TRANSACTIO

request . request with a

correct then adds the success message.

Alternate Course: Line 1: Invalid userid indicate error Scenario #4.2(normal)

View purchase request Use Case #4/ MAINTAIN PURCHASE REQUEST Actor Action 1 Ask for the request details. request. Alternate Course: Line 1: Invalid userid indicate error Use Case #5 n fine details Module #/Name Online Library Management System 19 ----------------------- Page 22----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Actors Purpose Overview Type Cross reference Typical Course of Action Scenario #5.1(normal) ew fine details ETAILS Actor Action 1 Enter the userid to request for the lay the fine fine details. Alternate Course: Line 1: Invalid userid indicate error 20 ----------------------- Page 23----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Use Case #6 intain Search Module #/Name Actors Purpose Online Library Management System Librarian, Staff, Faculty, Student Used for searching books. Ma System Response 2 System should details disp Vi Use Case #5/MAINTAIN FINE D Librarian,faculty,Staff,Student Used for viewing the fine details. User can view the fine details. Secondary R1.22 Maintai System Response 2 Displays the purchase

Overview Type Cross reference Typical Course of Action Scenario #6.1(normal) Search

Able to search according to search category. Secondary R1.20,R1.28

Use Case #6SEARCH Actor Action 1 User select the search category put. 21 ----------------------- Page 24----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 7. TECHNICAL DICTIONARY 1. 2. ccess User: One who intends to use this software Invalid user: One who does not have a valid userid and password to a the system 3. the system . 4. 5. m 6. Input validation: The checking of details entered by the user at the interface level. Login: The event through which the user gains access to the system. Librarian: One who manages the whole Online Library Management Syste Valid user: One who does have a valid userid and password to access System Response 2 Display the search out

22 ----------------------- Page 25----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 8. PERSISTENCE DESIGN [T#1/Login] This table , userid, stores the information about the User login includes category

password. [T#2/Student] This table stores information about the students includes studid, studname, branch, batch, address, phoneno, mailed. [T#3/Employee] This table stores information about the employees (Faculty and Staff) includ es empid, ename, desig, deptname, dateofjoin, mailed, phoneno, contactadd. [T#4/Membership] This table stores information about all the members of the library includes memid, memname, memtype, memdate. [T#5/Book] This table stores all the details of book includes bookid, bookcat, tilte, a uthorname, ce, publishername, edition, acquisitioned, acquisitiondate. [T#6/Booktransaction] This table stores tores bookid, memid, issuedate, returndate. [T#7/Purchaserequest] This table contains information of book request details stores memid, title , author, edition, suggestion, requestdate. 23 ----------------------- Page 26----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 9. DATA DICTIONARIES Table#/Name Module#/Name Project Name Description 1/LOGIN 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of user login information about of transaction details s pages, location, bookstatus, pri

Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 1. 9 Userid

Master userid Nibha kumari, Subhalaxmi Chaudhury Charulata Palai NA Y String

It stores the userid which is primary key in this table. 2. 10 It stores the category of the user. 3. 20 It stores the password entered by the user. 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 ----------------------- Page 27----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Key(s) Initial Size Growth Rate Designed by Checked by Modifications 1. studid Nibha kumari, Subhalaxmi Chaudhury Charulata Palai NA Password Y String Category Y String

studid Y String 9 It stores the student id which is primary key in this table. 2. studname 30 It stores the name of the student. 3. Y String

branch Y 20 It stores the branch entered by the student. 4. batch Y 4 It stores the batch entered by the student. 5. address Y 100 It stores the address entered by the student. 6. phoneno Y

String

Number

String

Number

15 It stores the phoneno entered by the student. 7. mailid Y 50 It stores the mailed entered by the student. 25 ----------------------- Page 28----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Table#/Name Module#/Name Project Name Description Type Key(s) Initial Size Growth Rate Designed by Checked by Modifications 1. 9 It stores the employee id which is primary key in this table. 2. ename 30 It stores the name of the employee. 3. Y String empid 3/EMPLOYEE 1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of employee Master empid Nibha kumari, Subhalaxmi Chaudhury Charulata Palai NA Y String String

desig Y String 15 It stores the designation (faculty/staff) entered by the employee. 4. deptname Y String 30 It stores the department name entered by the employee. 5. dateofjoin Y Date 8 It stores the date of join entered by the employee. 6. contactadd Y String 100 It stores the date of join entered by the employee. 7. phoneno Y Number 11 It stores the phone number entered by the employee. 8. mailid Y 50 It stores the mailid entered by the employee. 26 ----------------------- Page 29----------------------String

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

7 It stores the book id which is primary key in this table. 2. bookcat 20 Y String

It stores the book category. 3. title 50 Y String

It stores name of the book. 4. 30 It stores the author name of the book. 5. Publishername 30 Y String authorname Y Date

It stores publisher name of the book. 6. 5 It stores the edition of the book. 7. 5 It stores the no. of pages in a book. 8. 5 It stores the book in a particular location. 9. bookstatus 13 Y String location Y String pages Y Number edition Y String

It stores the availability status of a particular book. 10. price 7,2 Y Number

It stores the price of a book. 11. 10 It stores the acquisition id of a book. 12. 8 It stores the date on which the book has been acquired. Table#/Name 6/BOOKTRANSACTION acquisitiondate Y Date acquisitionid Y Number

Module#/Name Project Name Description Type Key(s)

1/ONLINE LIBRARY MANAGEMENT SYSTEM ONLINE LIBRARY MANAGEMENT SYSTEM Stores the information of transaction Transaction memid 28

----------------------- Page 31----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Initial Size Growth Rate Designed by Checked by Modifications 1.

Nibha kumari, Subhalaxmi Chaudhury Charulata Palai NA

memid Y String 9 It stores the member id which is referred from the membership table. 2. bookid Y String 7 It stores the book id which is reffered from the book table. 3. issuedate 8 It stores the issue date. 4. duedate 8 It stores the due date. 5. returndate 8 It stores the return date. 6. fineamt 4 It stores the total fine amount. Y Date

Date

Date

Number

29 ----------------------- Page 32----------------------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, Subhalaxmi Chaudhury Charulata Palai NA

1. 9

memid

String

It stores the member id which is referred from the membership table. 2. 50 It stores the book name which has to be brought. 3. author 30 It stores the author name of the book. 4. 5 It stores the edition of the requested book. 5. suggestion Y 100 It stores the user suggestion for the book. 6. 8 It stores the date on which a request for a book has been made.. 10. LIST OF CLASSES Class # 1/ clsLoginDetails Class # 2/ clsStudentDetails Class # 3/ clsEmployeeDetails Class # 4/ clsMemberDetails 30 ----------------------- Page 33----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Class # 5/ clsBookDetails Class # 6/ clsBookTransactionDetails Class # 7/ clsPurchaseRequest 11. CLASS DEFINITIONS Class#1 clsLoginDetails Attribute otype category er category userid id M/P P P Data Type String String 31 Description/Prot It stores the us It stores user requestdate Y String edition Y Sting title Y String

String

Date

----------------------- Page 34----------------------ONLINE LIBRARY MANAGEMENT SYSTEM password s password Class#2 clsStudentDetails Attribute ion/Prototype studid s the student id studname s the name of student branch s the branch name batch s the batch of student address s the address of student Phoneno tores the phoneno.of Mailed s the mailid of student Class#3 clsEmployeeDetails Attribute empid e id ename f employee desig tion of employee deptname epartment name of dateofjoin join of employee conaddress address of employee phoneno .of employee mailed of employee Class#4 clsMembershipDetails Attribute memid M/P P Data Type String Description/Prototype It stores the members P P P String String String It stores the name o It stores the designa It stores the d M/P P Data Type String Description/Prototype It stores the employe M/P P P P P P P Data Type String String String Number String Number Descript It store It store It store It store It store It s P String It store

String

student It store

P P P P

Date String Number String

employee It stores the date of It stores the contact It stores the phoneno It stores the mailid

hip id memname f member memtype hip type memdate hip date Class#5 clsBookdetails

P P P

String String Date

It stores the name o It stores the members It stores the members

Attribute bookid the table

M/P P

Data Type String

Description/Prototype It stores the book id in 32

----------------------- Page 35----------------------ONLINE LIBRARY MANAGEMENT SYSTEM bookcat title authorname publishername edition pages book location icular book bookstatus s of a book price acquisitionid acquisitiondate has been P P P P P String String Number Number Date It stores the location of a part It stores the availability statu It stores the price of the book It stores the acquisition id It stores the date on which the acquired 33 ----------------------- Page 36----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Class#6 ionDetails clsBookTransact P P P P P P String String String String String Number It It It It It It stores stores stores stores stores stores the book category the book name the author name the publisher name the edition the no. of pages in a

Attribute memid n the table bookid issuedate sue duedate

M/P P P P P

Data Type String String Date Date

Description/Prototype It stores the member id i It stores the book id It stores the date of is It stores the due date o

f return returndate on which the book has fineamt amount

Date

It stores

the date

Number

returned It stores the total fine

Class#7 clsPurchaseRequestDetails Attribute memid the table title author edition suggestion or the requested book requestdate h a request has been M/P P P P P P P Data Type String String String String String Date Description/Prototype It stores the member id in It It It It stores stores stores stores the the the the book name author name edition suggestion f

It stores the date on whic made

34 ----------------------- Page 37----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 12. LIST OF FORMS [F# 1/Index] It is the home page which contains three buttons loginas,aboutus and help fo r all type of users. [F# 2/LoginAs] It contains the user category to select to enter in to the login form. [F# 3/AboutUs] It contains the information about the developer group. [F# 4/Help] It contains the help page for the users. [F# 5/Login] Authorized user can enter in to the system through valid userid and password . [F#6/Librarian]

This form book search,

contains book

eight

buttons

such

as

book

information,

acquisition, book deletion, book issue, book return, request review,change p assword for the librarian. [F#7/BookInformation] This form displays the details of all the books. [F#8/ Book Search] It is used for searching the books according to the bookid, title, author, c ategory, publication as required. [F#9/BookAcquisition] This form is used for adding book details. 35 ----------------------- Page 38----------------------ONLINE LIBRARY MANAGEMENT SYSTEM [F#10/ BookAdded] This form is used for giving a message that a book has been added successful ly. [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 successf ully [F#13/BookIssue ] This is the form contains two buttons for entering member id and book id. [F#14/BookIssued ] This form is used for giving a message that a book has been issued successfu lly [F#15/ BookReturn] This form contains one button called book id so that specified users book wil l be returned .

[F#16/ BookReturned] This form is used for giving a message that a book has been returned success fully. [F#17/RequestReview] This is the form is used for viewing the purchase requests made by the user s. [F#18/ChangePassword] This is the form is used for changing the password both by the librarian an d user. [F#19/ChangePasswordConfirm] This form is used for giving a message that change password is confirm. [F#20/User] This form contains eight buttons such as book search, issued details, fine d etails, purchase request, change password for the users. 36 ----------------------- Page 39----------------------ONLINE LIBRARY MANAGEMENT SYSTEM [F#21/IssuedDetails] This is the form is used for viewing the issue details of a specific user b y entering the user id. [F#22/FineDetails] This form is used for viewing the total fine amount of a specific user by e ntering the user id . [F#23/PurchaseRequest] This is the form is used to send the purchase requests by giving user id, Title, author, edition, suggestion and date of request. [F#24/PurchaseRequestConfirm] This request form is used for has been sent giving a message that a purchase

successfully.

[F#25/Refistration] This form is used to add new user to the system by entering name,batch, bran ch,dept name, embership date of type, joining, userid, password, confirm password, m

membership date, contact address, phone no. and email id. 37 ----------------------- Page 40----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 13. FORM DESIGN DETAILS Index form Figure 13.1 Index Form

This form is the index form used for all the users which contains LoginAs, A bout Us And Help. Login Form Figure 13.2 Login Form 38 ----------------------- Page 41----------------------ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to enter in to the system by entering the userid and passw ord. Librarians entry form Figure 13.3 Librarians Entry Form This form is librarians entry form contains eight buttons used for viewing bo ok details searching the books, acquiring new book, deleting book details, issu ing book, returning book and viewing purchase requests. Search Figure 13.4 Search Form 39

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

This form is used for returning book by entering the bookid . Users entry form Figure 13.7 Users Entry Form This form is users entry form containing five buttons searching the books, bo oks issued uest for used for viewing the books issued, viewing the fine details and req

purchase of a book. Purchase Request Figure 13.8 Purchase Request Form 41 ----------------------- Page 44----------------------ONLINE LIBRARY MANAGEMENT SYSTEM This form is used for purchase of a new book by entering the user id. Change Password Figure 13.9 Change Password Form

This form is used id ,password, new

to

change

the

password

by

entering

use

password and confirm password. Registration Figure 13.10 Registration Form 42 ----------------------- Page 45----------------------ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to add new user by registering them. Book Acquisition Figure 13.11 Book Acquisition Form This form is used to add new books to the library. Book Deletion Figure 13.12 Book Deletion Form 43 ----------------------- Page 46----------------------ONLINE LIBRARY MANAGEMENT SYSTEM This form is used to delete book information from the system. 44 ----------------------- Page 47----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Issue Details Figure 13.13 Issue Details Form This form is used to view the issue details of a specific user by entering t he user id. Fine Details Figure 13.14 Fine Details Form This form is used to view the total fine amount of a specific user by enter ing the user id. 45

----------------------- Page 48----------------------ONLINE LIBRARY MANAGEMENT SYSTEM Request Review Figure 13.15 Request Review This form is used to review the requests made by the users by the librarian. 46 ----------------------- Page 49----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 14. ERROR CODE DESIGN These are the anticipated errors and the accompanying messages. 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 47 ----------------------- Page 50----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 15. DESIGN OF TEST CASES Test se Case # 1. Login: Login Form 1.1 Enter a zero length user id id 1.2 1.3 system. Enter a zero length password Enter correct login name and password Login Enter Your Password User logged form disposed. 2.Book Transaction : Book Transaction Form 2.1 Enter same book id for more than one ERROR:Sam Test Expected Respon 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

Enter Your User

into

e book id 2.2 Field member id 3.Book Acquisition: Book Acquisition Form 3.1 Enter already present book e book id 3.2 Field 4.Registration: Registration Form 4.1 Enter already present member id for new ber id 4.2 Field 5. Search: Book Search Form 5.1 To search without any search criteria ield 6. Purchase Request: Purchase Request Form 6.1 To send a request without filling any field Field. 6.2 Field. 7. Issue Details: Issue Details Form 7.1 To leave the user id field empty & submit Field. 8. Fine Details: Fine Details Form 8.1 To leave the user id field empty & submit Field. 16. SCOPE OF IMPROVEMENT This project has a scope for improvement in the following areas can be bettered by allowing for multiple books simultaneously. 48 ----------------------- Page 51----------------------ONLINE LIBRARY MANAGEMENT SYSTEM cations to user. thers Another improvement for reserving a particular book borrowed by o One improvement for allowing the administrator to send email notifi Currently the OLIMS allows applicants to issue books one by one.It ERROR: Missing ERROR: Missing To leave some field empty and submit ERROR: Missing ERROR: Missing ERROR:Missing F member. Enter without filling any field and submit ERROR: Missing ERROR: Same mem transaction. Enter Book Transaction without filling ERROR:Missing

id

for

new ERROR: Sam

book. Enter without filling any field and submit

ERROR: Missing

currently and cancelling the reservation made earlier for a particular book. 49 ----------------------- Page 52----------------------ONLINE LIBRARY MANAGEMENT SYSTEM 17. CONCLUSION This Online Library Management System e college library to search the books online .This Intranet based application will provide facilities to different kinds of users, which reduces the complexities arise d in the Manual Library System .Thus it puts an option for all categories of users to have the transaction details with added security features. This integrated system allows both the user component and librarian component to work independently 50 ----------------------- Page 53----------------------ONLINE LIBRARY MANAGEMENT SYSTEM REFERENCES [1] NTCS Project Documentation. 51 will provide an automated s/w for th