Final Project Report

SLIET LIBRARY MANAGEMENT SYSTEM
PROJECT REPORT ON
|LIBRARY MANAGEMENT SYSTEM}

For The Partial Fulfillment Of Diploma in Computer Science and Applications
Submitted By
SHAILBALA SHARMA (DCA/083026) SHAILZA KANWAR (DCA/083027) UMESH PATHAK (DCA/083031)
Under The Guidance Of

MISS MANISHA YADAV LECT. (C.S.E. DEPARTMENT)
Project Co-ordinator
MR. VINOD VERMA ASST. PROFESSOR (C.S.E. DEPARTMENT)
Department of Computer Science & Engineering SantLongowal Institute Of Engineering & Technology Longowal (Distt. Sangrur) ,Punjab.
Page 1
ACKNOWLEDGEMENT
We would like to acknowledge the help of all involved in the collation and review process of this Project, without whose support the project could not have been satisfactorily completed. A further special note of thanks goes to also to all the faculty of CSE Department whose contributions throughout the whole process from inception of the initial idea to final project have been immense valuable.
In particular, we thank Miss ManishaYadav (Lect. C.S.E. Department) who continuously prodded to keep the project and motivated us to accept the invitation to take on this project.
Obviously in any Project of this size it is impossible to remember, let only mention, everyone who had a hand in this work becoming what it is today. Various students and staff from The University of SLIET were critical in creating the final project. Their support was vital in achieving what we hope. The College deserves the greatest credit because their contribution were essential, giving us great platform to work. In the end, we again wish to thank all of the persons for their insights and excellent contributions to this Project. We also thank all of the people who assisted us in the reviewing process. We wholeheartedly thank everyone.
Page 2
CERTIFICATE
This is to certify that this report of LIBRARY MANAGEMENTSYSTEM embodies the original work done by SHAIL BALA ( DCA/083026), SHAILZA KANWAR( DCA/083027), UMESH PATHAK(DCA/083031)duringthis project submission as a partial fulfillment of theDIPLOMA IN COMPUTER SICENCE ,IV Semester, of the SANT LONGOWAL INSTITUTE OF ENGINEERING AND TECHNOLOGY.
Project Guide
Project Co-ordinator
MR. VINOD KUMAR VERMA
MISS MANISHA YADAV LECT. (C.S.E. DEPARTMENT)
ASST. PROFESSOR (C.S.E. DEPARTMENT)
Page 3
TABLE OF CONTENTS
1. Project Profile.5 2. Abstract...6 3. Introduction of Project..7 a) Goals b) Objectives c) Scope 4. Project Planning & Management.8 a) Project Development Approach b) Risk Management (i) Technical Risk (ii) Scheduling Risk (iii) Business Risk 5. Software Requirement Specification11 a) User Characteristics b) S/W Requirements c) H/W Requirements d) Data Dictionary 6. Modeling.21 a) Data Modeling(ERD) b) Functional Modeling(DFD) 7. Implementation.24 7. Software Testing41 8. Conclusion..42 9. Future Enhancement43 10.Bibliography47
Page 4
PROJECT PROFILE
PROJECT TITLE: SLIET LIBRARY MANAGEMENT SYSTEM
ORGANISATION: S.L.I.E.T
FRONT END TOOLS: JDK -1.6
BACK END TOOLS: Microsoft Access 2007
PROJECT DURATION: 11th January, 2010 27th April 27, 2010
SUBMITTED BY: SHAILBALA SHARMA (DCA/083026) SHAILZA KANWAR (DCA/083027) UMESH PATHAK (DCA/083031)
Page 5
ABSTRACT
This project named LIBRARY MANAGEMENT SYSTEM is used to automate the present SLIET library system that is manually handled. It helps in solving the tedious and time consuming task of librarians.
Some of the problems being faced in manual system are as follows:

