E-Billing System

E-Billing and Inventory System

Sr. No. Topic Page No.

1 Acknowledgement II
2 Preface III
3 Introduction to the Organization V
4 Certificate of College -
5 Certificate of Company -

CONTENTS

1 Project Profile 2

2 Project Definition 4

3 Existing Manual System

3.0 Introduction
3.1 Features of Existing System
3.2 Problem Faced by Current
System

4 Need for the new system

5 Tools and Technology

5.0 Hardware Requirements of
the System
5.1 Software Requirements of
the System
 E-Billing System

5.2 Tools Information

6 System Analysis and Design
6.0 Fact gathering Techniques
6.0.1.1 Interview
6.0.1.2 Review Record
6.0.1.3 Observations
6.0.1.4 Scope

7 Proposed System

8 System Diagram
8.1 Entity Relationship Diagram
8.2 Data Flow Diagram
8.2.1 Context Level Diagram
8.2.2 UML Diagram

9 Data Dictionary

10 Data Entry Screen Samples

11 Testing and Debugging

11.0 Testing Summary
11.1 Levels of Testing
11.2 Gantt Chart

12 Implementation

13 Limitations of Project

14 Future Enhancement
 E-Billing System

15 Bibliography
ACNOWEDGEMENT

PREFACE

Theoretical knowledge of our subject is important but

without understanding the practical aspects it turns out to
be useless. A technical student needs an intensive and
comprehensive understanding and knowledge of the subject
being studied. Thus an industrial training provides great
opportunity for students to get a practical view of the
various subjects. It is an excellent opportunity for them
exposed to working environment.

The training provides the platform for the new students

to prepare some groundwork before actually entering the
industry. It helps to understand the basic problem faced in
the industry and means and ways to overcome them.

Important training provides to be an important part of

the practical study curriculum.
 E-Billing System

Product Range

The product belongs to the company, but the brand

belongs to the consumer. The trust of our clients and
patrons is the real essence of our esteemed
organization, which inspires us to create ''better than
the best'' gift idols and costume jewelry. We employ
American Pewter metal along with Swaroswki
diamonds as our raw material to effectively cater to
our widespread clientele. All that is good breaks up
into little pieces. Serving the needs of our
customers, we are engaged as eminent
manufacturers and exporters of the products
enumerated below:-

Jewelry:

The term ''jewelry'' can be appropriately equated

with women of all centuries. Jewelry is the desire of
 E-Billing System

every woman and the good news is that there is

abundance of costume jewelry in the present day
markets. However, the downside of it is that it is
quite a difficult task to distinguish between the two
jewelry products appearing the same. The perfect
solution to get over with this confusion is going for a
superior quality product, which can last longer in
comparison with the others. Moji Gems Pvt. Ltd. is a
renowned name owing to the unsurpassed quality of
its reliable products.

Our jewelry is exclusively designed to complement

the outfit one is wearing. We also design precious
piece of jewelry, highly suitable for the occasion of
marriage

Earrings, Bracelets, Necklaces, Bridal Jewelry, Pearl

Jewelry, Stone Jewelry, Fashion Jewelry, Imported
Jewelry, Traditional Jewelry, Imitation Jewelry,
Handcrafted Jewelry.

Idols:

Idols are shapes given to creativity. We have a varied

range of idols of Gods that are exclusively designed to
complement any occasion. Our product features are
distinct and sharp.
 E-Billing System

Our Infrastructure

We are backed by eminent machinery and efficient

employee constituting the infrastructure of our corporate
entity. Our craftsmen are storehouse of talent, devotion,
creativity and innovation. These are the precious gem
stones of our company, contributing in its fame and name
in this industry. Machinery being another important
aspect of our infrastructure is carefully selected and
upgraded on a regular basis so as to derive best results
from it. In management, what matters is not how you
perceive your acts,but how you are perceived by others.

Quality Quotient

Quality is never an accident. It is the result of planning,

team work, and commitment to excellence. Quality is the
buzzword of our firm and we make incessant efforts to
improvise it on a regular basis. This is the primary reason
behind the sustenance and increasing numbers of our
clientele. Regular quality checks at every level right from
the initial stage of manufacturing till the attainment of
final output in the form of finished product assures that
all our attempts pay off and enable us to live up to the
expectations of our valued customers.

