Scribd
Upload
99 views28 pages

Final

This document describes an energy billing system web application. The objectives of the application are to provide an easy to use, accurate, secure and reliable system for electricity billing. The application allows users to manage consumer details, view bills and payments. It uses a three-tier architecture with presentation, application and data tiers. Technologies used include Java, HTML, servlets and Java server pages. Use case and sequence diagrams illustrate the functionality and flow of the application.

Uploaded by

Debu Tripathy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
99 views28 pages

Final

This document describes an energy billing system web application. The objectives of the application are to provide an easy to use, accurate, secure and reliable system for electricity billing. The application allows users to manage consumer details, view bills and payments. It uses a three-tier architecture with presentation, application and data tiers. Technologies used include Java, HTML, servlets and Java server pages. Use case and sequence diagrams illustrate the functionality and flow of the application.

Uploaded by

Debu Tripathy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 28

ENERGY BILLING SYSTEM

WEB BASED APPLICATION

Debu Tripathy (04010402709) C.S.E. 4th Year

INTRODUCTION

Energy Billing System is an Executive Information System that could be used for entering, calculating and monitoring the Billing details of the Electricity Consumers.

It provides environment to maintain the consumer details starting from getting new connection,

receiving bill, payments etc., and performance


information to the management.

OBJECTIVES

Easy to use, effective and efficient Accurate results Easy maintenance

Fast access
More feasibility More secure Provides high consistency More reliable

PURPOSE AND SCOPE

The purpose is to develop Electronic Billing System, which is a web application which provides a service to all the customers and employees to deal with the transactions.

This can be used as a real world application and by any organization and also as a general application with

few minor modifications.

MODULES DESCRIPTION

Login Consumer Details Query Consumer

Meter Details
Billing

REQUIREMENTS
Hardware RAM: 256 MB or above HARD DISK: 20 GB or above PROCESSOR: Intel Pentium IV, 2GHZ or above Software Java 5.0 or later Net Beans IDE, Apache Tomcat ODBC administrator Windows 32 bit

TECHNOLOGIES USED

JAVA:

Platform

independent,

object-oriented

and

innovative

programming language consisting of JVM and Java API.

HTML:

Hyper Text Mark-up Language, a means to describe the structure of text-based information in a document.

SERVLETS:

Extends the functionality of a web server and for accessing existing business systems.

TECHNOLOGIES (CONTINUED.)

Servlet Containers:

Specialized web server that supports Servlet execution.

JAVA SERVER PAGES (JSP):

Text page document that describes how to process request to create a response.

ARCHITECTURE

Three-tier is a client-server architecture in which the user interface, functional process logic, computer data storage and data access are developed and maintained as independent modules.

Presentation Tier:

Displays information, communicates with other tiers by outputting results to the browser/client tier and all other tiers in the network.

ARCHITECTURE (CONTINUED.)

Application Tier (Business Logic/Logic Tier):

Controls an applications functionality by performing detailed processing.

Data Tier:

Consists of Database Servers. Here information is stored and retrieved.

USE CASE DIAGRAM


HOMEPAGE:
sign in

login

clerk consumer management

ERO

user

revenue collection

billing & accounting

reports

logoff

USE CASE DIAGRAM


CONSUMER MANAGEMENT:
EBS

new consmer acquisition

ERO modify consumer

consmer delete consumer

query consumer

meter change

meter part change

maintains current data

SEQUENCE DIAGRAM
sign in user : user clerk : clerk 1: c_details 2: ERO no,circle id log in consumer management revenue collection billing & accounting reports log off administrator : ERO

3: uname,pwd 4: validated 5: manage 6: updated 7: r_details 8: receipt request 9: online/offline receipt issued 10: b_details 11: bill request 13: rp_details 14: req_report 15: report issued 16: logged off spot billing m/c

12: bill issued

17: logged out

CLASS DIAGRAM

ACTIVITY DIAGRAM

homepage

consumer management

revenue collection

billing and accounting

reports

online receipt RC no, identity reject

offline receipt

receipt cancel

accept

log off

SCREEN SHOTS

CONCLUSION

Earlier the billing process was manually calculated by using the database small tools and small scale packages at their desktop.

In my project ENERGY BILLING SYSTEM I have automated the entire billing system.

I am looking for more resources to move into this

direction and want to make a complete product that


works effectively and efficiently and it is not very much problematic.

FEEDBACK

User is ultimate destination, where the success or failure of any product is expected to be decided.

A person (user) far away from the programming side

of the project has a good knowledge of the system, so


he can test the possibilities for which the project could be a failure.

BIBLIOGRAPHY

Taking something entirely new as a project is always problematic as far as the availability of resources is concerned. I tried to get some good and feasible books for the topic, from library and friends.

Technical References: www.wikipedia.com www.youtube.com www.netbeans.org

THANK Y

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy