A project submitted by

………………………………………………………………

Roll Number: ………………………………………………..

on

CONTACT MANAGEMENT SYSTEM

to
Central Board of Secondary Education, New Delhi in partial fulfilment of curriculum
of COMPUTER SCIENCE NEW [083] (Class: XI) internal examination conducted
by CBSE, New Delhi.

2023-2024

NH-44 , Door No. 3/465 , R.K.Nagar, Thottilovanpatti, Nalli-626 205,

Sattur Taluk,Virudhunagar District, Tamilnadu.
 CERTIFICATE

This is to certify that .......................................................... is a student of class

XI with Roll Number ..................................................... has successfully completed
the project on CONTACT MANAGEMENT SYSTEM under the supervision of
the subject teacher Mrs.M.RAJALAKSHMI M.Sc.,B.Ed., during the academic session
2023 - 2024 in partial fulfilment of COMPUTER SCIENCE NEW[083] internal
examination.

Internal Examiner External Examiner

Principal
 ACKNOWLEDGEMENT

First and foremost, I would like to extend my heartiest gratitude to the ALMIGHTY for doing
and completing this project work successfully.
I express my sincere thanks to our MANAGEMENT.
I am especially indebted to our Principal Dr. P. VIJAYAKUMAR M.Sc.,M.Ed.,M.Phil.,Ph.D.,
and computer science teacher Mrs. M. RAJALAKSHMI M.Sc.,B.Ed., for their valuable
suggestions during the course of this project work.
I extend my sincere gratitude to my parents for their unconditional co-operation and motivation
extended to me to complete this project.

Signature of the Student

Contents

1. Introduction of the Project

2. System Requirements of the Project

3. Python Coding

4. Output of the Project

5. Bibliography
 Introduction of the Project

We the students of CLASS: XI of M.M.VIDYASHRAM SENIOR

SECONDARY CBSE SCHOOL have been assigned the work of CONTACT
MANAGEMENT SYSTEM.

To perform this task the students were divided into the group of three
students named as RAHUL.K, MURALI KRISHNA.G, ALSON THOMAS
VARGHESE is assigned the work of coding, analyzing the program and lead
the program to the conclusion.

The project starts with –

The history of contact management stretches back to Rolodex and Filofax systems,
developing into desktop-based standalone software and email clients with built-in contact
management functionality.

Despite these significant technical advances, many businesses find that their contact
management systems fundamentally amount to little more than a simple database containing
names, phone numbers and notes.

In recent years, the categories of sales management and Contact Management

System have grown closer together, as enterprises increasingly realise that a more unified
system, capable of capturing a wider range of business data, is key. By combining the
tracking of contacts, their engagements with your business, the products they buy, the ones
they don’t and the challenges they face, you can create one, single unified view of the
customer. That’s vital data not only for a successful sales team, but also in the delivery of
excellent customer service.

What’s needed is a fundamental move beyond a sophisticated contact book, and

towards systems that track the entire customer journey from start to end – and then connect
those to products.
 Contact management means storing, organizing, securing and tracking contact
information about your prospects and customers, sales leads, vendors, partners, stakeholders,
employees, (the list goes on) and making them easily available for all the members of your
organization.

The primary purpose of contact management software is to record contact information

in a central location to be easily accessed and updated. This information may include names,
addresses, phone numbers, email addresses, and social media profiles.

As we are the students of CLASS XI and we haven’t done this type of project before,
we have performed all that which we have learnt from our CBSE PROGRAMMING .Hence,
we know that this programming would be further done on a big platform. Since we have
started this programming from September month , we believe that this programming would
further help us a lot in our future.

We are also thankful to our group mates for cooperating with each other while

performing this task we have also polished the skills of group activity.
PROCESS

FIRSTLY, we have done the planning in a paper work regarding what have to do on

the assigned project CONTACT MANAGEMENT SYSTEM.

SECONDLY, we discussed our planning with our subject teacher and then he

provided us the right path to perform the work.

NEXT, we started our project on foot paths of our subject teacher.

THEN, we started our coding; coding took around 2 and half months for completion.

NEXT, we analyzed the mistakes done and then we corrected them.

THEN, we prepared the project format as shown above.

THANKS TO ALL OF WORTHY TEACHERS, PRINCIPAL, CO-ORDINATOR