Service Overview

COMPANY PROFILE
 E-Billing System

Chapter 1
PROJECT PROFILE
Project Title Inventory and E-Billing System
 E-Billing System

Chapter 2

PROJECT
DEFINITION
 E-Billing System

PROJECT DEFINITION

The layout and all development of the E-Billing and

Inventory System project is a stand-alone application.

It will manage all the details and records of the

customer, order information given by that particular
customer and provide facility to search information of all
customer and invoices. Back up facility is there to secure
the information from the any internal damage.

This project is windows based application performs on

Database System. This System enables person who makes
access of it can have benefit of decrease paper work and
smoothly work on it.
 E-Billing System

Chapter 3

EXISTING MANUAL
SYSTEM
 E-Billing System

3.0 INTRODUCTION

• The existing system is a Excel based System of the

respective company. The system is not being maintained
bundle of bugs to solve.

• The company decided to build as on new product and that

opportunity lies in our hands.

• Show the company existing system worked definitely well

till the kind and the no of reports generated was enough
for respective management to make proper decision.

• company management works on excel base system which

was not so flexible in calculation for making invoices.

• Duplication of data occurred in the existing system which

was the main data redundancy occurred in system.
 E-Billing System

3.1 FEATURE OF EXISTING SYSTEM

 All order monitoring done manually.

 Manual record keeping of the customers.
 Duplication of data cannot be avoided.
 No computer knowledge is required.

To search company by name of its ID, anther manual procedure

is required.

As the system is not computerized, necessary calculation is not

be done automatically. The main feature of existing system is it
can be used anywhere without use of computers
 E-Billing System

3.2 PROBLEM FACED BY CURRENT MANUAL

SYSTEM

The phase of system analysis process deals with

problems, which are affecting in current manual system.
The problems are those which affecting the company in
daily work

As the growing trend in the InfoTech world of computer

need of accuracy, perfect ness, speed and high memory
storage is a must. Each and every problem must be solved
with a least amount of time and energy.

The problems faced by existing system as described as

below:

 Difficulty in maintenance of record.

 Time consuming.
 Editing of data becomes tedious job.
 No security of data.
 Mistakes occurring in long calculation.
 Not proper generation of reports.
 Lack of Efficiency.
 Data inconsistency.
 Show the company existing system worked definitely well till
the kind and the no of reports generated was enough for
respective management to make proper decision.
 Company management works on excel base system which was
not so flexible in calculation for making invoices.
 E-Billing System

Chapter 4

NEED FOR THE NEW

SYSTEM
 E-Billing System

The current system is very tedious and lengthy as it is

manual. The system consists of many errors. There is lots
of limitation of the current system. If company want to
maintain the record of their customers it take lots of time
to record in the registers. Monitoring of orders and
maintaining invoices are very difficult in excel format. No
calculation is done automatically.

So, to minimize all this limitations of existing system

we have to implement new proposed system. This is
capable of handling whole system with less error. The need
to develop a new system is just to provide better facilities
to the user. Even to minimize the workload of other
employees in case of order monitoring. So there was an
urgent need to develop a system which provides faster
access and accurate information about the customer and
items. Quick generation of reports, less human errors and
less manpower required.

• The new system should be more accurate and user

friendly to show each and every error to the operator
at immediate point of mistake.

• The system project develop should adorn at the

security purpose of the system is concern.

• Data entry required should be minimum.

• Quick search and retrieval.

 E-Billing System

Chapter 5

TOOLS AND
TECNOLOGY
 E-Billing System

5.0 HARDWARE REQUIREMENT OF THE SYSTEM

This phase of software development process deals with
a brief study of different hardware used in the
computerized system. There is list of hardware materials
used during the making and also during the used of
proposed system. As the new system is to be made into a
computerized functional system, requirement of computer
is must. All the hardware needed here generally the basic
configuration of a typical office computer. A list of hardware
requirement used in the system given below:

Minimum Configuration :

To run the application software of the system in the

computer minimum configuration required is below:

 1.99 GHz Pentium® processor or other compatible.

 Intel® Chipset motherboard.
 512 RAM.
 40-80GB Hard Disk.
 Compact Disc Drive.
 Monitor.
 Keyboard.
 Mouse.
 Printer.
 E-Billing System

