Sei sulla pagina 1di 41

Library Management System

Library Management System


A Mini-Project Report submitted in partial fulfillment of the requirement for the award of the degree of

Bachelor of Technology In Computer Science & Engineering By


08M61A0577 08M61A0599 08M61A05A5 08M61A05D1 D.CHARAN TEJA K.HEMU Md.IMRAN Md.OMAR ALI SHUJA

Under the guidance of Mr. B PHANI VIJAY KRISHNA MCA DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING SWARNA BHARATHI INSTITUTE OF SCIENCE & TECHNOLOGY Pakabanda Street, Khammam-500 002.Ph: 08742-237777, 247777.
(2011 - 2012)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING


SWARNA BHARATHI INSTITUTE OF SCIENCE & TECHNOLOGY

CERTIFICATE

This is to certify that the mini-project report entitled LIBRARY MANGEMENT SYSTEM that is being submitted by D.Charanteja, K. Hemu, Md. Omar Ali Shuja & Md.Imran in partial fulfillment for the award of B.Tech in Computer Science & Engineering to the Jawaharlal Nehru Technological University, Hyderabad is a record of bona fide work carried out by him under my guidance and supervision.

INTERNAL GUIDE

HEAD OF THE DEPARTMENT

PRINCIPAL

EXTERNAL GUIDE

ACKNOWLEDGEMENT
We would wish to express our most sincere gratitude and indebtedness to our project guide Mr. Phani Vijay Krishna MCA, Asst. Prof., SBIT, khammam for his valuable guidance throughout the development of our project is indeed a great pleasure to knowledge his constant encouragement & inspiration, which included in us a sense of team spirit & there by helped in fluent evaluation of the project. We express our profound gratitude to our Head of the Department Mr. Madhira Srinivas for his valuable suggestions and support. We are grateful to our principal Prof. K. Rama Rao for providing us necessary facilities. We are also thankful to all the staff members of B.Tech Computer Science Engineering for their encouragement while presenting this technical seminar. We would like to mention the kind Co-operation & the Help extended by all our team members.

TEAM MEMBERS
D. CHRANTEJA K. HEMU Md. IMRAN Md. OMAR ALI SHUJA

DECLARATION
We hereby declare that the technical seminar report entitled by LIBRARY MANAGEMENT SYSTEM presented by us under the guidance of Mr. Phani Vijay Krishna,Asst. Prof., This technical report is submitted to Jawaharlal Nehru Technological University, Hyderabad for partial fulfillment of the requirements for the award of degree of BACHELOR OF TECHNOLOGY in COMPUTER SCIENCE ENGINEERING during the academic year 2011. We also hereby declare that this technical report have not been submitted in partial or full to any other university for any degree.

Contents
1. 2. 2.1. 2.2. 3. 3.1. 3.2. 3.3. 3.4. 4. 4.1. Abstract ........................................................................................................................................... 7 Introduction .................................................................................................................................... 9 Purpose ....................................................................................................................................... 9 Project Scope .............................................................................................................................. 9 Requirements ................................................................................................................................ 11 Functional Requirements .......................................................................................................... 11 Data Requirements ................................................................................................................... 11 Hardware Requirements ........................................................................................................... 11 Software Requirements ............................................................................................................ 11 Designing ....................................................................................................................................... 14 ER Diagram ................................................................................................................................ 14

4.2 UML Diagram................................................................................................................................. 15 4.3 Activity Diagram ............................................................................................................................ 16 4.4 Data Flow Diagram ........................................................................................................................ 18 4.5 Class Diagram ................................................................................................................................ 20 4.6 Sequence Diagram .......................................................................................................................... 21 4.7 Database Tables ............................................................................................................................ 23 5. Implementation Details .................................................................................................................... 25 5.1 Language Specification .................................................................................................................. 25 Java........................................................................................................................................................ 25 Why do I need Java? ............................................................................................................................. 25 7. Sample Outputs................................................................................................................................. 30 8. Testing ............................................................................................................................................... 34 9. Future Scope ..................................................................................................................................... 36 9.1 Software Scope: .............................................................................................................................. 36 10. Conclusion ....................................................................................................................................... 38 11. Bibliography .................................................................................................................................... 40

Abstract

1. Abstract
The library is an important module for any educational institute. Library may contain thousands of books, and its management is a very tough job. The care should be taken for proper distribution of the resources. It should be managed in a manner so that its resources are used efficiently and conveniently. For this rules and rights should be provided to each user. Our software is easy to use for both beginners and advanced users. It features a familiar and well thought-out, an attractive user interface, combined with strong searching Insertion and reporting capabilities. College Library Record Application is designed and developed for a receipt and issuance of books in the college library. The project is build using JAVA and Access. The librarians can add/delete/edit book and member details. Users can view the list of all books.

Introduction

2. Introduction
The Library Management System automates the basic library functions to aid in the dayto-day operations of a library. It supports functions such as issue, return, the very basic functions of searching for a particular book, etc.The software aims to make the system user friendly and efficient.

2.1.

Purpose

The purpose of this application are as follows : The software is for automation of library. It provides following facilities to

Operator: Can enter details related to a particular book. Can provide membership to members.

Admin: Can read and write information about any

Member: Can update, create, delete the record of membership as per requirement and implementation plants.

2.2.

Project Scope
To make the existing system more efficient. To provide a user friendly environment where user can be serviced better. Make functioning of library faster. Provide a system where the library staff can catch defaulters and not let them escape.

To minimize the loss done to books.

Requirements

10

3. Requirements
The Library Management System shall be required to maintain information about its users and books.It shall store databases for students, faculty and books.The student database stores information about a students roll no, name, address, course and year.The book database stores information about a book title, author, publisher, cost, bill number, year of publishing and pages.The faculty database stores information about a facultys id, name, department, and designation, address and telephone number.

