Software Requirements Specification For Library Management System Version 1.

0 ap
proved Prepared by Ankush Mishra EMPI S VC-MaGtics March 16,2010 Copyright 2010
by Ankush mishra.
Software Requirements Specification for LMS Page ii Table of Contents Introducti
on................................................................... ..........
.....................................................1 Purpose .................
............................................................... ................
................................................................ .. 1 The purpos
e of Software Requirements Specification (SRS) document is to describe the exter
nal behavior of the Online Library System. Requirements Specification d efines a
nd describes the operations, interfaces, performance, and quality assurance requ
irements of t he Online Library System. The document also describes the nonfunct
ional requirements such as the u ser interfaces. It also describes the design co
nstraints that are to be considered when the system is to be designed, and other
factors necessary to provide a complete and comprehensive description of t he r
equirements for the software. The Software Requirements Specification (SRS) capt
ures the complet e software requirements for the system, or a portion of the sys
tem. Requirements described in this document are derived from the Vision Documen
t prepared for the Online Library System......... ..............................
... 1 Document Conventions......................................................
...... ............................................................... 1 Intende
d Audience and Reading Suggestions....................................... ......
............................................. 2 Project Scope...................
................................................ ...............................
......................................... 4 References..........................
............................................ ...................................
...................................... 5 Overall Description....................
........................................ ........................5 Product Persp
ective............................................................. ............
........................................................ 5 Product Features.....
........................................................... ....................
.................................................. 5 User Classes and Characteri
stics................................................ ..........................
................................... 6 The information of all the users must be s
tored in a database that is accessible by the Online Library System. The univers
ity information security system must be compat ible with the Internet applicatio
ns. The Online Library System is connected to the institute c
omputer and is running all 24 hours a day. The users access the Online Library S
ystem from any computer that has Internet browsing capabilities and an Internet
connection. The billing system is connecte d to the Online Library System and th
e database used by the billing system must be compatible wi th the interface of
the Online Library System. The users must have their correct usernames and passw
ords to enter into the Online Library System...................................
.................... ...........................................................
...... 7 User Documentation.....................................................
......... ................................................................ 7 Sys
tem Features................................................................ ...
........................................................ 8 Module Description...
........................................................... ....................
....................................9 External Interface Requirements...........
...................................... .........................................
.... 11 User Interfaces.........................................................
........ .......................................................... 11 Hardware
Interfaces............................................................. ........
......................................................... 12 Software Interfaces
............................................................. ..................
................................................ 12 Communications Interfaces...
.................................................... ...........................
.................................. 12 Other Nonfunctional Requirements..........
..................................... ..........................................
.12 Performance Requirements....................................................
.... ........................................................... 12 Security Req
uirements........................................................... ...........
.................................................... 13 Software Quality Attribu
tes..................................................... .......................
....................................... 13
Software Requirements Specification for LMS Page iii Revision History Date Versi
on Description Author 16/Mar/2006 1.0 Software Requirements Document Initial Rel
ease. Specification Author
Software Requirements Specification for LMS Page 1 Introduction Purpose The purp
ose of Software Requirements Specification (SRS) document is to describe the ext
ernal behavior of the Online Library System. Requirements Spe cification defines
and describes the operations, interfaces, performance, and quality assur ance r
equirements of the Online Library System. The document also describes the nonfu
nctional requirements such as the user interfaces. It also describes the design
constrain ts that are to be considered when the system is to be designed, and ot
her factors necessary to pro vide a complete and comprehensive description of th
e requirements for the software. The Software Requirements Specification (SRS) c
aptures the complete software requirements for the system, or a portion of the s
ystem. Requirements described in this document are derived from the Vision Docum
ent prepared for the Online Library System Document Conventions Font Style Size
Heading Times New Roman Bold 18 Sub-Heading Times New Roman Bold 14 Other s Aria
l Regular 12
Software Requirements Specification for LMS Page 2 Intended Audience and Reading
Suggestions We are developing our project Library Management System for the col
lege or any Institute. But this project can be deployed in any organization. Thi
s SRS is mainly developed for the project development team. In this team there a
re the project m anager, developer, coder, tester and documentation writer and t
he user of the project al so. User (Customer) This document is intended to user
and customer to make them ensure that this document is well meeting the need of
the users. Project Manager This SRS document is also very important for the proj
ect manager to ensure that can estimate the cost easily by referring to the SRS
document and that it contai ns all the information require planning the project.
Project Developer The project developer will refer to the SRS document to make
sure that they deve loped exactly hat the customer requires. Tester
Software Requirements Specification for LMS Page 3 The tester will read this SRS
document and he will ensure that the requirements are understandable from funct
ionality point of view so that he can test the soft ware and validate its workin
g. Document Writer The document writer is reading the SRS document is to ensure
that they understand the document well enough to be able to write the users manu
als. Maintenance The SRS document helps the maintenance engineers to understand
functionality of the system, a clear knowledge of the functionality can help the
m to understan d design and code. Suggestions 1. The user can read the whole SRS
document but for him Introduction, Overall description and System features is m
uch required the software performance. 2. For the project manager the system fea
tures is very important. 3. The developer must go through the whole SRS for unde
rstanding the requirement and functioning of software. 4. The designer and coder
must see the class and object diagram and state transmission diagram for coding
the modules. 5. A tester must be aware of coding language and visit through the
code section and check the required output. 6. The document writer should write
the qualitative document so that it becomes easy and understand to every one.
Software Requirements Specification for LMS Page 4 Project Scope The Software Re
quirements Specification captures all the requirements in a singl e document. Th
e Online Library System that is to be developed provides the members of the Libr
ary and employees of the library with books information, online blocking of book
s and many other facilities. The Online Library System is supposed to have t he
following features. The product provides the members with online blocking of boo
ks capabilities and the Online Library System is up and running all day. The sys
tem provides logon facility to the users. The system provides the members with t
he option to check their account and/or change their options like password of th
e account whenever needed all through th e day during the library hours. The sys
tem allows the members to block the books 24 hours a day and all the through the
semester. The system lets the library staff to check which all members have blo
cked the bo oks and whether they can borrow any more books or not. The system al
lows the Librarian to create the books catalog, add/delete books an d maintain t
he books catalog. The system updates the billing system as and when the member b
orrows or returns a book. The book catalog is automated and the decision of offe
ring the book based on the category of the book is automatically decided. We als
o have an order department, which manages to add or remove a book from the Libra
ry. The features that are described in this document are used in the future phas
es o f the software development cycle. The features described here meet the need
s of all the users. The success criteria for the system is based in the level up
to which the features described in this document are implemented in the system.
Software Requirements Specification for LMS Page 5 References Web Address (a). w
ww.google.com Overall Description Product Perspective The Online Library System
is a package to be used by Libraries to improve the efficiency of Librarians, Li
brary employees and Users. The Online Library System to be developed benefits gr
eatly the members and the Librarian of institute. The syste m provides books cat
alog and information to members and helps them decide on the books to b orrow fr
om the library. The Librarian can keep the books catalog updated all the time so
that the members (students and the professors) get the updated information all
the time. Product Features The Online Library System provides online real time i
nformation about the books available in the Library and the user information. Th
e Product functions are mor e or less the same as described in the product persp
ective. The functions of the system includ e the system providing different type
of services based on the type of users [Member/Libraria n]. The member should b
e provided with the updated information about the books catalog. Provisions for
the members to borrow the books they want, if all the other required rules hold
good. The member is given a provision to check his account information and chang
e the account information any time in the given valid period. The members are pr
ovided with the books available roster and allowed to choose the books, which th
ey want to use in the coming up days.
Software Requirements Specification for LMS Page 6 The librarian can get the inf
ormation about the members who have borrowed or returned the books. The libraria
n is provided with interfaces to add/delete the books available in the book cata
log. The members when complete the book borrowing or returning process, the due
to be paid by the member must be calculated and the information about the member
and the due amount is sent to the university billing system. User Classes and C
haracteristics The users of the system are members, librarian of the institute a
nd the administrators who maintain the system. The members and the librarian are
assume d to have basic knowledge of the computers and Internet browsing. The ad
ministrators of th e system to have more knowledge of the internals of the syste
m and is able to rectify the sm all problems that may arise due to disk crashes,
power failures and other catastrophes to mai ntain the system. The proper user
interface, users manual, online help and the guide to in stall and maintain the
system must be sufficient to educate the users on how to use the sy stem without
any problems. Operating Environment Software Requirement Operating System -: Wi
ndow XP, Mac Database -: MySQL Language -: PHP 5.0 Web Server -: Apache
Software Requirements Specification for LMS Page 7 Hardware Requirement 512 MB R
AM, Pentium P3/P4, 20/40 GB Hard disk Design and Implementation Constraints The
information of all the users must be stored in a database that is accessible by
the Online Library System. The university information security system must be co
mpatible with the Internet applications. The Online Library System is connecte d
to the institute computer and is running all 24 hours a day. The users access t
he Onlin e Library System from any computer that has Internet browsing capabilit
ies and an Internet connection. The billing system is connected to the Online Li
brary System and the database used by the billing system must be compatible with
the interface of the Online L ibrary System. The users must have their correct
usernames and passwords to enter into the Online Library System. User Documentat
ion Online help is provided for each of the feature available with the Online Li
brar y System. All the applications provide an on-line help system to assist the
user. The nature of these systems is unique to application development as they
combine aspects of programming (hyperlinks, etc) with aspects of technical writi
ng (organization, p resentation). Online help is provided for each and every fea
ture provided by the system. The U ser Manual describes the use of the system to
Librarian and Employees. It describes the use of
Software Requirements Specification for LMS Page 8 the system on mobile systems.
The user manual should be available as a hard copy and also as online help. An
installation document will be provided that includes the inst allation instructi
ons and configuration guidelines, which is important to a full solution offering
. Also, a Read Me file is typically included as a standard component. The Read M
e includes a What s New With This Release section, and a discussion of compatibi
lity issues with earlier releases. Most users also appreciate documentation defi
ning any known bu gs and workarounds in the Read Me file. Since the installation
of Online Library System is a complex process, our experts will do it. So an in
stallation Guide will not be pr ovided to the user. Assumptions and Dependencies
The users have sufficient knowledge of computers. The institute computer should
have Internet connection and Internet server capabilities. The users know the E
nglish language, as the user interface will be provided in English. The product
can acc ess institute student database System Features Descriptions and Priority
1. First priority goes to the welcome form. when user will login the system the
re w ill be welcome screen which will assure to the use either ha wants to enter
or exit. 2. After the welcome form there will be login form. Through this form
only authenti cated users can login the system just by entering their name and p
assword. 3. Second priority goes to the menu form where the contents, manuals, a
nd some othe rs functions of the system. From the menu form the user can go any
form of the syst em. 4. In the menu form there will be a facility to select thei
r choice for working lik e if the user just only wants to search the book then h
e will only select the search fiel d and go to the searching. 5. Similarly if th
e user wants to just show the report then he will go to the repor t section and
present the report in the desired format.
Software Requirements Specification for LMS Page 9 6. He priority given through
user basic. 7. The menu show according to user and they can access all informati
on . Functional Requirements In this system there are lots of functioning. The u
ser can Search book and see his/her account information. He will be able to get
the records in any format. There will also be a reminder and digital diary throu
gh this he can go to know a bout its important date like his book submission dat
e. Admin can add new record and saw all record of any student as well as library
. Module Description Type of user Administrator (librarian) HOD of all Departmen
t Student Faculty Staff Administrator module: Budget (for all departm
verification Create user Accept/Reject user Change password Book inventory User
information Report generation Search Book
Software Requirements Specification for LMS Page 10 Complaint All user can send
their complaint User module Change password Book Search See account information
Fine information All user check their fine Fine by date & Month Book inventory P
urchasing book information Maintain book inventory Book search Normal search by
alphabet Quick search by type(Book id, Author, ISBN,Publication) Other charges B
ook Binding, chair , Rack Journals News paper
Software Requirements Specification for LMS Page 11 External Interface Requireme
nts User Interfaces The design or layout of every form will be very clear and ve
ry interactive to th e user. When the user open the software the welcome window
will appear. In the login window the user can easily entered the desired passwor
d and login n ame. Then it will give the successfully login message. From each a
nd every window the user can easily go to any desired window that is there is wi
ll be a absolute and relative linking. In every window & Mac there is help and s
upport option is present for the ease o f user. There will be a proper collectio
n of GUI interface, which will provide better lo ok and feel. In the screen layo
ut the background color is very light and the graphics and fon t style will be i
n proper manner and well organized. If the user will print any error statement t
hen it will give the proper error me ssage display. In each and every window the
re will be alert, confirm etc message box for displa ying message. The user will
be able to search any data from the record by using proper guideli ne shown in
the window & Mac. In the opening of the software there will be a menu window whe
re the overall tab le contents of the software will be present through which the
user can move to any desired w indow & Mac. This will provide the better securi
ty data because the menu window will be displ aying according to the login (admi
n or normal user). User can easily save its data in to the database and keep tra
ck of the records o f purchase, vendor and inventory etc. This software will be
easily understandable and operable by the user.
Software Requirements Specification for LMS Page 12 Hardware Interfaces The exis
ting Local Area Network (LAN) will be used for collecting data from the users an
d also for updating the Library Catalogue. Software Interfaces A firewall will b
e used with the server to prevent unauthorized access to the sy stem. Communicat
ions Interfaces The Online Library System will be connected to the World Wide We
b. Other Nonfunctional Requirements Performance Requirements This software is no
t breakdown suddenly in any disaster like power failure. The development of the
software will be based on the object oriented model. The timeline of this softwa
re must be in our mind. The performance of the functions and every module must b
e well. At every step the output of the one phase is the input of the other phas
e and it will be reliable and accurate. The risk factor must be taken at initial
step for better performance of the soft ware. For individual function the perfo
rmance will be well. For login to the software password and user name will be ma
tched to the password and name saved in the database and thus only authenticated
users are allowed to the login . There will be various ways of retrieving data
and it takes less time. There will be ambiguity in the data and the record.
Software Requirements Specification for LMS Page 13 This software will be well s
upported to the other embedded software such as digi tal dairy, notepad etc. The
overall performance of the software will reliable and enable the users to wo rk
efficiently. Security Requirements There will be proper security regarding to t
he accessing of data. The external security can be provided by given the login a
uthentication. The data that are stored in the database must be private. There i
s also required a user authentication. There is also the facility that the admin
can lock his private data that will no t be accessed by anyone. The whole softw
are is secure from the outside accessing. Software Quality Attributes Our softwa
re has many quality attribute that are given belowAdaptability This software is
adaptable by any organization. Availability-The availability of the software is
easy and for everyone. Correctness-The results of the function are pure and accu
rate. Flexibility-The operation may be flexible and reports can be presented in
many w ays. Maintainability-After the deployment of the project if any error occ
urs then it can be easily maintain by the software developer. Portability-The so
ftware can be deployed at any machine. Reliability-The performance of the softwa
re is better which will increase the re liability of the software. Reusability-T
he data and record that are saved in the database can be reused if needed.
Software Requirements Specification for LMS Page 14 Robustness-If there is any e
rror in any window or module then it does not effect the remaining part of the s
oftware. Testability-The software will be tested at every. Alpha Testing Beta Te
sting Acceptance Testing Usability-To performs any operations and to understand
the functioning of softwa re is very easy. Productivity-This software will produ
ce every desired result with accurately. Timelines-The time limit is very import
ant. It will save much time and provide f ast accessing. Cost effective-This sof
tware is less in cost and bearable by any organization.