NIST COLLEGE

Affiliated To Tribhuvan University

Report on project: “Customer Billing Information System"

Submitted by: Submitted To:

Shreeti Shrestha Yubraj Dahal
Bsc.csit (6th sem)
24457

Submission Date: 2080/02/

ABSTRACT
This project is mainly developed for the project requirement of JAKIA NET to ensure the
development skill of knowledge. By this system customer of JAKIA NET we be get their
service faster and easiest way. This system generates a digital billing and information system.

ACKNOWLEDGEMENT
We would like to express our greatest appreciation to all the individuals who have helped
and supported us throughout the project. We are thankful to our subject teacher for his
ongoing support during the project, from initial advice, and encouragement, which led to the
final report of this project. We would also like to thank our lab teacher who was always there
in our computer lab for assistance.
A special acknowledgement goes to our group members who helped us in completing the
project by exchanging interesting ideas and sharing their experience.
At the end, we want to thank our friends who displayed appreciation to our work and
motivated us to continue our work.
Table of Contents
1. INTRODUCTION.............................................................................................................................4
2. AIM...................................................................................................................................................4
3. ADMINISTRATIVE MODULE.......................................................................................................4
4. SYSTEM STUDY AND ANALYSIS...............................................................................................4
5. EXISTING SYSTEM........................................................................................................................4
5.1 Existing Manual System..............................................................................................................4
5.2 Process of Existing System..........................................................................................................5
5.3Problems with Existing System....................................................................................................5
6. PROPOSED SYSTEM......................................................................................................................5
6.1 Aim of proposed system..............................................................................................................5
6.2 Advantage of proposed system....................................................................................................5
6.3 Feasibility study...........................................................................................................................5
7. PROPOSED SYSTEM DESIGN.......................................................................................................6
7.1 Introduction.................................................................................................................................6
7.1.1 Logical design........................................................................................................................7
7.1.2 Physical design......................................................................................................................7
8. IMPLEMENTATION OF MODEL...................................................................................................7
8.1 Database design...........................................................................................................................7
8.2 Entity Relationship Model...........................................................................................................8
8.3 Identifying the entities.................................................................................................................8
8.4 Entity relationship diagram.........................................................................................................8
8.5 Relationship Cardinality.............................................................................................................9
8.6 Entity Relationship Diagram......................................................................................................10
8.7 Database table structure.............................................................................................................10
8.8 System Description....................................................................................................................12
8.8.1 Dataflow diagram...............................................................................................................12
8.8.2 Symbol of DFD....................................................................................................................12
8.8.3 Data flow diagram of Customer billing information system...............................................13
8.8.4 Task scheduling...................................................................................................................13
8.8.5 System specification...........................................................................................................13
8.8.6 Project cost estimation.......................................................................................................14
8.8.7 Estimating Time..................................................................................................................14
8.9 Systems Implementation............................................................................................................14
9. SCREENSHOTS.............................................................................................................................15
10. CONCLUSION & UPCOMING FEATURES...............................................................................18
11. REFERENCE................................................................................................................................18
1. INTRODUCTION
The Domain Customer Billing System will be used for storing customer billing information.
The customer of JAKIA NET has increased day by day. This system will help them to
arrange all bill, information of client and all the necessary thing, what they need within a
short time. This system contain customer information, payment. Customer can also paid their
bill via bkash as well as cash/ cheque.

2. AIM
In the existing system all information of customer, billing data, they need to store by paper
and pen basis. Our proposed system gave them the facility to store in a data base. It will be
reliable for them to store/ find a lot of date without missing file and in a short time.

3. ADMINISTRATIVE MODULE
This module is the main module which performs all the main operations in the system. The
major operations in the system are:
 Storing Customer Information.
 Add and delete old /new customer.
 Update old /new customer.
 Create other admin /customer user
 Create monthly report
 Create year report

4. SYSTEM STUDY AND ANALYSIS

