HRM Report

CHAPTER 1
INTRODUCTION
Human Resource Management System Page 1

1.1 INTRODUCTION:
The main goal of HRMS (Human Resource Management System) it deals with
everything from payroll to performance evaluation, covering the whole business. Human
Resources Software is used by businesses to combine a number of necessary HR
functions, such as storing employee data, managing payrolls, recruitment processes,
loans, benefits administration and keeping track of attendance records. It ensures
everyday Human Resources processes are manageable and easy to access. It merges
human resources as a discipline and, in particular, Human Resource Information Systems
provide a means of acquiring, storing, analysis and distributing information to various
stakeholders. HRS enables improvement in traditional processes and enhance strategic
decision making. On the whole, these ERP systems have their origin from software that
integrates information from different applications into one universal database. The
linkage of its financial and human resource modules through one database is the most
important distinction to the individually and proprietarily developed predecessors, which
makes this software application both rigid and flexible.
1.2 PURPOSE OF THE STYDY:
The HR center is a powerful application designed to allow companies to streamline their

human resource tasks and manager their employees more efficiently.
 Employee and Company Information

 Employee Time, Attendance, and Leave Request
 HR Documentation Management
The HR Center includes a comprehensive employee information database, work

information, beneficiary information, and more for each employee. It comes standard
with employee self-service access allowing employees to update their personal
information, request time off or input their daily timesheet entries. It also has role based
access level control that is functionally based on whether a user is an employee, a
manager, or HR administrators. With HR center managers and HR administrators can
manage a track.

1.3 OBJECTIVE OF THE STUDY:
To develop a software application that supports Specific to the HR Automation in an

intranet to a company there by allowing the interaction of all the employees pertaining to
that organization. To keep track of all the other departments related to that organization
like marketing, research etc.,
To allow the HR department of an organization to update the employee details whenever

there is a change in the employee profile pertaining to that organization .To bring on to a
string the employee specification suggestions and make them sure to post their
requirements to the HR.
1.4 SCOPE OF THE STUDY:
Allow for the creation of an application specification to the human resource that maintain
the intranet automation of the HR software i.e., which contains the data related to the
employee. This project can be used to identify a employee in the organization. The
project maintains the details of the entire employee. Each employee is given with
different employee Id.
1.5 PROJECT OVERVIEW:
The aim for making this project is to understand the typical system of “Human Resource
Management System” of the student.
The entire project covers following:
 Add new Employee Personal Details

 Add new Employee Job Details
 Update Employees personal Details
 Update Employees personal Details
 Monthly Attendance Detailed
 Add attendance
 Leave

 Payroll Function
 Loan
 Login Detailed
 All view Report
Our project will perform tasks defined above. It stores Employees information and
company information .it also uses the registration form for entry. It stores the records of
students registered for training and placement including. Who students are already
placed. It also has a form which shows the student’s information as well as the
information about the company and we will Search for Students of Employees no. Course
Login detailed print facilities and we can show information or data.
1.6 FEATURES:
The Training and Placement provides following features.
 Employee
 Personal Detailed
 Job Detailed
 Update Personal Detailed
 Update Job Detailed
 Attendance
 Monthly Attendance
 Add Monthly Attendance
 Leave
 Add Employees Leave
 Payroll
 Salary Structure
 Attendance Detailed
 Leave structure
 View All Reports

 Change Admin Password
 About Us
1.7 MODULES:
 Attendance Module.
 Payroll Module.
 Leave Module.
 Employee information management Module.
This application is developed by using Desktop application in visual C# (C sharp)
1.7 DEVELOPMENT METHODOLOGY:
System development methodology is a framework that is used to structure, plan and

control the process of developing an information system. A wide variety of such
frameworks have evolved over the years, each with its own recognized strengths and
weaknesses, and one system development methodology is not necessarily suitable for use
by all projects (Department of Health and Human Services, 2008).
Before, developing software, it is advisable to choose the methodology which suits best
for the selected system. Hence, before the start of this project, we have considered some
methodologies of system developed that helped us choose Waterfall model which was
presumed best for the development of “HRMS”.
1.8 WATERFALL MODEL:
The waterfall model is a sequential design process. This model is frequently used in
software development processes, in which improvement is seen as flowing steadily
downwards (like a waterfall) through the stages of conception, initiation, analysis, design,
construction, testing, production/implementation and maintenance.
Testing of the software is carried out only when the code has been fully developed. Each
work-product or activity is completed before moving on to next.

CHAPTER 2
REQUIREMENT SPECIFICATION

2.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.2 HARDWARE REQUIREMENTS:

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:
PROCESSOR: Intel dual Core, i3
RAM : 1 GB
HARD DISK : 80 GB
2.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 functionality 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
PLATFORM: Visual Studio Professional 2015
FRONT END: C# (C SHARP)
BACK END: My-SQL Server Database

CHAPTER 3
SYSTEM ANALYSIS

3.1 EXISTING SYSTEM:
As we know the manual processing is quite tedious, time consuming, less accurate in
comparison to computerized processing. Obviously the present system is not is exception
consultant encountering all the above problems.
1.Time consuming.
2.It is very tedious.
3.All information is not placed separately.
4.Lot of paper work.
5.Slow data processing.
6.Not user-friendly environment.
7.It is difficult to found records due file management system.
3.2 PROPOSED SYSTEM:
In new computerized system I tried to give these facilities.

1.Manually system changes into computerized system.
2.Friendly user interface.
3.Time saving.
4.Save paper work.
5.Connecting to database so we use different type of queries, data report.
6.Managing all the records of employee like attendance,salary and job etc. on just
a single click
7.Cost effective
8.Save space required for bulky file record.
3.3 FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly understood. Feasibility study is
a high level capsule version of the entire system analysis and design process. The
objective is to determine quickly at a minimum expense how to solve a problem. The
purpose of feasibility is not to solve the problem but to determine if the problem is worth
solving.

The system has been tested for feasibility in the following points.
 Technical Feasibility
 Operational Feasibility.
 Economic Feasibility.
 Legal and Ethical Feasibility
 Behavioral Feasibility
3.3.1 TECHNICAL FEASIBILITY:

This assessment is focused on gaining an understanding of the present technical resources
of the organization and their applicability to the expected needs of the proposed system.
It is an evaluation of the hardware and software and how it meets the needs of the
proposed system. The systems project is considered technically feasible if the internal
technical capability is sufficient to support the project requirements. The essential
questions that help in testing the technical feasibility of a system include the following:
 Is the project feasible within the limits of current technology?

 Does the technology exist at all?
 Is it available within given resource constraints?
 Is it a practical proposition?
 Is there enough manpower- programmers, testers & debuggers?
 Do the required software and hardware exist?
 Are the current technical resources sufficient for the new system?
 Can they be upgraded to provide the level of technology necessary for the new
system?
 Do we possess the necessary technical expertise, and is the schedule reasonable?
 Can the technology be easily applied to current problems?
 Does the technology have the capacity to handle the solution?
 Do we currently possess the necessary technology?

3.3.2 OPERATIONAL FEASIBILITY:
Operational feasibility is the measure of how well the project will support the customer
and the service provider during the operational phase. It is dependent on human resources
available for the project and involves projecting whether the system will be used if it is
developed and implemented. The essential questions that help in testing the technical
feasibility of a system include the following:
 Is the project feasible to operate or not?

 Does current mode of operation provide adequate throughput and response time?
 Could there be a reduction in cost and or an increase in benefits?
 Does current mode of operation offer effective controls to protect against fraud
and to guarantee accuracy and security of data and information?
 Does current mode of operation make maximum use of available resources,
including people, time, and flow of forms?
 Are the current work practices and procedures adequate to support the new
system?
 If the system is developed, will it be used?
 Does it agree with the government regulations
 Will the proposed system really benefit the organization?
 Will the system affect the customers in considerable way?
 How do the end-users feel about their role in the new system?
 How will the working environment of the end-user change?
3.3.3 ECONOMIC FEASIBILITY:

This assessment aims to determine the positive economic benefits to the organization that
the proposed system will provide. It typically involves a cost/ benefits analysis and it’s
the most frequently used method for evaluating the effectiveness of a new proposed
system. Possible questions raised in economic analysis are:
 Is the system cost effective?

 Do benefits outweigh costs?

 The cost of doing full system study
 The cost of business employee time
 Estimated cost of hardware
 Estimated cost of software/software development
 What are the savings that will result from the system?
 Cost of employees' time for study
 Cost of packaged software/software development
 Selection among alternative financing arrangements (rent/lease/purchase)
3.3.4 SCHEDULE FEASIBILITY:
It is the measure of how reasonable the project time table is or the deadline is reasonable
or not. During the lack of time or the time become mandatory, we must finish the project
within a given time period. It mainly addresses:
Can the project really be completed in the given period of time.
motivational feasibility
The project manager and development team merge their work activities and manage
whole project. They also motivate development team and customer organization
regarding their work activities at each step. It also provides an interface that is interactive
for the customer and is user friendly.
legal & ethical feasibility

Web application shall be official by government of the state as a legal system. This
application does conflict with any ethical and legal constraints and acceptable by society.
Application must be protected and will not leak privacy of any individual and
organization.
behavioral feasibility
People are inherently resistant to change and computer has known to facilitate change.
An estimate should be made of how strong a reaction the user staff is likely to have
towards the developments of computerized system. In the existing system more

manpower is required and time factor is more but in the proposed system, manpower and
time factors are reduced .So the remaining numbers are engaged with some other
important works.
3.4 SOFTWARE SPECIFICATION:
The concept of computer programming

Programming means designing a set of instructions to instruct the computer to carry out
certain jobs that are very much faster than human beings can do. The earliest
programming language is called machine language that uses binary codes comprises 0
and 1 to communicate with the computer. Machine language is extremely difficult to
learn . Fortunately, scientists have invented high level programming languages that are
much easier to master. Some of the high level programming languages are
Java, Javascript, C, C++, c# and Visual Basic.
3.4.1 USER REQUIREMENTS:

The system will be designed to be user friendly. The user friendly and interactive
interfaces design helps to achieve this by enabling customers to easily browse through the
menus and add delete modify or view information with just a few clicks and also produce
the necessary items with minimal delay and confusion. The system will be simple to use.
3.4.2 FUNCTIONAL REQUIREMENTS:

Functional requirements define the capabilities and functions that a system must be able
to perform successfully. The functional requirements of this Human Resource
Management System include:
 The system shall enable the admin to login to the system and perform his task.
 The user should be able to display the all menus of the system.
 The system shall display the record of added data.
 The system shall prompt user to add new data about employee, payroll,jobs detail
and attendance etc.
 The system shall provide visual confirmation of the entered data

 The system shall enable the user to view, create and edit descriptions
 The system shall allow the user to generate reports.
 The system shall allow the user to generate excel file of salary of employee.
3.4.3 NON-FUNCTIONAL REQUIREMENTS:

A non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviors. Some of the non-
functional requirements include:
The should be sufficient network bandwidth
 Backup- provision for data backup

 Maintainability- easy to maintain
 Performance/ response time- fast response
 Usability by target user community- easy to use
 Expandability- needs to be future proof or upgradable
 Safety- should be safe to use
 The non-functional requirements are ordered in descending order of importance.
In other words, the most important requirements are shown first.
3.5 CONSISTENT UPTIME:
The new system will be able to stay up and running at least 95% of the time. Any
downtime would be due to maintenance or upgrades. This downtime also includes any
potential failures/crashes.
dealing with large quantities of data
The developed system will have to deal with large quantities of data and. The large
quantity of data includes information and data retrieved from the database by user.

familiar interface
The new system will have an interface that shares some of the feel of the old system so
that users who are familiar with the old system will not have trouble adjusting to the new
system. The new system should display the information and show the changes made to it
in real-time.
focused layout
The new system will reduce the potential for confusion by having a focused layout. This
means that it will display information that is relevant to the current task and conversely,
leave out irrelevant information.
web accessibility
The new system will be compatible with screen readers to assist the visually impaired.
This means that screen readers should interpret the displayed text into speech and should
not output anything that does not correspond to displayed text. It is also important that the
colors are designed so that color-blind people can still distinguish changes in content.
effective recovery
The system must effectively recover from a crash within ten minutes. Effective recovery
means that the data is still in a consistent state accurate to 1 minute before the system
crashes when the system returns
3.6 LANGUAGE INTRODUCTION:
3.6.1.WHAT IS C#:
C# is a Most Modern event-driven programming language and integrated development
environment from Microsoft for its Component Object Model programming model first
released by sun microsoft. Microsoft intended C# to be relatively easy to learn and use.
C# is a high level Programming langauage, a user friendly programming language
designed for beginners, and it enables the rapid application development
(RAD) of graphical user interface (GUI) applications, access to databases using Data