AND MY DEAR GROUP MATES

ALSO A GREAT THANKS TO M.M. VIDYASHRAM SENIOR SECONDARY

CBSE SCHOOL FOR PROVIDING US THIS GOLDEN OPPORTUNITY.....

PYTHON

Python is a popular programming language. It was created by Guido van Rossum, and
released in 1991.

It is used for:

 web development (server-side),

 software development,
 mathematics,
 system scripting.

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 efficiency so to replace the unending

heaps of flies with a much sophisticated hard disk of the computer.

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

atomization various organisations. 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 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 of 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 and
the 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, and Develop 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, is
necessary 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 specific activities and resources required to complete a project.
A critical part of a project manager’s job is to coordinate discussions between user,
audit, security, design, development, and network personnel to identify and document as
many functional, security, and network requirements 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.
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 Master Plan.
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 script programs during the development phase. Program
designs are constructed in various ways. Using a top-down approach, designers first identify
and link major program 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 by Agency 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 assesses 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 reviewed and 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 on-going. 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 re-enter
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.
 System Requirements of the Project
Recommended System Requirements

Processors: Intel® Core™ i3 processor 4300M at 2.60 GHz.

Disk space: 2 to 4 GB.

Operating systems: Windows® 10.

Python Versions: 3.X.X or Higher.

Minimum System Requirements

Processors: Intel Atom® processor or Intel® Core™ i3 processor.

Disk space: 1 GB.

Operating systems: Windows 7 or later.

Python Versions: 2.7.X, 3.6.X.

Front End: Python

 PYTHON CODING:
from tkinter import *

import sqlite3

import tkinter.ttk as ttk

import tkinter.messagebox as tkMessageBox

#DEVELOPED BY Mark Arvin

root = Tk()

root.title("Contact List")

width = 700

height = 400

screen_width = root.winfo_screenwidth()

screen_height = root.winfo_screenheight()

x = (screen_width/2) - (width/2)

y = (screen_height/2) - (height/2)

root.geometry("%dx%d+%d+%d" % (width, height, x, y))

root.resizable(0, 0)

root.config(bg="#6666ff")

#============================VARIABLES===================================

FIRSTNAME = StringVar()

LASTNAME = StringVar()

GENDER = StringVar()

AGE = StringVar()

ADDRESS = StringVar()

CONTACT = StringVar()
#============================METHODS=====================================

def Database():

conn = sqlite3.connect("pythontut.db")

cursor = conn.cursor()

cursor.execute("CREATE TABLE IF NOT EXISTS `member` (mem_id INTEGER NOT NULL PRIMARY KEY
AUTOINCREMENT, firstname TEXT, lastname TEXT, gender TEXT, age TEXT, address TEXT, contact TEXT)")

cursor.execute("SELECT * FROM `member` ORDER BY `lastname` ASC")

fetch = cursor.fetchall()

for data in fetch:

tree.insert('', 'end', values=(data))

cursor.close()

conn.close()

def SubmitData():

if FIRSTNAME.get() == "" or LASTNAME.get() == "" or GENDER.get() == "" or AGE.get() == "" or ADDRESS.get() == ""
or CONTACT.get() == "":

result = tkMessageBox.showwarning('', 'Please Complete The Required Field', icon="warning")

else:

tree.delete(*tree.get_children())

conn = sqlite3.connect("pythontut.db")

cursor = conn.cursor()

cursor.execute("INSERT INTO `member` (firstname, lastname, gender, age, address, contact) VALUES(?, ?, ?, ?, ?,
?)", (str(FIRSTNAME.get()), str(LASTNAME.get()), str(GENDER.get()), int(AGE.get()), str(ADDRESS.get()),
str(CONTACT.get())))

conn.commit()

cursor.execute("SELECT * FROM `member` ORDER BY `lastname` ASC")

fetch = cursor.fetchall()

for data in fetch:

tree.insert('', 'end', values=(data))

cursor.close()
 conn.close()

FIRSTNAME.set("")

LASTNAME.set("")

GENDER.set("")

AGE.set("")

ADDRESS.set("")

CONTACT.set("")

def UpdateData():

if GENDER.get() == "":

result = tkMessageBox.showwarning('', 'Please Complete The Required Field', icon="warning")