Systems analysis is a problem solving technique that decomposes a system into its
component pieces for the purpose of the studying how well those component parts work and
interact to accomplish their purpose. According to the Merriam-Webster dictionary, systems
analysis is the process of studying a procedure or business in order to identify its goals and
purposes and create systems and procedures that will achieve them in an efficient way.
Analysis and synthesis, as scientific methods, always go hand in hand; they complement one
another. Every synthesis is built upon the results of a preceding analysis, and every analysis
requires a subsequent synthesis in order to verify and correct its results.
This field is closely related to requirements analysis or operations research.

5. EXISTING SYSTEM
5.1 Existing Manual System
System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the problem? Analysis begins when a
user or manager begins a study of the program using existing system.
In the current system we need to keep a number of records related to the customer and want
to enter the details of the customer manually. In this system only the authority views the
information of the customer and they want to enter the details of the customer. This is time
consuming and has much cost.
5.2 Process of Existing System
All of activities of this company has done by paper pen basis.

5.3Problems with Existing System

Analyzing the existing system we find out the following problem:
 It is a manual and traditional system.
 It’s a non-technological system.
 Customer/admin do not get the information properly about net bill.
 Users cannot participate as frequently.
 Modern Technology is not available.

6. PROPOSED SYSTEM
6.1 Aim of proposed system
In our proposed system we have the provision for adding the details of the customer by
themselves. So the overhead of the company authorities and the staff is become less. Another
advantage of the system is that it is very easy to edit the details of the customer and delete a
customer when it found unnecessary. The marks of the customer are added in the database
and so customer can also view the monthly bill whenever they want.

6.2 Advantage of proposed system

Our proposed system has several advantages:
 Users can view all the information about monthly bill
 Easy to calculate all the monthly income
 Fast access to database
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction

All the manual difficulties in managing the customer details in a company have been rectified
by implementing computerization.

6.3 Feasibility study

Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization
by the development of a system. The impact can be either positive or negative. When the
positives nominate the negatives, then the system is considered feasible. Here the feasibility
study can be performed in two ways such as technical feasibility and Economical Feasibility.
The developing system must be justified by cost and benefit. Criteria to ensure that effort
is concentrated on project, which will give best, return at the earliest. One of the factors,
which affect the development of a new system, is the cost it would require.

Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also all the resources are already available, it give an indication of the
system is economically possible for development.
 6.3.1 Technical Feasibility
We can strongly say that it is technically feasible, since there will not be much difficulty
in getting required resources for the development and maintaining the system as well. All
the resources needed for the development of the software as well as the maintenance of the
same is available in the organization here we are utilizing the resources which are available
already.

6.3.2 Economical Feasibility

Development of this application is highly economically feasible .The organization needed
not spend much money for the development of the system already available. The only thing is
to be done is making an environment for the development with an effective supervision. I f
we are doing so , we can attain the maximum usability of the corresponding resources .Even
after the development , the organization will not be in condition to invest more in the
organization .Therefore , the system is economically feasible.
The following are some of the important financial questions asked during preliminary
investigation:
 The costs conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.

6.3.3 OPERATIONAL FEASIBILITY STUDIES

A Project Requirement Specification (PRS) is a description of a particular software
product, program or a set of programs that performs a set of functions in a target
environment. The PRS emerges from the components of problem or requirements analysis.
In the PRS, the function and performance allocated to software as part of system engineering
refined by establishing a complete information description, a detailed functional description,
a representation of system behavior, an indication of performance requirements and design
constraints, appropriate validation criteria and other information pertinent to requirements.
The PRS includes an introduction, information description, functional description, validation
criteria. The first phase of PRS is an introduction, which describe in the next section of this
report.

7. PROPOSED SYSTEM DESIGN

7.1 Introduction
Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering.
If the broader topic of product development blends the perspective of marketing, design, and
manufacturing into a single approach to product development, then design is the act of taking
the marketing information and creating the design of the product to be manufactured.
Systems design is therefore the process of defining and developing systems to satisfy
specified requirements of the user.
Until the 1990s systems design had a crucial and respected role in the data processing
industry. In the 1990s standardization of hardware and software resulted in the ability to build
modular systems. The increasing importance of software running on generic platforms has
enhanced the discipline of software engineering.
Object-oriented analysis and design methods are becoming the most widely used methods for
computer systems design. The UML has become the standard language in object-oriented
analysis and design. It is widely used for modeling software systems and is increasingly used
for high designing non-software systems and organizations.

