Practical No-2 SE
Practical No-2 SE
1. Introduction:-
The purpose of Software Requirements Specification (SRS) document is to describe the external
behavior of the Online Library System. Requirements Specification defines and describes the
operations, interfaces, performance, and quality assurance requirements of the Online Library
System. The document also describes the nonfunctional requirements such as the user interfaces.
It also describes the design constraints that are to be considered when the system is to be
designed, and other factors necessary to provide complete and comprehensive description of the
requirements for the software. The Software Requirements Specification (SRS) captures the
complete software requirements for the system, or a portion of the system. Requirements
described in this document are derived from the Vision Document prepared for the Online
Library System
1.1 Purpose:-
Operator:
Admin:
1
• Can read and write information about any member.
2.) Scope:
• Any education institute can make use of it for providing information about author, content of
the available books.
• It can be used in offices and modifications can be easily done according to requirements.
4.) Assumptions
• This application is used to convert the manual application to the online application.
5.) Overview:
Project is related to library management which provides reading services to its members. Any
person can become a member of the library by filling a prescribed form.They can get the book
issued, so that they cab take home and return them.
6.) Functionality:
• Online membership.
2
Functional Requirements:
• The user can Search book and see his/her account information.
• There will also be a reminder and digital diary through this he can go to know aboutits
important date like his book submission date.
• Admin can add new record and saw all record of any student as well as library.
ModuleDescription
Type of user:
• Administrator(librarian)
• HODofallDepartment
• Student
• Faculty
• Staff
Administrator module:
• Budget(foralldepartment)
• Stockverification
• Createuser
• Accept/Rejectuser
• Changepassword
• Bookinventory
• Userinformation
• Reportgeneration
• SearchBook
Complaint
•
3
Allusercansendtheircomplaint
User module
• Changepassword
• BookSearch
• Seeaccountinformation
Fine information
• Alluserchecktheirfine
• Finebydate&Month
Book inventory
• Purchasingbookinformation
• Maintainbookinventory
Book search
• Normalsearchbyalphabet
• Quicksearchbytype(Bookid,Author,ISBN,Publication) Other charges
• BookBinding,chair,Rack
• Journals
• Newspaper
External Interface Requirements
User Interfaces
• The design or layout of every form will be very clear and very interactive to the user.
• When the user open the software the welcome window will appear.
• In the login window the user can easily entered the desired password and login name.
• Then it will give the successfully login message.
• From each and every window the user can easily go to any desired window that is there is
will be a absolute and relative linking.
• In every window & Mac there is help and support option is present for the ease of user.
• There will be a proper collection of GUI interface, which will provide better look and
feel.
www.ahirlabs.com 4
In the screen layout the background color is very light and the graphics and font style will
be in proper manner and well organized.
• If the user will print any error statement then it will give the proper error message display.
• In each and every window there will be alert, confirm etc message box for displaying
message.
• The user will be able to search any data from the record by using proper guideline shown
in the window & Mac.
• In the opening of the software there will be a menu window where the overall table
contents of the software will be present through which the user can move to any desired
window &Mac.
• This will provide the better security data because the menu window will be displaying
according to the login (admin or normal user).
• User can easily save its data in to the database and keep track of the records of purchase,
vendor and inventory etc.
• This software will be easily understandable and operable by the user.
HardwareInterfaces
• The existing Local Area Network (LAN) will be used for collecting data from the users
and also for updating the Library Catalogue.
SoftwareInterfaces
• A firewall will be used with the server to prevent unauthorized access to the system.
CommunicationsInterfaces
• The Online Library System will be connected to the World Wide Web.
PerformanceRequirements
• This software is not 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 software must be in our mind.
www.ahirlabs.com 5
Adaptability
• This software is adaptable by any organization.
Availability-
• The availability of the software is easy and for everyone.
Correctness-
www.ahirlabs.com 6
www.ahirlabs.com 7