else:

tree.delete(*tree.get_children())

conn = sqlite3.connect("pythontut.db")

cursor = conn.cursor()

cursor.execute("UPDATE `member` SET `firstname` = ?, `lastname` = ?, `gender` =?, `age` = ?, `address` = ?,

`contact` = ? WHERE `mem_id` = ?", (str(FIRSTNAME.get()), str(LASTNAME.get()), str(GENDER.get()), str(AGE.get()),
str(ADDRESS.get()), str(CONTACT.get()), int(mem_id)))

conn.commit()

cursor.execute("SELECT * FROM `member` ORDER BY `lastname` ASC")

fetch = cursor.fetchall()

for data in fetch:

tree.insert('', 'end', values=(data))

cursor.close()

conn.close()

FIRSTNAME.set("")

LASTNAME.set("")

GENDER.set("")

AGE.set("")

ADDRESS.set("")

CONTACT.set("")
def OnSelected(event):

global mem_id, UpdateWindow

curItem = tree.focus()

contents =(tree.item(curItem))

selecteditem = contents['values']

mem_id = selecteditem[0]

FIRSTNAME.set("")

LASTNAME.set("")

GENDER.set("")

AGE.set("")

ADDRESS.set("")

CONTACT.set("")

FIRSTNAME.set(selecteditem[1])

LASTNAME.set(selecteditem[2])

AGE.set(selecteditem[4])

ADDRESS.set(selecteditem[5])

CONTACT.set(selecteditem[6])

UpdateWindow = Toplevel()

UpdateWindow.title("Contact List")

width = 400

height = 300

screen_width = root.winfo_screenwidth()

screen_height = root.winfo_screenheight()

x = ((screen_width/2) + 450) - (width/2)

y = ((screen_height/2) + 20) - (height/2)

UpdateWindow.resizable(0, 0)

UpdateWindow.geometry("%dx%d+%d+%d" % (width, height, x, y))

if 'NewWindow' in globals():
 NewWindow.destroy()

#===================FRAMES==============================

FormTitle = Frame(UpdateWindow)

FormTitle.pack(side=TOP)

ContactForm = Frame(UpdateWindow)

ContactForm.pack(side=TOP, pady=10)

RadioGroup = Frame(ContactForm)

Male = Radiobutton(RadioGroup, text="Male", variable=GENDER, value="Male", font=('arial', 14)).pack(side=LEFT)

Female = Radiobutton(RadioGroup, text="Female", variable=GENDER, value="Female", font=('arial',

14)).pack(side=LEFT)

#===================LABELS==============================

lbl_title = Label(FormTitle, text="Updating Contacts", font=('arial', 16), bg="orange", width = 300)

lbl_title.pack(fill=X)

lbl_firstname = Label(ContactForm, text="Firstname", font=('arial', 14), bd=5)

lbl_firstname.grid(row=0, sticky=W)

lbl_lastname = Label(ContactForm, text="Lastname", font=('arial', 14), bd=5)

lbl_lastname.grid(row=1, sticky=W)

lbl_gender = Label(ContactForm, text="Gender", font=('arial', 14), bd=5)

lbl_gender.grid(row=2, sticky=W)

lbl_age = Label(ContactForm, text="Age", font=('arial', 14), bd=5)

lbl_age.grid(row=3, sticky=W)

lbl_address = Label(ContactForm, text="Address", font=('arial', 14), bd=5)

lbl_address.grid(row=4, sticky=W)

lbl_contact = Label(ContactForm, text="Contact", font=('arial', 14), bd=5)

lbl_contact.grid(row=5, sticky=W)

#===================ENTRY===============================

firstname = Entry(ContactForm, textvariable=FIRSTNAME, font=('arial', 14))

firstname.grid(row=0, column=1)
 lastname = Entry(ContactForm, textvariable=LASTNAME, font=('arial', 14))

lastname.grid(row=1, column=1)

RadioGroup.grid(row=2, column=1)

age = Entry(ContactForm, textvariable=AGE, font=('arial', 14))

age.grid(row=3, column=1)

address = Entry(ContactForm, textvariable=ADDRESS, font=('arial', 14))

address.grid(row=4, column=1)

contact = Entry(ContactForm, textvariable=CONTACT, font=('arial', 14))

