GOVERNMENT MULTIPURPOSE HIGHER SECONDARY SCHOOL

AMBIKAPUR (C.G.)

ACADEMIC YEAR 2024-25

PROJECT REPORT ON
MEDICAL SHOP MANAGEMENT SYSTEM
ROLL NO
NAME ADITI PANDEY
CLASS XII CBSE
SUBJECT INFORMATICS PRACTICES
SUB CODE 065
PROJECT GUIDE MISS CHETNA PATHAK
GOVT. MULTIPURPOSE HR. SEC. SCHOOL
 GOVT MULTIPURPOSE HIGHER SECONDARY SCHOOL

CERTIFICATE
This is to certify that ADITI PANDEY CBSE Roll no __________________
Has successfully completed the project work entitled MEDICAL SHOP
MANAGEMENT SYSTEM in the subject Informatics Practices (085) laid down in
the regulations of CBSE for the purpose of Practical Examination in Class XII to be
held in Govt. Multipurpose Higher Secondary School Ambikapur on ___________.

CHETNA PATHAK

Signature of External Examiner

Name:
Examiner Number:

1
 ACKNOWLEDGEMENT

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.
Iexpressmy heartfelt gratitude to my parents for constant encouragement while
carrying out this project.
I gratefully acknowledge the contribution of the individuals who contributed in
bringing this project up to this level, who continues to look after me despite my flaws,
I express my deep sense of gratitude to luminary The Principal, H. K JAISWAL who
has been continuously motivating and extending their helping hand to us. l.
My sincere thanks to MISS CHETNA PATHAK A guide, Mentor all the above a
friend, who critically reviewed my project and helped in solving each and every
problem, occurred during implementation of the project.

2
 TABLE OF CONTENTS
SR.NO. DESCRIPTION PAGE N0.
01 INTRODUCTION 4-5
02 FUTURE SCOPE / ASPECTS 5
03 HARDWARE & SOFTWARE 5-7
REQUIREMENTS
04 TECHNOLOGY USED 7-9
05 FEASIBILITY STUDY 9
06 SYSTEM DESIGN 9-10
07 ARCHITECTUAL DESIGN 10-13
08 TESTING & MAINTAINANCE 14-18
09 SOURCE CODE & OUTPUT 18-33
10 CONCLUSION 34
11 BIBLIOGRAPHY 34

3
 INTRODUCTION
Medical Shop Management System
1 Introduction:

The "Medical Shop Management System" has been developed to oven-ide the problems prevailing in
the practicing manual system. This software is supposed to eliminate and in some cases reduce the
hardships faces of the company to carry out operations in a smooth and effective manner.

The application is reduced as much as possible avoid error while entering the data. Is also provides
error message while entering invalid data. No formal knowledge is needed for the user to use the
system. Thus by this all it proves it is user friendly. Medical shop management system, as described
above, can lead to concentrate on their other activities rather to concentrate on the record keeping.

Every Organization, whether big or small, has challenges to overcome and managing the
informations of Medicines, Medical Shop, Company, Sells, Inventory. Every Medical Shop
Management System has different Medical Shop needs, therefore we design exclusive employee
management system that are adapted to your managerial requirements. This is designed to assist in
strategic planning, and will help you ensure that your organization is equipped with the right level of
information and details for your future goals. These systems will ultimately allow you to better
manage resources.

2 Objectives.

The main objective of the Project on Medical Shop Management System is to manage the details of
medical shop, medicines, stocks, shells, and inventory. The project is totally built at administrative
end and thus only administrator is guaranteed the access.

administrative end and thus only administrator is guaranteed the access.

Functionalities provided by the project:

Provides the searching facilities based on various factors. Such as medical shop
stock, company, inventory.

It tracks all the information of medicines, sells, company etc.

Manage the information of Medicines.

Shows the information and description of the Medical Shop, Stocks

To increase efficiency of managing the Medical Shop, Medicines

It deals with monitoring the information and transactions of Company.

4
 Editing, adding and updating of records is improved which result in proper resource
management of Medical Shop data.

3 Scope of the Project

