Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Library project report


Published on

Published in: Technology

Library project report

  1. 1. Library Management System Project Report On “Library Management System”Submitted By:
  2. 2. Library Management System ACKNOWLEDGEMENTThe satisfaction that accompanies that the successful completionof any task would be incomplete without the mention of peoplewhose ceaseless cooperation made it possible, whose constantguidance and encouragement crown all efforts with success.I grateful to my project guide for theguidance, inspiration and constructive suggestions that helpful tome in the preparation of this project.I also thank our colleagues who have helped in successfulcompletion of the project.
  3. 3. Library Management System CERTIFICATEThis is to certify that this report of Library Management System isoriginal work done by Diwijesh, during this project submission asa partial fulfillment of the requirement for the Summer ProjectTraining, of B.Tech, VII Semester, United College Of Engineering& Management.
  4. 4. Library Management System Table of ContentsSynopsisFeasibility StudyData TablesData Flow DiagramsEntity Relationship DiagramScreen Shots Of FormFuture ScopeConclusion
  5. 5. Library Management SystemLibrary Management System1. Introduction:-1.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 enter details related to a particular student/user. Can read and write information about any member. Can update, create, delete the record of membership as per requirement and implementation plants.
  6. 6. Library Management System2.) Scope : The different areas where we can use this application are : 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.3.) Technology Used : Front End : HTML, ASP.NET, Back End : SQL SERVER.4.) Assumptions This application is used to convert the manual application to the web application. Customized data will be used in this application. User does not have right to enter information about books
  7. 7. Library Management System5.) Overview :Project is related to library management which provides reading services toits members. Any person can become a member of the library by filling aprescribed form.They can get the book issued, so that they can take homeand return them.6.) Functionality : Easy Updation of record. Keeps the track of issues and submission of books
  8. 8. Library Management SystemFeasibility StudyIn feasibility study phase we had undergone through various steps whichare describe as under :1. Identify the origin of the information at different level.2. Identify the expectation of user from computerized system.3. Analyze the draw back of existing system (manual) system.WORKING OF PRESENT MANUAL SYSTEMThe staffs of library are involved in the following tasks.1. Membership process : person have to fill membership form and they areprovided with member id.
  9. 9. Library Management SystemDRAWBACKS OF PRESENT SYSTEMSome of the problems being faced in manual system are asfollows:1. Fast report generation is not possible.2. Tracing a book is difficult.3. Information about issue/return of the books are not properly maintained.4. No central database can be created as information is not available indatabase.PROPOSED SYSTEMThere 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 reduce paper work and provide datasecurity.5. All details will be available on a click.
  10. 10. Library Management System Data Tables:Table : StudentS. No. Coloum Data Type Length Description Name1 I.D. No. Text 50 Unique identification of the Student2 Name Text 50 Name of Student3 Branch Text 50 Branch of Student4 Address Text 100 Location of Student5 Contact Text 50 Contact of Student
  11. 11. Library Management SystemTable : BooksS. No. Coloum Data Type Length Description Name1 I.D. No. Text 50 Unique identification of the Book2 Book Text 50 Name of Book3 Author Text 50 Author of the Book
  12. 12. Library Management SystemTable : IssueS. No. Coloum Data Type Length Description Name1 I.D. No. Text 50 Unique identification of the Student2 Semester Text 50 Semester of Student3 Book 1 Text 50 Unique identification of book4 Book 2 Text 50 Unique identification of book5 Book 3 Text 50 Unique identification of book6 Book 4 Text 50 Unique identification of book7 Book 5 Text 50 Unique identification of book8 Book 6 Text 50 Unique identification of book9 Date Date 20 Date of Issue10 Status Text 50 Status of Issue
  13. 13. Library Management System E-R DIGRAMIt is clear that the physical objects from the previous section– the member, books, library – correspond to entities in theEntity-Relationship model, and the operations to be done onthose entities – holds, checkouts, and so on – correspond torelationships. However, a good design will minimize redundancyand attempt to store all the required information in as small aspace as possible.
  14. 14. Library Management System
  15. 15. Library Management System SNAPSHOTSlogin page :
  16. 16. Library Management SystemIssue page :
  17. 17. Library Management SystemReturn page :
  18. 18. Library Management SystemProfile page :
  19. 19. Library Management SystemAdd Profile page :
  20. 20. Library Management SystemUpdate/ Delete Profile page :
  21. 21. Library Management SystemEdit Book page :
  22. 22. Library Management SystemFuture Scope :FUTURE SCOPE OF APPLICATION :This application can be easily implemented under various situations.We can add new features as and when we require. Reusability ispossibleas and when require in this application. There is flexibilityin all the modules.SOFTWARE SCOPE: Extensibility: This software is extendable in ways that its originaldevelopers may not expect. The following principles enhances extensibilitylike hide data structure, avoid traversing multiple links or methods, avoidcase statements on object type and distinguish public and privateoperations. Reusability: Reusability is possible as and when require inthisapplication. We can update it next version. Reusable softwarereducesdesign, coding and testing cost by amortizing effortover several designs.Reducing the amount of code alsosimplifies understanding, whichincreases the likelihood thatthe code is correct. We follow up both types ofreusability:Sharing of newly written code within a project and reuse ofpreviously written code on new projects.
  23. 23. Library Management System Understandability: A method is understandable if someone other thanthe creator of the method can understand the code (as well as the creatorafter a time lapse). We use the method, which small and coherent helps toaccomplish this. Cost-effectiveness: Its cost is under the budget and make within giventime period. It is desirable to aim for a system with a minimum cost subjectto the condition that it must satisfy the entire requirement.Scope of this document is to put down the requirements, clearly identifyingthe information needed by the user, the source of the information andoutputs expected from the system.
  24. 24. Library Management SystemConclusion :From a proper analysis of positive points and constraints onthe component, it can be safely concluded that the product isa highly efficient GUI based component. This application isworking properly and meeting to all user requirements. Thiscomponent can be easily plugged in many other systems.