5.1 SOFTWARE REQUIREMENT OF THE SYSTEM

Along the hardware, used in the system it requires

software to make a system as well as to run a system with
the computer hardware. Collection of different type of
hardware into a specific type can form a computer but it
cannot execute different process its own. For efficient and
proper working of any system software must be installed.
This software may be in the form of operating system or
application software.

To make the system one also needs to use software.

To make the E-Billing and Inventory System for
“Company”, we have to use certain software, which are
listed below. The software used in the proposed system is
the latest versions of them and can give up-to-date and
perfect results of every process in the system. This
software comprises operating system and application
software used in the system.

Software used in designing code) of the system.

Operating System :: Microsoft Windows® XP

Application Software’s :: Microsoft Visual Studio 2008

Microsoft Access 2003

 E-Billing System

5.2 TOOLS INFORMATION

o FRONTEND TOOL: MICROSOFT VISUAL BASIC.NET

2008

The need of the hour was an environment that would allow

easy design of the user interface thus was born the art of
visual programming.
All the important coding techniques used by programmers,
in OOPS base coding is brought out in full and in great
detail. This is coupled with material on how to use the
various tool sub set available in vb.net in order to
understand the application development process, it is
helpful to understand some of the key concepts upon which
visual basic.net is buit.
Since, visual basic.net is a windows development language
we need some familiarity with the visual programming
environment.

• FEATURES OF VISUAL BASIC.NET

Visual basic.net provides complete set of tools to
simple rapid application development.
 E-Billing System

1) It provides a vital link to graphical environment

and allows you to develop applications based on standard
windows features: Dialog boxes, command buttons, pull
down menus, scroll bars, selection lists, date and time
picker etc. It also allows creating robust applications that
fully makes use of the graphical user interface.
2) Active X data objects (ADO) and OLEDB replace
the open database connectivity (ODBC) API as the
preferred method for accessing shared-file and client
server databases.
3) Internet techniques such as Dynamic HTML
(DHTML), Extensible mark up language (XML).Active server
pages (ASP) and active X.
4) Document offer browser-based alternatives for
displaying and updating data.
5) Extensions to Visual basic.net class modules assist
in writing middle tier DLLs for Microsoft transaction server
2.0.
6) A multitude of wizards and other graphical tools
aid developers new to visual basic.net.
7) It provides a vital link to graphical environment
and allows you to develop applications based on standard
windows features: Dialog boxes, command buttons, pull
 E-Billing System

down menus, scroll bars, selection lists, date and time

picker etc. It also allows creating robust applications that
fully makes use of the graphical user interface.
8) Active X data objects (ADO) and OLEDB replace
the open database connectivity (ODBC) API as the
preferred method for accessing shared-file and client
server databases.
9) Internet techniques such as Dynamic HTML
(DHTML), Extensible mark up language (XML).Active server
pages (ASP) and active X.
10) Document offer browser-based alternatives for
displaying and updating data.
11) Extensions to Visual basic.net class modules assist
in writing middle tier Visual basic.net is an event driven
programming language. Visual basic.net allows you to
adopt more of parallel approach, with independent sections
of code for code for each option that the user may select.
This is known as event driven programming language.
12) Data environment designer (DED).
13) Drag and drop form generation.
14) Data view window.
15) ADO data control (ADODC).
16) Hierarchical record sets and the flex grid control.
 E-Billing System

17) Data report design.

18) Data form wizards.
19) Format objects.
20) Data source classes and data building.
21) MTS transaction mode property of class modules.
22) Visual data tools(VDTS).
23) SQL editor.
24) Component creation.
25) Language.
26) Packaging and development wizard.
27) Data object wizard.
28) The integrated development environment.

BACKEND TOOL: Microsoft Access-2003

A database is a collection of information about groups of
time or individuals. database structure is provides by fields
categories of information simple database programs only
allows you to work one list of information at time one set of
fields & records more cables programs like access let you
group multiple list together & records.
Access database includes six do object tables, forms,
reports, queries, macros and visual basic modules before
 E-Billing System

you begin construing the database, you need to spend