Our project aims at business process automation, i.e we have tried to computerize various processed
of Medical Shop Management System.

In computer system the person has to fill the various forms & number of copies of
the forms can be easily generated at a time

To assist the staff in capturing the effort spent on their respective working areas.

To utilize resources in an efficient manner by increasing their productivity through

automation.

The system generates types of information that can be used for various purpose.

It satisfies the user requirement.

Be easy to understand by the user and operator.

Be easy to operate.

Have a good user interface.

Be expandable.

FUTURE SCOPE:

We can give more advance software for Medical Shop Management System including
more facilities.
We will host the platform on online servers to make it accessible worldwide.
Integrate multiple load balancers to distribute the loads of the system.

HARDWARE AND SOFTWARE REQUIRMENTS

1. INTRODUCTION:

To be used efficiently, all computer software needs certain hardware components or the other
software resources to be present on a computer. These pre-requisites are known as(computer)
system requirements and are often used as a guideline as opposed to an absolute rule. Most
software defines two sets of system requirements: minimum and recommended. With increasing
demand for higher processing power and resources in newer versions of software, system
requirements tend to increase over time. Industry analysts suggest that this trend plays a bigger part
in driving upgrades to existing computer systems than technological advancements.

2. HARDWARE REQUIREMENTS

5
 The most common set of requirements defined by any operating system or software application is
the physical computer resources, also known as hardware. A hardware requirements list is often
accompanied by a hardware compatibility list (HCL), especially in case of operating systems. An HCL
lists tested, compatibility and sometimes incompatible hardware devices for a particular operating
system or application. The following sub-sections discuss the various aspects of hardware
requirements.

HARDWARE REQUIREMENTS FOR PRESENT PROJECT.

RAM : 1

HARD DISK : 80 CIB

3 SOFTWARE REQUIREMENTS:

Software Requirements deal with defining software resource requirements and pre-requisites that
need to be installed on a computer to provide optimal functioning of an application. These
requirements or pre-requisites are generally not included in the software installation package and
need to be installed separately before the software is installed.

SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

OPERATING SYSTEM : Windows 7/ XP/8

FRONT END : PYTHON

DATABASE : MY SQL

6
7
 TECHNOLOGY USED
PYTHON

INTRODUCTION
It is widely used general purpose, high level programming language developed by Guido Van Rossum
in 1991.

IT IS USED FOR:
Software development, Web development (server-side), System scripting, Mathematics.

FEATURES OF PYTHON
Easy to use: due to simple syntax rule

Interpreted Language: code execution & interpretation line by line.

Cross-platform Language: it can run on windows' Linux% a cinetoshætcæqvally———

Expressive Language: less code to be written as it itself express the purpose of the code.

Completeness: support wide range of library.

Free & Open Source: can be downloaded freely and source code can be modify for improvement.

SHORTCOMINGS OF PYTHON
Lesser Libraries: as compared to other programming languages like

Slow Language: as it is interpreted languages it executes the program slowly.

Weak on Type-binding: it not pin point on use of a single variable for different data type.

MYSQL
MySQL "My S-Q-L", officially, but open-source relational database management system (RDBMS).It is
named after co-founder Wideness's daughter, My The SQL phrase stands for Structured Query
Language.

The MySQL development project has made its source code available under the terms
of the GNU General Public License, as well as under a variety of proprietary agreements.
MySQL was owned and sponsored by a single for-profit firm, the Swedish company AB,
now owned by Oracle Corporation.

8
 A popular choice of database for use in web applications, and is a central component of the widely
used LAMP open source web application software stack (and other 'AMP' stacks). LAMP is an
acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that
require a full-featured database management system often use MySQL.

For proprietary use, several paid editions are available, and offer additional functionality.
Applications which use MySQL databases include: TYP03, MODx, Joomla, Word Press, phpBB, MyBB,
Drupal and other software. MySQL is also used in many high-profile, largescale websites, including
Google(though not for searches), Face book, Twitter, Flickr,and YouTube.

