A Project Report

On
Employee Management System
For
AISSCE 2023
[As a part of the Computer Science Course]

SUBMITTED BY:
Name: Aasif Mohammed,
XII-A
[Roll No: ]
Under the Guidances of:
Ms. Gayathri Selvam
Head of Department
&

Ms. Sabira Karim

Faculty,
Department of Computer Science

1
DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is to certify that

, the student of class XII under the register no.: has

successfully completed the project entitled

, during the

academic year 2022-’23 in partial fulfilment of Computer Science Practical

Examination conducted by CBSE, New Delhi.

Internal Examiner External Examiner Principal

2
 TABLE OF CONTENTS

SERIAL NO DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE 07

06 PHASES OF SYSTEM DEVLOPMENT LIFE CYCLE 08

07 FLOW CHART 19

08 SOURCE CODE 20

09 OUTPUT 25

10 INSTALLATION FILE 28

11 TESTING 30

12 HARDWARE AND SOFTWARE REQURIMENTS 33

13 BIBLIOGRAPHY 34

3
 ACKNOWLEDGEMENT
I gratefully acknowledge the contribution of the individuals who contributed to bringing
this project up to this level. I take this opportunity to express my gratitude to the people
who have been instrumental in the successful completion of this project.

I express my deep sense of gratitude to the luminary The Principal, Mr. Abdul Majeed
M who has been continuously motivating and extending their helping hand to us.

I express my sincere thanks to the academician The Vice Principal, Ms. Anju B Nair, for
constant encouragement and the guidance provided during this project

I am overwhelmed to express my thanks to Ms. Gayathri Selvam, HOD of computer

Science, for providing me an infrastructure and moral support while carrying out this project
in the school.

My sincere thanks to Ms. Sabira Karim, teacher In-charge, 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

The guidance and support received from all the members who contributed and who are
contributing to this project, was vital for the success of the project. I am grateful for their
constant support and help.

4
 PROJECT ON EMPLOYEE MANAGEMENT SYSTEM

INTRODUCTION
The focus of this project is employee management system software. Having
complete control over one's personnel is advantageous. To make the project
easier to grasp, it is split into two sections.

In order to log in and register, it is given a user name and password. It records
the user's pay, his department of employment, and his performance in the
workplace. It replaces the department's current list of employee salaries, adds
a new employee, and updates the individual's age and performance.

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 s o l v e 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.

5
 PROPOSED SYSTEM

In today's brutally competitive world, when the adage "to err is human" is no
longer true, one cannot afford to rely on imperfect human people. It is also no
longer appropriate to explain away one's errors. In order to stay up with the
times, achieve the best results without problems, and increase efficiency, a
computer's hard drive has replaced the endless mounds of flies.

One has to use the data management software. Software has been an ascent
in atomization various organizations. Many software products working are now
in markets, which have helped in making the organizations work easier and
efficiently. Data management initially had to maintain a lot of ledgers and a lot
of 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.

6
 SYSTEM DEVELOPMENTS LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that

divides complex projects into smaller, more easily managed segments or
phases. Segmenting projects allows managers to verify the successful
completion of project phases before allocating resources to subsequent
phases.

Software development projects typically include initiation, planning, design,

development, testing, implementation, and maintenance phases. However, the
phases may be divided differently depending on the organization involved.

For example, initial project activities might be designated as request.

Requirements - definition, and planning phases, or initiation, concept-
development, and planning phases. End users of the system under
development should be involved in reviewing the output of each phase to
ensure the system is being built to deliver the needed functionality.

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

• Identity and validate an opportunity to improve business

accomplishments of the organization or a deficiency related toa
business need.
• Identity significant assumptions and constraints on solutions ot 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 ni a Concept Proposal. The Concept Proposal includes
information about the business process and the relationship to the
Agency/Organization.
• Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outlines the authority of
the project manager to begin the project.

Careful oversight is required to ensure projects support strategic

business objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins when an
opportunity to add, improve, or correct a system is identified and formally
requested through the presentation of a business case. The business case
should, at a minimum, describe a proposal's purpose, identify expected
benefits, and explain how the proposed system supports one of the
organization's business strategies. The business case should also identify
alternative solutions and detail as many informational, functional, and network
requirements as possible.

8
 SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and
the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

• Determine the feasibility and appropriateness of the alternatives

