BILLING SYSTEM

Software Design Specification

Submitted to
Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Engineering
in
Computer Science

DEPARTMENT OF COMPUTER SCIENCE

SUSHILA DEVI BANSAL COLLEGE OF
TECHNOLOGY
INDORE- 453331
2010
 BILLING SYSTEM

Software Design Specification

Submitted to
Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Engineering
In
Computer Science

PROJECT GUIDE SUBMITTED BY

Er. Dharmesh Dubey Ankit chitlangia (0829CS071008)
Ankush Rathore (0829CS071012)
Anshul Agrawal (0829CS071013)

DEPARTMENT OF COMPUTER SCIENCE

SUSHILA DEVI BANSAL COLLEGE OF
TECHNOLOGY
INDORE- 453331
 2010
SUSHILA DEVI BANSAL COLLEGE OF
TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Ankit Chitlangia (0829CS071008), Ankush Rathore

(0829CS071012), Anshul Agrawal (0829CS071013) have completed their

Software Design Specification for the project, titled “BILLING SYSTEM” as

per the syllabus and have submitted a satisfactory report on this project as a

part of fulfillment towards the degree of “BACHELOR OF

ENGINEERING” (Computer Science) from RAJIV GANDHI

PROUDYOGIKI VISHWAVIDHYALAYA, BHOPAL.

SIGNATURE

Er.Dharmesh Dubey
PROJECT GUIDE
 SUSHILA DEVI BANSAL COLLEGE OF
TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Ankit Chitlangia (0829CS071008), Ankush Rathore

(0829CS071012), Anshul Agrawal (0829CS071013) have completed their

Software Design Specification for the project, titled “BILLING SYSTEM” as

per the syllabus and have submitted a satisfactory report on this project as a

part of fulfillment towards the degree of “BACHELOR OF

ENGINEERING” (Computer Science) from RAJIV GANDHI

PROUDYOGIKI VISHWAVIDHYALAYA, BHOPAL.

SIGNATURE SIGNATURE

INTERNAL EXAMINER EXTERNAL EXAMINER

 ACKNOWLEDGEMENT

We express deep gratitude for enthusiasm and valuable suggestions that we got from our
guide Er.Dharmesh Dubey for successful completion of the Software Design
Specification of the project. This was not possible without the invaluable guidance of
our project guide.

We are also thankful to our project coordinator Hemant Pathak, for his technical
guidance, encouragement and support.

We are deeply indebted to Mrs. Ruchi Vijaywargiya, head, Department Of Computer

Science Engineering, for providing us support and resources for successful completion
of the work.

We pay deep regards to our Director Dr. N. Dagdee and our Executive Director Dr.
P.C. Sharma, who are instrumental in setting standards for the students to achieve.

Finally, we are thankful to all the people who are related to the project directly or
indirectly.

Ankit Chitlangia (0829CS071008)

Ankush Rathore (0829CS071012)
Anshul Agrawal (0829CS071013)
 Table of Contents
CHAPTER TITLE PAGE NO.

I Abstract…………………………………………………… I
II List of Diagrams…………………………………………. II
III List of Symbols…………………………………………… III
1. Introduction………………………………………………. 01

1.1 Purpose……………………………………………. 02

1.2 Scope………………………………………………. 03

1.3 Problem Domain………………………………….. 11

1.4 Proposed Solution………………………………… 13

2. System Overview ……………………………………….. 14

3. Design Considerations……..…………………………… 14

3.1 Assumptions and Dependencies……..……………. 15

3.2 General Constraints……………………………….. 17

3.3 Development Methods……………………………… 18

4. Architectural Strategies………………………………… 19

5. Detailed System Design ………………………………… 21

5.1 Use Case View………………………………………

5.2 Use case Descriptions………………………………

5.3 Activity Diagrams………………………………....

5.4 Sequence Diagrams……………………………….

5.5 Class Diagrams……………………………………

 5.6 State Chart Diagram………………………….....

5.7 Data Flow Diagram……………………………...

5.8 ER Diagram……………………………………...

6. Bibliography…………………………………………………………. 42
ABSTRACT

Billing System is a flexible Billing and invoicing software for particular one shop to
generate its customer bill and showing shop’s monthly profit or loss report. In this customer
Buy some product from shop and shop’s employee will make the bill with the help of this
software and then this software will manage customer database , Product database and
manage invoice number.
The Billing System must be able to provide the following services to the customer via
Employee:
• Generation of Bill.

