This page includes the SRS text for the library management system initiative. A method of production consists of separate phases, with each step ending with a given output. The primary explanation for using a staggered process is that it splits the issue of software development into a successful series of stages, each handling a separate software development question. This means that if the entire thing was solved simultaneously, the cost of implementation is smaller than what it would have been. In comparison, a staggered approach requires adequate consistency and progress testing at some specified stages during production (end of the process). Without this, one would have to wait until the end to see what software has been updated
The following steps are part of every problem-solving in software:—
Requirement analysis:
- Requirement Research is conducted to clarify the issue to be addressed by the automated framework.
In this step, there are two main operations: problem comprehension or review and definition of specifications. The goal of problem analysis is to consider the issue and its context, as well as the specifications of the new method to be created. The specifications must be defined in the requirement specification document until the issue is evaluated and the fundamentals understood. Both technical and performance specifications must be defined in the requirements document; the formats of inputs and outputs etc.
- Software Design :
The design process aims to prepare a response to the issue identified by the document of specifications. The first step in going from the problem domain to the solution domain is this process.
Three different outputs frequently emerge from the construction activity: architectural design, high-level design, and comprehensive design.
- Coding :
The coding phase’s key objective is to convert the system’s architecture into code in a given programming language. The coding process deeply impacts both testing and repair. The aim of coding should be to decrease the commitment to testing and servicing, so the emphasis should be on designing applications that are easy to read and understand while coding.
- Testing :
The testing purpose is to find flaws in the software. The primary purpose of the research is to identify software specifications, architecture, and coding errors.
The primary objective of the requirement stage is to create the Program Requirement Specification (SRS), which correctly captures the specifications of the customer. SRS is a file that explains what the program can do. SRS’s fundamental aim is to bridge the gap in connectivity between consumers, end-users, and creators of applications. Another aim is to make people identify their own needs.
Purpose:
Usually, the SRS includes a short project summary. The requirement document aims to define all the details needed for the program to be planned, created, and evaluated.
- This project aims to have a comfortable atmosphere for holding books and library members’ information.
- The key aim of this project is to use computers to maintain a basic circulation system and to provide numerous reports.
Scope:
The paper only covers the criteria for the Library Management Framework standards. There is no connection in this paper to any other part of the Library Management System. This paper also lists all of the external interfaces and dependencies.
Feasibility study:
The ultimate scope of the feasibility analysis was to include adequate details to allow a decision to be taken as to whether, in the light of other current library management technologies, the Library Management System project should continue and, if so, its relative priority.
The feasibility study process of this project has undergone different steps defined as follows:
- Identify the sources of the data at multiple stages.
- Identify the consumer preferences of the computerized device.
- Analyze the disadvantages of the new method (manual system)
Definition, Acronyms, Abbreviation:
- JAVA -> platform independence
- SQL -> Structured query Language
- DFD -> Data Flow Diagram
- CFD -> Context Flow Diagram
- ER -> Entity Relationship
- IDE -> Integrated Development Environment
- SRS -> Software Requirement Specification
Reference:
Pankaj Jalote’s An Advanced Approach Information Engineering Third Edition.
- Java:- Balaguru Swamy
- SQL:- JosephL Jorden
Overview:
The introduction of Library Management begins with master documents such as book descriptions, library information, entering and updating. The latest books will be changed automatically by some more transactions such as book issue, book return.
Overall Description :
Product Perspective:
The planned Library Management Scheme would take care of the specifics of the latest book at any moment. The book dilemma, book return, would immediately update the new book information so that the user will have the latest book details updated.
Product function:
- The key goal of this initiative is to minimize the work done manually.
- Book Problems, Refunds, and Fine Calculation/Management can be handled by this program. Generating separate
- Record-Keeping Records according to end-user criteria
User characteristics:
We have 2 levels of users
- User Module: The user can verify the availability of the books in the user module.
- Book return
- Administration module: The sub-modules in the administration module are as follows.
- Register user
- Entry book details
- Book issue
General Constraints:
To have updated & accurate values, any change about the library book must be registered.
Assumption and dependencies:
All the details entered will be reliable and up to date. This software package is built with the assistance of the sun micro framework using java as the front end. The back end of Microsoft SQL Server 2005, which is supported by Windows 7.
Specific Requirement:
External Interface Requirement:
It should be simple and easy for consumers to understand and use. It should also be an immersive interface. For the user and administrator, the device should prompt the login to the program and correct feedback parameters.
User Interface:
The program offers a decent graphical interface for the user that can be run on the device by an administrator, performing the necessary tasks such as designing, reviewing, displaying the book information.
- Allows users to access quick reports in between real hours, such as Book Issues/Returned, etc.
- Based on various requirements, stock verification, and search service.
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
Communication interface:
Window
Functional requirements:
- Book-entry: We can store the information of the books in this module.
- Register student: We will keep the new student’s information in this module.
- Book issue: This module is used to keep track of the specifics of book issues.
- Book Return: This module allows the return of books to be monitored.
Performance requirements:
The computer’s capability depends on the software’s efficiency. Provided the database size is big enough, the program will take any amount of inputs. This would be dependent on the memory space available.
Design constraints :
Whenever a library member wants to take a book, the book issued by the library authority can check all the book information as well as the student details and store it in the library database. Each member will have an identification card that will be used for the library book issue, fine payment, etc. A great deal of human interference can be avoided in the event of book retrieval.
System attributes :
- Maintainability: The device would not need any servicing. The database is created by the end-user and is thus retained by the end-user.
- Portability: The device is built to be stable, so it can not be portable.
- Availability: This system will only be usable until it operates on the system it is built on.
- Scalability: Applicable.
Other requirements:
There are no other requirements.
DOWNLOAD NOW