Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Project 36

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 33

PROJECT ON TELEPHONE BILLING MANAGEMENT SYSTEM

INTRODUCTION

The purpose of the project is to present the requirement of the Computerization of


Telephone Billing System. The project thus calculates the telephone bills
automatically. It does almost every work which is related to automatic telephone
billing connection system via- new connection , customer record modification,
viewing customer records & all works related to rate of bills, meter readings in
addition to bill calculation and bill generation. “Telephone Billing System ” is
developed as per seeing the increasing requirement to speed up the work and
incorporate a new work culture. Thus a new software has been proposed to reduce
manual work, improving work efficiency, saving time and to provide greater flexibility
and user-friendliness as the system previously followed was totally manual one with
lots of errors.
OBJECTIVES OF THE PROJECT

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

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when developing

small to medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct a research or applied Computer

Science project, requiring writing and presentation skills which exemplify

scholarly style in computer science.

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 outdated to rationalize your mistake. So, to keep

pace with time, to bring about the best result without malfunctioning and greater

efficiency so to replace the unending heaps of flies with a muchsophisticated hard

disk of the computer.

One has to use the data management software. Software has been an ascent

in customization various organizations. Many software products working are now in

markets, which have helped in making the organizations work easier and efficiently.

Data management initially had to maintain a lot of ledgers and a lot of paperwork has

to be done but now software production in this organization has made their work

faster and easier. Now only this software has to be loaded on the computer and work

can be done.

This prevents a lot of time and money. The work becomes fully automated

and any information regarding the organization can be obtained by clicking the

button. Moreover, now it’s an age of computers and automating such an organization

gives the better look.


SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that


divides complex projects into smaller, more easily managed segments or phases.
Segmenting projects allows managers to verify the successful completion of project
phases before allocating resources to subsequent phases.
Software development projects typically include initiation, planning,design,
development, testing, implementation,and maintenance phases. However, the
phases may be divided differently depending on the organization involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation, concept-development,and
planning phases. End users of the system under development should be involved in
reviewing the output of each phase to ensure the system is being built to deliver the
needed functionality.

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an


opportunity.
The purpose of the Initiation Phase is to:

● Identify and validate an opportunity to improve business accomplishments of

the organization or a deficiency related to a business need.

● Identify significant assumptions and constraints on solutions to that need.


● Recommend the exploration of alternative concepts and methods to satisfy

the need including questioning the need for technology, i.e., will a change in
the business process offer a solution?

● Assure executive business and executive technical sponsorship. The Sponsor

designates a Project Manager and the business need is documented in a


Concept Proposal. The Concept Proposal includes information about the
business process andthe relationship to the Agency/Organization.

● Infrastructure and the Strategic Plan. A successful Concept Proposal results

in a Project Management Charter which outlines the authority of the project


manager to begin
the project.

Careful oversight is required to ensure projects support strategic business


objectives and resources are effectively implemented into an organization's
enterprise architecture. The initiation phase begins when an opportunity to add,
improve, or correct a system is identified and formally requested through the
presentation of a business case. The business case should, at a minimum, describe
a proposal’s purpose, identify expected benefits, and explain how the proposed
system supports one of the organization’s business strategies. The business case
should also identify alternative solutions and detail as many informational, functional,
and network requirements as possible.
SYSTEM CONCEPT DEVELOPMENT PHASE
The System Concept Development Phase begins after a business need or
opportunity is validated by the Agency/Organization Program Leadership and the
Agency/Organization CIO.
The purpose of the System Concept Development Phase is to:

● Determine the feasibility and appropriateness of the alternatives.

● Identify system interfaces.

● Identify basic functional and data requirements to satisfy the business need.
● Establish system boundaries; identify goals, objectives, critical success

factors, and performance measures.

● Evaluate costs and benefits of alternative approaches to satisfy the basic

functional requirements

● Assess project risks

● Identify and initiate risk mitigation actions, andDevelop high-level technical

architecture, process models, data models, and a concept of operations. This


phase explores potential technical solutions within the context of the business
need.

