Srs for library

SRS FOR LIBRARY MANAGEMENT SYSTEM 1
1
SRS FOR LIBRARY MANAGEMENT SYSTEM MAII
by
FAROUQ UMAR IDRIS

2
1. INTRODUCTION
The project titled Library Management System is Library management software for monitoring
and controlling the transactions in a library .The project “Library Management System” mainly
focuses on basic operations in a library like adding new member, new books, and updating new
information, searching books and members and facility to borrow and return books.
Library Management System is a windows application written for Windows operating systems,
designed to help users maintain and organize library. Our software is easy to use for both
beginners and advanced users. It features a familiar and well thought-out, an attractive user
interface, combined with strong searching Insertion and reporting capabilities. The report
generation facility of library system helps to get a good idea of which are the books borrowed
by the members, makes users possible to generate reports’ hard copy.
The software Library Management System has four main modules.
1. Insertion to Database Module – User friendly input screen
2. Extracting from Database module – Attractive Output Screen
3. Report Generation module – borrowed book list & Available book list
4. Search Facility system – search for books and members

3
2. SYSTEM ANALYSIS
2.1. EXISTING SYSTEM:
System Analysis is a detailed study of the various operations performed by a system
and their relationships within and outside of the system. Here the key question is- what all
problems exist in the present system? What must be done to solve the problem? Analysis
begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions
handled by the present system. The commonly used tools in the system are Data Flow Diagram,
interviews, etc. Training, experience and common sense are required for collection of relevant
information needed to develop the system. The success of the system depends largely on how
clearly the problem is defined, thoroughly investigated and properly carried out through the
choice of solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed system should be analyzed thoroughly in
accordance with the needs.
System analysis can be categorized into four parts.
1. System planning and initial investigation
2. Information Gathering
3. Applying analysis tools for structured analysis
4. Feasibility study
5. Cost/ Benefit analysis.

4
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.

5
2.2. PROPOSED SYSTEM
Proposed system is an automated Library Management System. Through our
software user can add members, add books, search members, search books, update information,
edit information, borrow and return books in quick time. Our proposed system has the
following advantages.
1. User friendly interface
2. Fast access to database
3. Less error
4. More Storage Capacity
5. Search facility
6. Look and Feel Environment
7. Quick transaction
All the manual difficulties in managing the Library have been rectified by implementing
computerization.

6
2.3. FEASIBILITY ANALYSIS
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.
2.3.1. 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.
2.3.2. ECONOMICAL FEASIBILITY
Development of this application is highly economically feasible .The organization needed
not spend much money for the development of the system already available. The only thing is
to be done is making an environment for the development with an effective supervision. If 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 the organization
.Therefore, the system is economically feasible.

7
3. CONFIGURATION
3.1. HARDWARE CONFIGURATION
Processor : Pentium III 630MH
RAM : 128 MB
Hard Disk : 20GB
Monitor : 15” Color monitor
Key Board : 122 Keys

8
3.2. SOFTWARE CONFIGURATION
Operating System : Windows NT,
Windows 98,
Windows XP.
Language : Java 2 Runtime Environment
Database : MS Access2007.

9
4. SYSTEM REQUIREMENTS
This management system can be used in windows 98, Windows2000, Windows XP and
Windows NT, supported for other platform such as Applet, Macintosh and UNIX.
The system must be running Windows 98, Windows 98 or Windows NT4.0 operating system
and must meet the following hardware requirements.
1. For Windows 95 based computers , a 486 / 66 MHz or higher processor with 8MB
2. For Windows 98 based computers , a 500/88MHz or higher processor with 32 Mb of RAM
3. For Windows NT based computers , a 488 / 66 MHz or higher processor with 16 MB of
RAM
4. For Windows 200 based computers , a 700/850 MHz or higher processor with 512 MB of
5. Ram

10
4.1. ER DIAGRAM

11
4.2. DATA FLOW DIAGRAM

12

13
5. SOFTWARE INTERFACE
5.1. Add New Book
1. The software should be able to add a new book to database
2. The book subject field should be editable
3. The book subject field should contain alphanumeric characters.
4. The book title field should be editable
5. The book title field should contain alphanumeric characters.
6. The name of the Author field should be editable
7. The name of the Author field should be defaulted to contain alpha characters
8. The name of the publisher field should be editable
9. The name of the publisher field should only contain alpha characters
10. The edition number field should only contain numeric characters only