• Identify system interfaces.
• Identify basic functional and data requirements to satisfy the
business need. Establish system boundaries; identify goals,
objectives, critical success factors, and performance measures.
• Evaluate costs and benefits of alternative approaches to satisfy
the basic functional requirements
• Assess project risks
• Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a
concept of operations. This phase explores potential technical
solutions within the context of the business need.
• It may include several trade-off decisions such as the decision to
use COTS software products as opposed to developing custom
software or reusing software components, or the decision to use
an incremental delivery versus a complete, onetime deployment.
• Construction of executable prototypes Is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support
the Information Technology Project Request (ITPR)process.
• The ITPR must be approved by the State CIO before the project
can move forward.

9
PICTORIAL REPRESENTATION OF SDLC

10
 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' job is to coordinate discussions between

user, audit, security, design, development, and network personnel to identify
and document as many functional, security, and network requirements as
possible. During this phase, a plan is developed that documents the approach
to be used and includes a discussion of methods, tools, tasks, resources project
schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.

A Project Management Plan is created with components related to acquisition

planning, configuration management planning, quality assurance planning,
concept of operations, system security, verification and validation, and systems
engineering management planning.

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

12
 DESIGN PHASE
The design phase involves converting the informational, functional, and
network requirements identified during the initiation and planning phases into
unified design specifications that developers use to script programs during the
development phase. Program designs are constructed in various ways. Using a
top-down approach, designers first identify and link major program
components and interfaces, then expand design layouts a s they identify and
link smaller subsystem and connections. Using a bottom-up approach,
designers first identify and link minor program components and interfaces,
then expand design layouts as they identify and link larger systems and
connections. Contemporary design techniques often use prototyping tools that
build mock-up designs of items such as application screens, database layouts,
and system architectures. End users, designers, developers, database
managers, and network administrators should review and refine the
prototyped designs in an iterative process until they agree on an acceptable
design. Audit, security, and quality assurance personnel should be involved in
the review and approval process. During this phase, the system is designed to
satisfy the functional requirements identified in the previous phase. Since
problems in the design phase could be very expensive to solve in the later
stage of the software development, a variety of elements are considered in the
design to mitigate risk. These include:

• Identifying potential risks and defining mitigating design features.

• Performing a security risk assessment.
• Developing a conversion plan to migrate current data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and outputs.
• Allocating processes to resources.
• Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the preliminary
design for the system.
• Everything requiring user input or approval is documented and
reviewed by the user. Once these documents have been approved by
the Agency CIO and Business Sponsor, the final System Design Document
is created to serve as the Critical/Detailed Design for the system.
13
This document receives a rigorous review by Agency technical and functional
representatives to ensure that it satisfies the business requirements.
Concurrent with the development of the system design, the Agency
ProjectManager begins development of the Implementation Plan, Operations
and Maintenance Manual, and the Training Plan.

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

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

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

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

18
 FLOW CHART

Start python

Creation of table logid ,office and

performance

PROGRAM EXECUTION BY ("1.LOGIN")

("2.EMPLOYEE REGISTERATION")

("3.EMPLOYEE DETAILS")

("4.UPDATE SALARY")

("5.EMPLOYEES LIST")

"6.KNOW THE NUMBER OF EMPLOYEES")

("7.EMPLOYEE BALANCE ACCOUNT")

("8.WORK EXPERIENCE")

("9.KNOW YOUR SALARY")

(".EXITING")

STOP

19
SOURCE CODE

