Srs For Billing Sysetm

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
Table of Contents
1. 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 4

2.1 Product Perspective 4
2.1.1 System Interfaces 5
2.1.2 Interfaces 5
2.1.3 Hardware Interfaces 5
2.1.4 Software Interfaces 5
2.1.5 Communications Interfaces 5
2.1.6 Memory Constraints 5
2.1.7 Operations 5
2.1.8 Site Adaptation Requirements 5
2.2 Product Functions 5
2.3 User Characteristics 5
2.4 Constraints 5
2.5 Assumptions and Dependencies 5
2.6 Apportioning of Requirements. 5
3. Specific Requirements 5
3.1 External Interfaces 6
3.2 Functions 6
3.3 Performance Requirements 6
3.4 Logical Database Requirements 6
3.5 Design Constraints 6
3.5.1 Standards Compliance 6
3.6 Software System Attributes 6
3.6.1 Reliability 6
3.6.2 Availability 6
3.6.3 Security 6
3.6.4 Maintainability 6
3.6.5 Portability 6
3.7 Organizing the Specific Requirements 7
3.7.1 System Mode 7
3.7.2 User Class 7
3.7.3 Objects 7
3.7.4 Feature 7
f
3.7.5 Stimulus 7
3. 7.6 Response 7
3.7.7 Functional Hierarchy 7
3.8 Additional Comments 7
Change Management Process 7
Document Approvals 8
Supporting Information 8
f
1. Introduction
1.1 Purpose
The project “Billing system” is an application to automate the process of ordering
and billing of a “Departmental store” .This web based application is designed considering
the chain of departmental store which is located in various cities. This application also
administrates its users and customers.
This document is the 1 version of software requirement specifications for
the product BILLING MANAGEMENT SYSTEM (BMS) 1.0.The document
intends to describe the requirements for BMS 1.0.as a Stand-Alone System, which
handles purchase & Sales for a retail business having one store .
The Business working is as follows.
The Shops are those stores where every item sold . Items are Sales To
various Customer Which is Come To shop .
1.2 Scope
(1) The application is designed to maintain data related to the Store,

(2) Detail information about Customer .
(3) information about Product and the items sold in shop.
(4) Detail information about Stock .
(5) Detail information about Sales .
(6) Genration of Bill
1.3 Definitions, Acronyms, and Abbreviations.
1.4 References
www.google.com
1.5 Overview
2. The Overall Description
2.1 Product Perspective

The need for software is felt, as the earlier system is manual thus requiring
lot of paper work and making it difficult to keep track of all the previous
Sale,Product and their Stock. The system will give the advantage of keeping track
of all Sale ,Stock at any given point of time thus eliminating paper work and in turn
error caused by it
f
2.1.1 System Interfaces
2.1.2 Interfaces
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
f
3.1 External Interfaces
3.2 Functions
 User-friendly error messages are provided wherever necessary.

 Addition, deletion, modification of records as when needed.
 Bill generation for customers.
 Consistent user interface with high economic features built into it.

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
f
3.7 Organizing the Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Objects
3.7.4 Feature
The application will help the task maintaining the purchase s in a much
more organized way. Currently it involves lot of paper work thus requires time and
is also prone to error thus the benefit with a new system would be that work could
be done much faster and in a much more accurate manner. Also the Data for the
store, items will be available very easily
3.7.5 Stimulus
3. 7.6 Response
3.7.7 Functional Hierarchy
3.8 Additional Comments
Change Management Process
f
Document Approvals
Supporting Information

Srs For Billing Sysetm

Uploaded by

Copyright:

Available Formats

Srs For Billing Sysetm

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

Srs For Billing Sysetm

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What are the main sections covered in the document?

What are the main sections covered in the document?

Software Requirements Specifications Document

Software Requirements Specification (SRS) For Billing System

Software Requirements Specification

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

2. The Overall Description 4

Change Management Process 7

(1) The application is designed to maintain data related to the Store,

1.3 Definitions, Acronyms, and Abbreviations.

2. The Overall Description

2.1 Product Perspective

2.1.1 System Interfaces

Processor Pentium 500 MHz

2.1.4 Software Interfaces

2.1.6 Memory Constraints

2.1.8 Site Adaptation Requirements

2.2 Product Functions

2.3 User Characteristics

2.5 Assumptions and Dependencies

3.1 External Interfaces

 User-friendly error messages are provided wherever necessary.

3.3 Performance Requirements

3.4 Logical Database Requirements

3.5 Design Constraints

3.5.1 Standards Compliance

3.6 Software System Attributes

3.7 Organizing the Specific Requirements

3.7.1 System Mode

3.7.2 User Class

3.7.7 Functional Hierarchy

3.8 Additional Comments

Change Management Process

You might also like