A PROJECT REPORT ON

SUBJECT : INFORMATICS PRACTISES [065]

ACADEMIC YEAR : 2022 - 23

SUBMITTED BY : SUBMITTED TO :
Mrs. Preeti Taneja

BOARD ROLL NUMBER :

CLASS : XII
1
 INDEX
Sr.No TITLE Pg.No
1 ACKNOWLEDGEMENT
2 PROJECT ANALYSIS
3 MODULES
4 FUNCTIONS
5 DETAILED DESCRIPTION OF PROJECT
6 OPTION PROVIDED
7 SCREENSHOTS
8 SOURCE CODE
9 BIBLIOGRAPHY

2
 ACKNOWLEDGMENT

It is with pleasure that I acknowledge my sincere gratitude to

our teacher,
Ms.Preeti Taneja who taught and undertook the responsibility
of teaching the subject Infromatics practices. I have been
greatly benefitted from her classes.

I am especially filled with gratitude to our principal Mrs. Mamta

Singh who has always been a source of encouragement and
support and without whose inspiration this project would not
have been a successful. I would like to place on record heartfelt
thanks to him.

I would also like to thanks my family for encouraging and

supporting me during my academics and providing me with
such facilities to make my future brighter.

Finally, I would like to express my sincere appreciation to all

the other student of my batch, their friendship and the fine times
that we all shared together.

3
 PROJECT ANALYSIS PROJECT ON DENTAL MANAGEMENT SYSTEM

INTRODUCTION

The project Dental Management System is developed with a

view of assist dental hospital in their functioning. This
project is aimed at providing easy access to the
administration about their patient records and their employee
records.

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,

4
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 paper work has to be done but now
software product on 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.

5
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
y be divided differently depending on the organization
involved.

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

7
 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

8
 potential technical solutions within the context of the
business need.
It may include several trade
trade-off
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.
pr
The ITPR must be approved by the State CIO before the
project can move forward.

PICTORIAL REPRESENTATION OF SDLC:

9
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’ sjob 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.

REQUIREMENTS ANALYSIS 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

10
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

11
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

12
 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

13
 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

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

15
 START
FLOW CHART

IMPORT SYSIMPORT
MYSQL.CONNECTOR AS SQL

CREATESOURCE
DATABASE
CODE‘DENTAL
MANAGEMENT SYSTEM’

CREATE TABLE PATIENT_RECORD( PATIENT_NAME

VARCHAR(50),AGE INT(3) ,DOCTOR_CONSULTED VARCHAR (50),
ADDRESS VARCHAR(150), PHONE_NUMBER BIGINT (15))

CREATE TABLE SALARY_RECORD(EMPLOYEE_NAME

VARCHAR(50),PROFFESSION VARCHAR(20),SALARY_AMOUNT
VARCHAR(9),ADDRESS VARCHAR(150),PHONE_NUMBER BIGINT(15))

CREATE TABLE ACCOUNTS(USER_NAME VARCHAR(20) PRIMARY

KEY,PASSWORD VARCHAR(30) UNIQUE)

ADD YOUR ACCOUNT IN

ACCOUNTS TABLE

PRINT 1.ADD PATIENT RECORD

2.ADD SALARY RECORD
3.VIEW PATIENT RECORD
4.DELETE PATIENT RECORD

16
INPUT “ENTER
YOUR OPTION”

IF
OPTION
== 1:

IF
OPTIO
N == 2:

17
PRINT "EMPLOYEE DETAILS : "
INPUT'EMPLOYEE_NAME : '
INPUT'PROFFESSION : '
INPUT'SALARY AMOUNT : '
INPUT'ADDRESS : '

STOP

18
SOURCE CODE

import sys
import mysql.connector as sql
conn=sql.connect(host='localhost',user='root',passwd='manager'
)
cur=conn.cursor()
cur.execute("create database dental_management_system")
print("Database created succefully")
conn=sql.connect(host='localhost',user='root',passwd='manager'
,database='dental_management_system')
cur.execute('create table patient_record( Patient_Name
varchar(50),
Age int(3),
Doctor_Conculted varchar(50),
Address varchar(150),
Phone_Number bigint(15))')
cur.execute('create table salary_record( Employee_Name
varchar(50),
Proffession varchar(20),
Salary_Amount varchar(9),
Address varchar(150),
Phone_Number bigint(15))')
cur.execute('create table accounts( User_Name varchar(20)
primary key, password varchar(30) unique)')
print('Tables created successfully')
conn.commit()
user=input("Enter New User Name : ")
user=user.upper()
passwrd=input("Enter New Password : ")
passwrd=passwrd.upper()
cur.execute("insert into accounts values('" + user + "','" +
passwrd + "')")
print("ACCOUNT ADDED SUCCEFULLY")
conn.commit()