sometime designing the data base. a bad design virtual
database developer often spends as much time designing a
database as they do constructing it. To design a database,
you should follow these steps:
Every database begins with a problem & needs can be
solved by crating a systematic data-tracking system.
Once you established the tables you will be creating
determine what information about each entity should
include. Every field must be part of a species table and
every field should be automatic that means that you store
data & it’s smallest logical components Stores Street
address, city, state, zip code, later on.
A relationship ties tables to another by including the
primary key from one table to related table. After planned
the tables & relationship & before you begin construing
table & typing name & social security number when you are
convinced that the design is well conceived begin creating
tables and setting.
To determine whether the structure accomplished your
0objects and is easy to work with, being by entering a few
recodes that are a representative sample of the data.
 E-Billing System

When the access application windows opens, you

immediately see the access dialog box. Access includes a
database wizard that allows you to customize one of there
redesigned data based that come with access. If a
database you want to create is already in the list, you can
the wizard. After you click ok you are immediately
prompted to enter a file name and location for the
database in the file new database dialog box.
An auto form can have one of three different layout data
sheet tabular or columnar the auto form looks a lot like the
3 table’s data sheet views. Right
Down the navigation buttons you can move the column and
rows around just like the table.
Validations are a way to screen data begins entered in
table or form field’s validations are set in a fields
validations rule property. When you tab or click out the
field, access checks to makes sure the data you entered
matches the rule if not the validation text is displayed.
 E-Billing System

Chapter 6

SYSTEM ANALYSIS
AND
DESIGN

6.0 FACT GATHERING TECHNIQUES

Information gathering in many E-Billing and Inventory
system is not easy task. It has to be gathered in an
organized way so that

(a) No system details are left out.

 E-Billing System

(b) Right problems are identified.

(c) Repetitive work is avoided
(d) Wrong or incomplete details are not collected.

To do this, a proper search strategy must be decided

first, search strategy includes selecting information sources
and search methods. It also including modeling methods to
make senesce out of information so collected. Here an
overall idea about the search methods or fact gathering
techniques which are used during gathering information,

They are

(1) Interviewing.
(2) Record inspection.
(3) Observation.

We visited many times at the “Company” to get information

as well as problems which occurring in the current existing
manual system. As each and every person in the company
has different type of job to be done so we met some of
people in the Company.

6.0.1 Interviews:

Interview allows the analyst to collect or gather the

information from the individual or group who are who are
generally the current user of the system or potential user of
the proposed system.

Interview could be
 E-Billing System

(a) Structured
(b) Unstructured

Structured:

Here it is standardized questions as far as

response of the questions is concerned; they are
divided into two formats:

(a) Open response formats.

(b) Close response formats.

Unstructured:

Here, the questions are worded to suit the

respondent that provide the information about the areas
overlooked or not thought to be important.

6.0.2 Record Review

It is said to better believe in record than in people.

Thus a good analyst always gets facts from the documents.
A existing system can be better understood by the
examining existing documents, forms and files. In the
record reviews analyst examine information that has been
recorded about the system user.
 E-Billing System

Record May include:

1) Written policy manuals.

2) Rules and Regulations.
3) Standard operating procedures used in billing
system.
4) Forms and documents

Records do not show how tasks are performed or what

activities are actually occurring and where decision power
lies.

6.0.3 Observation:

Observation can bring in missed facts, new ways to

improve the existing procedures, duplicate work done
inadvertently, etc.
 E-Billing System

Observation can bring in what other fact-finding

methods cannot! But this task is delicate because people do
not like to be observed they work.

Observation can look for:

(a) Operational inefficiencies.
(b) Alternative routes and procedure.
(c) Interruption in normal flow of work.
(d) The usage of files and documents.
(e) Informal communication and channel, etc.

On site observation provides close view of the working

of the real system. He can observe people, objects,
and documents and occurrences of events.
 E-Billing System

Chapter 7

PROPOSED
SYSTEM
 E-Billing System

Generally in colleges the manual system is to be

computerized in order to overcome the problems,
which affect the existing manual system.
Computerized the existing system with the help
of some programming language, database package
ease the work of the system up to a great extent.
In computerized Billing and Inventory System all
information about the customer, quotation, its item
and etc i.e. managing of orders.
The information about customer is feed with the
help of key element. For a single item code different
price list is there.
 E-Billing System