7.1.1 Logical design

The logical design of a system pertains to an abstract representation of the data flows, inputs
and outputs of the system. This is often conducted via modelling, using an over-abstract (and
sometimes graphical) model of the actual system. In the context of systems design are
included. Logical design includes ER Diagrams.

7.1.2 Physical design

The physical design relates to the actual input and output processes of the system. This is laid
down in terms of how data is input into a system, how it is verified/authenticated, how it is
processed, and how it is displayed as In Physical design, the following requirements about the
system are decided.
 Input requirement,
 Output requirements,
 Storage requirements,
 Processing Requirements,
 System control and backup or recovery.
Put another way, the physical portion of systems design can generally be broken down into
three sub-tasks:
1. User Interface Design
2. Data Design
3. Process Design

User Interface Design is concerned with how users add information to the system and with
how the system presents information back to them. Data Design is concerned with how the
data is represented and stored within the system. Finally, Process Design is concerned with
how data moves through the system, and with how and where it is validated, secured and/or
transformed as it flows into, through and out of the system. At the end of the systems design
phase, documentation describing the three sub-tasks is produced and made available for use
in the next phase.

8. IMPLEMENTATION OF MODEL
8.1 Database design
Database design is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a data definition language, which can then be used
to create a database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are the
tables and view. In an object database the entities and relationships map directly to object
classes and named relationships. However, the term database design could also be used to
apply to the overall process of designing, not just the base data structures, but also the forms
and queries used as part of the overall database application within the database management
system.

8.2 Entity Relationship Model

Entity Relationship Model Also called an entity-relationship (ER) diagram. A graphical
representation of entities and their relationships to each other, typically used in computing in
regard to the organization of data within databases or information systems. An entity is a
piece of data-an object or concept about which data is stored.
A relationship is how the data is shared between entities. There are three types of
relationships between entities.

8.3 Identifying the entities

Identifying the entities according to the conceptual design:
 Administrator
 Users
 Add/delete customer
 Payment
 Report

8.4 Entity relationship diagram

In software engineering, an entity–relationship model (ER model) is a data model for
describing the data or information aspects of a business domain or its process requirements,
in an abstract way that lends itself to ultimately being implemented in a database such as a
relational database. The main components of ER models are entities (things) and the
relationships that can exist among them.

Entity–relationship modeling was developed by Peter Chen and published in a 1976 paper.
However, variants of the idea existed previously, and have been devised subsequently such as
super type and subtype data entities and commonality relationships.

Entity: An entity is any singular, identifiable and separate object. It refers to individuals,
organizations, systems, bits of data or even distinct system components that are considered
significant in and of themselves.

Attribute: attribute is a piece of information that describe a particular entity.a attribute is

describe by a oval.

Relationship: a relationship is a logical linkage between two or more entities.

8.5 Relationship Cardinality
Relationship cardinality refers to the number of entity instances involved in the relationship.
The cardinality ratio are:
 1:1(One to One)
 1:N(One to Many)
 M:N(Many to Many)

1. One-to-One
One instance of an entity (A) is associated with one other instance of another entity (B). For
example, in a database of employees, each employee name (A) is associated with only one
social security number (B).

2. One-to-Many
One instance of an entity (A) is associated with zero, one or many instances of another entity
(B), but for one instance of entity B there is only one instance of entity A. For example, for a
company with all employees working in one building, the building name (A) is associated
with many different employees (B), but those employees all share the same singular
association with entity A.

3. Many-to-Many
One instance of an entity (A) is associated with one, zero or many instances of another entity
(B), and one instance of entity B is associated with one, zero or many instances of entity A

Primary key:
A primary key is an attribute or collection of attributes that allow us to identify an entity
uniquely.
Naturally a underline (PK) is using in attribute to identifying primary key.

Foreign key:
A foreign key is an attribute of a relation which refers to an existing attribute of another
relationship.
8.6 Entity Relationship Diagram

8.7 Database table structure

1. Users

2. Customers
3. Dues

4. Payment

