Download Srs documents for library management system and more Summaries Earth science in PDF only on Docsity!
G. H. RAISONI COLLEGE OF ENGG., NAGPUR
(An Autonomous Institute under UGC Act 1956)
Department of First Year Engineering
Topic - Library Management System
1. Introduction 1.1 Purpose The main objective of this document is to illustrate the requirements of the project Library Management system. The document gives the detailed description of the both functional and non- functional requirements proposed by the client. The purpose of this project is to provide a friendly environment to maintain the details of books and library members. The main purpose of this project is to maintain easy circulation system using computers and to provide different reports. This project describes the hardware and software interface requirements using ER diagrams and UML diagrams. 1.2 Document Conventions
➢ Entire document should be justified.
➢ Convention for Main title
- Font face: Times New Roman
- Font style: Bold
- Font Size: 1 4
➢ Convention for Sub title
- Font face: Times New Roman
- Font style: Bold
- Font Size: 12 ➢ Convention for body
- Font face: Times New Roman
- Font Size: 12 1.3 Product Scope Library Management System is basically updating the manual library system into an internet- based application so that the users can know the details of their accounts, availability of books and maximum limit for borrowing. The project is specifically designed for the use of librarians
Name NAMAN SINGHAL , OM PATEL
Roll No. 27,
Section B
Semester V
Subject Software engineering for project management
Branch CSE
and library users. The product will work as a complete user interface for library management process and library usage from ordinary users. Library Management System can be used by any existing or new library to manage its books and book borrowing, insertion and monitoring. It is especially useful for any educational institute where modifications in the content can be done easily according to requirements. The project can be easily implemented under various situations. We can add new features as and when we require, making reusability possible as there is flexibility in all the modules. The language used for developing the project is Java as it is quite advantageous than other languages in terms of performance, tools available, cross platform compatibility, libraries, cost (freely available), and development process. 1.5 References ➢ Websites
- http://www.slideshare.net/
- http://ebookily.net/doc/srs-library-management-system 2. Overall Descriptions 2.1 Product Perspective This is a broad level diagram of the project showing a basic overview. The users can be either staff or student. This System will provide a search functionality to facilitate the search of resources. This search will be based on various categories viz. book name or the ISBN. Further the library staff personnel can add/update the resources and the resource users from the system. The users of the system can request issue/renew/return of books for which they would have to follow certain criteria. 2.2 Product Function The Online Library System provides online real time information about the books available in the Library and the user information. The main purpose of this project is to reduce the manual work. This software is capable of managing Book Issues, Returns, Calculating/Managing Fine Generating various Reports for Record-Keeping according to end user requirements. The Librarian will act as the administrator to control members and manage books. The member’s status of issue/return is maintained in the library database. The member’s details can be fetched by the librarian from the database as and when required. The valid members are also allowed to view their account information. 2.3 User Classes and Characteristics The system provides different types of services based on the type of users [Member/Librarian]. The Librarian will be acting as the controller and he will have all the privileges of an administrator. The member can be either a student or staff of the university who will be accessing the Library online. The features that are available to the Librarian are:-
➢ Users must have their correct usernames and passwords to enter into their online accounts and do actions The dependencies are :- ➢ The specific hardware and software due to which the product will be run ➢ On the basis of listing requirements and specification the project will be developed and run ➢ The end users (admin) should have proper understanding of the product ➢ The system should have the general report stored ➢ The information of all the users must be stored in a database that is accessible by the Library System ➢ Any update regarding the book from the library is to be recorded to the database and the data entered should be correct
3. External Interface Requirement The software provides good graphical interface for the user and the administrator can operate on the system, performing the required task such as create, update, viewing the details of the book. ➢ It allows user to view quick reports like Book Issued/Returned in between particular time. ➢ It provides stock verification and search facility based on different criteria. ➢ The user interface must be customizable by the administrator ➢ All the modules provided with the software must fit into this graphical user interface and accomplish to the standard defined ➢ The design should be simple and all the different interfaces should follow a standard template ➢ The user interface should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module 3.1 User Interface Login :- In case the user is not yet registered, he can enter the details and register to create his account. Once his account is created he can ‘Login’ which asks the user to type his username and password. If the user entered either his username or password incorrectly then an error message appears. Search :- The member or librarian can enter the type of book he is looking for and the title he is interested in, then he can search for the required book by entering the book name. Categories View :- Categories view shows the categories of books available and provides ability to the librarian to add/edit or delete category from the list.
Librarian’s Control Panel :- This control panel will allow librarian to add/remove users; add, edit, or remove a resource. And manage lending options. 3.2 Hardware Interfaces
- Processor: Pentium(R)Dual-core CPU
- Hard Disk: 40GB
• RAM: 256 MB or more
3.3 Software Interfaces This software package is developed using java as front end which is supported by sun micro system. Microsoft SQL Server as the back end to store the database.
- Operating System: Windows NT, windows 98, Windows XP
- Language: Java Runtime Environment, Net beans 7.0.1 (front end)
• Database: MS SQL Server (back end)
3.4 Communication Interfaces The Online Library System will be connected to the World Wide Web.
4. System Features. 1 The users of the system should be provided the surety that their account is secure. This is possible by providing :- ➢ User authentication and validation of members using their unique member ID ➢ Proper monitoring by the administrator which includes updating account status, showing a popup if the member attempts to issue number of books that exceed the limit provided by the library policy, assigning fine to members who skip the date of return
➢ Proper accountability which includes not allowing a member to see other member’s
account. Only administrator will see and manage all member accounts
5. Other Non-functional Requirements 5.1 Performance Requirement The proposed system that we are going to develop will be used as the Chief performance system within the different campuses of the university which interacts with the university staff and students. Therefore, it is expected that the database would perform functionally all the requirements that are specified by the university. ➢ The performance of the system should be fast and accurate
The following are the list of conventions and acronyms used in this document and the project as well: ➢ Administrator: A login id representing a user with user administration privileges to the software User: A general login id assigned to most users ➢ Client: Intended users for the software ➢ SQL: Structured Query Language; used to retrieve information from a database ➢ SQL Server: A server used to store data in an organized format ➢ Layer: Represents a section of the project ➢ User Interface Layer: The section of the assignment referring to what the user interacts with directly Application Logic Layer: The section of the assignment referring to the Web Server. This is where all computations are completed ➢ Data Storage Layer: The section of the assignment referring to where all data is recorded. ➢ Use Case: A broad level diagram of the project showing a basic overview ➢ Class diagram: It is a type of static structure diagram that describes the structure of a system by showing the system’s cases, their attributes, and the relationships between the classes Interface: Something used to communicate across different mediums Unique Key: Used to differentiate entries in a database
