Software Requirements

Specification
For

Library Management System

SubmittedBy:

LubabaRashid
FaryalAkram
SheebaLall
JavariaAsif
MaryamSohail

BSE-IV (B)

TableofContents
1. Introduction..............................................................................................................................3
1.1
1.2
1.3
1.4
1.5

Purpose...........................................................................................................................................3
DocumentConventions...................................................................................................................3
IntendedAudienceandReadingSuggestions.................................................................................3
ProductScope.................................................................................................................................3
References......................................................................................................................................3

2.1
2.2
2.3
2.4
2.5
2.6
2.7

ProductPerspective.........................................................................................................................4
ProductFunctions...........................................................................................................................4
UserClassesandCharacteristics.....................................................................................................4
OperatingEnvironment...................................................................................................................4
DesignandImplementationConstraints.........................................................................................5
UserDocumentation.......................................................................................................................5
AssumptionsandDependencies......................................................................................................5

2. OverallDescription..................................................................................................................4

3. ExternalInterfaceRequirements...........................................................................................6
3.1 UserInterfaces................................................................................................................................6
3.2 HardwareInterfaces........................................................................................................................6
3.3 SoftwareInterfaces.........................................................................................................................6

4. SystemFeatures.......................................................................................................................3
4.1 SystemFeature1.............................................................................................................................7
4.2 SystemFeature2............................................................................................................................7

4.3 SystemFeature3......8
5.OtherRequirements..8

1. Introduction
1.1 Purpose
This document describes the software requirements and specifications for a library management
system
The purpose of this project is to provide a friendly environment to maintain the details of
books and library members. The project describes hardware and software requirements of the
library management system.
1.2 DocumentConventions
Thedocumentiswrittentechnically.Thefontsizeof
Bodyis12andjustified.
Subheadingis14andbold.
Mainheadingis18andbold.
ThefontstyleisTimesNewRoman
Thereaderisassumedtohavebasicknowledgeofcomputer.
1.3 IntendedAudienceandReadingSuggestions
The document is intended for designer, developer, testers, maintainer, and to some extent
for the users.
1.4 ProductScope
Librarymanagementsystemisbasicallyupdatingthemanuallibrarysystem.Theproject
isspecificallydesignedfortheuseoflibrariansandlibraryusers.Theproductwillworkasa
completeuserinterfaceforlibrarymanagementprocesslibraryusageforordinaryusers.
Itisespeciallyusefulforeducationalinstitutionsanditcanbeeasilyimplementedunder
variousconditions.
1.5 References
https://www.student.cs.uwaterloo.ca/~cs445/Winter2010/Lectures/21_SRS.pdf
SoftwarerequirementsandSpecifications:AlexiconofPractice,PrinciplesandPrejudices
(ACMPress)byMichaelJackson.

2. OverallDescription
2.1 ProductPerception
The library management system provides various facilities to the users. The users are
administrators or the students. The system will provide a search facility, issue book facility, list
of members etc. It has to work together with computers/software owned by organization.
2.2 ProductFunctions
Software is to be designed to meet following requirements

Enter data of the book issued to student.

At the time of issuing a book to student it checks for the number of books issued to
student.

View list of students to whom the books are issued.

Update the information of the student if he wants to change the book.

Delete the data of the student when he returns the book.

It also check if the book is returned after the due date it can charge fine to the student.
2.3 UserClassesandCharacteristics

TheusersofLibrarymanagementsystemare:

Administrators:administratethewholesystem.
Students:usethesystemtoviewandissuetherequiredbooks.
Maintainers:maintainthesystem.

All VPs

Indirect

Library
manager

Finance

Interactor

Article
providers

S tudents

S taf

Us ers

External

Library
s taf

Sys tem
managers

Domain

UI
s tandards

Clas s ification
s ys tem

Cataloguers

2.4 OperatingEnvironment
Theproductwillbeoperatinginwindowsenvironment.Thehardwareconfiguration
includeHardDisk:40GB,Monitor:1.5Colormonitor,Keyboard:122keys.Thebasicinput
deviceiskeyboardandoutputdeviceisMonitor.
2.5 Assumptions
Theassumptionsare:
Thehardwarecomponentsofthewholesystemneverfail.
Thecodingshouldbeerrorfree
Thesystemshouldbeuserfriendlysothatitiseasytousefortheusers.
Thesystemshouldhavemorestoragecapacity.
Thesystemshouldavailable24hoursaday.
2.6 DesignandImplementationConstraints
TheConstraintsincludethatthesystemshould:

ValidateUsernameandnumber.
IssueLimitednumberofbooks.
Ifthelimitexceeds,thesystemwilldisplayanerrormessage.
Theusercanviewthebooksissuedonhisorhername.

2.7 UserDocumentation
Theusermanualfortheworkingofthesystemisavailablealongwiththesystem;also
theuserinterfaceinthesystemprovidesafriendlyenvironmentandisselfexplanatory.

3. ExternalInterfaceRequirements
3.1 UserInterfaces
The system will support a user friendly interface, so that the users can
use the functionalities of the whole system efectively and efficiently to
perform the required task such as create, update, view details etc.
The user interface will be customizable by the administrators.
The interface will provide a user friendly menu on the interface
to issue a book, deposit a book and search a book.
3.2

HardwareInterfaces

The hardware should support the following specification:

It should be capable of taking input from the user and processing on

that input to perform specific decisions.
It should support efficient keypads for the ease of users.
The hardware should specify mechanisms for continuous power supplies.
3.3 Softwareinterfaces

The software interfaces will be specified according to organizational

software systems, their operating systems and their special tools.
Typical platforms used are Microsoft operating systems (such as MSDOS, PC-DOS,
Windows NT, Windows 2000, Windows XP Professional, or Windows XP Embedded).
.

4. SystemFeatures
4.1 SearchBooks:
Description:
The system will allow the user to search the list of books.

4.2 CreateBookrecord:
Description:
The system will allow the administrator to add book to the list of books
4.3 IssueBooks:
Description:
The system will allow the user to issue a book on his or her account, allowing only a limited
number of books at a time. The system will be able to calculate fine in case of late deposition.
4.4 CreateanddisplayStudentrecords:
Description:
The system will allow the administrator to create and display the records of students/members.
4.5 DepositBook:
Description:
The system will allow the user to deposit the books issued on his part.
4.6 Editrecords:
Description:
The system will allow the administrator to edit the records of students and books.
4.7 DeleteRecords:
Description:
The system will allow the administrator to delete records of students and books.
4.8 PerformanceRequirements:

Thesystemmustbeabletoperformitstasksinunfavorablesurroundings.
Thetimetakenbytheprocessertocollectdatafromtheuser,analyzingthatdata,its
encryptionanddecryptionandresultingresponsewillcomeontime.Wehavetomake
surethattheprocessingshouldnotbeverylengthy.
4.9 SafetyandSecurityRequirements

Itisimportanttodecidewheretoplacethesystem.Itshouldbeplacedcarefullyinasafe
place.

Thereshouldbeproperauthenticationmechanismsthatshouldbefollowedbytheusers
toprivilegeaccesstothesystem.
Useraccessibilitymustbecensuredinallways.
Normaluserscanjustreadtheinformationbuttheycannoteditormodifyanything
excepttheirpersonalinformation.
4.10

SoftwareQualityAttributes:

Quality attributes are the overall factors that affect run-time behavior, system design, and user
experience. They represent areas of concern that have the potential for application wide impact
across layers and tiers. The quality attributes are:
1. Availability:
Thelibraryhastobeavailable24hoursaday. Availability will be affected by system errors,
infrastructure problems, malicious attacks, and system load.
2. Security:
The System should provide maximal security. This can be achieved by using User Ids and
passwordsforauthorizedusers..
3. Maintainability:
The ability to identify and fix a fault within a software component is what the maintainability
characteristic addresses. Onlymaintainersareallowedtoinstallthesystemonnewcomputers.
4. Durability
Information will be accurate and consistent.
4.11

BusinessRules

Business rules represent policies, procedures, and constraints that describe an enterprises way of
doing business. This includes the rules and regulations that the system users should abide by.
This includes the cost of project and the discount offers provided. The users should avoid illegal
rules and protocols. Neither admin nor member should cross the rules and regulations.

5. OtherRequirements
There are different categories of the users like Admin, student etc. depending upon the
category of the user access rights are decided. If the user is an administrator then he can be able
to modify the data, delete, append etc. if the user is a student he can simply view details of books
issued on his part.