MySQL is a relational database management system (RDBMS), and ships with no GUI tools to
administer MySQL databases or manage data contained within the databases. Users may use the
included command line tools, or use MySQL "front-ends", desktop software and web applications
that create and manage MySQL databases, build database structures, back up data, inspect status,
and work with data records. The official set of MySQL front-end tools,

MySQL Workbench is actively developed by Oracle, and is freely available for use.

FEASIBILITY STUDY
Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of the
existing business or proposed venture, opportunities and threats as presented by the environment,
the resources required to carry through, and ultimately the prospects for success. In its simplest
terms, the two criteria to judge feasibility are cost required and value to be attained. As such, a well-
designed feasibility study should provide a historical background of the business or project,
description of the product or service, accounting statements, details of the operations and
management, marketing research and policies, financial data, legal requirements and tax obligations.

1 Security Fesibility

2 Technical Feasibility

3 Economic Feasibility

4 Schedule Feasibility

SYSTEM DESIGN
The system design is the formal specification of the system to be build. This specification includes the
following:

1. Hardware Configuration: The hardware configuration specifies the hardware

platforms on which the intended system will run. This contains the specifications
regarding hardware devices like: computers, network resources and connections, power
backups, network devices, backup mechanism and other similar details. The depth of the
configuration may vary from system. For example, an information system may be
designed in such manner that it supports same set of hardware resources at every

9
 implementation whereas another information system may require different hardware
resources at different installations.

2. Software Configuration: The software configuration specifies the software platform

require for the intended information system. There can be much variation in the software
platform requirement of two software applications. The best example can be the
difference between a character user interface information system and graphic user
interface information system. The software configuration also specifies the function of
every modules and interface between various system modules. It also specifies the
function of every module of the system. The other main component of software
specification is the specification of database that will be a part of information system.

The software specification also specifies the user interface to the system.

ARCHITECTURAL DESIGN
Software architecture is the high level structure of a software system, the discipline of creating such
structures, and the documentation of these structures. It is the set of structures needed to reason
about the software system, and comprises the software elements, the relations between them, and
the properties of both elements and relations. The architecture of a software system is a metaphor,
analogous to the architecture of a building.

Software architecture choices include specific structural options from possibilities in the design of
software. For example, the systems that controlled the space shuttle launch vehicle have the
requirement of being very fast, and very reliable, in principle. Therefore an appropriate real-time
computing language would be chosen. Similarly, multiple redundant independently produced copies
of a program running on independent hardware and crosschecking results would be a software
system architecture choice to satisfy the need for reliability. Software architecture is about making
fundamental structural choices which are costly to change once implemented, i.e., which are used to
'house' the more changeable elements of the program, e.g., an operating system. Documenting
software architecture facilitates communication between stakeholders, captures early decisions
about the high-level design, and allows reuse of design components between projects

1 Data Dictionary:

A data dictionary, or metadata repository, as defined in the IBM Dictionary of Computing, is a

"centralized repository of information about data such as meaning, relationships to other data,
origin, usage, and format. The terms data dictionary and data repository indicate a more general
software utility than a catalogue. A catalogue is closely coupled with the DBMS software. It provides
the information stored in it to the user and the DBA, but it is mainly accessed by the various software
modules of the DBMS itself, such as DDL and DML compilers, the query optimiser, the transaction
processor, report generators, and the constraint enforcer. On the other hand, a data dictionary is a
data structure that stores metadata, i.e., (structured) data about data. The software package for a
stand-alone data dictionary or data repository may interact with the software modules of the DBMS,
but it is mainly used by the designers, users and administrators of a computer system for information
resource management. These systems maintain information on system hardware and software

10
 configuration, documentation, application and users as well as other information relevant to system
administration. If a data dictionary system is used only by the designers, users, and administrators
and not by the DBMS Software, it is called a passive data dictionary. Otherwise, it is called an active
data dictionary or data dictionary. When a passive data dictionary is updated, it is done so manually
and independently from any changes to a DBMS (database) structure. With an active data dictionary,
the dictionary is updated first and changes occur in the DBMS automatically as a result. Database
users and application developers can benefit from an authoritative data dictionary document that
catalogs the organization, contents, and conventions of one or more databases.