Quick search and retrieval process are their for

collecting the information about the item and
customers.
It also gives the information about pending work
orders

Chapter 7

SYSTEM
E-Billing System

DIAGRAM
 E-Billing System

8.0 ENTITY RELATIONSHIP DIAGRAM

E-Billing System
E-Billing System
 E-Billing System

Data Flow Diagram

 E-Billing System

Use Case Diagrams

Use case diagram for sales

 E-Billing System

Use Case Diagram for Customer Purchase an Item

 E-Billing System

Activity Diagram for Invoice

 E-Billing System

Activity Diagram for Invoice details

 E-Billing System

Manufacturing Balance Balance Stock Invoice

Data
Order
stock

UpdateInventory()

InformSales()

Sequence Diagram for Item Work Order Status and Balance Quantity
 E-Billing System

Sequence Diagram for Item Purchase

 E-Billing System

Class diagram for order processing system

 E-Billing System

Class diagram for invoice system

 E-Billing System

Collaboration Diagram
 E-Billing System

Data Dictionary

TABLE ATTRIBUTE CONTENTS TYPE PK

NAME NAME OR
FK
CUST_MASTER CUST_NO Customer Number NUMBER PK
COMP_NAME Company Name TEXT
OFFICE_ADD Office address TEXT
INVOICE_ADD Invoice address TEXT
CUST_EMAIL Customer Email TEXT
FACT_ADD Factory address TEXT
FACT_EMAIL Factory Email TEXT
FACT_TEL Factory Telephone NUMBER
FACT_FAX Factory Fax Number NUMBER
FACT_MOB Factory Mobile NUMBER
ITEM_MASTER OFF_TEL
ITEM_CODE OfficeCode
Item Telephone NUMBER PK
TEXT
CONT_1
ITEM_DESC Office Mobile
Item Description TEXT
OFF_FAX
GRADE Office Fax Number TEXT
Grade NUMBER
OFF_DIRTEL
PRORORTION1 Office Director
Prorortion1 NUMBER
TEXT
MASTER_BATCH Telephone
Master Batch TEXT
CONT_2
PRORORTION2 Office Director
Prorortion2 TEXT
ADDITIVES Mobile
Additives TEXT
OFF_PURTEL
MOULD_CODE Office Purchase
Mould Code NUMBER
TEXT
MOULD_LOC Telephone
Mould Location TEXT
CONT_3
CUST_NAME Office Purchase
Customer Name TEXT
MOULD_DETAILS Mobile Details
Mould TEXT
OFF_ACCTEL
SUPPLIER Office Account
Supplier NUMBER
TEXT
CTSH_NUMBER Telephone
CTSH Number NUMBER
CONT_4
SHOW_WEIGHT OfficeWeight
Show Account TEXT
NUMBER
ARTICLE_WEIGHT Mobile
Article Weight NUMBER
OFF_TECHTEL
PIECES_PER_KG Office Technical
Pieces Per Kg NUMBER
KGS Telephone
Moulds in KG NUMBER
PAYMENT_TERMS
PCS Payment
Mould InTerms
PCS TEXT
NUMBER
CUST_GST Customer GST TEXT
Number
CUST_CST Customer CST TEXT
Number
CUST_ECC Customer ECC TEXT
Number
CUST_NOTE Customer Note MEMO
 E-Billing System

QUOTATION_ QUOTATION_ Quotation Number AUTO PK