● It may include several trade-off decisions such as the decision to use COTS

software products as opposed to developing custom software or reusing


software components, or the decision to use an incremental delivery versus a
complete, onetime deployment.

● Construction of executable prototypes is encouraged to evaluate technology

to support the business process. The System Boundary Document serves as


an important reference document to support the Information Technology
Project Request (ITPR) process.

● The ITPR must be approved by the State CIO before the project can move

forward.

PICTORIAL REPRESENTATION OF SDLC:


PLANNING PHASE

The planning phase is the most critical step in completing development,


acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, isnecessary to coordinate activities and manage project risks
effectively. The depth and formality of project plans should be commensurate with
the characteristics and risks of a given project. Project plans refine the information
gathered during the initiation phase by further identifying the specificactivities and
resources required to complete a project.
A critical part of a project manager’sjob is to coordinate discussions between
user, audit, security, design, development, and network personnel to identify and
document as many functional, security, and networkrequirements as possible.
During this phase, a plan is developed that documents the approach to be used and
includes a discussion of methods, tools, tasks, resources, project schedules, and
user input. Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning, concept
of operations, system security, verification and validation, and systems engineering
management planning.

REQUIREMENTS ANALYSISPHASE

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 alevel 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.

The purposes of this phase are to:

● 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

The design phase involves converting the informational, functional, and


network requirements identified during the initiation and planning phases into unified
design specifications that developers use to scriptprograms during the development
phase. Program designs are c onstructed in various ways. Using a top-down
approach, designers first identify and link majorprogram components and interfaces,
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:

● Identifying potential risks and defining mitigating design features.

● Performing a security risk assessment.

● Developing a conversion plan to migrate current data to the new system.

● Determining the operating environment.

● Defining major subsystems and their inputs and outputs.

● Allocating processes to resources.

● Preparing detailed logic specifications for each software module. The result is

a draft System Design Document which captures the preliminary design for
the system.

● Everything requiring user input or approval is documented and reviewed by

the user. Once these documents have been approved by the Agency CIO and
Business Sponsor, the final System Design Document is created to serve as
the Critical/Detailed Design for the system.

● This document receives a rigorous review byAgency technical and functional

representatives to ensure that it satisfies the business requirements.


Concurrent with the development of the system design, the Agency Project
Manager begins development of the Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.
DEVELOPMENT PHASE

The development phase involves converting design specifications into


executable programs. Effective development standards include requirements that
programmers and other project participants discuss design specifications before
programming begins. The procedures help ensure programmers clearly
understand program designs and functional requirements. Programmers use
various techniques to develop computer programs. The large transaction oriented
programs associated with financial institutions have traditionally been developed
using procedural programming techniques. Procedural programming involves the
line-by-line scripting of logical instructions that are combined to form a
program.Effective completion of the previous stages is a key factor in the success
of the Development phase. The Development phase consists of:

● Translating the detailed requirements and design into system components.

● Testing individual elements (units) for usability.

● Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

● Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional requirements,
as defined in the functional requirements document, are satisfied by the
developed or modified system. OIT Security staff assess the system security
and issue a security certification and accreditation prior to
installation/implementation.

Multiple levels of testing are performed, including:


● Testing at the development facility by the contractor and possibly supported

by end users

● Testing as a deployed system with end users working together with contract

personnel

● Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing,a final Independent Verification &


Validation evaluation is performed and all documentation is reviewedand
accepted prior to acceptance of the system.

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.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued


performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can be
effectively adapted to respond to the organization’s needs. When modifications or
changes are identified, the system may reenter the planning phase.

The purpose of this phase is to:


● Operate, maintain, and enhance the system.

● Certify that the system can process sensitive information.

● Conduct periodic assessments of the system to ensure the functional

requirements continue to be satisfied.

● Determine when the system needs to be modernized, replaced, or retired.

CS PROJECT FINAL DRAFT: TELEPHONE BILLING SYSTEM

**********************************************************************************

import mysql.connector as mq