14
11. The numbers of pages field should contain numeric characters only
12. ISBN for the book field should contain numeric characters only
13. The number of copies field should contain numeric characters only
14. The name of the library field should contain alpha characters only
15. Shelf no field should contain numeric characters only

15
5.2. Listing All Books
1. The book information screen should appear after clicking insert the information button
2. User should be able to see the list of books in the database

16
5.3. Available Books
User should be able see the list of books available with their information including the
following
1. Bookid
2. Subject
3. Title
4. Author
5. Publisher
6. Edition
7. Pages
8. Isbn

17
5.4. Borrowed Books
The borrowed book field should be non-editable
User should be able see the list of book that are borrowed out to the customers
5.5. Remove Book
user should be able to remove a book from the database

18
5.6. Edit Book Details
1. User should be able to edit book information and update it to the database
2. All the fields that appears on the screen should be editable

19
5.7. Add a Member
The user should be able to add a new member by filling in the member information
1. Member ID
2. The password
3. Name
4. E-mail
5. Major
6. Expired

20
5.8. Listing all Members
The user should be able to view all the list of the members that have been register to the
database and with their basic information
1. member ID
2. ID
3. Name
4. E-mail
5. Major
6. expired

21
5.9. Edit a member
1. User should be able to edit member information
2. All the field that appears on the screen should be editable
5.1.1. Remove a member
1. User should be able to remove member information from the database
2. Only member ID field should be editable
3. User should be able to see the remove button

22
5.1.2. Search for Members and Books
1. User should be able to search for book and member
2. User should be able to see (search for a book) on the left side of the screen with the
following field
search by:
a. write the keyword
b. search button
3. user should be able to see (search for a member) on the right side of the screen with the
following field
search by
a. write the keyword
b. search button
c. cancel button

23
5.1.3. Borrow Books
User should be able to view the borrow books screen with the books information including the
following fields and buttons
1. write the book ID
2. write the member ID
3. the current date
4. the return date
5. borrow button
6. cancel button

24
5.1.4. Returning a Book
User should be able to view return book screen with the following fields and buttons
3. return date
4. total fine amount( if the customer return the book in time without any delay then the total
fine amount should field should remain non-editable, but if he didn’t return the book in
time then the field should be editable)
5. return button
6. cancel button

25
5.1.5. List of Issued Books
User should be able to view the issued books screen with the following information of the book
and customer
1. Book ID
2. Title
3. Member ID
4. Day of return
5. ID
6. Name
7. E-mail

26
5.1.6. Reserve a Book
Customers should be able to make book reservation
User should be able to view the book reservation screen including the following fields and
buttons
3. the current date
4. reservation till
5. reserve button
6. cancel button

27
6. SYSTEM DESIGN
6.1. INPUT DESIGN
Input design is the process of converting user-oriented input to a computer based
format. Input design is a part of overall system design, which requires very careful attention
.Often the collection of input data is the most expensive part of the system. The main objectives
of the input design are …
1. Produce cost effective method of input
2. Achieve highest possible level of accuracy
3. Ensure that the input is acceptable to and understood by the staff.
6.2. INPUT DATA
The goal of designing input data is to make enter easy, logical and free from errors as
possible. The entering data entry operators need to know the allocated space for each field;
field sequence and which must match with that in the source document. The format in which
the data fields are entered should be given in the input form .Here data entry is online; it makes
use of processor that accepts commands and data from the operator through a key board. The
input required is analyzed by the processor. It is then accepted or rejected. Input stages include
the following processes
1. Data Recording
2. Data Transcription
3. Data Conversion
4. Data Verification
5. Data Control

28
6. Data Transmission
7. Data Correction
One of the aims of the system analyst must be to select data capture method and
devices, which reduce the number of stages so as to reduce both the changes of errors and the
cost .Input types, can be characterized as.
1. External
2. Internal
3. Operational
4. Computerized
5. Interactive
Input files can exist in document form before being input to the computer. Input design
is rather complex since it involves procedures for capturing data as well as inputting it to the
computer.

