Professional Documents
Culture Documents
PROJECT REPORT ON
ROLL NO : 6043
NAME : A.RAJAGUHAN
CLASS : XII
PGT (CS)
TIRUPPUR DIST
TAMILNADU
1
SAINIK SCHOOL AMARAVATHINAGAR
CERTIFICATE
in the subject Computer Science (083) laid down in the regulations of CBSE for the
Amaravathinagar on______________.
(PM Jigajinni)
PGT Comp Sci
Master IC
Examiner:
Name: _______________
Signature:
2
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 16
09 OUTPUT 19
10 TESTING 20
12 BIBLIOGRAPHY 24
ACKNOWLEDGEMENT
3
Apart from the efforts of me, the success of any project depends largely on
the encouragement and guidelines of many others. I take this opportunity to express
my gratitude to the people who have been instrumental in the successful completion
of this project.
I express deep sense of gratitude to almighty God for giving me strength for
the successful completion of the project.
The guidance and support received from all the members who contributed
and who are contributing to this project, was vital for the success of the project. I am
grateful for their constant support and help.
4
PROJECT ON ELECTRICITY BILLING SYSTEM
INTRODUCTION
Number and displays it. The user can use the registration number to view their
Registered details. This programme can be used only if the Login ID and the
Password is correct.
The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
5
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really
wants to stand against today’s merciless competition where not to wise saying “to
err is human” no longer valid, it’s out-dated to rationalize your mistake. So, to keep
pace with time, to bring about the best result without malfunctioning and greater
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially hadto maintain a lot of ledgers and a lot of paperwork has
to be done but now software producton this organization has made their work
fasterand easier. Now only this software has to beloaded on the computer and work
can be done.
This prevents a lot of time and money. Thework becomes fully automated and
any information regarding the organization can beobtained by clicking the button.
6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
7
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
8
SYSTEM CONCEPT DEVELOPMENT PHASE
9
PLANNING PHASE
10
of operations, system security, verification and validation, and systems engineering
management planning.
REQUIREMENTSANALYSIS PHASE
This phase formally defines the detailed functional user requirements using
high-level requirements identified in the Initiation, System Concept, and Planning
phases. It also delineates the requirements in terms of data, system performance,
security, and maintainability requirements for the system. The requirements are
defined in this phase to a level of detail sufficient for systems design to proceed.
They need to be measurable, testable, and relate to the business need or
opportunity identified in the Initiation Phase. The requirements that will be used to
determine acceptance of the system are captured in the Test and Evaluation
MasterPlan.
Further define and refine the functional and data requirements and document
them in the Requirements Document,
Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what information is
generated, who generates it, where does the information go, and who
processes it),
Develop detailed data and process models (system inputs, outputs, and the
process.
Develop the test and evaluation requirements that will be used to determine
acceptable system performance.
DESIGN PHASE
11
then expand design layouts as they identify and link smaller subsystems and
connections. Using a bottom-up approach, designers first identify and link minor
program components and interfaces, then expand design layouts as they identify
and link larger systems and connections. Contemporary design techniques often use
prototyping tools that build mock-up designs of items such as application screens,
database layouts, and system architectures. End users, designers, developers,
database managers, and network administrators should review and refine the
prototyped designs in an iterative process until they agree on an acceptable design.
Audit, security, and quality assurance personnel should be involved in the review
and approval process. During this phase, the system is designed to satisfy the
functional requirements identified in the previous phase. Since problems in the
design phase could be very expensive to solve in the later stage of the software
development, a variety of elements are considered in the design to mitigate risk.
These include:
12
DEVELOPMENT PHASE
13
Testing as a deployed system with end users working together with contract
personnel
IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the
user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives established
during the planning phase. Implementation includes user notification, user training,
installation of hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues until the
system is operating in production in accordance with the defined user requirements.
14
FLOW CHART FOR LOGIN TABLE
START
15
SOURCE CODE
conn=sql.connect(host='localhost',user='root',passwd='manager'
,database='EBS')
if conn.is_connected():
print("successfully connected")
c1=conn.cursor()
print('************************WELCOME TO ELECTRICITY
BILLING SYSTEM************************')
print(dt.datetime.now())
print('1.NEW USER')
print('2.EXISTING USER')
print('3.EXIT')
if choice1==1:
if password==confirmpasswd:
16
info1="insert into newuser
values('{}','{}','{}')".format(username,password,confirmpasswd
c1.execute(info1)
conn.commit()
else:
print('Try again')
elif choice1==2:
password='{}'".format(username,password)
c1.execute(info2)
data=c1.fetchall()
if any(data):
print('************************WELCOME TO
print("1.ACCOUNT SETTINGS")
print("2.TRANSACTION")
print("4.GRAPHICAL REPRESENTATION")
print('5.EXIT')
17
choice2=int(input('ENTER YOUR CHOICE'))
if choice2==1:
print('1.NEW CUSTOMER')
if choice12==1:
accountno=random.randrange(1000000,999
9999,10)
NAME :')
BRANCH :')
NUMBER :'))
values({},'{}','{}','{}','{}',{},
{},'{}','{}')".format(accountno,bankname,bankbranch,name,addre
ss,areacode,phoneno,email,boxid)
c1.execute(info2)
18
conn.commit()
or no)")
if V=='yes':
continue
else:
break
elif choice12==2:
NUMBER:")
info6=c1.execute("delete from
info7=c1.execute("delete from
where username='{}'".format(use))
c1.execute(info6)
c1.execute(info7)
c1.execute(info8)
conn.commit()
or no)")
if V=='yes':
19
continue
else:
break
elif choice2==2:
number :'))
accountno="+str(accountno)
c1.execute(info10)
data3=c1.fetchall()
paid=row[6]
if paid=='yes':
bill')
break
else:
unit=random.randint(0,101)
',unit,'units of electricity.')
ruppees')
amount=150*unit
toda=dt.date.today()
deadline=dt.date(2020,1,30)
20
if deadline<toda:
fine=(toda-deadline)*30
totamt=amount+fine
GST=(15/100)*totamt
totalamt=totamt+GST
print('Pleae payup
transact")
if p=="YES"or 'Yes'or'yes':
print("Transaction
successful")
bill")
else:
sooner')
else:
totamt=0
GST=(15/100)*amount
totalamt=amount+GST
print('Pleae payup
21
p=input("Please Enter YES to
transact")
if p=="YES":
print("Transaction
successful")
bill")
else:
sooner')
values({},{},'{}',{},{},
{},'{}')".format(accountno,unit,toda,totamt,GST,totalamt,p)
c1.execute(info3)
conn.commit()
or no)")
if V=='yes':
continue
else:
break
elif choice2==3:
number :'))
22
info4="select * from AddNewCustomer where
accountno=" + str(accountno)
c1.execute(info4)
data1=c1.fetchall()
print("bankname:",row[1])
print("bankbranch:",row[2])
print("Person name:",row[3])
print("Residential address:",row[4])
print("area code:",row[5])
print("phone number:",row[6])
print("email:",row[7])
accountno=" + str(accountno)
c1.execute(info5)
data2=c1.fetchall()
GST:",row[3])
print("GST=",row[4])
23
print("amount to be paid including
GST:",row[5])
no)")
if V=='yes':
continue
else:
break
elif choice2==4:
Transaction"
c1.execute(info9)
L1,L2,=[],[]
for i in c1.fetchall():
L1.append(i[0])
L2.append(i[1])
plt.plot(L1,L2)
plt.title("GRAPH")
plt.show()
no)")
if V=='yes':
continue
else:
break
elif choice2==5:
24
print( "T
break
c='yes'
else:
break
no)")
else:
print( "THANK
V='no'
elif choice1==3:
print( "THANK
c='no'
break
else:
25
print("invalid choice")
else:
VISIT AGAIN!!!!")
c='no'
conn =
sql.connect(host='localhost',user='root',password='manager',da
tabase='EBS')
if conn.is_connected():
print("successfully connected")
c1=conn.cursor()
AddNewCustomer(accountno))')
print("table created")
26
OUTPUT
27
TESTING
28
process, however the most test effort is employed after the requirements have been
defined and coding process has been completed.
TESTING METHODS
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that
a test engineer takes when designing test cases.
SPECIFICATION-BASED TESTING
The black box tester has no "bonds" with the code, and a tester's perception
is very simple: a code must have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers don't. But, on the other
hand, black box testing has been said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
29
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these)
White box testing methods can also be used to evaluate the completeness of
a test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.
30
HARDWARE AND SOFTWARE REQUIREMENTS
31
VI. CD/DVD r/w multi drive combo: (If back up required)
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
32
BIBLIOGRAPHY
***
33