2 Entity Relationship Diagram:

In software engineering, an entity—relationship model (ER model) is a data model for describing the
data or information aspects of a business domain or its process requirements, in an abstract way that
lends itself to ultimately being implemented in such as a relational database. The main
components of ER models are entities (things) and the relationships that can exist among them.
Entity—relationship modelling was developed by Peter Chen and published in a 1976 paper.
However, variants of the idea existed previously, and have been devised subsequently such as super
type and subtype data entities and commonality relationships.

Introduction : An entity—relationship model is a systematic way of describing and defining a

business process. The process is modelled as components (entities) that are linked with each other
by relationships that express the dependencies and requirements between them, such as: one
building may be divided into zero or more apartments, but one apartment can only be located in one
building. Entities may have various properties (attributes) that characterize them. Diagrams created
to represent these entities, attributes, and relationships graphically are called entity—relationship
diagrams. An ER model is typically implemented as a database. In the case of a relational database,
which stores data in tables, every row of each table represents one instance of an entity. Some data
fields in these tables point to indexes in other tables; such pointers represent the relationships.

Conceptual data model

This is the highest level ER model in that it contains the least granular detail but establishes the
overall scope of what is to be included within the model set. The conceptual ER model normally
defines master reference data entities that are commonly used by the organization. Developing an
enterprise-wide conceptual ER model is useful to support documenting the data architecture for an
organization. A conceptual ER model may be used as the foundation for one or more logical data
models (see below). The purpose of the conceptual ER model is then to establish structural metadata
commonality for the mastu data entities between the set of logical ER models. The conceptual data
model may be used to form commonality relationships between ER models as a basis for data model
integration.

Logical data model

A logical ER model does not require a conceptual ER model, especially if the scope of the logical ER
model includes only the development of a distinct information system. The logical ER model contains
more detail than the conceptual ER model. In addition to master data entities, operational and

11
 transactional data entities are now defined. The details of each data entity are developed and the
entity relationships between these data entities are established. The logical ER model is however
developed independent of technology into which it is implemented.

Physical data model

One or more physical ER models may be developed from each logical ER model. The physical ER
model is normally developed to be instantiated as a database. Therefore, each physical ER model
must contain enough detail to produce a database and each physical ER model is technology
dependent since each system is somewhat different. The physical model is normally instantiated in
the structural metadata of a database management system as relational database objects such as
database tables, database indexes such as unique key indexes, and database constraints such as a
foreign key constraint or a commonality constraint. The ER model is also normally used to design
modifications to the relational database objects and to maintain the structural metadata of the
database.

The first stage of information system design uses these models during the requirements analysis to
describe information needs or the type of information that is to be stored in a database. The data
modelling technique can be used to describe any ontology (i.e. an overview and classifications of
used terms and their relationships) for a certain area of interest. In the case of the design of an
information system that is based on a database, the conceptual data model is, at a later stage
(usually called logical design), mapped to a logical data model, such as the relational model; this in
turn is mapped to a physical model during physical design. Note that sometimes, both of these
phases are referred to as "physical design". It is also used in database management system.

3 Data Flow Diagram:

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modelling its process aspects. A DFD is often used as a preliminary step to create an
overview of the system, which can later be elaborated. DFDs can also be used for the visualization of
data processing (structured design).

A DFD shows what kind of information will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. It does not show information about the
timing of process or information about whether processes will operate in sequence or in parallel

12
 Symbol Name Function

