Development of an online Library Management System (LiMS)


Title of the project


Development of an online Library Management System (LiMS)


Abstract of the project


This project is aimed at developing an online Library Management System (LiMS) for the college library. This is an Intranet based application that can be accessed throughout the campus. This system can be used to search for books/magazines, reserve books, find out who is having a particular book, put in requests to buy a new book etc. This is one integrated system that contains both the user component and the librarian component. There are features like email notifications/reminders, report generators etc in this system.




Generic Technlogy keywords


Databases, Network and middleware, Programming


Specific Technology keywords


MS-SQL server, HTML, Active Server Pages, Visual Basic 6


Project type keywords


Analysis, Design, Implementation, Testing, User Interface


Functional components of the project


Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of a functionality is not adequate, you can make appropriate assumptions and proceed.


There are registered people in the system (students, faculty, librarian et al). Each one of them may have some exclusive privileges (faculty, for example, could borrow reference books for a short period, while students cannot).


  1. A person should be able to


  • login to the system through the first page of the application


  • change the password after logging into the system


  • see the status of the books/journals borrowed/reserved by him and the respective due dates and other relevant details


  • search for a particular book/journal based on the name of the book/name of the author/subject/etc and also list for books/journals based on the name of the autor/subject etc


  • reserve a particular book/journal borrowed by others currently


  • cancel the reservation made earlier for a particular book/journal


  • see who has borrowed a particular book/journal and when is the due date for the same


  • place requests for purchasing new books to the library, by giving details about the name of the book, name of the author, publisher etc.


  • get help about the LiMS on how to use the different features of the system


  1. As soon as a reservation is made for a particular book, an automatic mail should be sent to the person who made the reservation about the details. Then, a mail should be sent to people who are having the book currently, stating a reservation has been made on that book.


  1. Automatic mails should be sent to the users about the expiry of due dates for the books/journals borrowed by them. An advance notification (say, 4 days before the expiry of the due date) should be sent as well.


  1. The librarian should be able to


·         include new books/journals or remove some books from the inventory


·         add new users to the system


·         see the purchase requests for new books and be able to approve/reject the same


Steps to start-off the project


The following steps will be helpful to start off the project.


  1. Study and be comfortable with technologies such as Active Server Pages/HTML and SQL server. Some links to these technologies are given in the ‘Guidelines and References’ section of this document


  1. Make a database of  books/journals


  1. Make a list of students/faculty who would be using the system


  1. Create the front-page of the system giving a brief description about the system and a login box


  1. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system


  1. Create other sub-systems like automatic notification, screens for various functions (like reservation, cancellation of reservation, purchase request for new books, approval page for the librarian etc)






Hardware requirements




Alternatives (If available)


PC with 2 GB hard-disk and 256 MB RAM






Software requirements




Alternatives (If available)


Windows 95/98/XP with MS-office

Not Applicable


MS-SQL server






Manpower requirements


2 to 3 students can complete this in 4 – 6 months if they work fulltime on it.


Milestones and Timelines



Milestone Name

Milestone Description





Week no. 

from the start

of the project





Requirements Specification

Complete specification of the system (with appropriate assumptions) including the database design (for storing the books/journals details). A document detailing the same should be written and a presentation on that be made.


Attempt should be made to add some more relevant functionalities other than those that are listed in this document.



Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


High-level and Detailed  Design

Listing down all possible scenarios (like searching for book/ journal, reserving a book/ journal, cancelling the reservation, submitting a purchase application for new books etc) and then coming up with flow-charts or pseudocode to handle the scenario.


The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).


Implementation of the front-end of the system

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for students/faculty and librarian for the various functions etc.


During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.


Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the books/journal database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing.




Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).


Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.


Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.


During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)


Guidelines and References (ASP tutorial) (SQL-server tutorial)

Tags :
Your rating: None