Software Requirements Specifications Document

Software Requirements Specification (SRS) For Billing System

(Firoj Patel)

Software Requirements Specification

Document

Version: (1.0) Date: (01/jan/2011)

f
 Software Requirements Specifications Document

Table of Contents

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview

2. The Overall Description

2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirement

3. Specific Requirements
3.1 External interfaces
3.2 Functions
3.3 Performance Requirements
3.4 Logical Database Requirements
3.5 Design Constraints
3.5.1 Standards Compliance
3.6 Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing the Specific Requirements
3.7.1 System Mode

f
 Software Requirements Specifications Document

3.7.2 User Class

3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3.7.6 Response
3.7.7 Functional Hierarchy
3.8 Additional Comments

4. Change Management Process

5. Document Approvals

6. Supporting Information

f
 Software Requirements Specifications Document

1. Introduction
1.1 Purpose
An application to automate the ordering and billing processes for a "Departmental store"
is the "Billing system" project. This web-based application was created with the chain of
department stores in several cities in mind. Additionally, this programme manages its customers'
and users' accounts.
The BILLING MANAGEMENT SYSTEM (BMS) 1.0 product's software requirement
specifications are contained in this document. The purpose of this paper is to outline the
specifications for BMS 1.0 as a Stand-Alone System, which manages sales and purchases
for a single-location retail operation. The Business working is as follows.
1.2 Scope

(1) The programme is made to keep track of data pertaining to the Store,
(2) Specifics about the customer.
(3) details about the merchandise and the product.
(4) Stock-specific information.
(5) Specific sales information.
(6) Bill Generation
1.3 Definitions, Acronyms, and Abbreviations.

1.4 References
www.google.com
1.5 Overview

2. The Overall Description

2.1 Product Perspective

Since the former method was manual and required a lot of paper labour, it was
challenging to maintain track of all previous sales, product orders, and stock levels. The
system will have the benefit of keeping track of all sales and inventory at any given
moment, which will eliminate paper work and the errors that result from it.
2.1.1 System Interfaces

2.1.2 Interfaces

f
 Software Requirements Specifications Document

2.1.3 Hardware Interfaces

Processor Pentium 500 MHz

RAM 128 MB or More
Hard Drive 20 MB Disk Drive
Space(Available)

2.1.4 Software Interfaces

Database MS-Acces
API JAVA JDK 1.6
Other Tool And Java (JDK), Swings
Technology
2.1.5 Communications Interfaces

2.1.6 Memory Constraints

2.1.7 Operations

2.1.8 Site Adaptation Requirements

2.2 Product Functions

2.3 User Characteristics

2.4 Constraints

2.5 Assumptions and Dependencies

2.6 Apportioning of Requirements.

3. Specific Requirements

3.1 External Interfaces

f
 Software Requirements Specifications Document

3.2 Functions

 Whenever appropriate, user-friendly error messages are presented.

 Record addition, deletion, and alteration as necessary.
 The creation of consumer bills.
 Consistent user interface with highly practical features.
3.3 Performance Requirements

3.4 Logical Database Requirements

3.5 Design Constraints

3.5.1 Standards Compliance

3.6 Software System Attributes

3.6.1 Reliability

3.6.2 Availability

3.6.3 Security

3.6.4 Maintainability

3.6.5 Portability

3.7 Organizing the Specific Requirements

f
 Software Requirements Specifications Document

3.7.1 System Mode

3.7.2 User Class

3.7.3 Objects

3.7.4 Feature

The application will make it much easier to maintain purchases in an organised

manner. The benefit of a new system would be that work could be done much more
quickly and accurately because the current method entails a lot of paper work, which
takes time and is also prone to error. The information for the shop and its products
will also be readily available.
3.7.5 Stimulus

3. 7.6 Response

3.7.7 Functional Hierarchy

3.8 Additional Comments

4. Change Management Process

5. Document Approvals

6. Supporting Information