Fast report generation is not possible. Tracing a book is difficult. Information about issue/return of the books is not properly maintained. No central database can be created as information is not available in database.
The new system will demolish all the bottlenecks of existing system and have below mentioned merits: The new system will minimize searching time as library users can refine searching by author name, subject name, publishers name. Unregistered users should be denied access to the Library System. Centralized data storage will help in faster data access and in implementing security measures to secure the data stored. A login module for authenticating the credentials of the library users and for allowing only registered members to login Library Management System. An add module using which librarians can add and remove books.
This project provides with following solutions:

It provides "better and efficient" service to members. Reduce the workload of librarian. Faster retrieval of information about the desired book. Provide facility for proper monitoring and reduce paper work and provide data security. All details will be available on a click.
Page 6
INTRODUCTION
GOALS:
Automate the existing Library ManagementSystem which is manually handled.
OBJECTIVES:
The new system will have the following objectives: To categorized the users i.e. 1. Students 2. Teaching staff 3. Non-Teaching staff So, they can login as different users and have different accessibility rights. A search catalog using which users (students, teaching and non-teaching staff )can search for books. All users need to register to the new Library System in order to issue and return books. A centralized database to store books and register students, teaching and nonteaching staffs information.
SCOPE:
The new system will have the following areas encompassed:
STUDENTS ---
Certificate Diploma Degree Post Graduate

TEACHING STAFF
NON- TEACHING STAFF
Page 7
PROJECT PLANNING AND MANAGEMENT

A. PROJECT DEVELOPMENT APPROACH:
A software engineer must incorporate a development strategy that encompasses the process, methods and tools layers. This strategy is referred to as process model. A software process model is chosen based on the project and application, the methods and tools to be used and controls and delivers those as required.
Here the project specifications are:

The requirements and objective of project are specified by the user. The number of developer is one. Time deadline is given by the user. Customer requires only final end product.
Based on all these specifications we have chosen: INCREMENTAL MODEL
The incremental model combines elements of the waterfall model applied in am iterative fashion. The incremental model applies linear sequences in a staggered fashion as calendar time progresses. Each linear sequence produces deliverable increments of the software. Using the incremental paradigm we first developed the various stand alone GUI applications Library Management System. In the second increment we created the database for this Project and associated various events so that connectivity with the database could be maintained. We also wish to have the third increment for the future reference to make this Project Online so that online accessibility of the SLIET Library could be possible. When an incremental model is used, the first increment is often a core product. That is basic requirements are addressed, but many supplementary features remain undelivered.
Page 8
The core product is used by the customer. As a result of use and evaluation, plan is developed for the next increment. The plan addresses the modification of the core product to better meet the needs of the customer and the delivery of additional feature and functionality. This process is repeated following the delivery of each increment, until the complete product is produced. The incremental process model like prototyping and other evolutionary approaches is iterative in nature. But unlike prototyping, the incremental model focuses on the delivery of operational product with each increment. Early increments are stripped down versions of the final product, but they do provide capability that serves the user and also provides a platform for evaluation by the user.
Increment # n Delivery of nth increment user
Library manager
Increment # 2
Administrator
Delivery of 2nd increment
Increment # 1
Delivery of 1st increment
Project Calendar Time
Incremental development is particularly useful when staffing is unavailable for a complete implementation by the business deadline that has been established for the project. Early increments can be implemented with fewer people. If the core product is well received,additional staff can be added to implement the next increment. In addition, increments can be planned to manage technical risks.
Page 9
B. RISK Management:
Risk management is a process of measuring or assessing risk and developing strategies to manage it. Strategies include avoiding the risk, reducing the negative effect of the risk and accepting some or all of the consequences of a particular risk.
i.
TECHNICAL RISK:
y Sometime problem occur due to database connectivity. When data queries are made if connectivity is not established then data cannot be accessed and users cannot access the library.
ii.
BUSINESS RISK:
y y This risk occur when the user requirement are not satisfied as per need. If proper information is not available to the user then it is of no use.
iii.
SCHEDULING RISK:
y y This risk occurs due to time management of project tasks. Completion of project within estimated time by proper management.
Page 10
SOFTWARE REQUIREMENT SPECIFICATION
a) USER CHARACTERISTICS:
User should have following characteristics as far as this project is concerned. Following are various types of users of this site:
ADMINISTRATOR (The one who manages the database):

