Академический Документы
Профессиональный Документы
Культура Документы
Project certificate
This is to certify that the project entitled LIBRARY MANAGEMENT SYSTEM by Mr. BHANU PANDAY student of MASTER OF COMPUTER APPLICATION , session [2011-2014], of INSTITUTE OF
MANAGEMENT
affiliated to UTTARAKHAND TECHNICAL UNIVERSITY, DEHRADUN , is hereby accepted and approved as a credible work. It is further certified that this work has not been submitted for similar purpose anywhere else.
STUDIES,
(DEHRADUN)
Internal Examiner
External Examiner
Page 1
Declaration
I am BHANU PANDAY hereby declare that the project work entitled LIBRARY MANAGEMENT SYSTEM in Under the guidance of Mr. Vishok and this work has not been submitted for similar purpose anywhere else except to INSTITUTE OF MANAGEMENT STUDIES (DEHRADUN), affiliated to UTTARAKHAND TECHNICAL UNIVERSITY, DEHRADUN .
Page 2
Acknowledgement
It is high privilege for me to express my deep sense of gratitude to all those faculty members who helped me in the completion of the project, especially my internal guide Mr. Vishok who was always there at hour of need. My special thanks to HOD, (Department of Computer Application, Institute Of Management Studies) for helping me in the completion of project work and its report submission.
Bhanu Panday
Page 3
Table of Contents
Introduction of project 05 Problem Specification...... 08 Feasibility Study11 Software Requirement Specifications.12 Design14 Entity Relationship Diagram......15 Data Flow Diagram......17 6. Input-Output form (Screen Layout)..20 7. Implementation....29 8. Testing...33 9. Conclusion36 10. Bibliography...38 1. 2. 3. 4. 5.
Page 4
Page 5
INTRODUCTION
Page 6
INTRODUCTION
Objective: To provide a Library Management System for college. Rational: To improve library uses services and reduce paperwork. Scope of Project:
To make the existing system more efficient. To provide a user friendly environment where user can be service 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. Any education institute can make use of it for providing information about. It can be used in offices and modifications can be easily done according to requirements.
Technology Used: Front End: C/C++ language. Back End: File System Using File Handling.
Purpose: The purpose of this application are as follows The software is for automation of library. It provides following facilities to.
Page 7
Operator: Can enter details related to a particular book. Can provide membership to members.
Overview:Project is related to library management which provides, Reading services to its members any person can become a member of the library by filling a prescribed form they can get the book issued, so that they can take home and return them.
Page 8
Problem Specification
Page 9
Problem Specification
In our existing system all the transaction of books are done manually, So taking more time for a transaction like borrowing a book or returning a book and also for searching of members and books. Another major disadvantage is that to preparing the list of books borrowed and the available books in the library will take more time, currently it is doing as a one day process for verifying all records. So after conducting the feasibility study we decided to make the manual Library management system to be computerized.
Some of the problems being faced in manual system are as Follows:1. Fast report generation is not possible. 2. Tracing a book is difficult. 3. Information about issue/return of the books is not Properly maintained. 4. No central database can be created as information is Not available in database. 5. Wastage of paper. 6. Take a lot of time to complete the task. 7. Problem to face searching a new Book in Book Bank.
Page 10
Feasibility Study
Page 11
Feasibility Study
Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility. Technical Feasibility: We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already. Economical Feasibility: Development of this application is highly economically feasible .The organization needed not spend much m one for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development , the organization will not be in a condition to invest more in t he organization .Therefore , the system is economically feasible.
Page 12
Page 13
Functional requirements: Accession number, roll number and teacher 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 untill she pays the appropriate fine or the same book. While inserting values in the database, only valid values must be entered. Data 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 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 teacher database stores information about a teachers id, name, department, and designation, address and telephone number. Software requirements: Operating System: Window Xp/98/2000/Vista/7. Turbo C/ C++/DosBox. RAM-512 MB, Intel Pentium.
Page 14
Design
Page 15
E-R DIGRAM
LIBRARY
contains
Book_name
Book_code
BOOKS
No. of Books
issue
Book_Author
Book_price
name
MEMBER
issue
Date_last
Page 16
id
id
STATUS OF RETURN
STATUS OF ISSUE
Book_code
Date_issue
Page 17
DFDS
Page 18
Page 19
Page 20
Page 21
Page 22
Screen Sort 1-
Page 23
Screen Sort 2-
Welcome project
Page 24
Screen Sort 3-
Main Menu
Page 25
Screen Sort 4-
Page 26
Screen Sort 5-
Page 29
Screen Sort 8-
Edit or Modify
Page 30
Implementation
Page 31
Page 32
b) Teacher: This will clear the record for a particular teacher whose identification number is entered. This option is chosen when a teacher leaves college. c) Student: This will clear the record for the particular student whose record needs to be deleted by entering her roll number in the required field. This option is chosen when a student leaves college . 3. UPDATE: This function updates data in the various records. This operation is supported by all the three entries. a) Book: This function generally would not be required for updating a books status as that data wouldnt change. b) Teacher: This will update the data of particular teacher, whose data has changed like address, phone number, etc. by entering her identification number. c) Student: This will update the data of student like address, course, etc. by entering students roll number. 4. SEARCH: This function is used to search particular data from the database. This function can search for data related to all the three entities: a) Book: To search for a particular book, to know whether it is currently available in library or not. This can be done by entering value in any one or more fields in the form to perform the search such as title or author name. b) Teacher: This will find out the particular teacher who currently has the book for which search is being carried out. c) Student: This will find out the particular student who possesses the particular book. 5. ISSUE: This operation is used for issuing a book to a member of the library. For this operation to be successful the member must meet some criteria like she should not have issued books to her maximum limit previously. All these checks are done by software. If the operation is successful, then the system automatically stores the date of issue and the due date by which the book must be returned. a) Student: When a student loans a book, the entry of the book is stored automatically in the students database with the due date of that book. b) Teacher: In case a member of teaching staff loans a book the entry is stored in teachers database with the due date of the book.
Department of Computer Application Page 33
6. RETURN: Using this operation a member returns the items, which she loaned, from the library back to it. If the book, which is loaned is not returned within specified time the member ends up as a defaulter and she is required to pay fine which is calculated automatically by the software. a) Teacher: It will delete the corresponding entry made in teachers database. b) Student: It will delete the corresponding entry made in students database. 7. DISPLAY: This is used to display each and every record, i.e. record of every book, teacher and student in the library. a) Book: Record of every book, i.e. its accession number, author name, publisher name, etc. b) Teacher: Record of every teacher, i.e. her id, department, no. of books issued, etc., who is member of the college library. c) Student: Record of every student, i.e. her roll number, course, no of books issued, etc., who is member of the college library. 8. EXIT: This takes user out of the application.
Page 34
Testing
Page 35
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. The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out. There are two major type of testing they are 1) White Box Testing. 2) Black Box Testing.
White box some times called Glass box testing is a test case design uses the control structure of the procedural design to drive test case. Using white box testing methods, the following tests where made on the system A) All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixe b) All logical decisions were checked for the truth and falsity of the values. Black box Testing Black box testing focuses on the functional requirements of the software. This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different class of errors that white box methods like.. 1) Interface errors 2) Performance in data structure 3) Performance errors 4) Initializing and termination errors
Page 37
Conclusion
Page 38
Conclusion
Our project is only a humble venture to satisfy the needs in a library. Several user friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization. The objective of software planning is to provide a frame work that enables the manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but almighty. 1. 2. 3. 4. It provides "better and efficient" service to members. Reduce the workload of employee. Faster retrieval of information about the desired book. Provide facility for proper monitoring reduce paper work And provide data security. 5. All details will be available on a click. 6. Provide the security system in to the software. 7. Faster, more reliable and easy to handle and work on it the software.
Page 39
Bibliography
Page 40
Bibliography
1. 2. 3. 4.
Let Us C by Yashavant Kanetkar Computer Science, C++ by Sumita Arora The Complete Reference, C++ by Herbert Schildt Software Engineering by Roger S. Pressman.
Page 41