19
if conn.is_connected:
print(" Dental Management
System ")
print("1. Login")
print("2. Exit")
print()
option=int(input("Enter your choise : "))
if option==1:
print()
user=input('User Name : ')
user=user.upper()
cur.execute("select * from accounts where User_Name
like '" + user + "'")
datas=cur.fetchall()
for i in datas:
value_1=i[0]
value_2=i[1]
if user==value_1:
password=input('Password : ')
password=password.upper()
if password==value_2:
print()
print('Login succefull')
print()
print("1. Add Patients records")
print("2. Add Salary records")
print("3. Veiw Patient Detail")
print("4. Delete patient detail")
print()
choise=int(input('Enter a option : '))
if choise==1:
print()
name=input('Name : ')
name=name.upper()
age=int(input('Age : '))

20
 doc=input('Doctor Consulted : ')
doc=doc.upper()
add=input('Address : ')
add=add.upper()
phone_no=int(input('Phone Number : '))
cur.execute("insert into patient_record
values('" + name + "'," + str(age) + ",'" + doc + "','" + add
+ "'," + str(phone_no) + ")")
conn.commit()
print('Record added')
if choise==2:
print()
emp_name=input( 'Employee_Name : ')
emp_name=emp_name.upper()
proffesion=input('Proffession : ')
proffesion=proffesion.upper()
salary=int(input('Salary Amount : '))
add=input('Address : ')
add=add.upper()
phone_no=input( 'Phone_Number : ')
cur.execute("insert into salary_record
values('" + emp_name + "','" + proffesion + "'," + str(salary)
+ ",'" + add + "'," + str(phone_no) + ")")
conn.commit()
print('Record added')
if choise==3:
print()
name=input('Name of the patient : ')
name=name.upper()
cur.execute("select * from patient_record
where patient_name like '" + str(name) + "'")
data=cur.fetchall()
if data!=0:
for row in data:
print()

21
 print("Patient Details : ")
print()
print('Name : ',row[0])
print('Age : ',row[1])
print('Doctor consulted :
',row[2])
print('Address : ',row[3])
print('Phone Number : ',row[4])
input()
else:
print()
print("Patient Record Doesnot Exist")
if choise==4:
print()
name=input('Name of the patient : ')
name=name.upper()
cur.execute("delete from patient_record
where Patient_Name like '" + name + "'")
print('Record Deleted Succefully')
else:
print('Invalid Password')
print('Tryagain')
elif option==2:
sys.exit()
conn.commit()
input()

22
 OUTPUT
OPTION – 1:

23
OPTION – 2:

24
OPTION – 3:

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

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

27
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

28
 INSTALATION PROCEDURE

Dental Management System :-

Pre-Requisites :-

1. You have to have the following softwares for the

successful running of this software; which are

I) Python (Only for the First time), it is

downloadable from 'www.python.org'.

II) MySQL (Only for the First time), it is

downloadable from 'www.mysql.org'.

Installation :-

1. There will be two folders namely 'Python Files' and

'EXE files'.

2. The folder 'Python Files' will contain the source code

of the software in python language. If you are running the
software by the 3rd step mentioned below you have to pre
install the following modules :-

I) mysql.connector

II) matplotlib.

29
 3. Open the files in any python editors and run it to
start and work on the software.

4. The folder 'EXE files' will contain two files namely

'main.exe' and 'Tables_in_mysql.exe'.

5. First run the 'Tables_in_mysql.exe' to create the

tables in MySQL.

6. Then run the file 'main.exe' to start and work on the

software.

CAUTION :-

If you are running the software through running the

python files or by running the .exe files ; first run the file
named 'Tables_in_mysql'.

The .exe file will take a lot of time; so be PATIENT.

30
 HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD
ATHALON(3800+- 4200+ DUAL CORE)
III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R
MSI
K9MM-V VIA K8M800+8237R PLUS
CHIPSET FOR AMD ATHALON
IV. RAM : 512MB+
V. Hard disk : SATA 40 GB OR ABOVE
VI. CD/DVD r/w multi drive combo: (If back up required)
VII. FLOPPY DRIVE 1.44 MB : (If Backup required)
VIII. MONITOR 14.1 or 15 -17 inch
IX. Key board and mouse
X. Printer : (if print is required –
[Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

31
 BIBLIOGRAPHY

1. Computer science With Python - Class XI By : Sumita

Arora
2. A Project Report On Blood Bank Management System (BBMS)

By : Praveen M Jigajinni
3. Website: https://www.w3resource.com

***

32