• Showing monthly Profit / Loss.

• Manage customer Database.

• Manage product Database.

• Manage Company Database.

• Invoice Manager.

• Showing Aging chart.

List of Diagrams:

 Use Case Diagram

 Activity Diagram

 Sequence Diagram

 Class Diagram

 State Chart Diagram

 Dataflow Diagram

 ER Diagram
1. Introduction
Billing System is software for generating bill of customer in shop and maintain shop’s
database like customer database , product database , managing invoice number and showing
monthly profif/loss report.

1.1 Purpose of this Project

The Purpose of making of this software is to reduce manual effort to make

bill and to maintain the record of product and customer and sell items .

1.2 Scope of the Project

This software package will perform as a part of the billing system described
in the system requirements specifications. This software product provides the control
necessary for the billing system to perform its activities.

1.3 Problem Domain

This section organized in subsections contains the details necessary for the system engineer
to create design specification of the software. The different processes in our system with
their respective inputs & outputs are as follows:
  Customer

Customer is any person which will come in our shop for purchasing any product . The
employee of shop will generate the bill of its purchasing item with the help of this
software.

 Generation of Bill

Customer information that includes his/her name, address, city, state, phone number etc.
And the weight of the item sold and item’s type.

 Showing Monthly Profit/Loss Report

After completing of the month , take the total of buy and sell of the product and compare
to that with previous month to show Profit or Loss.

 Manage Customer DataBase

In this all the Customer’s Information is managed

 Manage Product DataBase

In this all the Product’s Information is Managed.

 Invoice Manager

In this Invoice number or Bill number is Managed.

1.4 Proposed Solution

 When the billing system was developed the records were maintained on paper and
stored in files and it resulted in a huge amount of paperwork. Extracting any records
from such a bulk was a tedious job and reduced the efficiency of the system. Also the
chances of loss of data on account of a natural calamity or reckless handling were also
very high. Also when the records were kept manually there were chances of
inconsistency of data owing to human errors. As a result, in order to overcome these
shortcomings banking software was developed which entrusted this job of record
keeping to the computers and reduced a large amount of unnecessary problems.

The computers can perform computations very fast and maintain data
consistency & integrity. So programs are now used to maintain shop’s product database
and customer database and managing invoice number. Using this software, huge chunks
of data can be stored using databases that provide additional functionalities for
manipulating the data. This provided for a much easier access to any data present in the
database at the single click of a mouse.

2. System Overview

The project mentioned above can be implemented in JAVA consists of Java runtime
environment.
The Billing software will perform the following activities

• Generation of Bill.

• Showing Monthly Profit / Loss.

• Manage customer Database.

• Manage product Database.

• Manage Company Database.

• Invoice Manager.

• Showing Aging chart

3. Design Considerations

Some of the design constraints are as follows:

 The software will be menu driven.

 Menu section includes different GUI (JFrames in Java) that will be displayed &
entries will be made.

 Windows will be displayed before user makes each entry.

 Confirmation of action taken, input accepted or error condition will be displayed

after each input.

3.1 Assumptions and Dependencies

 The total available memory for programming logic, tables, etc as specified in
the document shall not be exceeded.

 The program will be written in java.

 The user will be guided through the use of some services with easy to read
instructions.

 The Shop’s database will be modified accordind to customer information.

 The shop’s database will be changed to meet Billing system requirements. The
address, the telephone no. of company,credit limit will be added to existing
information. This change will be made prior to developing the Billing software.

3.2 General Constraints

Hardware:
 (a) Minimum Hardware Configurations for Net beans 6

 OS: Microsoft Windows XP Professional, Windows Vista,2003.

 Processor: 800MHz Intel Pentium III or equivalent

 Memory: 512 MB

 Disk space: 750 MB of free disk space

(b) Minimum Hardware Configurations for Mysql:

 Physical memory (RAM) : 128 MB(minimum),256 MB (Recommended)

 200MHz(Minimum) Pentium III CPU

 Hard disk space : 1.5 GB

 Architecture : 32 bit or 64 bit

 OS: Windows NT Server, 2000, 2003, XP Professional

3.3 Development Methods

Software Engineering is the establishment and use of sound engineering

principle in order to obtain economically software that is reliable and work efficiently. It is a
layered technology. The bedrock that supports software engineering is a high quality focus.
Software engineering encompasses a process, management, technical methods and tools.