3.1. Functional Requirements


Roll number and faculty identification must all be unique as they form the primary keys of the respective tables.All new books must be entered in the accession table first, to avoid problems later.A book must not be deleted from student profile unless and until she pays the appropriate fine or the same book.While inserting values in the database, only valid values must be entered.

3.2. Data Requirements


The Library Management System shall be required to maintain information about its users and books.It shall store databases for students, faculty and books.The student database stores information about a students roll no, name, address, course and year.The book database stores information about a book title, author, publisher, cost, bill number, year of publishing and pages.The faculty database stores information about a facultys id, name, department, designation, address and telephone number.

3.3. Hardware Requirements


Processor : Intel Pentium IV 1.8 GHZ or above Clock speed : 500 MHZ System bus :32 bits RAM : 256MB of RAM HDD : 750MB of free space

3.4. Software Requirements


Operating System : WINDOWS XP SP2
11

Environment : JRE 1.5 Front end : J2SDK1.5 Back end : Microsoft Access 2007 Tools used: JDK 1.4, Rational Rose 98, NetBeans IDE 7.0.1

12

Designing

13

4. Designing
4.1. ER Diagram
It is clear that the physical objects from the previous section the member, books, library correspond to entities in the Entity-Relationship model, and the operations to be done on those entities holds, checkouts, and so on correspond to relationships. However, a good design will minimize redundancy and attempt to store all the required information in as small a space as possible.

14

4.2 UML Diagram


Use Case diagrams show the various activities the users can perform on the system.System is something that performs a function.They model the dynamic aspects of the system.

15

4.3 Activity Diagram

SearchBook

Issue Book

16

Return Book

Librarian Task

17

4.4 Data Flow Diagram

DFD 1

DFD 2

18

DFD 4

DFD 3

19

4.5 Class Diagram

20

4.6 Sequence Diagram

Searching

Issues Book

21

Return Book

Record Update

22

4.7 Database Tables

Book Details

Student Details

23

Implementation Details

24

5. Implementation Details 5.1 Language Specification


Java
Java is a programming language and computing platform first released by Sun Microsystems in 1995. It is the underlying technology that powers state-of-the-art programs including utilities, games, and business applications. Java runs on more than 850 million personal computers worldwide, and on billions of devices worldwide, including mobile and TV devices.

Why do I need Java?


There are lots of applications and websites that won't work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! Java was designed with a few key principles in mind: Easy to Use: The fundamentals of Java came from a programming language called c++. Although c++ is a powerful language, it was felt to be too complex in its syntax, and inadequate for all of Java's requirements. Java built on, and improved the ideas of c++, to provide a programming language that was powerful and simple to use. Reliability: Java needed to reduce the likelihood of fatal errors from programmer mistakes. With this in mind, object-oriented programming was introduced. Once data and its manipulation were packaged together in one place, it increased Javas robustness. Secure: As Java was originally targeting mobile devices that would be exchanging data over networks, it was built to include a high level of security. Java is probably the most secure programming language to date.

25

Platform Independent: Programs needed to work regardless of the machine they were being executed on. Java was written to be a portable language that doesn't care about the operating system or the hardware of the computer. The team at Sun Microsystems was successful in combining these key principles, and Java's popularity can be traced to it being a robust, secure, easy to use, and portable language.

26

Proposed System

27

6. PROPOSED SYSTEM
There will be three major components: 1. Stock maintenance. 2. Transaction entry. 3. Reports. Proposed system provides with following solutions: 1. It provides "better and efficient" service to members. 2. Reduce the workload of employee. 3. Faster retrieval of information about the desired book. 4. Provide facility for proper monitoring reduces paper work and provide data security. 5. All details will be available on a click.

28

Sample Outputs

29

7. Sample Outputs

Screen 2

Screen 1

30

Screen 4

Screen 3

31

Screen 6

Screen 5

32

Testing

33

8. Testing
It is integral part of any systems development life cycle without which the system developed is sure to fail and result in loss of economic and manpower investments besides users dissatisfaction and downfall of reputation. System testing is the stage of implementation, which aims at ensuring that the system works accurately and efficiently before actual operation commences. No program or system design is perfect, communication between the user and the designer is not always complete or clear. All this can result in errors. Another reason for system testing is its utility as a user oriented vehicle before implementation. The application system is worthless if does not meet user needs, thus the system should be tested to see whether it meets the user requirements. Testing here is conducted in bottom up approach as follows: Module testing: Here testing is done at each module level. Each case has been thoroughly tested to discover pitfalls. System testing: Here testing is done after all the modules have been integrated.

34

Future Scope

35

9. Future Scope
This application can be easily implemented under various situations. We can add new features as and when we require. Reusability is possible as and when require in this application. There is flexibility in all the modules.

9.1 Software Scope:


Extensibility: This software is extendable in ways that its original developers may not expect. The following principle enhances extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations.

Reusability: Reusability is possible as and when require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.

Understandability: A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method, which small and coherent helps to accomplish this.

Cost-effectiveness: Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement.

Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.

36

Conclusion

37

10. Conclusion
From a proper analysis of positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This application is working properly and meeting to all user requirements. This component can be easily plugged in many other systems. The Books and Students are given a particular unique id no. So that they can be accessed correctly and without errors. The computerization of the Library Management will not only improve the efficiency but will also reduce human stress thereby indirectly improving human recourses.

38

Bibliography

39

11. Bibliography
Books: Beginning Java Objects: From Concepts to Code by Jacquie Barker) Introduction to Java Programming (NIIIT publication) The Complete Reference Java(McGrawhill; Herbert Schildth- reprint 2008)

Web Sites: www.apache.org www.wikipedia.com

40