A PROJECT REPORT

ON
“PAYROLL MANAGEMENT”

PM SHRI KENDRIYA VIDYALAYA ARA

PATNA REGION

SUBMITTED BY
Name: VIKEY KUMAR SINGH
Enroll No.:
Class : XII
Group Members : VIKEY KUMAR SINGH
TUSHAR RAJ GUPTA
RAJ KUMAR

Under the Guidance of

Dr. Anu Aujla
PGT-CS
 DECLARATION

This is to certify that the Project Report entitled “PAYROLL

MANAGEMENT” which is submitted to the department of computer science,
PM SHRI Kendriya Vidyalaya Ara , Patna region is prepared by me. All the
coding is the result of my personal effort and due acknowledgement has been
made in the text to all other material used.

Date: 13/01/2025

Name of Student: VIKEY KUMAR SINGH

APPROVED BY-

Name of Subject Teacher/Guide: Dr. Anu Aujla

1
 TABLE OF CONTENT

PAGE
SER DESCRIPTION
NO

01 CERTIFICATE 03

02 ACKNOWLEDGEMENT 04

03 INTRODUCTION 05

04 OBJECTIVES OF THE PROJECT 05

05 PROPOSED SYSTEM 06

06 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 08

07 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 09

08 FLOW CHART

09 SOURCE CODE 18

10 OUTPUT 27

11 TESTING 32

12 HARDWARE AND SOFTWARE REQUIREMENTS 35

13 REFERNCES 36

2
 CERTIFICATE

This is to certify that the Project Report entitled “PAYROLL

MANAGEMENT” which is submitted by “VIKEY KUMAR
SINGH” and group in partial fulfillment of the requirement for the
award of practical marks for Computer Science, CBSE board
Examination is a record of the candidate’s own work carried out by
her under my supervision.

External Teacher Signature Internal Teacher Signature

3
 ACKNOWLEDGEMENT

I pay my gratitude and sincere regards to Dr. Anu Aujla,my project

guide for giving me the cream of his knowledge. I am thankful to her
as she has been a constant source of advice, motivation and
inspiration. I am also thankful to her for giving her suggestions and
encouragement throughout the project work.

I take the opportunity to express my gratitude and thanks to our

Principal, Teachers and library staff for providing me the opportunity
to utilize their resources for the completion of the project.

I am also thankful to my family and friends for constantly motivating

me to complete the project and providing me an environment which
enhanced my knowledge.

4
 PROJECT ON PAYROLL MANAGEMENT

INTRODUCTION
A payroll management system is an accounting method used to
process, streamline, and manage wages paid to employees. It
calculates salaries after the deduction of taxes, benefits payments,
track hours worked, issues payments through check or direct deposit
and keeps accurate records of all employees

OBJECTIVES OF THE PROJECT

● Accurate and Timely Payment: Ensure accurate and timely

payment of salaries, wages, and benefits to employees.
● Efficient Data Management: Maintain accurate and up-to-date
employee data, including personal details, salary information,
and benefits
● Automation of Payroll Processes: Automate payroll processes,
including salary calculations, tax deductions, and benefit
disbursements
● Reduced Errors and Discrepancies: Minimize errors and
discrepancies in payroll processing, reducing the need for
corrections and reimbursements
● Improved Employee Experience: Provide employees with easy
access to their payroll information, pay stubs, and benefits
details.

5
 PROPOSED OF THE PROJECT

● Employee Data Management: A centralized database to store

employee personal details, salary information, and benefits.

● Payroll Processing: Automated calculations for salary, taxes,

benefits, and deductions.

● Compliance Management: Ensures adherence to relevant laws,

regulations, and tax requirements.

● Reporting and Analytics: Provides insights into payroll trends,

costs, and compliance.

● Employee Self-Service: A secure portal for employees to

access their payroll information, pay stubs, and benefits details.

● Automated Payroll Processing: Calculates salaries, taxes,

benefits, and deductions.

● Tax Compliance: Ensures adherence to tax laws and

regulations.

● Benefits Administration: Manages employee benefits,

including health insurance, retirement plans, and time-off

policies.

6
● Direct Deposit: Offers employees the option to receive their

pay through direct deposit.

● Pay Stub Generation: Automatically generates pay stubs for

employees.

● Reporting and Analytics: Provides customizable reports and

analytics to support informed business decisions.

● Improved Accuracy: Reduces errors in payroll processing.

● Increased Efficiency: Automates payroll processes, reducing

manual labor.

● Enhanced Compliance: Ensures adherence to relevant laws,

regulations, and tax requirements.

● Better Employee Experience: Provides employees with easy

access to their payroll information.

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

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

9
 • 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.

10
• 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:

11
 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,

12
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 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

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

14
• Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the preliminary
design for the system.
• Everything requiring user input or approval is documented and reviewed
by the user. Once these documents have been approved by the Agency
CIO and Business Sponsor, the final System Design Document is created
to serve as the Critical/Detailed Design for the system.
• This document receives a rigorous review byAgency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system design, the
Agency Project Manager begins development of the Implementation
Plan, Operations and Maintenance Manual, and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into

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