contact.grid(row=5, column=1)

#==================BUTTONS==============================

btn_updatecon = Button(ContactForm, text="Update", width=50, command=UpdateData)

btn_updatecon.grid(row=6, columnspan=2, pady=10)

#fn1353p

def DeleteData():

if not tree.selection():

result = tkMessageBox.showwarning('', 'Please Select Something First!', icon="warning")

else:

result = tkMessageBox.askquestion('', 'Are you sure you want to delete this record?', icon="warning")

if result == 'yes':

curItem = tree.focus()

contents =(tree.item(curItem))

selecteditem = contents['values']

tree.delete(curItem)

conn = sqlite3.connect("pythontut.db")

cursor = conn.cursor()

cursor.execute("DELETE FROM `member` WHERE `mem_id` = %d" % selecteditem[0])

 conn.commit()

cursor.close()

conn.close()

def AddNewWindow():

global NewWindow

FIRSTNAME.set("")

LASTNAME.set("")

GENDER.set("")

AGE.set("")

ADDRESS.set("")

CONTACT.set("")

NewWindow = Toplevel()

NewWindow.title("Contact List")

width = 400

height = 300

screen_width = root.winfo_screenwidth()

screen_height = root.winfo_screenheight()

x = ((screen_width/2) - 455) - (width/2)

y = ((screen_height/2) + 20) - (height/2)

NewWindow.resizable(0, 0)

NewWindow.geometry("%dx%d+%d+%d" % (width, height, x, y))

if 'UpdateWindow' in globals():

UpdateWindow.destroy()

#===================FRAMES==============================

FormTitle = Frame(NewWindow)

FormTitle.pack(side=TOP)

ContactForm = Frame(NewWindow)

ContactForm.pack(side=TOP, pady=10)
 RadioGroup = Frame(ContactForm)

Male = Radiobutton(RadioGroup, text="Male", variable=GENDER, value="Male", font=('arial', 14)).pack(side=LEFT)

Female = Radiobutton(RadioGroup, text="Female", variable=GENDER, value="Female", font=('arial',

14)).pack(side=LEFT)

#===================LABELS==============================

lbl_title = Label(FormTitle, text="Adding New Contacts", font=('arial', 16), bg="#66ff66", width = 300)

lbl_title.pack(fill=X)

lbl_firstname = Label(ContactForm, text="Firstname", font=('arial', 14), bd=5)

lbl_firstname.grid(row=0, sticky=W)

lbl_lastname = Label(ContactForm, text="Lastname", font=('arial', 14), bd=5)

lbl_lastname.grid(row=1, sticky=W)

lbl_gender = Label(ContactForm, text="Gender", font=('arial', 14), bd=5)

lbl_gender.grid(row=2, sticky=W)

lbl_age = Label(ContactForm, text="Age", font=('arial', 14), bd=5)

lbl_age.grid(row=3, sticky=W)

lbl_address = Label(ContactForm, text="Address", font=('arial', 14), bd=5)

lbl_address.grid(row=4, sticky=W)

lbl_contact = Label(ContactForm, text="Contact", font=('arial', 14), bd=5)

lbl_contact.grid(row=5, sticky=W)

#===================ENTRY===============================

firstname = Entry(ContactForm, textvariable=FIRSTNAME, font=('arial', 14))

firstname.grid(row=0, column=1)

lastname = Entry(ContactForm, textvariable=LASTNAME, font=('arial', 14))

lastname.grid(row=1, column=1)

RadioGroup.grid(row=2, column=1)

age = Entry(ContactForm, textvariable=AGE, font=('arial', 14))

age.grid(row=3, column=1)

address = Entry(ContactForm, textvariable=ADDRESS, font=('arial', 14))

address.grid(row=4, column=1)
 contact = Entry(ContactForm, textvariable=CONTACT, font=('arial', 14))

contact.grid(row=5, column=1)

#==================BUTTONS==============================

btn_addcon = Button(ContactForm, text="Save", width=50, command=SubmitData)

btn_addcon.grid(row=6, columnspan=2, pady=10)

#============================FRAMES======================================

Top = Frame(root, width=500, bd=1, relief=SOLID)

Top.pack(side=TOP)

Mid = Frame(root, width=500, bg="#6666ff")