Access Objects, Remote Data Objects, or ActiveX Data Objects, and creation
of ActiveX controls and objects.
A programmer can create an application using the components provided by the C#

program itself. Over time the community of programmers developed third-party
components. Programs written in C# can also use the Windows API, which requires
external function declarations.
C# is a high-level programming language that evolved from the earlier DOS version that
is the best for beginners' All-purpose Symbolic Instruction Code. The code looks like
the English Language. Now, there are many versions of C# available in the market, the
latest being C# 2017 that is bundled with other programming languages. However, the
most popular one and still widely used by many C# programmers.
C# is a VISUAL object Programming Language because programming is done in a

graphical environment. In C#, you just need to drag and drop any graphical object
anywhere on the form and click on the object to enter the code window and start
programming.
3.6.2. LANGUAGE FEATURE:

Like the basic programming language, C# was designed to accommodate a steep learning
curve. Programmers can create both simple and complex GUI applications. Programming
in C# is a combination of visually arranging components or controls on a form,
specifying attributes and actions for those components, and writing additional lines
of code for more functionality. Since C# defines default attributes and actions for the
components, a programmer can develop a simple program without writing much code.
Programs built with earlier versions suffered performance problems, but faster computers
and native code
compilation has made this less of an issue. Though C# programs can be compiled into
native code executables from version 5 on, they still require the presence of around 1
MB of runtime libraries. Core runtime libraries are included by default in Windows
2000 and later, but extended runtime components still have to be installed. Earlier

versions of Windows (95/98/NT), require that the runtime libraries be distributed with the
executable.
An empty form in C#
Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g.,
text boxes, buttons, etc.) on the form (window). Controls have attributes and event
handlers associated with them. Default values are provided when the control is created,
but may be changed by the programmer. Many attribute values can be modified during
run time based on user actions or changes in the environment, providing a dynamic
application. For example, code can be inserted into the form resize event handler to
reposition a control so
That it remains centered on the form, expands to fill up the form, etc. By inserting code
into the event handler for a keypress in a text box, the program can automatically
translate the case of the text being entered, or even prevent certain characters from being
inserted.
C# can create executables (EXE files), ActiveX controls, or DLL files, but is primarily
used to develop Windows applications and to interface database systems. Dialog boxes
with less functionality can be used to provide pop-up capabilities. The controls provide
the basic functionality of the application, while programmers can insert additional logic
within the appropriate event handlers. For example, a drop-down combination box

automatically displays a list. When the user selects an element, an event handler is called
that executes code that the programmer created to perform the action for that list item.
Alternatively, a C# component can have no user interface, and instead provide ActiveX
objects to other programs via Component Object Model (COM). This allows for server-
side processing or an add-in module.
The runtime recovers unused memory using reference counting, which depends on
variables passing out of scope or being set to nothing, avoiding the problem of memory
leaks common to other languages. There is a large library of utility objects, and the
language provides basic support for object-oriented programming. Unlike many other
programming languages,C# is generally not case-sensitive—though it
transforms keywords into a standard case configuration and forces the case of variable
names to conform to the case of the entry in the symbol table. String comparisons are
case sensitive by default. The C# compiler is shared with other Visual Studio languages
(C, C++). Nevertheless, by default the restrictions in the IDE do not allow creation of
some targets (Windows model DLLs) and threading models, but over the years,
developers have bypassed these restrictions.
3.6.3 WHAT IS THE C# FILE?

Microsoft C# utilizes and creates a number of files at both design and run time. Which
files will be required by your project or application depends upon its scope and
functionality.
3.6.4 IS C# JUST A PROGRAMMING LANGUAGE?
It's more. C# was one of the first systems that made it practical to write programs for the
Windows operating system. This was possible because C# included software tools to
automatically create the detailed programming required by Windows. These software
tools not only create Windows programs, they also take full advantage of the graphical
way that Windows works by letting programmers "draw" their systems with a mouse on
the computer. This is why it's called "Visual and OOP" programming.

C# also provides a unique and complete software architecture. "Architecture" is the way
computer programs, such as Windows and C# programs, work together. One of the major
reasons why C# has been so successful is that it includes everything that is necessary to
write programs for Windows.
3.7 DATABASE MY_SQL INTRO AND INSTALLIONS:
3.7.1. DATABASE INTRODUCTION:

A database is an organized collection of data. It is the collection
of schemas, tables, queries, reports, views, and other objects. The data are typically
organized to model aspects of reality in a way that supports processes requiring
information.
A database management system (DBMS) is a computer software application that

interacts with the user, other applications, and the database itself to capture and analyze
data. A general-purpose DBMS is designed to allow the definition, creation, querying,
update, and administration of databases. Well-known DBMSs
include MySQL, PostgreSQL, MongoDB, MariaDB, Microsoft SQL Server, Oracle, MS
Access etc.
Formally, a "database" refers to a set of related data and the way it is organized. Access
to this data is usually provided by a "database management system" (DBMS) consisting
of an integrated set of computer software that allows users to interact with one or more
databases and provides access to all of the data contained in the database (although
restrictions may exist that limit access to particular data). The DBMS provides various
functions that allow entry, storage and retrieval of large quantities of information and
provides ways to manage how that information is organized.
Because of the close relationship between them, the term "database" is often used
casually to refer to both a database and the DBMS used to manipulate it.

3.7.2. MY_SQL INTRODUCTION:
MY-SQL is a database management system (DBMS) from Microsoft that combines
the relational Microsoft Jet Database Engine with a graphical user interface and software-
development tools. It is a member of the DBMS queries suite of applications, included in
the Professional and higher editions or sold separately.
MY-SQL stores data in its own format based on the Access Jet Database Engine. It can
also import or link directly to data stored in other applications and databases.
Software developers, data architects and power users can use My-SQL to
develop application software. Like other Microsoft Office applications, MY-SQL is
supported by an object.
object-based programming language that can reference a variety of objects including

DAO (Data Access Objects), ActiveX Data Objects, and many other ActiveX
components. Visual objects used in forms and reports expose their methods and
properties in the C# application programming environment, and C# application code
modules may declare and call Windows operating system operations.
3.7.3 MY_SQL FEATURES:

MySQL is offered under two different editions: the open source MySQL Community
Server and the proprietary Enterprise Server. MySQL Enterprise Server is differentiated
by a series of proprietary extensions which install as server plugins, but otherwise shares
the version numbering system and is built from the same code base.
 Major features as available in MySQL 5.6:

 A broad subset of ANSI SQL 99, as well as extensions
 Cross-platform support
 Stored procedures, using a procedural language that closely adheres to SQL/PSM
 Triggers
 Cursors
 Updatable views

 Online DDL when using the InnoDB Storage Engine.
 Information schema
 Performance Schema that collects and aggregates statistics about server execution
and query performance for monitoring purposes.[69]
 A set of SQL Mode options to control runtime behavior, including a strict mode to
better adhere to SQL standards.
 X/Open XA distributed transaction processing (DTP) support; two phase
commit as part of this, using the default InnoDB storage engine
 Transactions with savepoints when using the default InnoDB Storage Engine. The
NDB Cluster Storage Engine also supports transactions.
 ACID compliance when using InnoDB and NDB Cluster Storage Engines[70]
 SSL support
 Query caching
 Sub-SELECTs (i.e. nested SELECTs)
 Built-in replication support (i.e., master-master replication and master-slave
replication) with one master per slave, many slaves per master. Multi-master
replication is provided in MySQL Cluster, and multi-master support can be added
to unclustered configurations using Galera Cluster.
 Full-text indexing and searching
 Embedded database library
 Unicode support
 Partitioned tables with pruning of partitions in optimizer
 Shared-nothing clustering through MySQL Cluster
 Multiple storage engines, allowing one to choose the one that is most effective for
each table in the application.
 Native storage engines InnoDB, MyISAM, Merge, Memory (heap), Federated,
Archive, CSV, Blackhole, NDB Cluster.
 Commit grouping, gathering multiple transactions from multiple connections
together to increase the number of commits per second.

 The developers release minor updates of the MySQL Server approximately every
two months. The sources can be obtained from MySQL's website or from
MySQL's GitHub repository, both under the GPL license.
limitations
When using some storage engines other than the default of InnoDB, MySQL does not
comply with the full SQL standard for some of the implemented functionality, including
foreign key references and check constraints.
Up until MySQL 5.7, triggers are limited to one per action / timing, meaning that at most
one trigger can be defined to be executed after an INSERT operation, and one
before INSERT on the same table. No triggers can be defined on views.
deployment
LAMP software bundle, displayed here together with Squid.
MySQL can be built and installed manually from source code, but it is more commonly
installed from a binary package unless special customizations are required. On
most Linux distributions, the package management system can download and install
MySQL with minimal effort, though further configuration is often required to adjust
security and optimization settings.

Though MySQL began as a low-end alternative to more powerful proprietary databases,
it has gradually evolved to support higher-scale needs as well. It is still most commonly
used in small to medium scale single-server deployments, either as a component in
a LAMP-based web application or as a standalone database server. Much of MySQL's
appeal
originates in its relative simplicity and ease of use, which is enabled by an ecosystem of
open source tools such as phpMyAdmin. In the medium range, MySQL can be scaled by
deploying it on more powerful hardware, such as a multi-processor server with gigabytes
of memory.
There are, however, limits to how far performance can scale on a single server('scalinup'),
so on larger scales, multi-server MySQL ('scaling out') deployments are required to
provide improved performance and reliability. A typical high-end configuration can
include a powerful master database which handles data write operations and
is replicated to multiple slaves that handle all read operations The master server
continually pushes binlog events to connected slaves so in the event of failure a slave can
be promoted to become the new master, minimizing downtime. Further improvements in
performance can be achieved by caching the results from database queries in memory
using memcached, or breaking down a database into smaller chunks called shards which
can be spread across a number of distributed server clusters.
backup software
MySql dump is a logical backup tool included with both community and enterprise
editions of mysql. it supports backing up from all storage engines. mysql enterprise
backup is a hot backup utility included as part of the mysql enterprise subscription
from oracle, offering native innodb hot backup, as well as backup for other storage
engines.
Extra backup is an open-source mysql hot backup software program. features include hot,
non-locking backups for innodb storage, incremental backups, streaming, parallel-
compressed backups, throttling based on the number of i/o operations per second, etc.

high availability software
MySQL Fabric is an integrated system for managing a collection of MySQL servers, and
a framework on top of which high availability and database sharding is built. MySQL
Fabric is open-source, and supports procedure execution in the presence of failure,
providing an execution model usually called resilient execution. MySQL client libraries
are extended so they are hiding the complexities of handling failover in the event of a
server failure, as well as correctly dispatching transactions to the shards.
cloud deployment
MySQL can also be run on cloud computing platforms such as Amazon EC2. Some
common deployment models for MySQL on the cloud are:
virtual machine image
In this implementation, cloud users can upload a machine image of their own with
MySQL installed, or use a ready-made machine image with an optimized installation of
MySQL on it, such as the one provided by Amazon EC2.
mysql as a service
Some cloud platforms offer MySQL "as a service". In this configuration, application
owners do not have to install and maintain the MySQL database on their own. Instead,
the database service provider takes responsibility for installing and maintaining the
database, and application owners pay according to their usage. Notable cloud-based
MySQL services are the Amazon Relational Database Service; Rackspace; HP
Converged Cloud; Heroku and Jelastic.
3.7.4. WHY TO USE MY_ SQL:
Very simply, MY_SQL is an information management tool that helps you store
information for reference, reporting, and analysis. MY_SQL helps you analyze large
amounts of information, and manage related data more efficiently than Microsoft

Excel,Acess or other spreadsheet applications. This article shows you when to use
MY_SQL, and how it can help make you more effective.
3.8 INSTALLATION OF MY-SQL:
To use for C# programming, you need to install XAMPP. See " How to Install".
Download "XAMPP IDE" installer from https://www.apachefriends.org/index.html.

XAMPP is the most popular C# development environment .XAMPP is a completely free,
easy to install Apache distribution containing MariaDB, PHP, and Perl. The XAMPP
open source package has been set up to be incredibly easy to install and to use

CHAPTER 4
SYSTEM DESIGN

4.1 INTRODUCTION TO SYSTEM DESIGN:
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. Systems design could
be seen as the application of systems theory to product development. There is some
overlap with the disciplines of systems analysis, systems architecture and systems
engineering. The logical design of a system pertains to an abstract representation of the
data flows, inputs and outputs of the system. This is often conducted via modeling, using
an over-abstract (and sometimes graphical) model of the actual system. In the context of
systems, designs are included. Logical design includes entity-relationship diagrams (ER
diagrams).
Our proposed system has several advantages
 User friendly interface

 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction
4.1.1 LOGICAL DESIGN:

Logical design of an information system shows the major features and also how they are
related to one another. The first step of the system design is to design logical design
elements. This is the most creative and challenging phase and important too. Design of
proposed system produces the details of the state how the system will meet the
requirements identified during the system analysis that is, in the design phase we have to
find how to solve the difficulties faced by the existing system. The logical design of the
proposed system should include the details that contain how the solutions can be
implemented, given to the system. diagram represents an elided view of the elements that
make up a system. The same element may appear in all diagrams, only a few diagrams, or
in no diagrams at all. In theory, a diagram may contain any combination of things and

relationships. In practice, however, a small number of common combinations arise,
which are consistent with the five most useful views that comprise the architecture of a
software-intensive system. For this reason, the UML includes nine such diagrams:
 Use case diagram

 Collaboration diagram
 Activity diagram
 Data Flow Diagram
 Deployment diagram
4.1.2 PHYSICAL DESIGN:

The process of developing the program software is referred to as physical design. We
have to design the process by identifying reports and the other outputs the system will
produce. Coding the program for each module with its logic is performed in this step.
Proper software specification is also done in this step.
4.1.3 MODULAR DESIGN:

A software system is always divided into several sub systems that makes it easier for the
development. A software system that is structured into several subsystems makes it easy
for the development and testing. A system cannot be decomposed into several subsystems
in any way. There must some logical barrier, which facilitates the separation of each
module. The separation must be simple but yet must be effective so that the development
is not affected. The system under consideration has been divided into several modules
taking inconsideration the above-mentioned criteria. The System have only one module.
Which is Administrator module.
4.1.4 INPUT DESIGN:

The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are
necessary to put transaction data into a usable form for processing data entry. The activity
of putting data into the computer for processing can be achieved by inspecting the

computer to read data from a written or printed document or it can occur by having
people keying the data directly into the system. The design of input focuses on
controlling the amount of input required, controlling errors, avoiding delay, avoiding
extra steps and keeping the process simple. The system needs the data regarding the asset
items, depreciation rates, asset transfer, physical verification for various validation,
checking, calculation and report generation.. The error raising method is also included in
the software, which helps to raise error message while wrong entry of input is done. So in
input design the following things are considered
 What data should be given as input?
 How the data should be arranged or coded?
 Methods for preparing input validations and steps to follow when error occur
 The samples of screen layout are given in the appendix.
4.1.5 OUTPUT DESIGN:

Computer output is the most important and direct information source to the user. Output
design is a process that involves designing necessary outputs in the form of reports that
should be given to the users according to the requirements. Efficient, intelligible output
design should improve the system's relationship with the user and help in decision
making. Since the reports are directing referred by the management for taking decisions
and to draw conclusions they must be designed with almost care and the details in the
reports must be simple, descriptive and clear to the user. So while designing output the
following things are to be considered
 Determine what information to present
 Arrange the presentation of information in an acceptable format
 Decide how to distribute the output to intended receipts
Depending on the nature and future use of output required, they can be displayed on the
monitor for immediate need and for obtaining the hardcopy. The options for the output
reports are given in the appendix

4.1.6 DATABASE DESIGN:
The overall objective in the development of database technology has been to treat data as
an organizational resource and as an integrated whole. DBMS allow data to be protected
and organized separately from other resources. Database is an integrated collection of
data. The most significant form of data as seen by the programmers is data as stored on
the direct access storage devices. This is the difference between logical and physical data
Database files are the key source of information into the system. It is the process of
designing database files, which are the key source of information to the system. The files
should be properly designed and planned for collection, accumulation, editing and
retrieving the required information.
The organization of data in database aims to achieve three major objectives:
 Data integration.
 Data integrity.
 Data independence
4.2 INTRODUCTION TO UML:
4.2.1 UML DESIGN:
The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the software system and its components. It is
a graphical language, which provides a vocabulary and set of semantics and rules. The
UML focuses on the conceptual and physical representation of the system. It captures the
decisions and understandings about systems that must be constructed. It is used to
understand, design, configure, maintain, and control information about the systems.
4.2.2 THE UML IS A LANGUAGE FOR:

o Visualizing
o Specifying
o Constructing
o Documenting

visualizing
Through UML we see or visualize an existing system and ultimately we visualize how
the system is going to be after implementation. Unless we think, we cannot implement.
UML helps to visualize, how the components of the system communicate and interact
with each other.
Specifying
Specifying means building, models that are precise, unambiguous and complete UML
addresses the specification of all the important analysis, design, implementation decisions
that must be made in developing and deploying a software system.
Constructing
UML models can be directly connected to a variety of programming language through
mapping a model from UML to a programming language like JAVA or C++ or VB.
Forward Engineering and Reverse Engineering is possible through UML.
Documenting
The Deliverables of a project apart from coding are some Artifacts, which are critical in
controlling, measuring and communicating about a system during its development
requirements, architecture, desire, source code, project plans, tests, prototypes releasers,
etc...
4.3 UML APPROACH:
4.3.1 UML DIAGRAM:
A diagram is the graphical presentation of a set of elements, most often rendered as a

connected graph of vertices and arcs. You draw diagrams to visualize a system from
different perspectives, so a diagram is a projection into a system. For all but most trivial
systems, a diagram represents an elided view of the elements that make up a system. The
same element may appear in all diagrams, only a few diagrams, or in no diagrams at all. In
theory, a diagram may contain any combination of things and relationships. In practice,
however, a small number of common combinations arise, which are consistent with the five

most useful views that comprise the architecture of a software-intensive system. For this
reason, the UML includes such diagrams:
 Use case diagram

 Class Diagram
 Collaboration diagram
 Data Flow Diagram
 Deployment diagram
Content for use case diagram

There are three basic elements that make up a use case:
 Actors: Actors are the type of users that interact with the system.
 System: Use cases capture functional requirements that specify the intended
 behavior of the system.
 Goals: Use cases are typically initiated by a user to fulfill goals describing the
activities and variants involved in attaining the goal.
 Use cases are modeled using unified modeling language and are represented by
ovals containing the names of the use case. Actors are represented using lines
with the name of the actor written below the line. To represent an actor's
participation in a system, a line is drawn between the actor and the use case.
Boxes around the use case represent the system boundary. Characteristics
associated with use cases are:
 Organizing functional requirements
 Modeling the goals of system user interactions
 Recording scenarios from trigger events to ultimate goals
 Describing the basic course of actions and exceptional flow of events
 Permitting a user to access the functionality of another event

 The steps in designing use cases are:
 Identify the users of the system

 For each category of users, create a user profile. This includes all roles played by