MASTER NUMBER NUMBER
VENDOR_NUMBER Vendor Number NUMBER
CUST_NUMBER Customer Number NUMBER FK
CUST_NAME Customer Name TEXT
CUST_ADD Customer address TEXT
ATTN Attn TEXT
REFERENCE Reference TEXT
DELIVERY Delivery TEXT
CUST_DETAILS CUST_NO Customer number NUMBER FK
TAXES Taxes Applicable NUMBER
ITEM_CODE Item Code TEXT
PAYMENT Payment NUMBER
ITEM_DESC Item Description TEXT
FRIGHT Freight TEXT
PRICEIN Price In TEXT
VALIDITY Validity TEXT
PCS_KG Pcs Per KG TEXT
NOTE Note TEXT
TAXES Taxes Applicable TEXT
Q_DATE Quotation Date Date/time
REMINDER Quotation Reminder YES/NO
E-Billing System
QUOTATION_ MINIMUM_QTY Minimum Quantity NUMBER
DETAILS ITEM_CODE Item Code TEXT
ITEM_DESC Item Description TEXT
PRICE_INE-Billing System
Price In NUMBER
UNITPERKG\PCS Unit Per Kg Or Pcs NUMBER
TOOLING_PRICE Tooling Price NUMBER
QUOTATION_ Quotation Number NUMBER FK
NUMBER
PERFORMA_ PERFORMA_ Performa Invoice AUTO PK
MASTER INVOICE_NO Number NUMBER
VEN_NO Vendor Number NUMBER
CUST_NO Customer Number NUMBER
CUST_NAME Customer Number TEXT
ATT Attn TEXT
REFE Reference TEXT
DELIVERY Delivery TEXT
PAYMENT Payment TEXT
FRIGHT Freight TEXT
NOTE Note TEXT
PEFORMA_ PEFORMA_INV_NO Performa Invoice NUMBER FK
DETAILS Number
REQ_QTY Required Quantity NUMBER
ITEM_CODE Item Code TEXT
ITEM_DESC Item Description TEXT
PRICE_IN_RS Price In RS NUMBER
AMOUNT_IN_RS Amount In RS NUMBER
ORDER_MASTER WORKORDER_NO Work Order Number NUMBER PK
QUOTATION Quotation Number NUMBER
DATE Work Order Date Date/Time
CUST Customer Name TEXT
PLANNED_DATE Planned Date Date/Time
NOTE Work Order Note TEXT
ORDER_DETAILS WORKORDER_NO Work Order Number NUMBER FK
ITEM_CODE Item Code TEXT
ITEM_DESC Item Description TEXT
QTY Quantity NUMBER
PRICE_IN Price In RS NUMBER
UNIT Unit NUMBER
BALANCE Balance NUMBER
ORDER_PROCESS WORK_ORDER_NO Work Order Number NUMBER FK
PERFORMA_INV_NO Performa Invoice NUMBER
Number
PURCHASE_ORDER Purchase Order NUMBER
_NO Number
DATE Date Date/Time
NOTE Text TEXT
ORDER_PROCESS WORK_ORDER_NO Work Order Number NUMBER FK
_DETAILS ITEM_CODE Item Code TEXT
ITEM_DESC Item Description TEXT
QTY Quantity NUMBER
PRICEIN_UNIT Price In Unit NUMBER
PCSPERKG Pieces Per Kg NUMBER
BALANCE Balance NUMBER
TAX_INVOICE CUST_NAME Customer Name TEXT
CUST_ADD Customer Address TEXT
GST_TIN GST TIN TEXT
E-Billing System
 E-Billing System

Chapter 10

DATA ENTRY
SCREENS

10.0 INTRODUCTION
This section refers to the various types of interfaces,
which the users has to face during operating the
computerized system of “E-Billing and Inventory System”.

The section refers with the entire interfaced [screens] a

user will have to face while operating the current system. It
show the various screens appearing in the current
 E-Billing System

transactions. All the screens of different transactions in the

system are shown here.

The different transaction’s screens shown here in the

below given order:

1. Export
a. ARE
b. CER BY CEN EX OFF
c. CER BY CUSTOM OFF
d. REBATE SANCTION ORDER
e. EXPOST BY POST

2. Domestic
a. Master
i. Customer Master
ii. Item Master
iii. Packing Master
b. Transaction
i. Quotation
ii. Order Entry
iii. Order Monitoring
iv. Performa Invoice
v. Invoice
1. Tax Invoice
2. Retail Invoice
3. Retail Labour Invoice
c. Reports
i. Customer Report
ii. Item Report
d. Setting
i. Tax Setting
ii. Retail Setting
 E-Billing System

iii. Retail Labour Setting

e. Exit

3. Utilities
a. Backup
b. Change Password

4. Exit

10.1 FORM LAYOUT

 E-Billing System

This form is the starting form of the system if LOGIN

SUCCESSFUL then you can do the work in to the system.
 E-Billing System