def menu():
print("\t\t\t ONLINE TELEPHONE BILLING SYSTEM")
print("\t\t\t ===============================\n")
print("\t\t\t\t MAIN MENU")
print("\t\t\t\t =========\n")
print("\t\t1. Register User \t 2. Search customer \n")
print("\t\t3. Update Customer \t 4. Generate Bill \n")
print("\t\t5. Delete Customer \t 6. Display records \n")
print("\t\t7. Help \t 8. Exit \n")

def register():
print("\n\t\t\tNew Customer Registration.....")
print("\t\t\t==============================\n")
print("Details of the customer are phone_no, name, address, aadhar_no respectively:")
ph=input("Enter your Phone number:")
n=input("Enter your Name:")
add=input("Enter your Address:")
adh=input("Enter your 12-digit Aadhar Card number:")

con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="insert into customer(Phno,name,address,aadhar_no,ftp)values({},'{}','{}','{}',
{})".format(ph,n,add,adh,0)
cur.execute(query)
con.commit()
print("\nSuccessfully Registered the user.....")
con.close()

def search():
print("\n\t\t\tSearch Customer.....")
print("\t\t\t====================\n")
print("Details of the customer are phone_no, name, address, aadhar_no, bill,status(paid
or unpaid), first time payer(yes:0/no:1) respectively:")
ph=input("\nEnter your phone number:")

con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="select * from customer where Phno={}".format(ph)
cur.execute(query)
res=cur.fetchall()
if res==[]:
print("Customer does not exist.....")
else:
print(res)
con.close()

def modify():
print("\n\t\t\tUpdate Customer Data.....")
print("\t\t\t=========================\n")
ph=input("\nEnter your phone number:")

con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="select * from customer where Phno={}".format(ph)
cur.execute(query)
res=cur.fetchall()
if res==[]:
print("Customer does not exist.....")
else:
print("1. Name\n2. Address\n3. Aadhar_no")
ch=int(input("Enter choice to update:"))
if ch==1:
n=input("Enter new name:")
query="update customer set name='{}' where phno={}".format(n,ph)
cur.execute(query)
con.commit()
print("Successfully updated name.....")
elif ch==2:
add=input("Enter new address:")
query="update customer set address='{}' where phno={}".format(add,ph)
cur.execute(query)
con.commit()
print("Successfully updated address.....")
elif ch==3:
adr=input("Enter new aadhar_no:")
query="update customer set aadhar_no='{}' where phno={}".format(adr,ph)
cur.execute(query)
con.commit()
print("Successfully updated aadhar_no.....")
else:
print("Please choose the correct choice.....")
con.close()

def billing():
print("\t\t\tBilling.....")
print("\t\t\t============\n")
ph=input("\nEnter your phone number:")

con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="select * from customer where phno={}".format(ph)
cur.execute(query)
res=cur.fetchall()
if res==[]:
print("Customer does not exist.....")
else:
calls=int(input("Enter number of calls:"))
bill=0
finalbill=0
ftime=0
next50to100_=0
next100to150_=0
over150_=0
if res[0][6]==0:
ftime=0
if calls>150:
bill=bill+(calls-150)*3 + 50*2 + 50*1
next50to100_=50
next100to150_=100
over150_=(calls-150)*3

elif 100<calls<=150:
bill=bill+(calls-100)*2 + 50*1
next100to150_=(calls-100)*2
next50to100_=50

elif 50<calls<100:
bill=bill+(calls-50)*1
next50to100_=(calls-50)*1

elif res[0][6]==1:
ftime=1
if calls>150:
bill=bill+(calls)*3
over150_=calls*3

elif 100<calls<150:
bill=bill+(calls)*2
next100to150_=calls*2
elif calls<100:
bill=bill+(calls)*1
next50to100_=calls*1

