Your SlideShare is downloading. ×
Library Management System
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Library Management System

13,679
views

Published on

Library Management System

Library Management System

Published in: Technology, Education

5 Comments
17 Likes
Statistics
Notes
  • nice
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • thanks for your comments..
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Amit: Very interesting. Thank you. I noticed, though, that your application appears to be restricted to paper books or perhaps operates behind a paradigm that assumes that e-books should be treated the same as paper books in the library.

    The difference, though, between a solid book and an e-book is that e-books can become PART of the total software package, as opposed to being a thing that is merely tracked by it.

    E-publication also blurs and changes the line between books, magazines, and other 'paper' media. Organizing according to the differences between them presents entirely different challenges in a digital environment.

    With text-to-speech now available on even the cheapest of PC's, another door is now open. And that gets one thinking about how libraries might handle video- and/or coordinate and associate video with books to assist the patron. (Just as long as it doesn't encourage students to watch the movie instead of reading the book. :-) )

    So, I look at this as a terrific start and not the finished product. (Not that there will ever be a finished product, since we're living in an age when entirely new types of media are invented every year.)

    I am anxious to see where this will lead you.
    Herb
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • i like this presentation
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • thanks for your support
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
13,679
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
1,224
Comments
5
Likes
17
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. INTRODUCTION  A library management system, also known as an automated library system is software that has been developed to handle basic housekeeping functions of a library.  It’s a well organized software solution for a library.  It help to provide information on any book present in library to the user as well as staff member.  It keeps a track of book issued, returned and added to library.
  • 2. SCOPE OF PROJECT:  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.
  • 3. REQUIREMENTS:  The Library Management System shall be required to maintain information about its users and books.  It shall store databases for students, teachers and books.  The student database stores information about a student’s 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 teacher database stores information about a teacher ’s id, name, department, designation, address and telephone number.
  • 4. PROJECT AIM AND OBJECTIVE  To eliminate the paper work in library.  To record every transaction in computerized system so that problem such as record file missing won’t be happen.  To design a user friendly graphical user interface which suit the user.  To save the cost and time.
  • 5. Log In Add New Member Update/Delete Member Add a Book Update/Delete Book Search For a Book Check In Book Check Out Book Pay Late Fee View Book Detail View Member Detail Search For a Member
  • 6.  A data flow diagram(DFD) is graphical representation of the “flow” of data through an information system.  A DFD shows what kinds of information will be input to and output from the system.  One of the most widely used system analysis process models is the data flow diagram.
  • 7. MODULES  LOGIN  SIGNUP  BOOKS  BOOK SEARCH
  • 8. SYSTEM CONFIGURATION 1.HARDWARE CONFUGRATION: PROCESSOR : PENTIUM IV 3.0 GHz  MEMORY : 256 MB RAM : 40GB  HARD DISK 2.SOFTWARE CONFUGRATION: INTERFACE : ASP  DATABASE : MS ACCESS  PLAT FORM : WINDOWS 7
  • 9. DATA BASE DESIGN
  • 10. TABLE NAME: MEMBER Field Name Type Name Member_Id Number First Name Text Last Name Text Phone NO Text Address Memo Password Text Gender Text DOB Date/Time
  • 11. TABLE NAME: BOOK Field Name Type Name ACC_NO Number Book Name Text Author Name Text Publisher Text Price Currency Edition Text Subject Text Branch Text
  • 12. TABLE NAME: PAYMENT Field Name Type Name Member_Id Text Amount Currency Payment_Date Date/Time Payment_Type Text
  • 13. TABLE NAME: ISSUE_RETURN Field Name Type Name ACC_NO Text Member_Id Text Date_Issue Text Date_return Text Expire_Date Text
  • 14. SCREEN SHOTS
  • 15.  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.
  • 16. CONCLUSION The system has been developed using ASP and MS access , the system was able to process and update the database with more ease. It helped in developing a total integrated system. Thus the project “LIBRARY MANAGEMENT SYSTEM” can be altered in accordance with the future requirements of the organization.