Srs Library Management System PDF
Srs Library Management System PDF
Srs Library Management System PDF
Specification
For
Table of Contents
1. Introduction................................................................................................................................1
1.1 Purpose ......................................................................................................................................... ....1
1.2 Document Conventions.................................................................................................... .................1
1.3 Intended Audience and Reading Suggestions............................................................................ ........2
1.4 Project Scope.......................................................................................................... ..........................3
1.5 References............................................................................................................................. ............4
2. Overall Description....................................................................................................................4
2.1 Product Perspective............................................................................................................ ...............4
2.2 Product Features.................................................................................................... ...........................5
2.3 User Classes and Characteristics..................................................................................................... ..6
2.4 Operating Environment............................................................................................................. ........6
2.5 Design and Implementation Constraints...................................................................... .....................6
2.6 User Documentation...................................................................................................... ...................6
2.7 Assumptions and Dependencies.................................................................................................... ....7
7
3. System Features ........................................................................................................................7
3.1. Database – Storage ................................................................................................................7
3.2. Functional Requirements...................................................................................... ..........................8
3.2.1 Interface Requirements.............................................................................................................. ..8
4.Non Functional Requirements..................................................................................................9
4.1. User Interfaces.............................................................................................................................. .9
4.4. Communications Interfaces................................................................................................ .........10
5.Other Nonfunctional Requirements.......................................................................................10
5.1Performance Requirements...................................................................................................11
5.2Safety Requirements................................................................................................................... .....11
5.3Security Requirements............................................................................................ ........................11
5.4Hardware Constraints....................................................................................................... ...............11
5.5 Software Constraints............................................................................................... ......................11
5.6Design Constraints.......................................................................................................... ................12
6.Other Requirements.................................................................................................................12
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for library management system
Page 1
1.Introduction
1.1Purpose
1.2Document Conventions
The following are the list of conventions and acronyms used in this
document and the project as well:
Administrator: A login id representing a user with user administration
privileges to the software
User: A general login id assigned to most users
Client: Intended users for the software
SQL: Structured Query Language; used to retrieve information from
a database
SQL Server: A server used to store data in an organized format
ASP: Active Server Pages: A Web Page formatted on the server and
delivered to the browser.
Layer: Represents a section of the project
User Interface Layer: The section of the assignment referring to
what the user interacts with directly.
Software Requirements Specification for library management system
Page 2
1.3Intended Audience and Reading Suggestions
1.4Project Scope
within allotted dead line and also within the budget allotted. It is
little more than planned, the firm will still view it as a success if it has
management organization
1.5References
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document. Provide enough information so that the reader could
access a copy of each reference, including title, author, version number, date, and source or
location.>
2.Overall Description
2.1Product Perspective
2.2Product Features
There are two different users who will be using this product:
Librarian who will be acting as the administrator
Student of the University who will be accessing the Library online.
2.3User Classes and Characteristics
There are various kinds of users for the product. Usually web products
are visited by various users for different reasons.
2.4Operating Environment
2.5Design and Implementation Constraints
2.6User Documentation
The product will include user manual. The user manual will include product
overview, complete configuration of the used software (such as SQL server),
technical details, backup procedure and contact information which will include
email address. There will be no online help for the product at this moment. The
product will be compatible with the Internet Explorer 6.0 or higher. The
databases will be created in the Microsoft SQL server 2000
Software Requirements Specification for library management system
Page 7
2.7Assumptions and Dependencies
3. System Features
3.1. Database – Storage
13.1.1. Description and Priority
Proposed Database is intended to store, retrieve, update, and
manipulate information related to university which include
Books availability
Staff information
Student details
My Account
Calculation of fines
able to modify, view, add, deleting and all other functions that
can be performed on the database.
This section gives the list of Functional and non functional requirements
which are applicable to the Library Management System.
This section describes how the software interfaces with other software
products or users for input or output.
3.2.1.1UserInterfaces
Describes how this product interfaces with the user.
GUI
Describes the graphical user interface if present. This section should
include a set of screen dumps or mockups to illustrate user interface
features.
1. Description
The user interface must be customizable by the administrator
2. Criticality
This issue is essential to the overall system. All the modules
provided with the software must fit into this graphical user
interface and accomplish to the standard defined.
3. Technicalissues
In order to satisfy this requirement the design should be simple
and all the different interfaces should follow a standard template.
There will be the possibility of changing colors and images, plus
Software Requirements Specification for library management system
Page 9
4. Risks
To reduce the circumstances under which this requirement might
not able to be satisfied, all the designers must have been
developed web sites previously and they must be aware of html
restriction and cross browsers implementations before starting the
designing. In order to reduce the probability of this occurrence the
entire design team will be trained in basic html development and
macromedia fireworks, this tool will be used instead of Photoshop.
Server Side:
Software Requirements Specification for library management system
Page 10
Client side:
5.Other Nonfunctional Requirements
Software Requirements Specification for library management system
Page 11
5.1Performance Requirements
The proposed system that we are going to develop will be used as the Chief
performance system within the different campuses of the university which
interact with the university staff and students. Therefore, it is expected that
the database would perform functionally all the requirements that are
specified by the university.
5.2Safety 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
5.3Security 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.
Software Quality Attributes
The Quality of the database is maintained in such a way so that it can be very
user friendly to all the users of the database
5.4Hardware Constraints
The system requires a database in order to store persistent data. The
database should have backup capabilities.
5.6Design Constraints
The system must be designed to allow web usability. That is, the
system must
be designed in such a way that will be easy to use and visible on most
of the browsers.
6.Other Requirements
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Appendix C: Issues List
< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>