control over the Administrator is main authority in this system and bears the complete Library Management System.
TEACHING STAFF:
Come under the category of users who can issue more books in number as compared to others and for a long duration of time also.
NON TEACHING STAFF:

Come under the category of such users who have facilities a little less as compared to above category.
STUDENTS:
These are the most common library users.
b) SOFTWARE REQUIREMENTS:
y y y 32 BIT OPERATING SYSTEM 9X/2000/Vista/XP Jdk-1.6 MS Access 2007
c) HARDWARE REQUIREMENTS:
The minimum hardware required is: y y y y Compatible Pentium II processor Memory 128 MB RAM Hard disk space 10 GB Monitor supports SVGA color monitors
Page 11
d)
DATA DICTIONARY:
Data dictionary is a repository that contains description of all data objects. Dictionary includes a description of named entity, description of entity, its data type and size.
Database - Library Table 1 - Bcat
Description - It contains the Category of books available in the Library.
FIELD sCat
DATA TYPE Text
SIZE 50
DESCRIPTION Category of Book
CONSTRAINT Primary key
Page 12
Database - Library Table 2 - Books
Description - It contains all the booksalong with their details.
FIELD BId Bname Bauthor
DATA TYPE Number Text Text
SIZE
DESCRIPTION Id of the book
50 50
Name of book Names of the authors of the books Categorize the book as reference or non-reference
Bref
Number
Bcat
Text
50
Gives the category of book Id of the member
Mid Bissue
Number Date
DD/M Stores the ISSUE M/YYY DETAILS OF BOOK Y DD/M Stores the M/YYY return DETAILS Y OF BOOK
Breturn
Date
Page 13
Database - Library Table 3 - Bsearch
Description - It gives the details of the book when that particular book is being searched.
FIELD Bid Name
DATA TYPE Number Text Cat Text
SIZE
DESCRIPTION Id of the book
50 50
Name of the book Category of the book Name of the author Give ID of the member to whom the book has been issued Categorizes the book as reference or non reference
Author Mid
Text Text
50 50
ref
Text
50
Page 14
Database - Library Table 4 - Clerks
Description - It contains the information about the Library operators.
FIELD Id
DATA TYPE Number
SIZE
DESCRIPTION Stores the id of library operators
Password
Text
50
Stores the password assigned to the operators.
Page 15
Database - Library Table 5 - BookIssue
Description - It stores the details of the issued books.
FIELD Bookid
DATA TYPE Number
SIZE
DESCRIPTION Gives the Id of the book
BookName
Text
50
Stores the name of issued book Stores the name of The author of issued book.
BookAuthor
Text
50
Category
Text
50
Stores the category of issued book. Gives the Id of the member to whom the book is issued.
MemberId
Number
Page 16
Database - Library Table 6 - Users

