Software Requirements

Specification
for

<Name of the Project>

Version 1.0 approved

Prepared by <name of the person>

<Name of the college and department>

<Date>
SRS for Web Based Address Book Page ii

Table of Contents

Introduction...................................................................................................................................1
Purpose
................................................................................................................................................................... 1
The purpose of Software Requirements Specification (SRS) document is to describe
the external behavior of the Web based address Book system. Requirements Specification defines and
describes the operations, interfaces, performance, and quality assurance requirements of the Web
based address Book 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 a complete and comprehensive description of the
requirements for the software. The Software Requirements Specification (SRS) captures the complete
software requirements for the system....................................................................................................... 1
Document Conventions............................................................................................................................ 1
Intended Audience and Reading Suggestions.......................................................................................... 2
Project Scope............................................................................................................................................ 3
References................................................................................................................................................ 4
Overall Description....................................................................................4
Product Perspective.................................................................................................................................. 4
Product Features....................................................................................................................................... 4
User Classes and Characteristics............................................................................................................. 5
The information of all the users must be stored in a database that is accessible by the
Web based address Book system. The Web based address Book system is running all 24 hours a day.
The users access the Web based address Book system from any computer that has Internet browsing
capabilities and an Internet connection. The users must have their correct usernames and passwords to
enter into the system................................................................................................................................. 6
System Features............................................................................................................................ 6
Module Description.......................................................................................................................7
External Interface Requirements................................................................................................ 7
User Interfaces.............................................................................................................................. 7
Hardware Interfaces................................................................................................................................. 8
Software Interfaces.................................................................................................................................. 8
Communications Interfaces...................................................................................................................... 8
Other Nonfunctional Requirements............................................................................................8
Performance Requirements...................................................................................................................... 8
Security Requirements............................................................................................................................. 9
Software Quality Attributes..................................................................................................................... 9

Revision History

Date Version Description Author

SRS for Web Based Address Book Page iii
SRS on Web Based Address Book
Other Nonfunctional Requirements1

Introduction

Purpose

The purpose of Software Requirements Specification (SRS) document is

to describe the external behavior of the Web based address Book system. Requirements
Specification defines and describes the operations, interfaces, performance, and quality
assurance requirements of the Web based address Book 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 a complete and comprehensive description of the requirements for the
software. The Software Requirements Specification (SRS) captures the complete software
requirements for the system.

Document Conventions

Font Style Size

Heading Times New Roman Bold 18

Sub-Heading Times New Roman Bold 14

Other’s Arial Regular 12

SRS on Web Based Address Book
Other Nonfunctional Requirements2

Intended Audience and Reading Suggestions

We are developing our project Web based address Book system for the users.
But this project can be deployed in any organization. This SRS is mainly developed for the
project development team. In this team there are the project manager, developer, coder, tester
and documentation writer and the user of the project also.

User (Customer)

This document is intended to user and customer to make them ensure that this
document is well meeting the need of the users.

Project Manager

This SRS document is also very important for the project manager to ensure that
can estimate the cost easily by referring to the SRS document and that it contains all the
information require planning the project.

Project Developer

The project developer will refer to the SRS document to make sure that they developed
exactly what the customer requires.

Tester

The tester will read this SRS document and he will ensure that the requirements
are understandable from functionality point of view so that he can test the software and
validate its working.
SRS on Web Based Address Book
Other Nonfunctional Requirements3

Document Writer

The document writer is reading the SRS document is to ensure that they
understand the document well enough to be able to write the users manuals.

Maintenance

The SRS document helps the maintenance engineers to understand functionality

of the system, a clear knowledge of the functionality can help them to understand design and
code.

• Suggestions

1. The user can read the whole SRS document but for him Introduction, Overall
description and System features is much required the software performance.
2. For the project manager the system features is very important.
3. The developer must go through the whole SRS for understanding the
requirement and functioning of software.
4. The designer and coder must see the class and object diagram and state
transmission diagram for coding the modules.
5. A tester must be aware of coding language and visit through the code section
and check the required output.
6. The document writer should write the qualitative document so that it becomes
easy and understand to every one.

Project Scope

The Software Requirements Specification captures all the requirements in a single