29
6.3 OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide a permanent copy of these result for latter
consultation .Computer output is the most important and direct source of information to the
users. Designing computer output should proceed in an organized well through out the manner.
The right output must be available for the people who find the system easy o use. The outputs
have been defined during the logical design stage. If not, they should defined at the beginning
of the output designing terms of types of output connect, format, response etc,
Various types of outputs are
1. External outputs
2. Internal outputs
3. Operational outputs
4. Interactive outputs
5. Turn around outputs
All screens are informative and interactive in such a way that the user can full fill his
requirements through asking queries.

30
7. DATABASE DESIGN
The general theme behind a database is to handle information as an integrated whole. A
database is a collection of interrelated data stored with minimum redundancy to serve many
users quickly and effectively. After designing input and output, the analyst must concentrate on
database design or how data should be organized around user requirements. The general
objective is to make information access, easy quick, inexpensive and flexible for other users.
During database design the following objectives are concerned:-
1. Controlled Redundancy
2. Data independence
3. Accurate and integrating
4. More information at low cost
5. Recovery from failure
6. Privacy and security
7. Performance
8. Ease of learning and use

31
8. TABLES USED
8.1 Table Name: Books
Field Name Data Type Description
BookId AutoNumber Primary Key
Subject Text (30) -
Title Text (30) -
Author Text (25) -
Publisher Text (25) -
Copyright Number -
Edition Number -
Pages Number -
ISBN Text -
NumberOfBooks Number -
NumberOfAvailbleBooks Number -
NumberOfBorrowedBooks Number -
Library Text(25) -
Availble Yes/No -
ShelfNo Number -

32
8.2 Table Name: Borrow
BookId Number Primary Key
MemberID Number -
DayOfBorrowed Date/Time -
DayOfReturn Date/Time -

33
8.3 Table Name: Members
MemberId AutoNumber Primary Key
ID Number -
Password Text(10) -
NAME Text(25) -
EMAIL Text(25) -
Major Text(10) -
NumberOfBooks Number -
Mony Number -
Expired Date/Time -

34
9. SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a
working system. The implementation phase constructs, installs and operates the new system.
The most crucial stage in achieving a new successful system is that it will work efficiently and
effectively.
There are several activities involved while implementing a new project they are
1. End user training
2. End user Education
3. Training on the application software
4. System Design
5. Parallel Run And To New System
6. Post implementation Review
9.1. END USER TRAINING:
The successful implementation of the new system will purely upon the involvement of the
officers working in that department. The officers will be imparted the necessary training on the
new technology.
9.2. END USER EDUCATION:
The education of the end user start after the implementation and testing is over. When
the system is found to be more difficult to under stand and complex, more effort is put to
educate the end used to make them aware of the system, giving them lectures about the new
system and providing them necessary documents and materials about how the system can do
this.

35
9.3. TRAINING OF APPLICATION SOFTWARE:
After providing the necessary basic training on the computer awareness, the users will
have to be trained upon the new system such as the screen flows and screen design type of help
on the screen, type of errors while entering the data , the corresponding validation check at
each entry and the way to correct the data entered. It should then cover information needed by
the specific user or group to use the system.
9.4. POST IMPLEMENTATION VIEW:
The department is planning a method to know the states of t he past implementation
process. For that regular meeting will be arranged by the concerned officers about the
implementation problem and success

36
10. SOFTWARE TESTING
Is the menu bar displayed in the appropriate contested some system related features
included either in menus or tools? Do pull –Down menu operation and Tool-bars work
properly? Are all menu function and pull down sub function properly listed ?; Is it possible to
invoke each menu function using a logical assumptions that if all parts of the system are
correct, the goal will be successfully achieved .? In adequate testing or non-testing will leads to
errors that may appear few months later.
This create two problem
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system
The purpose of the system testing is to consider all the likely variations to which it will be
suggested and push the systems to limits.
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.

37
10.1. WHITE 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
1. 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 fixed
2. All logical decisions were checked for the truth and falsity of the values.
10.2. 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

38
11. 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.

39
12. BIBLIOGRAPHY
1. http://www.java2s.com/
2. http://www.javaworld.com/javaworld/jw-01-1998/jw-01-bookreview.html
3. Database Programming with JDBC and Java by O'Reilly
4. Head First Java 2nd Edition
5. http://java.sun.com/javase/technologies/desktop/

Srs for library

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Srs for library

Similaire à Srs for library (20)

Plus de farouq umar

Plus de farouq umar (19)

Dernier

Dernier (20)

Srs for library