Description - It stores the details of the Members of Library.
FIELD Username
DATA TYPE Text
SIZE 50
DESCRIPTION Stores the valid username . Stores the corresponding password for the username.
CONSTRAINT
Password
Text
50
Page 17
Database - Library Table 7 - Mecat
Description - It stores the details of the issued books.
FIELD Mcat
DATA TYPE Number
SIZE
DESCRIPTION Store the serial number of member categories
Cname
Text
50
Stores the Category of user(student,teachi ng .) It stores the max.number of books that can be issued to a member It stores the max.number of days for which a book can be issued to a member
Blmt
Number
Dlmt
Number
Page 18
Database - Library Table 8 - Members
Description - It stores the details of the Members of Library.
FIELD Id
DATA TYPE Number
SIZE
DESCRIPTION Stores the member ID
Password
Text
50
Stores the password assigned to the member. Stores the name of the member. Stores the date since the member has been registered. It stores the number of books held by the member. Stores the value of fine charged to the member. Stores the category Id of the members corresponding to the Mecat table.
Mname
Text
50
Mstart
Date
Bcnt
Number
Mbdues
Number
Mcat
Number
Page 19
Database - Library Table 9 - MSearch
Description - It stores the details of the member who has been searched.
FIELD Mid
DATA TYPE Number
SIZE
DESCRIPTION Stores the Id of member who has been searched.
CONSTRAINT
Mname
Text
50
Stores the name of member who has been searched Stores the number of books held by the member who has been searched
Bcnt
Number
Mcat
Text
50
Stores the category of member who has been searched Stores the category of book held by the member who has been searched
Bc
Number
Page 20
MODELING
a) DATA MODELING (ER DIAGRAMS):
Page 21
1. FUNCTIONAL MODELING: DATA FLOW DIAGRAMS:
USER
RESPONSE
UPDATED INFORMATION
ADMINISTRATOR
REQUESTS
UPLOAD INFORMATION
LIBRARY MANAGEMENT SYSTEM
CONTEXT DIAGRAM (LEVEL 0):
It represents the entire software element as a single bubble with single input and output data indicated by incoming and outgoing arrows, respectively.
Page 22
LEVEL -1DFD
Admin
Request for login
Connects to
Checks
Database TRANSACTI -ONS
LOGON User
Connect s
Responds to Receives message
Validates
Send Messag
Receives message
Sends message
ISSUE BOOK
LEVEL- 2DFD
Page 23
IMPLEMENTATION
Snapshots of the Library Management System:1. LOGON PAGE:-This page selects the category of the user and logon the particular
user after verifying the username and the password.
As in the above snapshot the category selected is administrator and after verifying the username and password the administrator has been logged in.
Page 24
2. Accessibility rights of the Administrator:After the admin logs into the Library the various accessibility rights of the Administrator are being displayed in following snapshots. Administrator is the supreme controller of the Library and can carry all the operations.
For instance, in the above snapshot administrator is having the right to add a new book also a new member.
Page 25
3. Accessibility rights of the Administrator:Along with the right to add a new book or to add a new member the Administrator can also delete a book and also the member whenever it is required. Administrator has the monopoly in these rights to delete a book or a member.
For instance, in this snapshot Administrator is having the ability to delete a book or a member.
Page 26
4. More accessibility rights of Administrator:Besides, adding a book, adding a member, deleting a book, deleting a member, etc. administrator also has the right to create a new Librarian(clerk), create a new member category and also to create a new book category.
As in the above snapshots the administrator has the right to add a new Librarian, add a new book category and also to add a new member category.
Page 27
5. Accessibility rights of librarian:Librarian has imited rights which include issuing a book, returning a book, collecting fines.
For instance, in the above snapshot two tasks have been performed by the Librarian, one, issue book with book_id 2001. This form displays the member details to whom the book will be issued along with the issue details. The other task is returning the book with book_id 101. A confirmatory dialogue box appears reporting the return of the book if no fine is charged.
Page 28
6. Accessibility rights of Librarian:Besides, having the basic accessibility to issue and return a book the Librarian can also search for a particular book and a particular member in order any of the user require the information about the availability of a book.
For instance in the above snapshots, the Librarian with id- 83026 is accessing two forms, one for searching the book end the other for searching a member.
Page 29
7. Collecting fines:Librarian also collects fines from users accordingly as they are charged. This fine is either collected at the time the book is returned to the Librarian or through a separate form that is designed specially to collect the form as shown below.
The above form is designed to collect the fine. For example the member Ram with member id 10010 has been charged Rs 10.00 as fine and is been prompted to pay the fine.
Page 30
8. Accessibility rights of the user:A user can simply search the book and the member for getting information about their availability. A user has no other right other than to search the book and member as depicted by the snapshot below.
The above snapshot displays that a member searches a book by its id (101) And the corresponding information about the book has been displayed in the table display.
Page 31
9. Accessibility rights of the user:The user can also search a member, to get the details about the user as in the below displayed snapshot the user seeks the information the user by the name and the corresponding details are displayed in the table display.
The member has the id 83026, name shailbala, no of books held is zero, belongs to the student category, and the books that can be issued is limited to three.
Page 32
10. Help menu:This Library Management also has a help menu for the new operators to access the library without any difficulty. This help is accessible from all the operators( admin, member, librarian). It contains the various short keys used to access the Library. Also the information about the Library Management System is available through the help menu. The snapshot displayed below gives the pictorial view of it.
Page 33
11. Pop up menu:This Library Management System also has a pop up menu as shown in snapshot below. This also serves as a short way to carry on the various tasks that are required to be performed by the operator.
Page 34
12. Background color:Besides the various functions that are performed by this Library, one addition thing is that it sets the background color of the Library Management first page to give it an attractive look.
Page 35
13. JDBC(JAVA DATABASE CONNECTIVITY):Creating a DSN has some specified steps as given below. The connectivity to the backend is necessary to be carried out properly so that the application could run properly. The various steps are as follows:-
To create a DSN, we need to perform the following tasks: Selecting the required driver for the DSN. Specifying the connection details for a DSN. Testing the created DSN.
1. First comes the selecting the required driver for the DSN:-
START -- SETTINGS --- CONTROL PANEL CONTROL PANEL -- ADMINISTRATIVE TOOLS ADMINISTRATIVE TOOLS --- ODBC DATA SOURCE ADMINISTRATOR
Page 36
ODBC DATA SOURCE ADMINISTRATOR DIALOG BOX
Page 37
CREATE NEW DATA SOUCE DIALOG BOX
Page 38
MICROSOFT ACCESS SETUP DIALOG BOX
Page 39
SELECTION OF THE REQUIRED DATABASE FROM THE SELECT DATABASE DIALOG BOX
Page 40
SOFTWARE TESTING
This phase comprises the testing of the application in order to detect the various flaws that occur in the project and further sort out all the flaws. The following observations were made while undergoing the testing phase of this project:-
SEARCH MODULE:Whenever a search function was performed by the Library operator, then in order to have a new search the window of search module had to be closed and reopened again rather than having a simple refresh option. SETTING THE BACKGROUND COLOR:The Library Management System had a unique characteristic of setting the background color. But the background color once given does not persist its value , i.e, once the user sets the background color and closes the application, the next time when it is reloaded the color disappears and the background appears white. ISSUE BOOK MODULE:Whenever an already issued book is entered in the Issue Book module then the system prompts that, that particular book has been already issued. Here if the operator wants to reset the field and issue another then the various buttons on being clicked prompt that the book has been already issued rather than performing their desired tasks.
Page 41
CONCLUSION
This Library Management Project has been created with the aim to automate the present Library management system of our college, which is manually handled and is a very time consuming and tedious task. By means of our project we have tried to remove all the flaws that we find in the present system. Also we have been able to sort out all the flaws to our level best. This project has three category of operators( the Administrator- having the supreme control over the Library, Librarian- only limited up to issuing and returning of the book, user). The user has also been categorized in to three parts each having different facilities being provided by the Library. For example- There are three categories of users( Teaching, Non-teaching, Student). The Teaching staff can hold five books at a time, the Non-teaching can hold 4 books at a time and the Students can only have 3 books. So, conclusion drawn is that this Library works according to the needs of our college and the categories are all designed keeping in mind the system prevailing in SLIET.
Page 42
FUTURE ENHANCEMENTS
Later on the existing automated system could be enhanced to online LIBRARY MANAGEMENT SYSTEM bookstore which would not only include books but also some of the following features:-

