Software Requirements Specifications Document

Software Requirements Specifications Document
4CS09
Software Requirements Specification (SRS) Template
Items that are intended to stay in as part of your document are in bold;
explanatory comments are in italic text. Plain text is used where you might
insert wording about your project.
The document in this file is an annotated outline for specifying software

requirements, adapted from the IEEE Guide to Software Requirements
Specifications (Std 830-1993).
Tailor this to your needs, removing explanatory comments as you go along.

Where you decide to omit a section, you might keep the header, but insert a
comment saying why you omit the data.
/opt/scribd/conversion/tmp/scratch9051/59497780.doc Page 1 of 12
05/30/11f
4CS09
(SHG3.4)
(Team Name)
Gaurav gupta
Gaurav sharma
Gajanand sharma
Software Requirements Specification
Stock Maintenance
Version: (1.0) Date: (23/03/2011)
05/30/11f
Table of Contents
Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations. 4
1.4 References 4
1.5 Overview 4
2. The Overall Description 5
2.1 Product Perspective 5

2.1.1 System Interfaces 6
2.1.2 Hardware Interfaces 6
2.1.3 Software Interfaces 7
2.2 Product Functions 7
2.3 User Characteristics 7
2.4 Constraints 7
2.5 Assumptions and Dependencies 8
3. Specific Requirements 8
3.1 External Interfaces 8

3.2 Software System Attributes 8
3.2.1 Reliability 8
3.2.2 Availability 8
3.2.3 Security 9
3.2.4 Maintainability 9
3.3 Organizing the Specific Requirements 9
9
3.3.1 System Mode 9
9
3.3.2 Objects 9
3.3.3 Feature 10
Document Approvals 10
05/30/11f
Introduction
1.1 Purpose
Stock maintenance is a system which is control and manage of
stock in any organization. it will explain the purpose and feature of
system, the interfaces of the system, what the system will do, the constraints
under which it must operate and how the system will react to external
stimuli. This document is intended for both the stakeholders and the
developers of the system.the system provide the following facilities.
1. Information about profit and loss of organization for particular product.
2. Information about vendor.
3. Selling information,buying information and reorder information about
Products.
1.2 Scope
1. Team member must be have a valid id and password.
2. If password is not valid then give the instruction that your id is locked.
3. search product and sale products.
4. Reserve order and cancel order.
5. Purchage product.
1.3 Definitions, Acronyms, and Abbreviations.

1. Id identification number
1.4 References
1. Books – Roger S. Pressman software Engineering

2. Site -- http:// www.wikipedia.org
1.5 Overview
Stock maintenance is a system which is control and manage of stock in any
organization . the system provide the following facilities.
1. Information about profit and loss of organization for particular product.
2. Information about vendor.
3. Selling information,buying information and reorder information about
05/30/11f
Products.
4.search product and sale products.
5.Reserve order and cancel order.
6. Purchage product.
2. The Overall Description
Describe the general factors that affect the product and its requirements.
This section does not state specific requirements. Instead, it provides a
background for those requirements.
2.1 Product Perspective
Stock maintenance is a system which is control and manage of
stock in any organization Information about profit and loss of organization
for particular product and all Information about vendor and Selling
information, buying information and reorder information about Products.
The complete overview of the system is as shown in the overview

diagram below:
The product to be developed has interactions with the users,
admin , staff who are do work of the organization.
The product has to interact with other systems like: not with
internet with intranet only .
Administrator Stock
information
05/30/11f
Stock maintenance
Proposed system
Usersss Interanet
2.1.1 System Interfaces

Mention only pages names
1. System need a id and password of user which provide security for

system.
2. search to the product for particular code no.
3. The System need to the type of user means tell which type of user is
use (staff , worker, adminstrater)
4. issue the product according the choice of users.
2.1.2 Hardware Interfaces

Hardisk 1 gb
Ram 250 mb
05/30/11f
Processor p4
2.1.3 Software Interfaces
1. A firewall will be used with the server to prevent unauthorized access

to the system
Frontend ASP.net with c#
Backened Sql sever
Tools Rational rose (IBM tool), ms word
Operating system (XP, window 7 or higher version )
2.2 Product Functions
2.2.1 Admin : explain all task of admin