Start/end An end oval poi{t.re resents a start

or

A line is a connector that shows relationships

between the representative shapes.

Input/output A parallelogram represents

input or ouptut.

A rectangle represents a
process.

Decision A diamond indicates a

decision.

4 Flow Chart:

A flowchart is a type of diagram that represents an algorithm, workflow or process, showing the
steps as boxes of various kinds, and their order by connecting them with arrows. This diagrammatic
representation illustrates a solution model to a given problem. Flowcharts are used in analyzing,
designing, documenting or managing a process or program in various fields. Flowcharts are used in
designing and documenting complex processes or programs. Like other types of diagrams, they help
visualize what is going on and thereby help the people to understand a process, and perhaps also
find flaws, bottlenecks, and other lessobvious features within it. There are many different types of
flowcharts, and each type has its own repertoire of boxes and notational conventions. The two most
common types of boxes in a flowchart are:

a processing step, usually called activity, and denoted as a rectangular box

a decision, usually denoted as a diamond.

A flowchart is described as "cross-functional" when the page is divided into different swim lanes
describing the control of different organizational units. A symbol appearing in a particular "lane" is
within the control of that organizational unit. This technique allows the author to locate the
responsibility for performing an action or making a decision correctly, showing the responsibility of
each organizational unit for different parts of a single process. Flowcharts depict certain aspects of
processes and they are usually complemented by other types of diagram. For instance, Kaoru
Ishikawa defined the flowchart as one of the seven basic tools of quality control, next to the
histogram, Pareto chart, check sheet, control chart, cause-and-effect diagram, and the scatter
diagram. Similarly, in UML, a standard concept-modelling notation used in software development,
the activity diagram, which is a type of flowchart, is just one of many different diagram types.
Common alternative names include: flowchart, process flowchart, functional flowchart, process map,
process chart, functional process chart, business process model, process model, process flow

13
 diagram, yy_Qds flow diagram, business flow diagram. The terms "flowchart" and "flow chart" are
used interchangeably.

TESTING AND MANTENANCE

1 Testing and Types of Testing:

Testing is the process in which the system is operated with sample inputs and outputs are tested for
correctness, assuming it to be accurate. The intent is to find maximum possible errors in the system.
If the outputs are per the criteria, the system is treated to be correct and if the outputs are deviated
from the actual outputs, it indicates errors in the system. Testing is very important when the system
is ready to install. Is a problem of the system is discovered at later stage, it can be more problematic
as lot of data would have been entered in the system till then. The other reason of testing is that the
designers must evaluate the system from users point of view. They should ensure that the system
has been designed in such a manner that it can be operated easily by the users. In general, the
demands of users are often compromised to provide better design efficiency. Errors are created due
to the gap of communication between actual users and the developers of system.

1. White box testing:

White box testing also called "Glass box testing" is a test design method which uses the control
structure of the procedural design to drive the derive the test cases. Using white box testing
software engineers can derive text cases that guarantee that all independent paths within a module
have been exercised at least once. These cases execute all logical decisions on their true & false sides
and also execute all loops at their boundaries and within their operational bounds.

• It is also called as STRUCTURAL TESTING or GLASS BOX TESTING.

• Testers use the knowledge of internal logic of the system.
• Mostly verification techniques are used.
• It does no ensure that the user requirement had been met.
• The test may not mimic the real world situations.
• Example: feasibility review, designer review, code inspection and code walk through.
2. Black box testing:

Black box testing is the term used to refer to the tests, which are conducted at the software
interface. Black box testing focuses on the functional requirement of the software. Black box tests
enables a software engineers to drive set of input conditions that will fully exercise functional
requirements for a program.

14
 • It is also called as FUNCTIONAL TESTING. These tests are conducted at interface.
• Testers do not have information about the internal functionality of the system.
• Mostly validation techniques are used.
• It stimulates the actual system usage.
• They have potential of not detecting the logical error.
• Example: unit testing, integration testing, system testing and acceptance testing.
3. Unit testing:

Unit testing focuses verification effort on the smallest unit of the software i.e. an independent
modules. In unit testing control paths of module are tested by using component level design
description as guide. The most general errors which are uncovered by unit testing are initialization
errors, Arithmetic precedence errors, mixed mode operation and comparison errors.

• In unit testing the individual component are tested independently to ensure their
quality.

• The focus is to uncover the error in design and implementation.

• The various tests that are conducted during the unit test are described below.
I. Modules interfaces are tested for proper information flow in out of the program.

Il. Local data are examined to ensure that integrity is maintained.

111. All the basis (independent) paths are tested for ensuring that all statements
in the module have been executed only once.

IV. All errors handling paths should be tested.

4. Integration testing:

A group of dependent components are tested together to ensure their quality of

their integration unit.

The objective is to take unit tested components and build a program structure that
has been dictated by software design

The focus of integration testing is to uncover errors in:

Design and construction of software architecture.

15
 Integrated functions or operations at subsystem level.

Interface and interaction between them.

Resources interaction and environment integration.

5. System testing:

The objective of system testing is to detect and correct any errors present in system before it is
finally handed over to the user for conducting the user acceptance testing. In this phase, the
performance and acceptance standards for the system are developed. It is used to examine the
system failure or below standard performance of the system.

Various types of system tests are:

Stress testing.

Performance testing.

Recovery testing.

Security testing.

The main focus of such testing is to test

System function and performance.

System reliability and recoverability (recovery test).

System installation (installation test).

System behaviour in special conditions (stress test).

System user operations (acceptance test).

Hardware and software integration and collaboration.

I. Recovery testing:

• Recovery testing is intended to check the system's ability to recover from failures.
• In this type of testing the software is focused to fail and then it is verified whether
the system recovers properly or not.

Il. Security testing:

• Security testing verifies that system protection mechanism prevent improper

penetration of data alteration.

• It also verifies that protection mechanism built into the system prevent intrusion
such ad unauthorized internal or external access or wilful damage.

16
 • System design goal is to make the penetration attempt more costly the value of
information that will be obtained in it.

III. Stress testing:

This is used to ensure that the developed system performs well, even under peak loads. In this
method the system is tested under very high loads for small time duration. For example, if you are
designing a system for a telephone company, the load on the system will increase during peak hours.
Therefore, it must be tested during peak hours to measure the stress.

Determines breakpoint of a system to establish maximum service level.

In stress testing the system is executed in manner that demands resources in

abnormal quality, frequency or volume.

A variation of stress testing is a technique called sensitivity testing.

The sensitivity testing is a testing in which it is tried to uncover data from a

large class of valid data may cause instability or improper processing.

IV. Performance testing:

Performance testing evaluates the run time performance of the software

especially real time software.

In performance testing resources utilization such as CPU load, throughout,

response time, memory usage can be measured.

For big system involving many users connecting to servers performing

testing is very difficult.

2 Maintenance:

Software maintenance is the activity of modifying the software product after delivery in order to
correct faults, improve performance and to improve other attributes. Software maintenance is a vital
element in SDLC. Normally and more often done by the developers/software maintainers. In
software maintenance, software maintenance plan and software maintenance process are also key
consideration. Software maintenance plan is the planning which should be very accurate. Software
maintenance process is the sequence of steps followed during the software maintenance process.
Which includes:

Implementation Process

Problem and modification analysis process

Process acceptance of the modification

The migration process

Last maintenance process

17
 Types of maintenance:

1. Corrective Maintenance: Corrective maintenance means a reactive modification done in the

software product after the delivery. The purpose of corrective maintenance is to correct/or fix
discovered problems in the system.

2. Adaptive Maintenance: Adaptive maintenance is also a modification done after delivery, in

order to keep the software product usable in changing environments/business environment. If
this is not done properly by the time of change, business opportunities will be lost.

3. Perfective Maintenance: A software should be efficient/less resources consuming/and

should be easy to cope with. Perfective maintenance is done in order to improve the software
performance. Also improving the maintainability is a concern.

4. Preventive Maintenance: Of course as it sounds, it's just preventing. Preventive maintenance

is done, to detect and correct latent faults before they become effective faults.

This simply means the prevention of failure problems.

SOURCE CODE
#Connecting python with mysql

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',database='medical_store')

if conn.is_connected:

print('successfully connected')

c1=conn.cursor()

c1.execute('create table account_details(User_Name varchar(30)primary key,password varchar(30)

unique)')

c1.execute('create table customers_details(account_number int primary key,patient_name

varchar(30),age int,address varchar(50),phone_number bigint(11),balance_amount float)')

c1.execute('create table medicines_details(medicine_name varchar(30),medicine_code int,gst

float,sgst float,total_cost float)')

c1.execute('create table SS_bill(medicine_name varchar(30),medicine_code int ,gst float,sgst

float,cost_per_item float,quantity int,discount_on_balance_amount float,total_amount float)')

print('table created')

import sys

18
 import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='manager',database='dental_management')

