Library management system project SRS document

This page contains Library management system project SRS document. The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Library Management System (LMS). This SRS will allow for a complete understanding of what is to be expected of the LMS to be constructed. The clear understanding of the LMS and its functionality will allow for the correct software to be developed for the end user and will be used for the development of the future stages of the project.

This SRS will be used by the software engineers constructing the LMS and the Library end users.  The software engineers will use the SRS to fully understand the expectations of this LMS to construct the appropriate software.  The Library end users will be able to use this SRS as a “test” to see if the software engineers will be constructing the system to their expectations.  If it is not to their expectations the end users can specify how it is not to their liking and the software engineers will change the SRS to fit the end users’ needs.

Scope

Library Management system is the system that manages the member data, staff data, members’ registration process and create receipt for the fine paid by the member.

This system is designed in favor of the Library management which helps them to save the records of the member about their transactions. It helps them from the manual work from which it is very difficult to find the record of the books and the transaction of the members, and the information of about those ones who had membership in the Library.

We design this system on the request of the Library management. This system automatically calculates all the books and issued books transactions. Through this it’s possible to check the personal profile of all the current member within fraction of seconds. 

Project Description

Library Management system is the system that manages the book data, staff data members’ registration process and create receipt for the fine paid by the member.

Product Perspective

The LMS is an independent stand–alone system.  It is totally self contained.

User characteristics:

• The user of this product is supposed to be fairly educated about the usage of the computers.
• Should be able to use and do according to the graphical user interface
• The users of this software are expected to know the basic operation of the LMS transactions. They should have a basic idea as to how to use a GUI and how to Familiarity with navigating menus and using tabs, buttons and other control interfaces is also necessary.

Functional Requirements

• Login Module:
  • Input: Admin enters the Login Id and password.
  • Processing: Checks login Id and password is valid or not.
  • Output        : Admin is directed to next page where he can add, delete or  update the products.
    
• Books:
  • Input          : Book Details are entered.
  • Processing : The book details which we have entered will be stored.
  • Output       : book details will be displayed when ever member will come for book request.

• Member Management:
  • Input: Admin Enters the detailsof the person who wants to be member in Library
  • Processing: Member details will be stored.
  • Output: Membership is issued.

Hardware interface:

• Operating system : window
• Hard disk :40 GB
• RAM : 256 MB
• Processor : Pentium(R)Dual-core CPU

Software interface :

•  Java language
• Net beans IDE 7.0.1
• MS SQL server 2005

Functional requirements:

• Book entry: In this module we can store the details of the books.
• Register student: in this module we can keep the details of the new student.
• Book issue: This module is used to keep a track of book issue details.
• Book return: This module enables to keep a track of return the books.

Design constraints :

Each member will be having a identity card which can be used for the library book issue, fine payment etc. whenever library member wish to take a book, the book issued by the library authority will be check both the book details as well as the student details and store it in library database. In case of retrieval of book much of human intervention can be eliminated.

Video demo of the project