It control the all system and maintan the all information
up to date for particular product .admin is work as a controller for all
systems.
It update time to time cost of product ,how much stocks are available for
products in organization .
2.2.2 Users : explain all task of users what he can do ?

The system uses security requirements to provide the login
facility to the users.users is use all information about products.users is use list of
items which is available .
2.3 User Characteristics

The users of the system are members of the organisation and the
administrators who maintain the system. The members are assumed to
have basic knowledge of the computers and Internet browsing. The
administrators of the system to have more knowledge of the internals of the
system and is able to rectify the small problems that may arise due to disk
crashes, power failures and other catastrophes to maintain the system. The
proper user interface, users manual, online help and the guide to install and
maintain the system must be sufficient to educate the users on how to use
the system without any problems .
2.4 Constraints
05/30/11f
Provide a general description of any other items that will limit the
developer's options. These can include:
1. The users must have their correct usernames and passwords to enter
into the pay roll managment System
2. Software limitations only work in xp and windows 7 not in 98 ,vista
and linux .
3. It is control only by administrator.
6. Reliability requirements
8. Safety and security considerations
2.5 Assumptions and Dependencies

1. The users have sufficient knowledge of computers.
2. The computer should have lan facility
3. The users know the English language, as the user interface will be
provided in English
3. Specific Requirements
3.1 External Interfaces

Include pages of yr project like login page for admin , staff
Product category pages
Product detail page
Orde page
Etc ok
Description of these pages in the form of table like
Name control description
3.2 Software System Attributes

3.2.1 Reliability
The system has to be very reliable due to the importance of data

and the damages incorrect or incomplete data can do.
3.2.2 Availability
05/30/11f
The system is available 100% for the user and is used 24

hrs a day and 365 days a year. The system shall be operational 24
hours a day and 7 days a week..
3.2.3 Security
Specify the factors that would protect the software from

accidental or malicious access, use, modification, destruction, or disclosure.
Specific requirements in this area could include the need to:
1. Utilize certain cryptographic techniques
2.Keep specific log or history data sets
3.Assign certain functions to different modules
4.Restrict communications between some areas of the program
5.Check data integrity for critical variables
3.2.4 Maintainability
Specify attributes of software that relate to the ease of

maintenance of the software itself. There may be some requirement for
certain modularity, interfaces, complexity, etc. Requirements should not be
placed here just because they are thought to be good design practices. If
someone else will maintain the system
3.3 Organizing the Specific Requirements
3.3.1 System Mode

1. product :
When the user choose this mode then system open and ask the
product quality like product compny , colors and range of price.
2. Administator :
It control the all system and maintan the all information up to
date for particular product .
3.3.2 Objects
1. Administrator
2. Team members
05/30/11f
3.3.3 Feature
1. Multilevel reports.
2. Feed back from users for the organization.
3. Information of the organigation level scheme
Document Approvals
Identify the approvers of the SRS document. Approver name, signature, and
date should be used.
05/30/11f
05/30/11f
05/30/11f

Software Requirements Specifications Document

Uploaded by

Copyright:

Available Formats

Software Requirements Specifications Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specifications Document

Uploaded by

Copyright:

Available Formats

Software Requirements Specifications Document

Software Requirements Specification (SRS) Template

The document in this file is an annotated outline for specifying software

Tailor this to your needs, removing explanatory comments as you go along.

Software Requirements Specification

Version: (1.0) Date: (23/03/2011)

2. The Overall Description 5

2.1 Product Perspective 5

3.1 External Interfaces 8

1.3 Definitions, Acronyms, and Abbreviations.

1. Books – Roger S. Pressman software Engineering

2. The Overall Description

The complete overview of the system is as shown in the overview

2.1.1 System Interfaces

1. System need a id and password of user which provide security for

4. issue the product according the choice of users.

2.1.2 Hardware Interfaces

2.1.3 Software Interfaces

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

2.2 Product Functions

2.2.1 Admin : explain all task of admin

2.2.2 Users : explain all task of users what he can do ?

2.3 User Characteristics

2.5 Assumptions and Dependencies

3.1 External Interfaces

3.2 Software System Attributes

The system has to be very reliable due to the importance of data

The system is available 100% for the user and is used 24

Specify the factors that would protect the software from

Specify attributes of software that relate to the ease of

3.3 Organizing the Specific Requirements

3.3.1 System Mode

You might also like