• Translating the detailed requirements and design into system components.

15
 • Testing individual elements (units) for usability.
• Preparing for integration and testing ofthe IT system.

INTEGRATION AND TEST PHASE

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

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

Multiple levels of testing are performed, including:

• Testing at the development facility by the contractor and possibly

supported by end users
• Testing as a deployed system with end users working together with
contract personnel
• Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing,a final Independent
Verification & Validation evaluation is performed and all documentation
is 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

16
the planning phase. Implementation includes user notification, user training,
installation of hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues until
the system is operating in production in accordance with the defined user
requirements.

OPERATIONS AND MAINTENANCE PHASE

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

performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can
be effectively adapted to respond to the organization’s needs. When
modifications or changes are identified, the system may 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

17
 SOURCE CODE
import mysql.connector as m

import datetime

from tabulate import tabulate

db=input("Enter name of your database : ")

mydb=m.connect(host="localhost",user="root",password="vikey@123")

mycursor = mydb.cursor()

sql="CREATE DATABASE if not exists %s" % (db,)

mycursor.execute(sql)

print("Database created successfully..")

mycursor=mydb.cursor()

mycursor.execute("Use "+db)

TableName=input("Name of Table to be created:")

query="Create table if not exists "+TableName+"\

(empno int primary key,\

name varchar(15) not null,\

job varchar(15),\

BasicSalary int,\

DA float,\

HRA float,\

GrossSalary float,\

Tax float,\

NetSalary float)"

print("Table"+TableName+"created successfully...")

mycursor.execute(query)

18
while True:

print('\n\n\n')

print("*"*95)

print('\t\t\t\t\tMAIN MENU')

print("*"*95)

print('\t\t\t\t1. Adding Employee records')

print('\t\t\t\t2. For Displaying of All the Employees')

print('\t\t\t\t3. For Displaying Records of a particular Employee')

print('\t\t\t\t4. For Deleting Records of all the Employee')

print('\t\t\t\t5. For Deleting a Record of a particular Employee')

print('\t\t\t\t6. For Modification in a Record')

print('\t\t\t\t7. For Displaying Payroll')

print('\t\t\t\t8. For Displaying Salary Slip for all the Employee')

print('\t\t\t\t9. For displaying Salary Slip for a particular Employee')

print('\t\t\t\t10. For Exist')

print('Enter Choice:-',end='')

choice=int(input())

if choice==1:

try:

print('Enter employee information:-')

mempno=int(input('Enter Employee No. :'))

mname=input('Enter Employee Name :')

mjob=input('Enter Employee Job :')

mbasic=float(input('Enter BAsic Salary :'))

if mjob.upper()=="OFFICER" :

mda=mbasic*0.5

mhra=mbasic*0.35

19
 mtax=mbasic*0.2

elif mjob.upper()=="MANAGER" :

mda=mbasic*0.45

mhra=mbasic*0.30

mtax=mbasic*0.15

else:

mda=mbasic*0.40

mhra=mbasic*0.25

mtax=mbasic*0.1

mgross=mbasic+mda+mhra

mnet=mgross-mtax

rec =(mempno,mname,mjob,mbasic,mda,mhra,mgross,mtax,mnet)

query="insert into "+TableName+" values(%s,%s,%s,%s,%s,%s,%s,%s,%s)"

mycursor.execute(query,rec)

mydb.commit()

print('Record added successfully.')

except:

print('Something went wrong')

elif choice==2:

try:

query='select * from '+TableName

mycursor.execute(query)

#print(query)