document. The Web based address Book system that is to be developed provides
SRS on Web Based Address Book
Other Nonfunctional Requirements4

convenience to manage their contacts. The Web based address Book system is supposed
to have the following features.
1. User can access his/her account.
2. He/She can insert, delete, update contacts.
3. Data of user must remain secure from unauthorized use.

The features that are described in this document are used in the future phases of the software
development cycle. The features described here meet the needs of all the users. The success
criteria for the system is based in the level up to which the features described in this
document are implemented in the system.

References

Web Address
(a). www.google.com

Overall Description

Product Perspective

The Web based address Book system is a package to be used by users to

manage their contacts.The system provides insert , edit ,delete , search facilities. The user is
provided a login id and password so his information can be secure.

Product Features

The Web based address Book system is management of information about the
contacts given by user. The Product functions are more or less the same as described in the
product perspective. The functions of the system include the system providing different type
of services based on the type of users[DBA/USER].
SRS on Web Based Address Book
Other Nonfunctional Requirements5

User Classes and Characteristics

The users of the system are users and DBA who maintain the system. The
users are assumed to have basic knowledge of the computers and Internet browsing.The
proper user interface, users manual, help of system must be sufficient to educate the users on
how to use the system without any problems.

Operating Environment

Software Requirement

Operating System -: Window XP,Linux

Database -: MySQL
Language -: PHP 5.0
Web Server -: Apache

Hardware Requirement

512 MB RAM, Pentium P3/P4, 20/40 GB Hard disk

SRS on Web Based Address Book
Other Nonfunctional Requirements6

Design and Implementation Constraints

The information of all the users must be stored in a database that is accessible
by the Web based address Book system. The Web based address Book system is running all
24 hours a day. The users access the Web based address Book system from any computer
that has Internet browsing capabilities and an Internet connection. The users must have their
correct usernames and passwords to enter into the system.

Assumptions and Dependencies

The users have sufficient knowledge of computers. The institute computer

should have Internet connection and Internet server capabilities. The users know the English
language, as the user interface will be provided in English.

System Features

Descriptions and Priority

1. First priority goes to the welcome form. when user will login the system there will be
welcome screen which will assure to the use either ha wants to enter or exit.
2. After the welcome form there will be login form. Through this form only authenticated
users can login the system just by entering their name and password.
3. Second priority goes to the menu form where the contacts can be added,deleted and
updated. From the menu form the user can go any form of the system.

Functional Requirements
• In this system there are lots of functioning.
• The user can Search, insert, edit, delete or see his/her account information.
• He will be able to get the records in any format.
 SRS on Web Based Address Book
Other Nonfunctional Requirements7

Module Description

Type of user

• Administrator
• Users

Administrator module:

• Create user
• Delete user
• Change password
• User information

User module
• Change password
• Insert, edit, delete, search contacts
• See account information

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.
SRS on Web Based Address Book
Other Nonfunctional Requirements8

• 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.
• There will be a proper collection of GUI interface, which will provide better look and feel.
• In the screen layout the background color is very light and the graphics and font style will
be in proper manner and well organized.
• 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 & Linux.
• User can easily save its data in to the database and update as their need.
• This software will be easily understandable and operable by the user.

Hardware Interfaces

The existing Local Area Network (LAN) will be used for collecting data from the users.

Software Interfaces

A firewall will be used with the server to prevent unauthorized access to the system.

Communications Interfaces

The Web based address Book system will be connected to the World Wide Web.

Other Nonfunctional Requirements

Performance Requirements

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

SRS on Web Based Address Book
Other Nonfunctional Requirements9

• 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 formats of retrieving data.
• The overall performance of the software will reliable and enable the users to work
efficiently.

Security Requirements

• 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.
• Capcha security is also provided.
• The whole software is secure from the outside accessing.

Software Quality Attributes

Our software has many quality attribute that are given below-
Adaptability This software is adaptable by all users.
Availability- The availability of the software is easy and for everyone.
Correctness- The results of the function are pure and accurate.
Flexibility- The operation may be flexible and contacts can be accessed in many
formats.
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.
SRS on Web Based Address Book
Other Nonfunctional Requirements10

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.
Usability-To performs 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.
Cost effective-This software is less in cost and bearable by any organization.