After completion of the login procedures the form is look

like the above from on which you can select the any module
and you can do the work in to the particular module.
 E-Billing System

Domestic:

After selection the domestic module you can work on any

Master and Transaction forms as above mention.
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
E-Billing System
 E-Billing System

After selection the Utilities menu you can work on any

Backup and Change Password facility.
 E-Billing System

After clicking on back up menu the back up is store in D:

drive of computer system.
 E-Billing System

This form helps the user to change its password by

entering current password.
 E-Billing System

Chapter 11

TESTING AND
DEBUGGING
 E-Billing System

Testing involves exercising the program using data like the real
data processed by the program. The existence of the program
defects or inadequacies is inferred from unexpected system outputs.
Testing may be carried out during the implementation phase to
verify that the software behaves as intended by its designer and
after the implementation is complete.
Testing is just like quality assurance to review of software
products and related documents for correctness, completeness,
reliability, and maintainability. And it includes assurance that the
system meets the specifications and requirements for it is intended
use and performance. The common view of testing is to prove that
are no errors.
System testing is too much expensive as well as it is not
possible for analyst to prove that software is free and clear of
errors. Therefore, the most useful approach is the process of
executing a program with the explicit intention of finding errors.

Different kinds of testing are used to test different kind of

characteristics of the program:

1. Statistical Testing: Statistical testing may be used to test

the program’s performance and reliability.

2. Defect Testing: Defect testing is intended to find areas

where the program does not conform to its specification.
 E-Billing System

Testing Fundamental

1. Testability

Software testability is simply how easily a computer program

can tested. Since testing is so profoundly difficult, it plays to know
what can be done to streamline it. Sometimes programmers are
willing to do things that will help the testing process, and a checklist
of possible design points, features, and so on can be useful in
negotiating with them.
There are certainly that could be used to measure testability in
most of its aspects. Sometimes, testability is used to mean hoe
adequately a particular set of tests will cover the product.

2. Operability

“The better it works, more efficiently it can be tested.”

1. The system has few bugs
(Bugs add analysis and reporting overhead to the
test process.)

2. No bugs block the execution of tests.

3. The product evolves in functional stages
(Allows simultaneous development and testing.)

3. Obeservability - “What you see is what you test.”

1. Distinct output is generated for is generated for each
input.
 E-Billing System

2. System states and variables are visible during

execution.
3. Past system states and variables are visible.
4. All factors affecting the output are visible.
5. Internal errors are automatically reported.
6. Source code is accessible.
 E-Billing System

4. Controllability - “The better we can control the software, the

more the testing can be automated and optimized.”

1. All possible outputs can be generated through some

combination of input.
2. All code is executable through some combination of input.
3. Software and hardware states and variables can be controlled
by the test engineer.
4. Input and output formats are consistent and structured.
5. Test can be conveniently specified, automated and reproduced.

5. Decomposability - “By controlling the scope of testing, we can

more quickly isolate problems and smarter retesting.”

1. The software system is built from independent modules.

2. Software modules can be tested independently.
3. Simplicity. “The less there is to test, the more quickly we can
test it.”
4. Functional simplicity
5. Structural simplicity
6. Code simplicity.

6. Stability - “The fewer the changes, the fewer the disruptions to

testing.”

1. Changes to the software are infrequent.

2. Changes to the software are controlled.
3. Changes to the software do not invalidate existing tests.

7. Understandability - “The more information we have, the smarter

we will test.”

1. The design is well understood.

a. Dependencies between internal, external and shared
components are well understood.
2. Changes to design are communicated.
3. Technical documentation is instantly accessible.
4. Technical documentation is specific and detailed.
 E-Billing System

8.2 TYPES OF TESTING

1. Unit Testing

Systems are not designed as entire system or nor they tested as

single system. Unit testing focuses first on the modules,
independently of one another to locate the errors in coding and logic
and that contained within that module alone.
For example, Test cases needed to check user, whether user is
authorized or not, as well as if user is authorized then which
permissions are granted and then checks whether user allows to do
function with respect to the permissions assigned to him/her.
We have performed unit testing from bottom up, tested each
components of the modules independently. Than integrate all the
components and tested each modules independently. After that we
have merged all the modules and tested the whole system.

