Employee Management System
Employee Management System
Employee Management System
1. Certificate
2. Acknowledgements
3. Declaration
4. Aim
5. Coding
6. Output Screenshots
7. Hardware Requirements
8. Bibliography
1
DECLARATION
I hereby declare that the project work
entitled:
“EMPLOYEE MANANGEMENT
SYSTEM”
is prepared by us,
- student names
2
AIM
Write a program using Python and MY-SQL
connectivity for Employee Management System.
3
PROJECT ON EMPLOYEE MANAGEMENT SYSTEM
INTRODUCTION
This project is all about software for Employee management system. It helps to have a
full-fledged control over his/her employees. The project is divided into 2 sections to make the
It receives user name and password to log in and register .It keeps the record of user
salary ,his department of working, his performance in the office. It adds a new employee, his
salary, department, updates an existing salary, list of employee, age and his performance.
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
project, requiring writing and presentation skills which exemplify scholarly style in
computer science.
4
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants to
stand against today’s merciless competition where not to wise saying “to err is human” no
longer valid, it’s outdated to rationalize your mistake. So, to keep pace with time, to bring
about the best result without malfunctioning and greater efficiency so to replace the unending
One has to use the data management software. Software has been an ascent in
atomization various organisations. Many software products working are now in markets,
which have helped in making the organizations work easier and efficiently. Data management
initially had to maintain a lot of ledgers and a lot of paper work has to be done but now
software product on this organization has made their work faster and easier. Now only this
This prevents a lot of time and money. The work becomes fully automated and any
information regarding the organization can be obtained by clicking the button. Moreover,
now it’s an age of computers of and automating such an organization gives the better look.
5
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
The systems development life cycle is a project management technique that divides
complex projects into smaller, more easily managed segments or phases. Segmenting projects
allows managers to verify the successful completion of project phases before allocating
development, testing, implementation, and maintenance phases. However, the phases may be
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.
6
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need or an opportunity.
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
Proposal. The Concept Proposal includes information about the business process and
Project Management Charter which outlines the authority of the project manager to
begin
the project.
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
7
SYSTEM CONCEPT DEVELOPMENT PHASE
The System Concept Development Phase begins after a business need or opportunity
CIO.
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
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
process.
The ITPR must be approved by the State CIO before the project can move forward.
8
PICTORIAL REPRESENTATION OF SDLC:
PLANNING PHASE
The planning phase is the most critical step in completing development, acquisition,
and maintenance projects. Careful planning, particularly in the early stages of a project, is
necessary to coordinate activities and manage project risks effectively. The depth and
formality of project plans should be commensurate with the characteristics and risks of a
given project. Project plans refine the information gathered during the initiation phase by
further identifying the specific activities and resources required to complete a project.
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,
operations, system security, verification and validation, and systems engineering management
planning.
9
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
maintainability requirements for the system. The requirements are defined in this phase to
alevel of detail sufficient for systems design to proceed. They need to be measurable,
testable, and relate to the business need or opportunity identified in the Initiation Phase. The
requirements that will be used to determine acceptance of the system are captured in the Test
Further define and refine the functional and data requirements and document them in
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
10
DESIGN PHASE
The design phase involves converting the informational, functional, and network
requirements identified during the initiation and planning phases into unified design
specifications that developers use to scriptprograms during the development phase. Program
designs are constructed in various ways. Using a top-down approach, designers first identify
and link majorprogram components and interfaces, then expand design layouts as they
identify and link smaller subsystems and connections. Using a bottom-up approach, designers
first identify and link minor program components and interfaces, then expand design layouts
as they identify and 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
11
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
the development of the system design, the Agency Project Manager begins
DEVELOPMENT PHASE
other project participants discuss design specifications before programming begins. The
procedures help ensure programmers clearly understand program designs and functional
programming involves the line-by-line scripting of logical instructions that are combined
12
INTEGRATION AND TEST PHASE
during the integration and test phase. The user, with those responsible for quality
Security staff assess the system security and issue a security certification and
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
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
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
13
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 reenter
continue to be satisfied.
14
FLOW CHART
Start Python
PROGRAM EXECUTION BY
("1.LOGIN")
("2.EMPLOYEE
REGISTERATION")
("3.EMPLOYEE
DETAILS")
("4.UPDATE SALARY")
("5.EMPLOYEES LIST")
("7.EMPLOYEE BALANCE
ACCOUNT")
("8.WORK
EXPERIENCE")
("9.KNOW YOUR
SALARY")
(".EXITING")
STOP
15
SOURCE CODE
================================================================
#table creation
conn=sql.connect(host='localhost',user='root',passwd='123',
database='employees')
cur = conn.cursor()
MANAGEMENT
SYSTEM===========================================================
=')
importdatetime as dt
print(dt.datetime.now())
print('1.REGISTER')
print()
print('2.LOGIN')
print()
print()
if n== 1:
name=input('Enter a Username=')
print()
print()
16
V_SQLInsert="INSERT INTOlog_id (user_id,password) values (" + str (passwd) + ",' " +
cur.execute(V_SQLInsert)
conn.commit()
print()
importmainp
if n==2 :
print()
V_Sql_Sel="select * from log_id where password='"+str (passwd)+"' and user_id= ' "
cur.execute(V_Sql_Sel)
ifcur.fetchall() is None:
print()
else:
print()
importmainp
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++
# MAINP.PY FILE #
import time
print ("\t\t\t",time.ctime())
17
importmysql.connector as sql
conn=sql.connect(host='localhost',user='root',password='123',
database='employees')
mycursor=conn.cursor()
def menu():
c='yes'
while(c=='yes'):
print("1.login")
print("2.employee registration")
print("3.employee details")
print("4.update salary")
print("5.employees list")
print("7.work experience")
print("exiting")
if choice==1:
login()
elif choice==2:
register()
elif choice==3:
details()
18
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
def login():
import sys
else:
sys.exit()
def register():
importmysql.connector as sql
conn=sql.connect(host='localhost',user='root',password='123',
19
database='employees')
mycursor=conn.cursor()
+v_em_name+"','"+v_em_dept+"',"+str(v_em_salary)+","+str(v_em_age)+")"
mycursor.execute(v_sql_insert)
conn.commit()
def details():
importmysql.connector as sql
conn=sql.connect(host='localhost',user='root',password='123',
database='employees')
mycursor=conn.cursor()
results=mycursor.fetchall()
conn.commit()
for x in results:
print(x)
defem_salary():
importmysql.connector as sql
conn=sql.connect(host='localhost',user='root',password='123',
20
database='employees')
mycursor=conn.cursor()
em_name='{}'".format(nam))
conn.commit()
defem_list():
importmysql.connector as sql
try:
conn=sql.connect(host='localhost',user='root',password='123',
database='employees')
mycursor=conn.cursor()
list_=mycursor.fetchall()
for x in list_:
print (x)
a=mycursor.rowcount()
except:
defem_count():
importmysql.connector as sql
conn=sql.connect(host='localhost',user='root',password='123',
database='employees')
mycursor=conn.cursor()
21
count=mycursor.fetchall()
for x in count:
conn.commit()
def salary():
mycursor.execute(a)
salary=mycursor.fetchall()
for x in salary:
conn.commit()
defem_perform():
+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")
22
==================================================================
==
23
OUTPUT
24
25
26
TESTING
information about the quality of the product or service under test , with respect to the context
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
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
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
Black box testing treats the software as a "black box," without any knowledge of
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability
27
SPECIFICATION-BASED TESTING
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-
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
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, 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)
28
Types of white box testing:-
api testing - Testing of the application using Public and Private APIs.
For example, the test designer can create tests to cause all statements in the program
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
29
HARDWARE AND SOFTWARE REQUIREMENTS
X. Printer : required
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
30
INSTALLATION PROCEDURE
-------------------------------------
Pre-Requisites :-
------------------------
1. You have to have the following software for the successful running of this
II) MySQL (Only for the First time), it is downloadable from 'www.mysql.org'.
31
CONCLUSION
In this chapter, the results were discussed, problems faced and limitations were
elaborated. Future recommendations for the extension and improvement of the system have
32
BIBLIOGRAPHY
2. Website: https://www.youtube.com
**********
33
THANK YOU
34