O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Presentation2

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 21 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Semelhante a Presentation2 (20)

Anúncio

Presentation2

  1. 1. Library Management System GUIDE :: Mr.Vinod Lalbag BY :: Tejaswini Bankar Mrs. Anuradha
  2. 2. Contents Introduction Software & Hardware Requirements Proposed System Scope And Festures Data Flow Diagram Screen Shots Of Project Conclusion References
  3. 3. Introduction Today most of the library is using either manual system for tracking the day to day activity or they are using desktop, spread sheet like MS Excel application to manage the day to day activity. In this proposed Library Management System it will run in client server mode and user can check the book availability, they can search the books, library staff can issue, receive book, and management can check the report. System will store historical data. Management can anytime view the total book status, library card status.
  4. 4. Software & Hardware Requirements Software Specification: •OS:Windows XP •Jdk7.0 •MySql •Win2000Advance Server •NetBeans
  5. 5. Hardware Specification •P-4 •RAM-2GB •HardDisk-160MB •RAID Front End: •Java Back End: •MySQL
  6. 6. Proposed System There will be the Three components: Stock maintenance Transaction entry Reports Proposed system provides with following solutions: It provides "better and efficient" service to members. Less manual work. Easy to findout availability of books. We can find out the record of the book by user
  7. 7. Scope & Features  Any education institute can make use of it for providing information about author, content of the available books. It can be used in offices and modifications can be easily done according to requirements  From an end-user perspective, the Library Management System Project consists of two functional elements: Master and Transaction Module.
  8. 8. Master and Security module: Master and security module includes user security management, login security, book details, member master, library card, library transaction. •Login: Check the user by user name and password, All user needs to enter user name and password to access the system, system check the user name and password and give access the system resource only valid user. •Main Screen: It display available options, menus and toolbars to the logged user. System display option as per user rights. It also show the name of user currently logged in.
  9. 9. Transaction Module: Transaction module includes issuing, receiving book and transaction report. •Issuing Book : This form used to issue book to the member. In this screen user selects book id, and library card id, system display the book and card history. If book is already issued it display message and details of last issued details. Same way system display card history for the library card no, if book already available it shows the message. If book is available and there is no book pending for received then book is issued and system saves the details. System also has powerful search facility to find the book and member id.
  10. 10. Data Flow Diagram Figure . Context Flow Diagrams give us the complete details about the inputs and outputs for a given system.
  11. 11. High Level Solution Architecture
  12. 12. Use Case
  13. 13. Data Flow & Process Flow Chart
  14. 14. Flow Chart
  15. 15. Screen Shots Of Project Login
  16. 16. Welcome Screen
  17. 17. User Master
  18. 18. Help
  19. 19. References WEBSITES: http://www.google.com http://www.microsoft.com http://www.msdn.com. http://www.vb123.com http://www.vbcode.com http://www.sqltuner.com BOOKS: Java Complete Reference 8th Eddition BlackBook
  20. 20. Conclusion This project was developed to fulfill user and business requirement; however there are lots of scopes to improve the performance of the Library Management System in the area of user interface, database performance, and query processing time. Etc.
  21. 21. Thank You

×