Академический Документы
Профессиональный Документы
Культура Документы
SUBMITTED BY:
1. HARSHAL DALVI.
2. SHUBHAM KASAR.
3. PRIYANKA DEORE.
4. BHAGYASHRI KHAIRNAR.
Scope
2 01
Requirement Analysis
4.1 Functional Requirement 02
3
4.2 Non Functional Requirement
Data Modeling
a. ER Diagram
b. Relational model 03
4
c. Normalization
Software Requirements
a. Front End
b. Back End
5 04
c. Database Connectivity
Scope
This application is basically written as a solution to the drawbacks of existing
system. This application can be used as a real world application and by any
organization. It’s could be used as a general application with few minor
modifications.
Purpose
The purpose of this application is to develop “EBS” (Electronic Billing System),
which is a web application which provides a service to all the customers and
employees to deal with the transactions online.
Page: 1
Requirement Analysis
In software engineering, a functional requirement defines a function of a software
system or its component. A function is described as a set of inputs, the behavior, and
outputs. Functional requirements may be calculations, technical details, data
manipulation and processing and other specific functionality that show how a use case
is to be fulfilled. They are supported by non-functional requirements, which impose
constraints on the design or implementation (such as performance requirements,
security, or reliability).As defined in requirements engineering, functional
requirements specify particular behaviors of a system. This should be contrasted with
non-functional requirements which specify overall characteristics such as cost and
reliability
Functional Requirements-
Page: 2
Data Modeling
ER diagram
Relational Modeling
Page: 3
Software Requirements
Front End:-
- jdk-8u181-windows-x64(JAVA)
- NetBeans 8.2 IDE
Back End:-
-MySQL 8.0.12
Database Connectivity:-
-MySQL connector.jar
-jdbc.odbc connector
Page: 4
GUI (Graphical User Interface)
Front Page
Page: 5
Administrator Login
Customer Login
Page: 6
Help
Page: 7
Source Code
1) Login_Form Code :
package Billing_System;;
import java.awt.Toolkit;
import java.awt.event.WindowEvent;
import java.sql.*;
import javax.swing.*;
import java.util.logging.Level;
import java.util.logging.Logger;
Page: 8
if (uname.equalsIgnoreCase(usertxt.getText()) && passwd.equals(passtxt.getText()))
{
JOptionPane.showMessageDialog(null,"Login Successful");
close();
MainForm mf = new MainForm();
mf.setVisible(true);
}
else
{
JOptionPane.showMessageDialog(null,"Incorrect UserName or Password...
Please Try again");
usertxt.setText("");
passtxt.setText("");
}
} catch (Exception ex) {
JOptionPane.showMessageDialog(null,"Incorrect UserName or Password... Please Try
again");
usertxt.setText("");
passtxt.setText("");
}
}
private void registerbtnActionPerformed(java.awt.event.ActionEvent evt) {
close();
Register R=new Register();
R.setVisible(true);
}
private void cancelbtnActionPerformed(java.awt.event.ActionEvent evt) {
this.hide();
Frontpage F;
F = new Frontpage();
F.setVisible(true);
}
Page: 9
Testing
Test case Expected actual
S.No Explanation Remarks
Name output output
Username &
Username & Username &
Password
2 Authentication Password Password is Fail
should not
confirmation not matched
matched
Email should
Email should Email not
6 Acceptance have correct Fail
not accepted accepted
format
Consumer
Enter Correct
number Consumer is
7 Authentication consumer Pass
should accepted
number
accepted
Page: 10
Consumer
Enter Correct
number Consumer is
8 Authentication consumer Fail
should not present
number
present
Cannot leave
Field should Field is not
10 Field any field Pass
not empty Empty
empty
Cannot leave
Field should Field is
11 Field any field Fail
empty Empty
empty
Bill Details
Print the Bill Bill Details
12 Print should be Pass
Details are printed
printed
Mobile no.
Mobile No. Mobile no. Is
13 Mobile No Should be of Pass
Is 10 Digit of 10 digit
10 digit
Mobile no.
Mobile No. Should be Mobile no. Is
14 Mobile No Fail
Is 10 Digit not of 10 not 10 digit
digit
Reading Reading
Reading
should be should
15 Update reading updated Pass
enter in updated
successfully
database successfully
Page: 11
Conclusion
We have been given the problem of Billing of Electricity Consumers. Earlier the
Billing process is manually calculated by using the database small tolls and small
scale packages at their desktop. In our project “ENERGY BILLING SYSTEM”
we have automated the entire billing system is Online and centralized with all
offices which they have in the central power distribution company limited.
In Consumer Management, I have tracked all the information of the consumer and
have given the privileged modifications, changes.
Page: 12