0% found this document useful (0 votes)
15 views7 pages

Practical No-2 SE

Uploaded by

Bishal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views7 pages

Practical No-2 SE

Uploaded by

Bishal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Experiment No.

Aim: - Development of SRS document, Design document for the selected


project.

Software Requirements Specification (SRS)

Library Management System (LMS)

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:-

The purpose of this application is as follows:

• The software is for automation of library.

• It provides following facilities to

Operator:

• Can enter details related to a particular book.

• Can provide membership to members.

Admin:

1
• Can read and write information about any member.

• Can update,create, and delete the record of membership as per


requirement and implementation plants.

2.) Scope:

The different areas where we can use this application are :

• 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.

3.) Technology Used:

Front End: Java, Netbeans.

Back End: MS Access, SQL.

4.) Assumptions

• This application is used to convert the manual application to the online application.

• Customized data will be used in this application.

• User does not have right to enter information about books.

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.

• Keeps the track of issues and submission of books.

2
Functional Requirements:

• In this system there is lots of functioning.

• The user 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 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.

Other Nonfunctional Requirements

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

The performance of the functions and every module must be well.


• At every step the output of the one phase is the input of the other phase and it will be
reliable and accurate.
• The risk factor must be taken at initial step for better performance of the software.
• For individual function the performance will be well.
• For login to the software password and user name will be matched 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.
• This software will be well supported to the other embedded software such as digitaldairy,
notepad etc.
• The overall performance of the software will reliable and enable the users to work
efficiently.
SecurityRequirements
• There will be proper security regarding to the accessing of data.
• The external security can be provided by given the login authentication.
• The data that are stored in the database must be private.
• There is also required a user authentication.
• There is also the facility that the admin can lock his private data that will not be accessed
by anyone.
• The whole software is secure from the outside accessing.
SoftwareQualityAttributes
• Our software has many quality attribute that are given below-

Adaptability
• This software is adaptable by any organization.
Availability-
• The availability of the software is easy and for everyone.
Correctness-

www.ahirlabs.com 6

The results of the function are pure and accurate.


Flexibility-
• The operation may be flexible and reports can be presented in many ways.
Maintainability-
• After the deployment of the project if any error occurs then it can be easily maintain by
the software developer.
Portability-
• The software can be deployed at any machine.
Reliability-
• The performance of the software is better which will increase the reliability of the
software. Reusability-
• The data and record that are saved in the database can be reused if needed. Robustness-
• If there is any error in any window or module then it does not effect the remaining part of
the software.
Testability-
• The software will be tested at every. Alpha Testing Beta Testing Acceptance Testing
Usability-
 To perform any operations and to understand the functioning of software is very easy.
Productivity-
• This software will produce every desired result with accurately.
Timelines-
• The time limit is very important. It will save much time and provide fast
accessing. Costeffective-
• This software is less in cost and bearable by any  Organization.

www.ahirlabs.com 7

You might also like