the users relevant to the system.
 Identify significant goals associated with each role to support the system. The
system’s value proposition identifies the significant role.
 Create use cases for every goal associated with a use case template and maintain
the same abstraction level throughout the use case. Higher level use case steps are
treated as goals for the lower level.
 Structure the use cases
 Review and validate the users

Basic Use Case Symbols:

4.3.2 USE CASE DIAGRAM:
A use case diagram in the Unified Modeling Language(UML) is a type of behavioral

diagram defined by and created from a use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their
goals (represented as use cases), and any dependencies between those use cases.
Use case diagrams are formally included in two modeling languages defined by the
OMG: the unified modeling language (UML) and the systems modeling language
(SysML)
 Use case diagram of our project:

Figure 4.3.2 Use Case Diagram

4.3.3 CLASS DIAGRAM:
Class is nothing but a structure that contains both variables and methods. The Class
Diagram shows a set of classes, interfaces, and collaborations and their relationships.
There is most common diagram in modeling the object oriented systems and are used to
give the static view of a system. It shows the dependency between the classes that can be
used in our system.
The interactions between the modules or classes of our projects are shown below. Each
block contains Class Name, Variables and Methods.
The below figure shows that there is one person who is managing all the Entities.
Class diagram shows how different entities (people, things, and data) relate to each other.
In other words, it shows the static structures of the system (Bell, 2003).

Figure 4.3.3 Class Diagram

4.3.4 COLLABORATION DIAGRAM:
A Collaboration Diagram also called a communication diagram or interaction diagram, is

an illustration of the relationships and interactions between software objects. The concept
is more than a decade old, although it has been refined as modeling paradigms have
evolved.
Figure 4.3.4 Collaboration Diagram

4.3.5 CONTEXT LEVEL DIAGRAM:
The Context Diagram shows the system under consideration as a single high-level
process and then shows the relationship that the system has with other external entities
(systems, organizational groups, external data stores, etc.).
Figure 4.3.5 Context Level Diagram
4.3.6 ER DIAGRAM:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 as a way to
unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually
represent data objects. Since Chen wrote his paper the model has been extended and
today it is commonly used for database design for the database designer, the utility of the
ER model is:
It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.

• It is simple and easy to understand with a minimum of training. Therefore, the model
can be used by the database designer to communicate the design to the end user.
• In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.
Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-
many. A one-to-one (1:1) relationship is when at most one instance of an entity A is
associated with one instance of entity B. For example, "employees in the company are
each assigned their own office. For each employee there exists a unique office and for
each office there exists a unique employee. A one-to-many (1:N) relationships is when
for one instance of entity A, there are zero, one, or many instances of entity B, but for one
instance of entity B, there is only one instance of entity A. An example of a 1: N
relationships is a department has many employees each employee is assigned to one
department
A many-to-many (M:N) relationship, sometimes called non-specific, is when for one
instance of entity A, there are zero, one, or many instances of entity B and for one
instance of entity B there are zero, one, or many instances of entity A. The connectivity
of a relationship describes the mapping of associated.
ER Notation
There is no standard for representing data objects in ER diagrams. Each modeling
methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used; among the more common are
Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of
a connection. The notation used in this document is from Martin. The symbols used for
the basic ER constructs are:

• Entities are represented by labeled rectangles. The label is the name of the entity.
Entity names should be singular nouns.
• Relationships are represented by a solid line connecting two entities. The name
of the relationship is written above the line. Relationship names should be verbs
• Attributes when included, are listed inside the entity rectangle. Attributes which
are identifiers are underlined. Attribute names should be singular nouns.
• Cardinality of many is represented by a line ending in a crow's foot. If the crow's

foot is omitted, the cardinality is one.
• Existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar (looks like a 1) next to the entity for
an instance is required. Optional existence is shown by placing a circle next to
the entity that is optional.
• Steps involved in creating an ERD include:

• Identifying and defining the entities.
• Determining all interactions between the entities.
• Analyzing the nature of interactions/determining the cardinality of the

relationships.
• Creating the ERD.
• An entity–relationship model (ER model) describes inter-related things of interest

in a specific domain of knowledge. An ER model is composed of entity types
(which classify the things of interest) and specifies relationships that can exist
between instances of those entity types.

This is represent an entity This is represent the attribute
This is represent the relation

4.4 DATA STORE:
A data store is a holding place for information within the system: It is represented by an
open ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or
may be short-term accumulations: for example batches of documents that are waiting to
be processed. Each data store should be given a reference followed by an arbitrary
number.
Figure 4.4 Data Store

CHAPTER 5
SYSTEM DEVELOPMENT
&
IMPLEMENTATION

5.1 INTRODUCTIONT OF SYSTEM DEVELOPMENT
The systems development also referred to as the application development is a term used
in systems engineering, information systems and software engineering to describe a
process for planning, creating, testing, and deploying an information system. The
systems development life-cycle concept applies to a range of hardware and software
configurations, as a system can be composed of hardware only, software only, or a
combination of both.
The system development life cycle framework provides a sequence of activities for
system designers and developers to follow. It consists of a set of steps or phases in
which each phase of the SDLC uses the results of the previous one.
The SDLC adheres to important phases that are essential for developers, such as
planning, analysis, design, and implementation, and are explained in the section below.
It includes evaluation of present system, information gathering, and feasibility study and
request approval.

SDLC MODEL

5.2 IMPLEMENTATION:
Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus it can be considered to be the most critical stage in achieving a
successful new system and in giving the user, confidence that the new system will work
and be effective.
The implementation stage involves careful planning, investigation of the existing system
and it’s constraints on implementation, designing of methods to achieve changeover and
evaluation of changeover methods
5.2.1 SOFTWARE IMPLEMENTATION:

Implementation is the stage of the project where the theoretical design is turned into a
working system. It can be considered to be the most crucial stage in achieving a
successful new system gaining the users confidence that the new system will work and
will be effective and accurate. It is primarily concerned with user training and
documentation. Conversion usually takes place about the same time the user is being
trained or later. Implementation simply means convening a new system design into
operation, which is the process of converting a new revised system design into an
operational one.
Implementation includes all those activities that take place to convert from the existing
system to the new system. The new system may be a totally new, replacing an existing
manual or automated system or it may be a modification to an existing system. Proper
implementation is essential to provide a reliable system to meet organization
requirements. The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old
system to the new system. The system can be implemented only after through testing is
done and if it is found to be working according to the specifications. The system
personnel check the feasibility of the system. The more complex the system being
implemented, the more involved will be the system analysis and design effort required
to implement the three main aspects: education and training, system testing and
changeover.

 Planning and Scheduling of the implementation.
 Organizational Planning and Personal Administration.
 Final System Design and Testing
 Establishment of Standards of Performance and Control Procedure.
 Conversion form Old to new System.
5.2.2 IMPLEMENTATION PROCEDURES:
Implementation refers to the final process of moving the solution from development
status to production status. Depending on your project, this process is often called
deployment, go-live, rollout or installation. For the purposes of Lifecycle Step, all of
these terms are synonymous with "implementation." The implementation phase deals
with issues of quality, performance, baselines, libraries, and debugging. The end
deliverable is the product itself. The Implementation Phase has one key activity:
installing and releasing the new system in its target environment. After this phase, the
system enters the Operations and Maintenance Phase for the remainder of the system’s
operational life..
5.3 OBJECTIVES AND GOALS:

Objective
Successful completion of the Implementation Phase should comprise:
• Production installation and release
• Training of end users on the system.
Goals
The purpose of the Implementation Phase is to deploy and enable operations of the new
information system in the production environment

CHAPTER 6
SYSTEM TESTING

6.1 INTRODUCTION TO SYSTEM TESTING:
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product It is
the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.
6.2 TYPES OF TESTING:
6.2.1 UNIT TESTING:
Unit testing involves the design of test cases that validate that the internal program logic
is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual
software units of the application. It is done after the completion of an individual unit
before integration. This is a structural testing, that relies on knowledge of its construction
and is invasive. Unit tests perform basic tests at component level and test a specific
business process, application, and/or system configuration. Unit tests ensure that each
unique path of a business process performs accurate to the documented specifications and
contains clearly defined inputs and expected results.
6.2.2 INTEGRATION TESTING:
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfied, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically
aimed at exposing the problems that arise from the combination of components.

6.2.3 FUNCTIONAL TESTING:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centered on the following items:
 Valid Input : identified classes of valid input must be accepted.

 Invalid Input : identified classes of invalid input must be rejected.
 Functions : identified functions must be exercised.
 Output : identified classes of application outputs must be exercised.
 Systems/Procedures : interfacing systems or procedures must be invoked.
Organization and preparation of functional tests are focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identifying
Business process flows; data fields, predefined processes, and successive processes must
be considered for testing. Before functional testing is complete, additional tests are
identified and the effective value of current tests is determined.
6.2.4 SYSTEM TEST:
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system
testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration
points.

6.2.5 WHITE BOX TESTING:
White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
6.2.6 BLACK BOX TESTING:
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box.You cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.
6.2.7 UNIT TESTING:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be
conducted as two distinct phases.
6.3 TEST STRATEGY AND APPROACH:

Field testing will be performed manually and functional tests will be written in detail.
6.3.1 TEST OBJECTIVES:
 All field entries must work properly.

 Pages must be activated by the identified link.
 The entry screen, messages and responses must not be delayed
6.3.2 FEATURES TO BE TESTED:
 Verify that the entries are of the correct format.

 No duplicate entries should be allowed.
 All links should take the user to the correct page.

6.4 INTEGRATION TESTING:
Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company
level – interact without error.
6.4.1 TEST RESULTS:
All the test cases mentioned above passed successfully. No defects encountered.
6.4.2 ACCEPTANCE TESTING:

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.
o Test Results:
o All the test cases mentioned above passed successfully. No defects
encountered.
6.5 DEBUGGING:
Debugging is not tested, but it always occurs as a consequence of testing. It begins with
the execution of a test case. Results are assessed and lack of correspondence between
expected and actual performance is encountered. Debugging is one of the more
frustrating parts of programming. It has elements of problem solving or brain teasers
coupled with the annoying recognition that you have made a mistake. While testing my
software I found some errors, which I corrected in debugging modes. I found Syntax
errors in Black box testing and Logical errors in white-box testing.

6.5.1 SYNTAX ERRORS:
These are caused by typographical errors and incorrect use of the Programming language.
6.5.2 LOGIC ERRORS:
These are caused by the incorrect use of the control structure. These errors were
identified while testing procedure and were corrected in debugging mode.

CHAPTER 7
USER’S GUIDE

SCREEN SHORT:
SCREEN SPLASH:

7.1 LOGIN FORM:
Login page in computer security, logging in is the process by which an individual gains
access to a computer system by identifying and authenticating themselves. The user
credentials are typically some form of "username" and a matching "password",[and these
credentials themselves are sometimes referred to as a login, (or a logon or a sign in or a
sign on).In practice, modern secure systems also often require a second factor for extra
security.
When access is no longer needed, the user can log out (log off, sign out or sign off).
The page contains a form with two fields "USER NAME" and "Password". The admin is
required to enter the user name and password to use the system and to continue to next
page.

Figure 7.1 Login Page Screen Shot
7.2 DASH BOARD:

A dashboard is a visual display of the most important information needed to achieve one
or more objectives; consolidated and arranged on a single screen so the information can
be monitored at a glance. It also contain some quick links. It is not designed exclusively
for executives but rather should be used by the general workforce as effective dashboards
are easy to understand and use. The displayed data automatically updated without any
assistance from the user. The frequency of the update will vary by organization and by
purpose. The most effective dashboards have data updated at least on a daily basis. This
is the page which welcome the user after logging in it has the bar on top containing the
list of all activities that an admin can perform. It also include a bar named as ' Statistics'
which shows the summary of total activity of HRMS.
Figure 7.2 Dashboard Screen Shot

7.3 ADD NEW EMPLOYEE AND JOB TITLE:
Figure 7.3 Foam New Employee and job Screen Shot
7.3.1 ADD PERSONAL DETAIL:

Figure 7.3.1 Personal Detail Screen Shot
7.3.2 ADD JOB DETAIL:
Figure 7.3.2 Job Detail Screen Shot

7.3.3 EDIT PERSONAL DETAIL:
Figure 7.3.3 Edit Personal Detail Screen Shot

7.3.4 EDIT JOB DETAIL:
Figure 7.3.4 Edit Job Detail Screen Shot

7.4 ADD MONTHLY ATTENDANCE:
Figure 7.4 Monthly Attendance Screen Shot
7.4.1 EXCEL REPORT OF MONTHLY ATTENDANCE:

Figure 7.4.1 Excel Report of Attendance Screen Shot
7.5 ADD EMPLOYEE LEAVE:
Figure 7.5 Employee Leave Screen Shot
7.5.1 ADD LEAVE DETAIL:

Figure 7.5.1 Leave Detail Screen Shot
7.6 ADD PAYROLL STRUCTURE:
Figure 7.6 Payroll Structure Screen Shot
7.6.1 ADD SALARY STRUCTURE:

Figure 7.6.1 Salary Structure Screen Shot
7.6.2 PAYROLL LEAVE REPORT:
Figure 7.6.2 Payroll Leave Report Screen Shot
7.6.3 PAYROLL DETAIL REPORT:
Figure 7.6.3 Payroll Employee Report Screen Shot

7.7 ADD EMPLOYEE LOAN:
Figure 7.7 Employee Loan Screen Shot
7.7.1 ADD EMPLOYEE LOAN STRUCTURE:

Figure 7.7.1 Employee Loan Screen Shot
7.8 HRM REPORT FORM:
Figure 7.8 HRM Report Screen Shot
7.8.1 EMPLOYEE PERSONAL REPORT:
Figure 7.8.1 Employee Personal Report Screen Shot

7.8.2 EMPLOYEE JOB REPORT:
Figure 7.8.2 Employee Job Report Screen Shot
7.8.3 EMPLOYEE ATTENDANCE REPORT:
Figure 7.8.3 Employee Attendance Report Screen Shot

7.8.4 EMPLOYEE LEAVE REPORT:
Figure 7.8.4 Payroll Leave Report Screen Shot
7.8.5 EMPLOYEE PAYROLL REPORT:
Figure 7.8.5 Employee Payroll Report Screen Shot

7.9 CHANGE PASSWORD:
Figure 7.9 Change Password Screen Shot
7.10 ABOUT US:
Figure 7.10 About us Screen Shot

CHAPTER 8
CONCLUSION

8.1 CONCLUSION:
Since we are entering the details of the Employee electronically in the” Human Resource
Management System”, data will be secure. Using this application, we can retrieve the
Employee’s history with a single click. Thus, processing information will be faster. It
guarantees accurate maintenance of Employee details. It easily reduces the book keeping
tasks and thus reduces the human effort and increases accuracy speed.
The system manages has data for multiple Employee for various dates and times. Each
time a Employee visits HRMS his/her Employee entry is stored in the database by a
Admin. Next time a user can only search the Employee, after he may view his/her entire
Employee history as and when needed. The Admin may view Employee history etc
Attendance, loan, salary,payroll and leaves.

REFERENCES

8.2 REFERENCES:
1.Osborn, John (August 1, 2000). "Deep Inside C#: An Interview with Microsoft Chief
Architect Anders Hejlsberg". O'Reilly Media. Retrieved November 14, 2009.
2. "Generics (C# Programming Guide)". Microsoft. Retrieved March 21, 2011.
3."ISO/IEC 23270:2003 - Information technology - C# Language Specification". Iso.org.
August 23, 2006. Retrieved October 4, 2012.
4. "ISO/IEC 23270:2006 - Information technology - Programming languages - C#".
Iso.org. January 26, 2012. Retrieved October 4, 2012.
5. Hejlsberg, Anders (October 1, 2008). "The A-Z of Programming Languages C#
". Computerworld.
6. "Microsoft C# FAQ". Microsoft. Archived from the original on February 14, 2006.
Retrieved March 25, 2008.
7. "Visual C#.net Standard" (JPEG). Microsoft. September 4, 2003. Retrieved June
18, 2009.


HRM Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HRM Report

Uploaded by

Copyright:

Available Formats

CHAPTER 1

Human Resource Management System Page 1

1.2 PURPOSE OF THE STYDY:

The HR center is a powerful application designed to allow companies to streamline their

 Employee and Company Information

The HR Center includes a comprehensive employee information database, work

Human Resource Management System Page 2

To develop a software application that supports Specific to the HR Automation in an

To allow the HR department of an organization to update the employee details whenever

1.4 SCOPE OF THE STUDY:

1.5 PROJECT OVERVIEW:

The entire project covers following:

 Add new Employee Personal Details

Human Resource Management System Page 3

The Training and Placement provides following features.

Human Resource Management System Page 4

This application is developed by using Desktop application in visual C# (C sharp)

1.7 DEVELOPMENT METHODOLOGY:

System development methodology is a framework that is used to structure, plan and

1.8 WATERFALL MODEL:

Human Resource Management System Page 5

Human Resource Management System Page 6

2.2 HARDWARE REQUIREMENTS:

HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

PROCESSOR: Intel dual Core, i3

2.3 SOFTWARE REQUIREMENTS:

Human Resource Management System Page 7

OPERATING SYSTEM: Windows 7/ XP

PLATFORM: Visual Studio Professional 2015

FRONT END: C# (C SHARP)

BACK END: My-SQL Server Database

Human Resource Management System Page 8

Human Resource Management System Page 9

3.2 PROPOSED SYSTEM:

In new computerized system I tried to give these facilities.

3.3 FEASIBILITY STUDY:

Human Resource Management System Page 10

3.3.1 TECHNICAL FEASIBILITY:

 Is the project feasible within the limits of current technology?

Human Resource Management System Page 11

 Is the project feasible to operate or not?

3.3.3 ECONOMIC FEASIBILITY:

 Is the system cost effective?

Human Resource Management System Page 12

3.3.4 SCHEDULE FEASIBILITY:

Can the project really be completed in the given period of time.

legal & ethical feasibility

Human Resource Management System Page 13

3.4 SOFTWARE SPECIFICATION:

The concept of computer programming

3.4.1 USER REQUIREMENTS:

3.4.2 FUNCTIONAL REQUIREMENTS:

Human Resource Management System Page 14

3.4.3 NON-FUNCTIONAL REQUIREMENTS:

The should be sufficient network bandwidth

 Backup- provision for data backup

In other words, the most important requirements are shown first.

3.5 CONSISTENT UPTIME:

dealing with large quantities of data

Human Resource Management System Page 15

3.6 LANGUAGE INTRODUCTION:

Human Resource Management System Page 16

A programmer can create an application using the components provided by the C#