Shambhunathinstituteof
engineeringandtechnology
• Software requirement
specifications
For
Library ManagementSystem
Preparedby:
Shubham yadav
Vijay mishra
Rohit Singh
AcademicYear:20-21
Mini project
• Shambhunath institute of engineering and technology
1. Introduction
1. Purpose
The main objective of this document is to illustrate the requirements of the project Library Management
[Link] documentgivesthedetaileddescriptionof thebothfunctional andnon-functionalrequirementsproposed
by the [Link] purpose of this project is to provide a friendly environment to maintain the details of books and
library [Link] 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
diagramsandUML diagrams.
2. DocumentConventions
Entiredocumentshouldbejustified.
Conventionfor Main title
Font face: Times New Roman
Fontstyle: Bold
FontSize: 14
Conventionfor Sub title
Font face: Times New Roman
Fontstyle: Bold
Font Size:12
Conventionfor body
Font face: Times New Roman
FontSize: 12
3. ScopeofDevelopmentProject
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 theuseof librarians andlibrary users. The product will work as acomplete
user interface for library managementprocess andlibrary usagefrom ordinary users. Library Management System
can be used byany existing or newlibrary to manageits books andbook 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 canbeeasily implementedundervarious [Link] canaddnewfeatures asandwhenwe
require,makingreusabilitypossibleasthereis flexibilityin all themodules.
Thelanguageusedfor developingtheprojectis Javaas it is quiteadvantageousthanother
languagesin termsof performance, toolsavailable, crossplatformcompatibility, libraries, cost (freely available), and
developmentprocess.
4. Definitions,Acronyms andAbbreviations
JAVA ->platformindependence SQL->
Structured queryLanguage ER-> Entity
Relationship
UML ->Unified ModelingLanguage
IDE-> IntegratedDevelopmentEnvironment SRS->
SoftwareRequirement Specification
• Shambhunath institute of engineering and technology
ISBN ->InternationalStandardBook Number
IEEE ->Institute of Electrical andElectronicsEngineers
1.5References
Books
SoftwareRequirementsandSpecifications: A Lexicon of Practice, Principles and Prejudices(ACM
Press)by MichaelJackson
SoftwareRequirements(Microsoft) SecondEditionBy Karl E. Wiegers
SoftwareEngineering:A Practitioner’sApproachFifth EditionBy RogerS. Pressman
Websites
[Link]
[Link]
2. Overall Descriptions
1. ProductPerspective
Use CaseDiagramof Library ManagementSystem
*
searches
search_book check_limit
1
1 requests
1..* check_availability
1 1..*
1
User 1 monitors_request
<<include>>
issue_book 1
request_renew
1
monitors_renew 1
<<include>> 1
performs verify_member
0..* Librarian
1
give_book take_book
1..*
<<include>>
renew_book
Student adds_new_book
0..* 1..*
perform_transaction_updation
*
Staff *
return_book
View_logs <<extend>> add_book
calculate_fine
update_record
This is abroadlevel diagramof theproject showing abasicoverview. The userscanbeeither staff or student..This
Systemwill provide asearchfunctionality tofacilitate thesearchof resources. This searchwill bebasedonvarious
categories viz. book name or the ISBN. Further the library staff personnel can add/update the resources and the
resourceusersfromthe
• Shambhunath institute of engineering and technology
[Link] thesystemcanrequestissue/renew/returnof books for which theywould haveto follow certain
criteria.
2.2ProductFunction
Entity Relationship Diagramof Library Management System
TheOnline Library Systemprovidesonlinerealtimeinformationaboutthebooksavailablein theLibrary andtheuser
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
[Link] Librarianwill actastheadministratortocontrolmembersandmanage [Link]’s
statusof issue/returnis [Link]’s detailscanbefetched bythelibrarian fromthe
[Link] viewtheiraccountinformation.
2.3UserClassesandCharacteristics
• Shambhunath institute of engineering and technology
The systemprovidesdifferent typesof servicesbasedonthetypeof users [Member/Librarian]. TheLibrarian
will be acting as the controller and he will have all the privileges of anadministrator. The membercan beeither a
studentorstaff of theuniversitywho will beaccessingtheLibraryonline.
ThefeaturesthatareavailabletotheLibrarian are:-
A librarian canissue abookto themember.
Can view thedifferent categoriesof books availablein theLibrary
Can view theList of books availablein each category
Can takethebook returnedfromstudents
Add books andtheir informationto the database
Edit theinformation of existingbooks
Can checkthereportof theexistingbooks
Can checkthereportof theissuedbooks
Can accessall theaccountsof thestudents
The featuresthatareavailableto theMembers are:-
Can view thedifferent categoriesof books availablein theLibrary
Can view theList of books availablein each category
Can own anaccountin the library.
Can view thebooksissuedto him
Can putarequestfor anewbook
Can view thehistory of books issuedto him previously
Can searchfor aparticularbook
2.4OperatingEnvironment
The product will be operating in windows environment. The Library Management System is a website and shall
operatein all famousbrowsers,for amodel wearetaking Microsoft Internet Explorer,Google Chrome,andMozilla
[Link] it will becompatible with theIE 6.0. Most of thefeatureswill becompatiblewith theMozilla Firefox
& [Link] onlyrequirementtousethisonlineproductwould betheinternetconnection.
ThehardwareconfigurationincludeHardDisk: 40GB, Monitor:15”Colormonitor, Keyboard:
[Link],mouseandoutputdevicesaremonitor, printeretc.
5. AssumptionsandDependencies
The assumptionsare:-
The codingshouldbeerrorfree
The systemshouldbeuser-friendly sothatit is easyto usefor theusers
The information of all users,books andlibraries mustbe storedin adatabase thatisaccessibleby the website
Thesystemshouldhavemorestoragecapacity andprovidefastaccesstothedatabase
The systemshouldprovidesearchfacility andsupportquick transactions
The Library System is running24hoursaday
Users may access from anycomputer thathasInternet browsingcapabilities andan
Department of Information Technology
• Shambhunath institute of engineering and technology
Internetconnection
Usersmusthavetheir correct usernames andpasswordsto enterinto theironline accounts anddoactions
The dependenciesare:-
The specific hardwareandsoftware dueto which theproductwill berun
On thebasisof listing requirementsandspecification theproject will bedevelopedandrun
The endusers(admin)shouldhaveproperunderstandingof theproduct
The systemshouldhavethegeneralreportstored
The information of all theusersmustbestoredin adatabasethatis accessibleby theLibrarySystem
Any updateregardingthebook from thelibrary is to berecordedto thedatabaseandthedataenteredshouldbe
correct
6. Requirement
SoftwareConfiguration:-
This software packageis developedusingjava asfront endwhich is supportedby sunmicro system. Microsoft SQL
Server asthebackendto storethedatabase.
Operating System:Windows NT, windows 98, Windows XP Language:
Java Runtime Environment,Net beans7.0.1 (front end) Database:MS SQL
Server (back end)
HardwareConfiguration:- Processor:
Pentium(R)Dual-core CPU HardDisk:
40GB
RAM: 256MB ormore
7. DataRequirement
Theinputsconsist of thequerytothedatabaseandtheoutputconsistsof thesolutionsfor [Link]
alsoincludes theuserreceivingthedetailsof [Link] thisproject theinputswill bethequeriesasfiredbythe
users like createanaccount, selecting books and putting into account. Now theoutput will be visible when theuser
requeststheservertoget detailsof theiraccountin theformof time, dateandwhich booksarecurrentlyin theaccount.
3. ExternalInterfaceRequirement
1. GUI
The software providesgoodgraphicalinterfacefor theuserandtheadministrator canoperateon thesystem,
performingtherequiredtasksuchascreate,update,viewing thedetailsof thebook.
It allows userto view quick reportslike Book Issued/Returned in betweenparticular time.
It providesstockverification andsearchfacility basedondifferentcriteria.
The userinterfacemustbecustomizable by theadministrator
All themodulesprovidedwith thesoftware mustfit into this graphicaluserinterfaceandaccomplish to the
standarddefined
The designshouldbe simpleandall thedifferent interfaces shouldfollow astandard
• Shambhunath institute of engineering and technology
template
The userinterfaceshouldbeableto interactwith theusermanagementmoduleandapartof theinterfacemustbe
dedicatedtothelogin/logout module
Login Interface:-
Incasetheuseris notyetregistered,hecanenterthedetailsandregistertocreatehisaccount. Oncehisaccountis created
he can ‘Login’ which asks the user to type his username and password. If the user entered either his username or
passwordincorrectlythenanerrormessageappears.
Search:-
The memberorlibrariancanenterthetypeof book heis lookingfor andthetitleheis interested in,thenhecansearchfor
therequiredbookbyenteringthebookname.
CategoriesView:-
Categoriesview showsthecategoriesof books availableandprovidesability to thelibrarianto add/editordeletecategory
from thelist.
Librarian’sControlPanel:-
This control panelwill allowlibrarianto add/removeusers;add,edit,orremove [Link] managelendingoptions.
4. SystemFeatures
Theusersof thesystemshouldbe providedthesuretythattheiraccountis [Link] possiblebyproviding:-
Userauthenticationandvalidationof membersusingtheiruniquememberID
Propermonitoringbytheadministratorwhichincludesupdatingaccountstatus,showing apopupif themember
attempts to issue number of books that exceed the limit provided by the library policy, assigning fine to
memberswhoskipthedateof return
Proper accountability which includes not allowing a member to see other member’s account. Only
administratorwill seeandmanageall memberaccounts
5. OtherNon-functional Requirements
1. PerformanceRequirement
The proposed systemthat wearegoing todevelop will beusedastheChief performance system within thedifferent
campuses of the university which interacts with the university staff and students. Therefore, it is expected that the
databasewould performfunctionallyall the requirementsthatarespecifiedbytheuniversity.
Theperformanceof thesystemshouldbefastandaccurate
Library Management System shall handle expected and non-expected errors in ways that prevent loss in
information and long downtime period. Thus it should have inbuilt error testing to identify invalid
username/password
Thesystemshouldbeabletohandlelargeamountof [Link] shouldaccommodate highnumberof books
anduserswithoutanyfault
2. SafetyRequirement
• Shambhunath institute of engineering and technology
The databasemaygetcrashedatanycertain time dueto virus or operating systemfailure. Therefore, it is required to
takethedatabasebackupsothatthedatabaseis notlost. Proper UPS/inverter facility shouldbetherein caseof power
supplyfailure.
3. SecurityRequirement
System will usesecureddatabase
Normal userscanjust readinformation buttheycannoteditor modify anythingexcepttheir personalandsome
otherinformation.
System will havedifferent typesof usersandeveryuserhasaccessconstraints
Properuserauthenticationshouldbeprovided
No oneshouldbeableto hackusers’password
Thereshouldbe separateaccountsfor adminandmemberssuchthatnomembercanaccessthedatabaseand
only adminhastherightsto updatethedatabase.
4. Requirementattributes
Theremay bemultiple adminscreatingtheproject, all of them will havetheright tocreatechangesto the
system. But themembers or otheruserscannotdochanges
The project shouldbeopensource
The Quality of thedatabaseis maintainedin suchaway sothatit canbe veryuserfriendly to all theusersof the
database
The userbeableto easily download andinstall the system
5. BusinessRules
A businessruleis anythingthatcapturesandimplementsbusinesspolicies andpractices. A rule canenforcebusiness
policy, makeadecision, or infer newdatafrom existing [Link] includes therules andregulations thattheSystem
usersshouldabideby. This includes thecostof the project andthediscount offers provided. The usersshouldavoid
illegal rulesandprotocols. Neitheradminnormembershouldcrosstherulesand regulations.
6. UserRequirement
The usersof thesystemaremembersandLibrarian of theuniversity whoactasadministrator to maintain thesystem.
Themembersareassumedtohavebasicknowledgeof thecomputersand [Link] the
systemshould havemoreknowledgeof theinternals of thesystemandis able to rectify thesmall problemsthat may
ariseduetodiskcrashes,power [Link],user
manual, online helpandtheguidetoinstall andmaintain thesystemmustbesufficient toeducatethe usersonhowto
usethesystemwithoutanyproblems.
Theadminprovidescertainfacilitiestotheusersin theform of:-
Backupand Recovery
ForgotPassword
Datamigrationi.e. wheneveruserregistersfor thefirst time thenthedatais storedin theserver
Datareplication i.e. if thedatais lost in onebranch,it is still storedwith theserver
Auto Recoveryi.e. frequentlyautosaving theinformation
Maintaining files i.e. File Organization
The servermustbemaintainedregularly andit hasto beupdatedfromtime to time
• Shambhunath institute of engineering and technology
6. OtherRequirements
1. DataandCategoryRequirement
There are different categories of users namely teaching staff, Librarian, Admin, students etc. Depending upon the
categoryof [Link] meansif theuseris an administratorthenhecanbeable tomodifythe
data,delete, append etc. All other users except the Librarian only have the rights to retrieve the information about
database. Similarly there will be different categories of books available. According to the categories of books their
relevantdata [Link] the particular
format.
2. Appendix
A: Admin, Abbreviation, Acronym, Assumptions; B: Books, Business rules; C: Class, Client, Conventions; D:
Data requirement, Dependencies; G: GUI; K: Key; L: Library, Librarian; M: Member; N: Non-functional
Requirement; O: Operating environment; P: Performance,Perspective,Purpose; R: Requirement, Requirement
attributes;S: Safety,Scope, Security, Systemfeatures;U: User, Userclassandcharacteristics,User requirement;
3. Glossary
Thefollowing arethelist of conventionsandacronyms usedin this documentandtheproject aswell:
Administrator:A login id representingauserwith useradministrationprivileges to thesoftware
User:A generallogin id assignedto mostusers
Client: Intendedusersfor thesoftware
SQL: Structured QueryLanguage;usedto retrieve informationfrom adatabase
SQL Server:A serverusedto storedatain anorganizedformat
Layer:Representsasection of the project
User InterfaceLayer:The section of theassignment referringto what theuserinteracts with directly
Application Logic Layer:The section of theassignment referringto [Link] whereall
computationsare completed
DataStorageLayer:The section of theassignment referringto whereall datais recorded
Use Case:A broadlevel diagramof theproject showingabasic overview
Class diagram: It is atype of static structure diagramthatdescribes the structure of asystemby showing the
system’s cases,theirattributes,andtherelationshipsbetweenthe classes
Interface:Somethingusedtocommunicate acrossdifferent mediums
UniqueKey: Usedtodifferentiateentriesin adatabase
4. ClassDiagram
A classis anabstract,user-defineddescriptionof atypeof [Link] identifiestheattributesof the dataandtheoperations
thatcanbeperformedoninstances(i.e. objects)of thedata.A classof datahasaname,asetof attributesthatdescribes
its characteristics, andasetof operationsthat canbeperformedon theobjectsof thatclass. Theclasses’structureand
theirrelationshipsto each otherfrozenin time represent thestaticmodel. In this project therearecertain main classes
Shambhunath institute of engineering and technology
which are related to other classes required for their working. There are different kinds of relationships between the
classes as shown in the diagram like normal association, aggregation, and generalization. The relationships are
depictedusing arole nameandmultiplicities. Here ‘Librarian’, ‘Member’and‘Books’ arethe most important classes
which arerelatedtoother classes.
Department of Information Technology