Mid.pack(side=TOP)

MidLeft = Frame(Mid, width=100)

MidLeft.pack(side=LEFT, pady=10)

MidLeftPadding = Frame(Mid, width=370, bg="#6666ff")

MidLeftPadding.pack(side=LEFT)

MidRight = Frame(Mid, width=100)

MidRight.pack(side=RIGHT, pady=10)

TableMargin = Frame(root, width=500)

TableMargin.pack(side=TOP)

#============================LABELS======================================

lbl_title = Label(Top, text="Contact Management System", font=('arial', 16), width=500)

lbl_title.pack(fill=X)
#============================ENTRY=======================================

#============================BUTTONS=====================================

btn_add = Button(MidLeft, text="+ ADD NEW", bg="#66ff66", command=AddNewWindow)

btn_add.pack()

btn_delete = Button(MidRight, text="DELETE", bg="red", command=DeleteData)

btn_delete.pack(side=RIGHT)

#============================TABLES======================================

scrollbarx = Scrollbar(TableMargin, orient=HORIZONTAL)

scrollbary = Scrollbar(TableMargin, orient=VERTICAL)

tree = ttk.Treeview(TableMargin, columns=("MemberID", "Firstname", "Lastname", "Gender", "Age", "Address",

"Contact"), height=400, selectmode="extended", yscrollcommand=scrollbary.set, xscrollcommand=scrollbarx.set)

scrollbary.config(command=tree.yview)

scrollbary.pack(side=RIGHT, fill=Y)

scrollbarx.config(command=tree.xview)

scrollbarx.pack(side=BOTTOM, fill=X)

tree.heading('MemberID', text="MemberID", anchor=W)

tree.heading('Firstname', text="Firstname", anchor=W)

tree.heading('Lastname', text="Lastname", anchor=W)

tree.heading('Gender', text="Gender", anchor=W)

tree.heading('Age', text="Age", anchor=W)

tree.heading('Address', text="Address", anchor=W)

tree.heading('Contact', text="Contact", anchor=W)

tree.column('#0', stretch=NO, minwidth=0, width=0)

tree.column('#1', stretch=NO, minwidth=0, width=0)

tree.column('#2', stretch=NO, minwidth=0, width=80)

tree.column('#3', stretch=NO, minwidth=0, width=120)

tree.column('#4', stretch=NO, minwidth=0, width=90)

tree.column('#5', stretch=NO, minwidth=0, width=80)

tree.column('#6', stretch=NO, minwidth=0, width=120)

tree.column('#7', stretch=NO, minwidth=0, width=120)

tree.pack()

tree.bind('<Double-Button-1>', OnSelected)

#============================INITIALIZATION==============================

if __name__ == '__main__':

Database()

root.mainloop()
OUTPUT OF THE PROJECT
Finally, we conclude our work and present the output of the Project.

MAIN SCREEN
 TESTING
Software Testing is an empirical investigation conducted to provide stakeholders with
information about the quality of the product or service under test [1], with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks
at implementation of the software. Test techniques include, but are not limited to, the process
of executing a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided its
design and development, so that it works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method employed, can be
implemented at any time in the development 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.
BLACK BOX TESTING
Black box testing treats the software as a "black box," without any knowledge of
internal implementation. Black box testing methods include: equivalence partitioning,
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability
matrix, exploratory testing and specification-based testing.
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to the

applicable requirements. [16] Thus, the tester inputs data into, and only sees the output from,
the test object. This level of testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output value (or behaviour),
either "is" or "is not" the same as the expected value specified in the test case. Specification-
based testing is necessary, but it is insufficient to guard against certain risks
ADVANTAGES AND DISADVANTAGES
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 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
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)
Types of white box testing: -
The following types of white box testing exist:
• API testing - Testing of the application using Public and Private APIs.
• Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in the program to
be executed at least once.
• fault injection methods.
• mutation testing methods.
• static testing - White box testing includes all static testing.
CODE COMPLETENESS EVALUATION
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.
Two common forms of code coverage are:
• Function Coverage: Which reports on functions executed and
• Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage
BIBLIOGRAPHY
1. python.org

2. Codeacademy.com

3. tutorialsPoint.com

4. w3schools.com

5. learndigital.withgoogle.com

6. LearnPython.org