Online tutorials Online queries regarding books. Online test series Online magazines and newspapers Online submission of the fine imposed by the library Latest question papers
In regards of our future enhancements we have also designed some of the web pages that we wish to implement in future.
Page 43
Page 44
Page 45
Page 46
BIBLIOGRAPHY
BOOKS:-
The complete Reference HerbettSchildt Tata Mc.Graw Hill
J2SE 5 edition
Programming with Java E. Balagurusamy Tata Mc.Graw Hill
3rd edition
Software Engineering Roger.S. Pressman Tata Mc.GrawHill
Sixth Edition
Developing Applications Using Java NIIT Publications
Page 47

Final Project Report

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Final Project Report

Enviado por

Direitos autorais:

Formatos disponíveis

SLIET LIBRARY MANAGEMENT SYSTEM

|LIBRARY MANAGEMENT SYSTEM}

Under The Guidance Of

SLIET LIBRARY MANAGEMENT SYSTEM

SLIET LIBRARY MANAGEMENT SYSTEM

MISS MANISHA YADAV LECT. (C.S.E. DEPARTMENT)

ASST. PROFESSOR (C.S.E. DEPARTMENT)

SLIET LIBRARY MANAGEMENT SYSTEM

SLIET LIBRARY MANAGEMENT SYSTEM