cur=conn.cursor()

if conn.is_connected:

print(" SS MEDICAL STORE ")

print("1. Login")

print("2. Exit")

print()

option=int(input("Enter your choise : "))

if option==1:

print()

user=input('User Name : ')

user=user.upper()

c1.execute("select * from accounts where User_Name like '" + user + "'")

datas=c1.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. Patients records")

print("2. Salary records")

print("3. Veiw Patient Detail")

19
 print("4. Delete patient detail")

print()

choise=int(input('Enter a option : '))

if choise==1:

print()

s_no=int(input('S.no : '))

name=input('Name : ')

name=name.upper()

age=int(input('Age : '))

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(" + str(s_no) +",'" + name + "'," + str(age) +

",'" + doc + "','" + add + "'," + str(phone_no) + ")")

conn.commit()

print('Record added')

if choise==2:

print()

s_no=int(input('S_No : '))

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()

20
 phone_no=input('Phone_Number : ')

cur.execute("insert into salary_record values(" + str(s_no) +",'" + 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()

for row in data:

print()

print('Name : ',row[1])

print('Age : ',row[2])

print('Doctor consulted : ',row[3])

print('Address : ',row[4])

print('Phone Number : ',row[5])

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:

21
 sys.exit()

conn.commit()

input()

OUTPUT
SS MEDICAL STORE

1. Login

2. Exit

Enter your choice: 1

User Name: JOHN_DOE

Password: PASSWORD123

Login successful

1. Patients records

2. View Patient Detail

Enter an option: 1

S.No: 1

Name: JANE SMITH

Age: 30

Doctor Consulted: DR. BROWN

Address: 123 DENTAL AVE

Phone Number: 5551234567

22
 Record added

1. Patients records

2. View Patient Detail

Enter an option: 2

Name of the patient: JANE SMITH

Name: JANE SMITH

Age: 30

Doctor Consulted: DR. BROWN

Address: 123 DENTAL AVE

Phone Number: 5551234567

23
24
 Tl IE USERNAME!!:")

PASSWORD!!:")

PASSWORD FROM USER DATA WHERE USERNAME-"'-FUN

FOR I IN ROW:

WIIILE(TRUE):

THE TASK YOU CAN PERFORM

PRINT(

l . ADMINISTRATION

2. PATIENT (ADMISSION NAD DISCHARGE PROCESS)

3. SIGN OUT

FOR THE TASK FROM USER

YOUR CHOICE"))

USER WANTS TO ENTER ADMINISTRATION OPTION

PRINT(

l . snow DETAILS

2. ADD NEW MEMBER

3. DELETE EXISTING ONE

25
 4. EXIT

YOUR CIIOICE:"))

%SIIOWING THE EXISTING DETAILS

PRINT(

l . DOCTOR DETAILS

2. NURSE DETAILS

3. orllER WORKERS

#ASKING USER'S CHOICE

YOUR CHOICE:"))

USER WANTS TO SEE THE DETAILS OF DOCTORS

IF

* FROM
DOCTOR DETAILS")

FOR I IN ROW.

13=0

ILY_SALARY"]

PRINT(D)

USER WANTS TO SEE DWI'AILS OF NURSES

El-IF C-=2:

26
27
28
29
30
31
32
33
 CONCLUSION
Our project is only humble venture to satisfy the need to manage their product work. Several user
friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all
the requirements of the College.

• A description of the background and context of the project and its relation to work
already done in the area.

• Made statement of the aims and objective of the project.

• The description of purpose, Scope and applicability.

• We include feature and operations in detail, including screen layouts.

We designed user interface and security issue related to system.

Our system is very easy to operate.

BIBLIOGRAPHY

THE END .... THANk YOU.......

34
35