Professional Documents
Culture Documents
System
Software Requirements Specification
Version 1.0
Supervisor Name:
Revision History
Date Version Description Author
(dd/mm/yyyy)
23-Oct-2009 1.0 Library Management System Mc060401541
23-NOV-2009 2 Library Management System MC060401541
30-DEC-209 3 Library Management System MC060401541
PURPOSE ........................................................................................................................................................4
INTENDED AUDIENCE .......................................................................................................................................4
PROJECT SCOPE................................................................................................................................................4
FUNCTIONAL/NONE FUNCTION REQUIREMENTS.....................................................................................................6
FUNCTION REQUIREMENT...................................................................................................................................6
THE LIBRARIAN...............................................................................................................................................6
MEMBER................................................................................................................................................6
Asst. Librarian........................................................................................................................................7
Guest.......................................................................................................................................................7
NONE FUNCTIONAL REQUIREMENT...................................................................................................................7
Safety Requirements................................................................................................................................7
Security Requirements............................................................................................................................7
Software Quality Attributes....................................................................................................................7
Hardware Constraints............................................................................................................................7
Software Constraints..............................................................................................................................7
Hardware Interfaces...............................................................................................................................7
Software interfaces.................................................................................................................................8
ACTORS..................................................................................................................................................8
LIBRARIAN DATABASE........................................................................................................................8
MEMBER................................................................................................................................................8
GUEST....................................................................................................................................................8
USER CASE DIAGRAM MAIN VIEW....................................................................................................................9
USAGE SCENARIOS.........................................................................................................................................10
Login.....................................................................................................................................................10
Search Article......................................................................................................................................10
Request Article......................................................................................................................................11
Check Account.....................................................................................................................................11
Maintain inventory...............................................................................................................................12
Manage Member Permission...............................................................................................................12
Manage Article Permission.................................................................................................................13
Inquiry Issuance...................................................................................................................................13
Inquiry Article......................................................................................................................................14
Inquiry members..................................................................................................................................15
Check In Article...................................................................................................................................15
Check Out Article................................................................................................................................16
Inquiry waiting for approvals..............................................................................................................16
Issue Member Ship...............................................................................................................................17
Request registration..............................................................................................................................17
Purpose
This document describes the software requirements and specification (SRS) for LMS
software. The document is intended for the customer and the developer (designers, testers
, maintainers).
The reader is assumed to have basic knowledge of LMS.
Knowledge and understanding of Unified Modeling Language (UML) diagrams is also re
quired.
Intended Audience
The intended audience consists of
• Software Project Managers
• Software Engineers
• Software Developers
• Library Organizers
Project Scope
LMS is essentially meant of collections. It is a multi-user version and can take care of all
the fundamental functions of a Library like Cataloguing, Circulation, Accessioning and
Housekeeping. It can satisfactorily cater to all the basic functions of a small library.
Overall Description
Modern Libraries are not made up of just Books but CD ROM’s, Articles, Project
Reports, Bound volumes are substantial part of the holding, Managing the holdings
manually is a not a simple job. There are few solutions but many a times, we find
ourselves "making them works" by finding "ways to work around" system inadequacies.
Moreover we have limited staff resources, these "work around" waste time, effort, and
skills that should be spent on user services.
Many solutions do not keep up with the technological changes and hence prove to be
time wasters.
Circulation
Circulation module deals with issue and return of material from the Library. It is a
barcode and smart card enabled system and hence the issue and return of
material is handled uniformly. You can issue member cards and also do the transactions.
Functional/None Function Requirements
This section gives the list of Functional and non functional
requirements that are applicable to the Library Management system
Function Requirement
The Librarian
1. Add Article
New entries must be entered in database
2. Update Article
Any changes in articles should be updated in case of update
3. Delete Article
Wrong entry must be removed from system
4. Inquiry Members
Inquiry all current enrolled members to view their details
5. Inquiry Issuance
Inquiry all database articles
6. Check out Article
To issue any article must be checked out
7. Check In article
After receiving any article system will reenter article by Checking
8. Inquiry waiting for approvals
Librarian will generates all newly application which is in waiting list
9. Reserve Article
This use case is used to reserve any book with the name of librarian, it can be
pledged
10. Set user Permission
From this user case Librarian can give permission categorically, also
enabling/disabling of user permission can be set through this use case
MEMBER
1. Authentication
User must authenticated before accessing system
2. Search Article
User can search any article
3. Request Article
After successful searching member mark this book as requested article
4. Check Account
This use case is used to check account details
Asst. Librarian
Prepare Library database
All data base must be prepared
Guest
1. Register user
User must full fill all application form for registration
Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup
Security Requirements
We are going to develop a secured database for the university .There are different
categories of users namely teaching staff, administrator, library staff ,students etc.,
Depending upon the category of user the access rights are decided. It means if the user is
an administrator then he can be able to modify the data, delete, append etc., all other
users other than library staff only have the rights to retrieve the information about
database.
Hardware Constraints
The system requires a database in order to store persistent data. The database should have
backup capabilities.
Software Constraints
The development of the system will be constrained by the availability of required
software such as database and development tools.
The availability of these tools will be governed by
Hardware Interfaces
Server
Operating System: Windows
Processor: Pentium 4.0 GHz or higher
RAM: 1GB Mb or more
Hard Drive: 80 GB or more
Client
Operating System: Windows.
Processor: Pentium III or 2.0 GHz or higher.
RAM: 512 Mb or more
Software interfaces
Oracle database 8i or 10g
Developer 2000
USECASE Actors
• Librarian
• Member
• Guest
• Asst. Librarian
ACTORS
The actors which are participating in the case are 4 namely
LIBRARIAN
The one who manages the library and its database and rapidly keeps on updating the
students or people records for issuing books and etc.
LIBRARIAN DATABASE
You can say this as an assistant librarian.
MEMBER
Library has registered members who is authorized to issue articles from library
GUEST
A guest who doesn’t have the membership of the library comes to it and wants to have
membership.
User Case Diagram Main View
14.request
1.Login
registration
12.Approve user
Registration
Asst.Librarian 5.Maintain
Guest
Inventory
«uses»
6 Manange Member
Permission
13. Issue
MemberShip
7 Manage Articles 4.CheckAccount
Permission
8. Inquiry Member
Issuances
2.Search Article
9.Inquiry Articles
«extends»
10. Inquiry Members
Librarian
11 Check In Article
«extends»
12. Check out 3. Request Article
article
Usage Scenarios