PROJECT TITLE: SLIET LIBRARY MANAGEMENT SYSTEM

FRONT END TOOLS: JDK -1.6

BACK END TOOLS: Microsoft Access 2007

PROJECT DURATION: 11th January, 2010 27th April 27, 2010

SLIET LIBRARY MANAGEMENT SYSTEM

Some of the problems being faced in manual system are as follows:

This project provides with following solutions:

SLIET LIBRARY MANAGEMENT SYSTEM

Certificate Diploma Degree Post Graduate

NON- TEACHING STAFF

SLIET LIBRARY MANAGEMENT SYSTEM

PROJECT PLANNING AND MANAGEMENT

Here the project specifications are:

Based on all these specifications we have chosen: INCREMENTAL MODEL

SLIET LIBRARY MANAGEMENT SYSTEM

Increment # n Delivery of nth increment user

Delivery of 2nd increment

Delivery of 1st increment

Project Calendar Time

SLIET LIBRARY MANAGEMENT SYSTEM

SLIET LIBRARY MANAGEMENT SYSTEM

SOFTWARE REQUIREMENT SPECIFICATION

ADMINISTRATOR (The one who manages the database):

NON TEACHING STAFF:

SLIET LIBRARY MANAGEMENT SYSTEM

Database - Library Table 1 - Bcat

Description - It contains the Category of books available in the Library.

DATA TYPE Text

DESCRIPTION Category of Book

CONSTRAINT Primary key

SLIET LIBRARY MANAGEMENT SYSTEM

Database - Library Table 2 - Books

Description - It contains all the booksalong with their details.

FIELD BId Bname Bauthor

DATA TYPE Number Text Text

DESCRIPTION Id of the book

CONSTRAINT Primary key

Gives the category of book Id of the member

SLIET LIBRARY MANAGEMENT SYSTEM

Database - Library Table 3 - Bsearch

FIELD Bid Name

DATA TYPE Number Text Cat Text

DESCRIPTION Id of the book

CONSTRAINT Primary key

SLIET LIBRARY MANAGEMENT SYSTEM

Database - Library Table 4 - Clerks

Description - It contains the information about the Library operators.

DATA TYPE Number

DESCRIPTION Stores the id of library operators

CONSTRAINT Primary key

Stores the password assigned to the operators.

SLIET LIBRARY MANAGEMENT SYSTEM

Database - Library Table 5 - BookIssue

Description - It stores the details of the issued books.

DATA TYPE Number