5.Staff
8.8 System Description

8.8.1 Dataflow diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. A DFD is often used as a preliminary step
to create an overview of the system, which can later be elaborated. [2] DFDs can also be used
for the visualization of data processing (structured design).
A DFD shows what kind of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of process or information about whether processes will operate
in sequence or in parallel (which is shown on a flowchart)

8.8.2 Symbol of DFD

External Entity
An external entity can represent a human, system or subsystem. It is where certain data
comes from or goes to. It is external to the system we study, in terms of the business process.
For this reason, people used to draw external entities on the edge of a diagram.

Process
A process is a business activity or function where the manipulation and transformation of
data takes place. A process can be decomposed to finer level of details, for representing how
data is being processed within the process.

Data Store
A data store represents the storage of persistent data required and/or produced by the process.
Here are some examples of data stores: membership forms, database table, etc.

Data Flow
A data flow represents the flow of information, with its direction represented by an arrow
head that shows at the end(s) of flow connector.
 8.8.3 Data flow diagram of Customer billing information system

8.8.4 Task scheduling

Project scheduling is an activity of distributing the estimated efforts within the planned
project duration. There are some basic rules for project scheduling. They are as follows:
 Compartmentalization
 Interdependency
 Time allocation
 Effort validation
 Defined responsibility
 Defined outcomes

8.8.5 System specification

Hardware requirements
Mother board : Dual core
Processor : 2.0 GHZ clock speed
RAM : 512 MB
Hard disk : 20 GB
 Monitor : Samsung
Keyboard : 104 keys
Software requirement
Operating system : Windows 7
Front end : Java Script, HTML, CSS
Back end : PHP, JQUERY, Java Script
Report : Microsoft office

8.8.6 Project cost estimation

Personal cost:
Our team completed this project. We are three member work this project
3*1000 = 3000 BDT

Project cost
 Hardware accessories cost = 30000 BDT
 Software accessories cost = 5000 BDT
 Electricity and other bil = 2000 BDT
Total cost = (3,000+30,000+5,000+2,000)
= 40,000 BDT

8.8.7 Estimating Time

Project →Phases → Activities → Steps

Week
Sl. Activity Detailed Activity required
Conduct interviews 0.5
Administrator questionnaires 1
1 Data Gathering Read Company Reports 1
Introduce Prototype 2
Observe reactions to Prototype 1
2 Data Flow & Decision Analysis Analyze Data flow 3
Perform Cost/ Benefit analysis 0.5
3 Proposal Preparation Prepare Proposal 0.5
Present Proposal 0.5

8.9 Systems Implementation

Systems implementation is the construction of the new system and the delivery of that system
into production (that is, the day-to-day business or organization operation
The construction phase does two things: builds and tests a functional system that fulfills
business or organizational design requirements, and implements the interface between the
new system and the existing production system. The project team must construct the
database, application programs, user and system interfaces, and networks. Some of these
elements may already exist in your project or be subject to enhancement.
System testing:
We analyze and build our system and after that we test our project. We show our project to
the client and our course instructor.

9. SCREENSHOTS
10. CONCLUSION & UPCOMING FEATURES
CONCLUSION
Our project is only a humble venture to satisfy the needs in an Institution. Several user
friendly coding have also adopted. This package shall prove to be a powerful package in
satisfying all the requirements of the organization.

The objective of software planning is to provide a frame work that enables the manager
to make reasonable estimates made within a limited time frame at the beginning of the
software project and should be updated regularly as the project progresses.

UPCOMING FEATURES
 Database security system – We do not implement any database backup process right now.
At present it will done by manual process.
 Online payment – In future subs will be able to pay by online system. Like credit card /
debit card/ online banking etc.
 Individual login I’d & password – Now there is a common I’d & password for all staff.
But we will provide individual I’d & password for every staff.

11. REFERENCE
Bibliography
1) http://www.javaworld.com/javaworld/jw-01-1998/jw-01-bookreview.html
2) Database Programming with JDBC and Java by O'Reilly
3) Head First Java 2nd Edition
4) http://www.jdbc-tutorial.com/
5) Java and Software Design Concepts by Après