print("\t\t\tBilling.....")
print("\t\t\t============\n")
old_bill=res[0][4]
if res[0][5]!="Paid":
print("\n\t\tPending bill amount:",old_bill)
if ftime==0:
print("\n\t\tFirst 50 free calls:",0)
print("\n\t\tNext 51-100 calls@1.0Rs/call:",next50to100_)
print("\n\t\tNext 100-150 calls@2.0Rs/call:",next100to150_)
print("\n\t\tNext over 150 calls@3.0Rs/call:",over150_)
else:
print("\n\t\tTotal calls",calls)
if calls>150:
print("\n\t\tover 150 calls is Rs3.0/call =",over150_)
elif 100<calls<150:
print("\n\t\tbetween 150-100 calls is Rs2.0/call =",next100to150_)
else:
print("\n\t\tbelow 100 calls is Rs1.0/call =",next50to100_)

print("\n\t\tNew bill amount: ",bill)


print("\n\t\t========================")
finalbill=old_bill+bill
print("\t\tTotal amount to pay: ",finalbill)
else:
print("\n\t\tLast paid bill amount",old_bill)
print("\n\t\tTotal calls",calls)
if calls>150:
print("\n\t\tover 150 calls is Rs3.0/call =",over150_)
elif 100<calls<150:
print("\n\t\tbetween 150-100 calls is Rs2.0/call =",next100to150_)
else:
print("\n\t\tbelow 100 calls is Rs1.0/call =",next50to100_)

print("\n\t\tNew bill amount: ",bill)


print("\n\t\t========================")
finalbill=bill
print("\t\tTotal bill amount: ",finalbill)

print("\t\t========================")
ch=input("\nPress Y to pay the bill now or any other key to pay later:")
if ch in ['Y','y','yes','Yes']:
if ftime==0:
query="update customer set bill='{}',status='Paid',ftp=1 where
phno={}".format(finalbill,ph)
else:
query="update customer set bill='{}',status='Paid' where
phno={}".format(finalbill,ph)
cur.execute(query)
con.commit()
print("Successfully paid the bill.....")

else:
query="update customer set bill='{}',status='Unpaid',ftp=1 where
phno={}".format(finalbill,ph)
cur.execute(query)
con.commit()
print("Please make payment as soon as possible.....")
con.close()

def remove():
ph=input("\nEnter your phone number:")

con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="select * from customer where phno={}".format(ph)
cur.execute(query)
res=cur.fetchall()
if res==[]:
print("Customer does not exist.....")
else:
ch=input("Are you sure to delete the customer.....Yes/No:")
if ch in ['Y', 'y','yes', 'Yes']:
query="delete from customer where Phno={}".format(ph)
cur.execute(query)
con.commit()
print("Successfully deleted from database.....")
else:
print("No changes made in the databse")
con.close()
def display():
con=mq.connect(host="localhost",user="root",password="Calvin@0203",database="teleph
one")
cur=con.cursor()
query="select * from customer"
cur.execute(query)
res=cur.fetchall()
con.commit()
fh=open('tele_file.txt','w+')
for eachrecord in res:
strformat=str(eachrecord)
fh.write(strformat)
fh.write('\n')
fh.flush()
fh.close

fh=open('tele_file.txt',"r")
readr=fh.read()
print(readr)
fh.close()
con.close()

def helping():
print("\t\t\tHelp")
print("\t\t\t====")
print("First 50 calls are free")
print("51-100 calls are 1.0 Rs per call")
print("101-150 calls are 2.0 Rs per call")
print("Above 150 calls are 3.0 Rs per call")
while True:
menu()
ch=int(input("Enter your choice:"))
if ch==1:
register()
elif ch==2:
search()
elif ch==3:
modify()
elif ch==4:
billing()
elif ch==5:
remove()
elif ch==6:
display()
elif ch==7:
helping()
elif ch==8:
exit()
else:
print("Please choose the correct choice and try again")

ch=input("\n\nPress y to continue and any other key to exit:")


if ch not in ["Y","y","yes","Yes"]:
break
****************************************************************************

#registering customer
#searching customer
#updating customer
#generating bill for a first time payer(1st 50
calls free offer applicable)
#generating bill for same customer again(1st
50calls free offer NOT applicable)
#refusing to pay bill generated for first time
payer
#finally paying total bill for customer who
refused to pay before
#deleting customer
#displaying records from file
#help
# exit

**********************************************************************************

You might also like