print(tabulate(mycursor, headers=['EmpNo','Name','Job','Basic Salary','DA','HRA','Gross

Salary','Tax','Net Salary'], tablefmt='francy_grid'))

'''myrecords=mycursor.fetchall()

for rec in myrecords:

20
 print(rec)'''

except:

print('Something went wrong')

elif choice==3:

try:

en=input('Enter employee no. of the record to be displayed.')

query="select * from "+TableName+" where empno="+en

mycursor.execute(query)

myrecord=mycursor.fetchone()

print("\n\nRecord of Employee NO.:"+en)

print(myrecord)

c=mycursor.rowcount

if c==-1:

print('Nothing to display')

except:

print('Something went wrong')

elif choice==4:

try:

ch=input('Do you want to delete all the records (y/n)')

if ch.upper()=='Y':

mycursor.execute('delete from '+TableName)

mydb.commit()

print('All the records are deleted.')

except:

print('Something went wrong')

elif choice==5:

21
 try:

en=input('Enter employee no. of the records to be deleted.')

query='delete from '+TableName+' where empno='+en

mycursor.execute(query)

mydb.commit()

c=mycursor.rowcount

if c>0:

print('Deletion done')

else:

print('Employee no. ', en, 'not found')

except:

print('Something went wrong')

elif choice==6:

try:

en=input('Enter employee no. of the record to be modified.')

query='select * from '+TableName+' where empno='+en

mycursor.execute(query)

myrecord=mycursor.fetchone()

c=mycursor.rowcount

if c==-1:

print('Empno '+en+' does not exist')

else:

mname=myrecord[1]

mjob=myrecord[2]

mbasic=myrecord[3]

print('empno :',myrecord[0])

print('name :',myrecord[1])

22
 print('job :',myrecord[2])

print('basic :',myrecord[3])

print('da :',myrecord[4])

print('hra :',myrecord[5])

print('gross :',myrecord[6])

print('tax :',myrecord[7])

print('net :',myrecord[8])

print('----------------------')

print('Type value to modify below or just press Enter for no change')

x=input('Enter name')

if len(x)>0:

mname=x

x=input('Enter job')

if len(x)>0:

mjob=x

x=input('Enter basic salary ')

if len(x)>0:

mbasic=float(x)

query='update '+TableName+' set

name='+"'"+mname+"'"+','+'job='+"'"+mjob+"'"+','+'basicsalary='\

+str(mbasic)+' where empno='+en

print(query)

mycursor.execute(query)

mydb.commit()

print('Record modified')

except:

print('Something went wrong')

elif choice==7:

23
 try:

query='select * from '+TableName

mycursor.execute(query)

myrecords=mycursor.fetchall()

print("\n\n\n")

print(95*'*')

print('Employee Payroll'.center(90))

print(95*'*')

now = datetime.datetime.now()

print("Current Date and Time:",end=' ')

print(now.strftime("%d-%m-%Y %H:%M:%S"))

print()

print(95*'-')

print('%-5s %-15s %-10s %-8s %-6s %-6s %-7s %-6s %-7s'\

%('Empno','Name','Job','Basic','DA','HRA','Gross','Tax','Net'))

print(95*'-')

for rec in myrecords:

print('%4d %-15s %-10s %8.2f %8.2f %8.2f %9.2f %8.2f %9.2f'%rec)

print(95*'-')

except:

print('Something went wrong')

elif choice==8:

try:

query='select * from '+TableName

mycursor.execute(query)

myrecords=mycursor.fetchall()

print("\n\n\n")

24
 print(95*'*')

print('Salary Slip'.center(90))

print(95*'*')

now = datetime.datetime.now()

print("Current Date and Time:",end=' ')

print(now.strftime("%d-%m-%Y %H:%M:%S"))

print()

print(95*'-')

for rec in myrecords:

print('%4d %-15s %-10s %8.2f %8.2f %8.2f %9.2f %8.2f %9.2f'%rec)

print(95*'-')

except:

print('Something went wrong')

elif choice==9:

try:

en=input("Enter employee number where pay slip you want to reteive")

query='select * from '+TableName+ 'where empno '+en

now = datetime.datetime.now()

print("\n\n\n\t\t\tSALARY SLIP ")

print("Current Date and Time:",end=" ")

print(now.strftime("%d-%m-%y %H:%M:%S"))

#print(query)

print(tabulate(mycursor, headers=['Empno','Name','Job','BAsic Salary','DA','HRA','Gross

Salary','Tax','Net Salary'], tablefmt='francy_grid'))

except Exception as e:

25
 print('Something went wrong')

elif choice==10:

break

else:

print('Wrong Choice.')

OUTPUT
================================================================

CREATINGH DATABASE
● PYTHON OUTPUT

● MYSQL OUTPUT

26
 ADDING EMPLOYEE RECORDS
● PYTHON OUTPUT

● MYSQL OUTPUT

27
 FOR DISPLAYING ALL EMPLOYEE DETAILS
● PYTHON OUTPUT

● MYSQL OUTPUT

28
 FOR DISPLAYING PARTICULAR EMPLOYEE
● PYTHON OUTPUT

FOR DELETING RECORDS OF A PARTICULAR EMPLOYEE

● PYTHON OUTPUT

29
● MYSQL OUTPUT

FOR MODIFICATIO IN A RECORDS

● PYTHON OUTPUT

● MYSQL OUTPUT

30
 DISPLAYING PAYSLIP OF EMPLOYEES
● PYTHON OUTPUT

DISPLAYING SALARY SLIP OF EMPLOYEES

● PYTHON OUTPUT

TESTING

31
Software Testing is an empirical investigation conducted to provide
stakeholders with information about the quality of the product or service under
test, 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.

32
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

33
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 testingincludes 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.

HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : INTEL OR AMD

34
 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 ATHLON

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. Keyboard and mouse

X. Printer : required

SOFTWARE REQUIREMENTS:

• Windows O
• Python–
• MySQL
REFERENCES
1.Python Documentation : https://docs.python.org/

2.MySQL Documentation : https://dev.mysql.com/doc/

3.PyMySQL Library : https://pypi.org/project/PyMySQL/

THANK YOU

35