2. System Testing:
System Testing does not test the software per se but rather the
integration of each module in the system. The primarily concern is
the compatibility of each individual module. Analyst trying to find
areas where module has been assigned different specifications for
data each length type, and data element name.

3. Storage Test:
We have to specify capacity for the system when it is designed
and constructed. Capacity measures in terms of the number of
records than the disk will handle of file can contain.

4. Performance Test
When we are developing a design their concerns are more on
reports inputs and processing sequence then on performance time.
Performance time testing is conducted prior to implementation to
determine how long it takes to receive to an inquiry.
We have used only one connection for whole system which also
increases performance time. In beginning we can’t measure the
performance time. But after system is loaded with data, we can sure
about performance time.
 E-Billing System

5. Recovery Testing
The system should be capable of recover the stored data, if the
user has performed the illegal operations or delete records.
For example, we have provided facility, user deletes some
records, there is a message: “Are You Sure Want to Delete?” If user
press no button, then data will not been deleted. Means user has
given one chance before deleting any records.

6. Human Factor Testing

As human being, the users can enter any type of data and save
transaction if there is no data validation.
For example, in our project, we provide the test cases so that
the user can’t enter some digital value in the name field. And
although, user make mistake, we have provided a message box to
acknowledge this error to user.
 E-Billing System

11.2 GANTT CHART

What is Gantt Charts?

The simplest planning uses bar charts that show each

activity in a system project and the amount of time activity
will take. The analyst first identifies each task and
estimates the amount of time needed for it. When this
information is transferred to the bar chart, the tasks are
listed from top to bottom on the left side of the chart in the
order in which they will be undertaken. Calendar time is
shown from left to right. A horizontal bar marked on the
chart of each task, indicating when it starts and when it is
expected to be completed.

Gantt Charts are most manageable when the project

consists of a limited number of tasks and activities.
Otherwise, the size of chart becomes unwieldy and includes
so many bars that it is difficult to use information.

Scheduling of our system using Gantt Chart is given

Below:

Activity Months
1 2 3 4 5 6

Project Development Plan

Requirement Study

Design

Development

Integration

System Testing

Documentation
 E-Billing System

Chapter 12

IMPLEMENTATION
 E-Billing System

Implementation is a process of having system personal

check out and new equipment into use, trained user installs
the new application and constructor any files of data
needed to use it.

Depending on the size of the organization that will be

involve in using. The application and the risk associated
with its use. System developers may choose to pilot or to
test the operation in only one are of the form, say in one
department with only one or two persons. Some times they
will run old and new system together to compare the result.

Each implementation strategy has its merits,

depending on the situation in which it’s consider regardless
of the implementation of the strategy used, developer
strive to ensure that the system initial use it’s trouble-free.
Since every system and its environment undergo continual
change, the information system should keep pace in this
senesce implementation is an on going process.
 E-Billing System

Chapter 13

LIMITATION OF
THE PROJECT
 E-Billing System

The new proposed system is such well developed that

the limitation of the system is insignificant. The proposed is
very flexible and gives desired output. It matches all the
current requirement even more than that. But still there are
some boundaries of the proposed system. We know the
system is being developed with the use of computer. The
proposed system is computerized E-Billing and Inventory
System.

Hence, to run the proposed system we need

computers, which are very expensive. So, at first to
implement the proposed system the company must
financially strong. Computers, printers and many more
equipment are necessary for proposed system. Moreover,
extra training is necessary for this system. The user of the
system must have enough knowledge to run the system.
So, extra training is required to conduct to make the user
literate for this system.

This system does not work where electricity and other

basic needs are not available.
 E-Billing System

If power supply is not there then the system will not work.

Chapter 14

FUTURE
 E-Billing System

ENHANCEMENT

 Export modules can be added later.

 All code will be like item code.

 Giving the information to the customers about new

item on their cell phones.
 E-Billing System

Chapter 15

BIBLOGRAPHY
 E-Billing System

SOFTWARE ENGINEERING
By Roger.S. Pressman

VISUAL BASIC.NET Black Book

By Evangeleous Petereous

ASP.Net Professional
By Wrox Publications

MSDN 2002
By Microsoft
E-Billing System