================================================================
#table creation
import mysql.connector as sql
conn=sql.connect(host='localhost',user='root',passwd='manager',datab
ase='employees')
cur = conn.cursor()
#cur.execute('create table user_table(username varchar(25) primary
key,passwrd varchar(25) not null )')
print('=========================WELCOME TO START EMPLOYEE MANAGEMENT
SYSTEM============================================================')
import datetime as dt
print(dt.datetime.now())
print('1.REGISTER')
print()
print('2.LOGIN')
print()

n=int(input('enter your choice='))

print()

if n== 1:
name=input('Enter a Username=')
print()
passwd=int(input('Enter a 4 DIGIT Password='))
print()
V_SQLInsert="INSERT INTO log_id (user_id,password) values (" +
str (passwd) + ",' " + name + " ') "
cur.execute(V_SQLInsert)
conn.commit()
print()
print('USER created succesfully')
import mainp

if n==2 :
name=input('Enter your Username=')
print()
passwd=int(input('Enter your 4 DIGIT Password='))
V_Sql_Sel="select * from log_id where password='"+str
(passwd)+"' and user_id= ' " +name+ " ' "
cur.execute(V_Sql_Sel)
if cur.fetchall() is None:
print()
print('Invalid username or password')
else:

20
 print()
import mainp

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
# MAINP.PY FILE #
import time
print ("\t\t\t",time.ctime())

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()

def menu():
print(" EMPLOYEES MANAGEMENT SYSTEM ")
c='yes'
c=input("do you want to continue or not(yes or No):")
while(c=='yes'):
print("1.login")
print("2.employee registeration")
print("3.employee details")
print("4.update salary")
print("5.employees list")
print("6.know the number of employees")
print("7.work experience")
print("8.know your salary")
print("exiting")
choice=int(input(" enter the choice: "))
if choice==1:
login()
elif choice==2:
register()
elif choice==3:
details()
elif choice==4:
em_salary()
elif choice==5:
em_list()
elif choice==6:
em_count()

elif choice==7:
em_perform()
elif choice==8:
salary()
else:
print ("exit")
break
else : print("Thank You")

21
def login():
import sys
user_id=input("enter USER ID :")
pwd=int(input("enter the password :"))
if user_id == 'vishal'and pwd == 6054:
print("welcome to EMPLOYEE MANAGEMENT SYSTEM ")
else:

print("invalid user id and password")

sys.exit()

def register():
import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()
v_em_no=int(input("enter your employee ID"))
v_em_name=input ("enter your name:")
v_em_dept=input( "enter department you want to join : ")
v_em_salary=input ("enter your salary:")
v_em_age=int(input("enter your age:"))
v_sql_insert="insert into office values("+int(v_em_no)+",'"
+v_em_name+"','"+v_em_dept+"',"+str(v_em_salary)+","+str(v_em_age)+"
)"
mycursor.execute(v_sql_insert)
conn.commit()
print("congrats you have joined suuceessfully")
print(" registerd suyccessfully ")
def details():
import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()
mycursor.execute("select* from OFFICE")
results=mycursor.fetchall()
conn.commit()
for x in results:
print(x)
def em_salary():
import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()
nam=input("enter your name")

22
 mycursor.execute("update office set
em_salary=em_salary+em_salary*10/100 where
em_name='{}'".format(nam))

conn.commit()

def em_list():
import mysql.connector as sql
try:

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()
mycursor.execute("select em_name from office order by
em_name asc")
list_=mycursor.fetchall()
for x in list_:
print (x)
a=mycursor.rowcount()
print("total employees are",a)
except:
print ("unable to show the list")
def em_count():
import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',password='manager',dat
abase='employees')
mycursor=conn.cursor()
mycursor.execute("select count(distinct em_name) from office")
count=mycursor.fetchall()
for x in count:
print(" numbr of employees:",x)
conn.commit()

def salary():
nam=input("enter your name :")
a=mycursor.execute("select em_salary from office where
em_name='{}'".format(nam))
mycursor.execute(a)
salary=mycursor.fetchall()
for x in salary:
print( x,"is your current salary",nam )
conn.commit()
def em_perform():
v_em_no=int(input("enter your employee ID"))
v_em_name=input ("enter your name:")
v_em_dept=input( "enter department you want to join : ")

23
v_em_performance=input("enter your performance:")
v_em_work=input ("enter your experience(YEARS):")
v_sql_insert="insert into em_performance
values("+str(v_em_no)+",'"
+v_em_name+"','"+v_em_dept+"','"+v_em_performance+"',"+str(v_em_work
)+")"
print(v_sql_insert)
mycursor.execute(v_sql_insert)
conn.commit()
print("performance added")

menu() # PYTHON MODULE :Tables_in_mysql

====================================================================

24
OUTPUT

25
26
27
 INSTALLATION PROCEDURE

employee 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 'TABLEE Files' and 'MAIN

files'.

2. The folder 'TABLEE 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 :-

A.) mysql.connector

28
 B.)IMPORT time

3. Open the files in any python editors and run it to start

and work on the software.

4. The folder '6054' 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.

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

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

31
 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

32
 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 : 512 MB+

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 : required

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

33
 BIBLIOGRAPHY

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

2. Website: https://www.youtube.com

34