The foundation for software engineering is the process layer. Process defines
a framework for a set of key process areas. Software engineering methods provides the
technical How’s for building software. Software engineering tools provide automated or
semi automated support for the process and the methods.

 Software Model Used:

“The linear sequential model”

 In this project the linear sequential model has been used. It is
sometimes called the life cycle or the waterfall model. This model suggests a systematic
sequential approach to software development that begins at the system level and progresses
through analysis, design, coding, testing and support.

Code Test
Analysis
System/information Design

engineering

Linear
Sequential Model

 Why Linear Sequential Model?

The project entitled “Billing System” has been developed

following the linear sequential model.

The first step in the development of the project was the analysis
which involved the establishment of requirements for all system elements and then
allocating some subset of these requirements to software. Requirement gathering at the
system level with a small amount of top-level design and analysis was done.
 A clear separation between the planning and designing of the project and the
actual implementation is achieved through this model. This helps in reducing the complexity
of the project development.

4. Architectural Strategies

 Software:

Java: Java Language is used for making the project of Billing System.

Mysql: Mysql is used for storing the data

Mysql basically does three things:

• Lets you put data into it.
• Keep the data
• Lets you get the data and work with it.
  Performance Requirements:

The customer will be provided with sufficient amount of time to check item or do any other
operation that he wants to perform but ideally speaking more transactions/ operations in
lesser time will certainly increase the performance.

 Safety Requirements:

The Database may get crashed at any certain time due to virus or operating system failure;
therefore it is required to take the database backup.

 Security Requirements:

We are going to develop a secured database for the Billing system. There are different
Categories of users namely admin and employee of the shop etc, depending upon the
category of user the access rights are decided. Software quality Attributes the quality of the
database is maintained in such a way so that it can be very user friendly to all the user of the
Database.

Software Quality Attributes:

Our billing software will possess certain quality attributes built into the work product.

 Reliability:
The software will have been thoroughly tested at time of delivery so that computational
errors will not occur. It will be written in a modular structure to make modifications as easy
as possible.

 Maintainability:
All the modules will be as maintainable as possible so that changes in one module will not
produce software errors in another part of the system.

5. Detailed System Design

5.1 Use-case Diagram

5.2 Use -Case Description
1. Use Case Specification: Login
1.1 Brief Description
This use case describes how a bank employee logs in BMS to access bank database.
1.2 Basic Flow
1.2.1 Employee enters login id and password.
1.2.2 Bank database validates employee.
1.2.3 On success employee can access the system.
1.3 Alternate Flow
If in basic flow, the details specified by employee are invalid then he is informed that
login failed.

2. Use Case Specification: Perform Transaction

2.1 Brief Description
This use case describes how employee performs the transaction requested by the
customer.
2.2 Basic Flow
2.2.1 Employee enters account number and transaction type.
2.2.2 Employee enters the amount involved in the transaction.
2.2.3 BMS checks for available balance & asks if receipt is required to customer.
2.2.5 Employee dispenses cash to customer.
2.3 Alternate Flow
2.3.1 If in step 2.2.1 of basic flow, incorrect account number is encountered, then customer
informed of the problem.
2.3.2 In step 2.2.3 of basic flow, if there are insufficient funds for amount requested,
customer is informed of the problem & use case resumes at step 2.2.2 of basic flow.
2.3.3 In step 2.2.3 of basic flow, if customer chooses to have receipt, BMS will prompt
printer to print the receipt.

3. Use Case Specification: Manage Account

3.1 Brief Description
Employee must be able to open and close account as intended by the customer.
3.2 Basic Flow
3.2.1 Customer must fill a form providing personal details to open account to employee if
customer selects open account.
3.2.2 Bank database validates all details.
3.2.3 If successful, bank allocates a CIF number.
3.2.4 Employee asks for account selection to customer. Customer gets account number.
3.3 Alternate Flow
3.3.1 In step 5.2.2 of basic flow, if incorrect details are found then problem is reported to
the customer.
3.3.2 In step 5.2.2 of basic flow, "Close Account" is selected; employee enters account
number & available balance to the customer.

5.3 Activity Diagram

For Login:
For Product status:
For bill generation:
 5.3 Sequence diagrams:

For Login:
For print:
For Report Generation:
For Product Database:
5.4 Class diagram
5.5 Data Flow Diagram

DFDLevel-0
DFD Level-1
5.6 ER Diagram
.
6) Bibliography

 Roger S. Pressman, “Software Engineering - A Practitioner’s

Approach”, Tata McGraw Hill Publications.