Software Report Specifications (SRS) : Billing Management System

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 12

Software Report

Specifications (SRS)
For

Billing Management System

Version 1.0

Prepared by Khushbu Gupta


Jain Software
31/07/2022
Table Content
1) Introduction

2) Objective

3) Project category

4) Types of Reports

5) Technologies and tools

6) Hardware

7) Future scope

8) Analysis of Present System

9) Problem of Existing System

10) Characteristic of Proposed System

11) Feasibility Analysis

I. Need for Feasibility Study

ii. Technical Feasibility

iii. Behavioral Feasibility

iv. Economic Feasibility

v. Product Perspective

12) Data flow diagram

13) Entity Relation Diagram

14) Data tables

15) Flow chart

16) Input forms

17) Conclusion
1. Introduction

An application to automate the ordering and billing processes for a "Departmental store" is the
"Billing system". 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.

2. Objective

The following goals will be served by this system :

1. Add and maintain records of products that are currently available.


2. Add and update customer information.
3. Update and add new product descriptions.
4. Add and manage the newly added product category.
5. Provides the owner with monthly, weekly, and yearly economic and financial statistics.
6. Offers a practical billing pattern solution.
7. Create a user- and customer-friendly environment.

3. Project category
RDBMS:

The RDBMS idea is the foundation of the project (i.e. Relational Database Management
System)."A database that stores data in the form of tables that are connected to one another in
a specific way."

4. Types of reports
1. Daily Sales Report

2. Monthly Customer Report

3. Daily Product Report

4. Due Date Report (Report of a particular Day)

5. Billing Report

5. Technologies and Tools

1 Web Technology: Asp.net (Microsoft visual studio 2005 framework 2.0)

2 Database: MySQL Server-2005

3 Development Tool: MS Visual Studio 2005

4 Web Server: IIS

5 Web browser: Internet Explorer service pack 1

6 Languages Used: C#.net, JavaScript

7 Others: Themes, CSS

6. Hardware

CPU configuration

- AMD processors 4000+ series

- RAM 1 GB DDR2

Monitor

-17” color

- Operating System

-Windows XP with service pack 2


7. Future Scope

1. The storekeeper will benefit from this project's quick billing.


2. This software makes it possible for store owners to have an excellent database of every
consumer that visits and buys something there.
3. Project will make it possible to view a report on the product and category.
4. Simple to maintain in the long run.

8. ANALYSIS OF PRESENT SYSTEM

Prior to implementing a new system, it is crucial to thoroughly research the existing one (if there
is one). The process by which this system transforms data sources, such transaction data, into
information products, like reports and displays, requires analysis of how it employs hardware,
software, network, and human resource resources. Therefore, we should record the methods
used to carry out the input, processing, output, storage, and control functions of an information
system.

9. PROBLEM OF EXISTING SYSTEM

1. Inability of modification of data: Data modification is not possible in the current


system, making it difficult to manage large amounts of data effectively and efficiently for
effective results, save customer information, etc. in a database that can be changed.

2. Not user-friendly: The current system lacks usability because

Data maintenance is ineffective, with delayed data retrieval and storing.


3. Difficulty in reports generating: Reports take a long time to generate in the current
system, either because they don't generate at all or because they do so with a lot of
difficulty.

4. Manual operator control: There is manual operator control, which causes a lot of
confusion and mistakes.

5. Lot of paperwork: Existing system requires lot of paper work and even a small
transaction require many papers fill. Moreover any unnatural cause (such as fire in the
organization) can destroy all data of the organization. Loss of even a single paper led to
difficult situation because all the papers are interrelated.

6. Inability of sharing the data: The current system prohibits the sharing of data. This
implies that in the current system, no two people can use the same data. Additionally,
without the actual transfer of data, the two departments of a company cannot
communicate with one another.
7. No support in decision-making: Management decision-making is not supported by the
current system.

8. No support in strategic competitive advantage: Strategic competitive advantages are


not supported by the current system.

10. CHARACTERSTIC OF THE PROPOSED SYSTEM

1. Easiness in modification of data: The proposed system provides managing of huge data
effectively and efficiently for efficient results, storing the details of the customers,
employees etc. in such a way that the database can be modified.

2. User friendly: The proposed system is user friendly because the retrieval and storing of
data is fast and data is maintained efficiently. Moreover the graphical user interface is
provided in the proposed system, which provides user to deal with the system very easily.
3. Reports are easily generated: Reports can be easily generated in a proposed system. So
any type of reports can be generated in a proposed system, which helps the managers in a
decisions-making activity.

4. Sharing the data is possible: Data can be shared in proposed system. This means that
two or more persons can use the same data in existing system provided that they have right
to access that data. Also the two or more departments in an organization can easily
interact with each other without the actual movement of data.

5. No or very few paperwork: The proposed system either does not require paper work or
very few paper works is required. All the data is feted into the computer immediately and
various bills and reports can be generated through computers. Since all the data is kept in a
database no data of the organization can be destroyed. Moreover, work becomes very easy
because there is no need to keep data on papers.

6. Support strategic competitive advantage: Proposed system supports strategic


competitive advantages. Since the proposed systems provide easiness in reports generating
it will provide strategic advantages among competitors.

7. Computer operator control: Computer operator control will be there no errors. Moreover,
storing and retrieving of information is easy. So work can be done speedily and in time.

11. FEASIBILITY ANALYSIS


Title: Feasibility report for the computerization of the various activities of the company.

Background: Inconsistent and outdated information is a concern the company is dealing


with in its operations. Report production takes a lot of time and is not very useful for making
decisions. Therefore, we need a system that can deliver timely information.

Method of study: The analytical process included visits to the company's various
departments on field trips. We looked up the following records and sources:

• The purchase order containing the things to be bought.

• The accounts book.

• Distributing purchase orders to vendors.

• The invoices paid to vendors.

• Bills are distributed to clients.

• Provide suppliers with any purchase return forms.


NEED FOR FEASIBILITY STUDY

The purpose of the feasibility study is to determine whether it is worthwhile to execute the
suggested system. A feasibility study evaluates a proposed system's ability to function, how
it will affect how well an organization can meet user needs, and how efficiently it will utilize
resources. It is typically carried out by a small group of experts who are experienced in the
system analysis and design process, knowledgeable about the business or organization
being involved or affected by the project, and familiar with information system
methodologies.

The key consideration involve in the feasibility study are:

1. Technical

2. Behavioral

3. Economic

1. TECHNICAL FEASIBILITY

The present computer system's (hardware, software, etc.) ability to support the suggested
system addition is what determines technical viability. A different application might overtax
the system or demand more hardware, for instance, if the system is already functioning at
70% of its theoretical capacity. The project is deemed unfeasible if the budget is seriously
constrained.

The environment and technology employed in this project are

SOFTWARE
Front End

1. Language used: ASP.NET.


We use this language is supports event driven programming feature.

2. ADO.NET
3.

Back end

Supporting Software: SQL Server 2005. This is used to storing data in the form of tables. It is
easy to use.

OPERATING SYSTEM:

Platform: Windows XP . Our system requires window operating system, which is easily
available.

HARDWARE:
Computer system powered by an Intel processor, with a keyboard and mouse as input
devices. Due of its availability and upgrade, this has been chosen.

There is enough information recorded in the numerous registers kept by the various
departments, which will aid in digitizing the data that is already available.

2. BEHAVIOURAL FEASIBILITY:

An analysis of how end users' actions may affect how the system is incorporated. People
are naturally averse to change; thus, computers must be aware of this resistance in order to
facilitate changes. The likelihood of the user staff reacting negatively to the creation of a
computerized system should be estimated. Since it is well known that a computer
installation can affect employee employment status changes, transfers, and retraining, the
introduction of a candidate system necessitates extra work to inform, persuade, and train
the employees on new business practices.
The suggested system will have an impact on the user organization's personnel. No
employees' positions will be lost by the suggested system because its sole purpose is to
satisfy informational needs. In actuality, the suggested technique will aid the firm in
lessening the extensive labor required. Additionally, increasing user participation at every
step of the project will boost its chances of success.

The crew lacks the necessary training to operate a computerized system. They are adamant
that the working procedure is mechanical because they are accustomed to the manual entry
approach. There is a big demand for attention in this area.

Our system is also feasible for organization because it supports of the organization and its
strategic plan.

4. ECONOMIC FEASIBILITY:

The process includes figuring out the predicted savings and benefits from a candidate
system and contrasting them with the costs. The choice to develop and execute the system
is made if the benefits outweigh the expenses. Otherwise, further alterations are made in
the proposed system

1. Manpower cost

2. Hardware and software cost

DATABASE DESIGN

DATABASE NAME - BILLING SYSTEMDB

_CATEGORY_MASTER

COLUMN NAME DATA TYPE


ID INT(PRIMARY KEY)
CATEGORY_NAME VARCAHR(MAX)
_CUSTOMER_MASTER
COLUMN NAME DATA TYPE
Customer_ID INT
Customer_Name VARCAHR(MAX)
Customer_Address VARCAHR(MAX)
Date DATETIME

_ORDER_DETAILS
COLUMN NAME DATA TYPE
Customer_ID INT
Order_ID INT
Units INT
Price FLOAT
Discount FLOAT

_PRODUCT_MASTER
COLUMN NAME DATA TYPE
_PRODUCT_ID INT
_PRODUCT_NAME VARCAHR(MAX)
ID INT(FOREIGN KEY)
PRICE FLOAT
STOCK INT
REORDER_LEVEL INT

Conclusion
This was our project of System Design Lab about “Billing System”.

Development of this System takes a lot of efforts from us. We think this system gave a

lot of satisfaction to all of us.

Though every task is never said to be perfect in this development field even more

improvement may be possible in this system.

We learned so many things and gained a lot of knowledge about development field.
We hope this will prove fruitful to us.

You might also like