Project Report

On
PG SYSTEM

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

KHALSA COLLEGE OF ENGINEERING AND TECHNOLOGY

SUBMITTED TO: SUBMITTED BY:

Er. Supreet Kaur Rozy Bawa (1315273)

1
CONTENT
S.NO TITLE PAGE.NO
1. INTRODUCTION TO PROJECT 3-4
2. Time Schedule 5
3. Requirement Analysis 6-7
4. METHODOLOGY 8-14
5. Current Status Of Development 15
6. DATA FLOW DIAGRAMS 16-21
7. HARDWAREREQUIREMENT 22
SOFTWARE REQUIREMENT

9. 24

2
INTRODUCTION TO HRM
The human resources of an organization consist of all people who perform its
activities. Human resource management (HRM) is concerned with the personnel
policies and managerial practices and systems that influence the workforce. In
broader terms, all decisions that affect the workforce of the organization concern
the HRM 3Function .

The activities involved in HRM function are pervasive throughout the

organization. Line managers, typically spend more than 50 percent of their time for
human resource activities such hiring, evaluating, disciplining, and scheduling
employees. Human resource management specialists in the HRM department help
organizations with all activities related to staffing and maintaining an effective
workforce. Major HRM responsibilities include work design and job analysis,
training and development, recruiting, compensation, team-building, performance
management and appraisal, worker health and safety issues, as well as identifying
or developing valid methods for selecting staff. HRM department provides the
tools, data and processes that are used by line managers in their human resource
management component of their job.

Activities it Perform:

(1) Organizational design,

(2) Staffing,

(3) Performance Management and Appraisal,

(4) Employee and Organizational Development, and

(5) Reward Systems, Benefits and Compliance

3
 Functions of Human Resource Management System

4
Aim of Project
The main aim of the project was to develop a Human Resource Module for the
Automation of HR Software in which all the information regarding the employees in the
company will be present. This has to be developed with good Interaction/
communication facilities between the employees and HR Administrator in such a
manner that a level of hierarchy was maintained between the various employees.

The web pages about an employee are created dynamically based on the user id and
password and links are provided to web pages containing information about Employee
General Profile, Salary Details, Payroll and other static links to various other pages. An
Information Hierarchy is maintained i.e. the information regarding a particular employee
is accessed by the same or any person above him in the information hierarchy. There
was also a provision for updating the details.

Each employee has the facility of Updating his General Details, Contact Details,
Education Details, Certification Details, Skill Details and Project Details. User Controls
are provided for Navigating through the web Pages.

HR Admin page is created with HR Admin Tasks. HR Administrator is provided with

facility of Adding Employee in to the company. He adds the new employee’s General
details and can also enter his Contact, Skill, Education, Certification, and Project
Details. He also has the facility of Viewing / Updating all Employees General, Contact,
Educational and other details.

The function of Human Resources departments is generally administrative and common

to all organizations. Organizations may have formalized selection, evaluation, and
payroll processes. Efficient and effective management of "Human Capital" progressed
to an increasingly imperative and complex process. The HR function consists of tracking
existing employee data which traditionally includes personal histories, skills, capabilities,
accomplishments and salary. To reduce the manual workload of these administrative
activities, organizations began to electronically automate many of these processes by
introducing specialized Human Resource Management Systems. HR executives rely on
internal or external IT professionals to develop and maintain an integrated HRMS.
Before the client–serverarchitecture evolved in the late 1980s.

5
Modules It Support
In This Project We Create Two User. Each User have Different Functionality According To Their
work In a organization.

1) Administrator

2) Employee

ADMINISTRATOR
1)ADMIN

 User Management
 Job
 Organization
 General Info

2) PIM

 Employee List
 Add Employee
 Bulk Update

3) Leave Management

 Config
 Assign Leave
 Leave List

4 ) Time Management

 Attendance
 Time Sheet
 View Attendance

5) Recruitment

 Candidate
 Vacancy

6
Employee
Each Employee of The Company have Login Id and Password. Each Employee Can Login Into
Their Account By Proper Id and Password. If They Fill Incorrect Password Then Invalid Access
Pop on the Window. If They Fill valid Password Then They Login To Their Account.

1) Leave Management
 Apply Leave.
 My Leave
2) Time Management
 Time Sheet For a Week
 My Attendance
3) MY Info
4) Recruitment
5) Training

7
Software life Cycle Models
System Engineering and Analysis
At this step the developers decide a roadmap of their plan and try to bring up the best
software model suitable for the project. System analysis includes Understanding of
software product limitations, learning system related problems or changes to be done in
existing systems beforehand, identifying and addressing the impact of project on
organization and personnel etc. The project team analyzes the scope of the project and
plans the schedule and resources accordingly.

Software Requirement Analysis

If the feasibility report is positive towards undertaking the project, next phase starts with
gathering requirements from the user. Analysts and engineers communicate with the
client and end-users to know their ideas on what the software should provide and which
features they want the software to include.

Design

3.1 Design Phase

The design phase decides how the system will operate, in terms of the hardware,
software, and network infrastructure; the user interface, forms, and reports that will
be used; and the specific programs, databases, and files that will be needed.
Although most of the strategic decisions about the system were made in the
development of the system concept during the analysis phase, the steps in the
design phase determine exactly how the system will operate.

The design phase has four steps:-

1. The design strategy must be developed. This clarifies whether the system will be
developed by the company’s own programmers, whether it will be outsourced to
another firm (usually a consulting firm), or whether the company will buy an
existing software package.

8
2. This leads to the development of the basic architecture design for the system that
describes the hardware, software, and network infrastructure that will be used. In
most cases, the system will add or change the infrastructure that already exists in
the organization. The interface design specifies how the users will move through
the system (e.g., navigation methods such as menus and on-screen buttons) and the
forms and reports that the system will use.

3. The database and file specifications are developed. These define exactly what
data will be stored and where they will be stored.

4. The analyst team develops the program design, which defines the programs that
need to be written and exactly what each program will do. This collection of
deliverables (architecture design, interface design, database and file specifications,
and program design) is the system specification that is handed to the programming
team for implementation.

At the end of the design phase, the feasibility analysis and project plan are re-
examined and revised, and another decision is made by the project sponsor and
approval committee about whether to terminate the project.

The purpose of the design phase is to plan a solution of the problem specified by
the requirement document. This phase is the first step in moving from problem
domain to the solution domain. The design of a system is perhaps the most critical
factor affecting the quality of the software, and has a major impact on the later
phases, particularly testing and maintenance. The output of this phase is the design
document. This document is similar to a blue print or plan for the solution, and is
used later during implementation, testing and maintenance.
The design activity is often divided into two separate phase-system design and
detailed design. System design, which is sometimes also called top-level design,

9
aims to identify the modules that should be in the system, the specifications of
these modules, and how they interact with each other to produce the desired
results. At the end of system design all the major data structures, file formats,
output formats, as well as the major modules in the system and their specifications
are decided.
During detailed design the internal logic of each of the modules specified in system
design is decided. During this phase further details of the data structures and
algorithmic design of each of the modules is specified. The logic of a module is
usually specified in a high-level design description language, which is independent
of the target language in which the software will eventually be implemented. In
system design the focus is on identifying the modules, whereas during detailed
design the focus is on designing the logic for each of the modules. In other words,
in system design the attention is on what components are needed, while in detailed
design how the components can be implemented in software is the issue.
A design methodology is a systematic approach to creating a design by application
of set of techniques and guidelines. Most methodologies focus on system design.
The two basic principles used in any design methodology are problem partitioning
and abstraction. A large system cannot be handled as a whole, and so for design it
is partitioned into smaller systems. Abstraction is a concept related to problem
partitioning. When partitioning is used during design, the design activity focuses
on one part of the system at a time. Since the part being designed interacts with
other parts of the system, a clear understanding of the interaction is essential for
properly designing the part. For this, abstraction is used. An abstraction of a
system or a part defines the overall behavior of the system at an abstract level
without giving the internal details.

10
Next step is to bring down whole knowledge of requirements and analysis on the desk
and design the software product. The inputs from users and information gathered in
requirement gathering phase are the inputs of this step. The output of this step comes in
the form of two designs; logical design and physical design. Engineers produce meta-
data and data dictionaries, logical diagrams, data-flow diagrams and in some cases
pseudo codes.

Coding
This step is also known as programming phase. The implementation of software design
starts in terms of writing program code in the suitable programming language and
developing error-free executable programs efficiently.

Testing
The testing phase involves the testing of the developed system using various kinds of
data. An elaborated testing of data is prepared and a system is tested using the test
data. While testing, errors are noted and corrections remade, the corrections are also
noted for future use.
SYSTEM TESTING
Testing is a set of activities that can be planned in advance and conducted
systematically. The proposed system is tested in parallel with the software that consists
of its own phases of analysis, implementation, testing and maintenance. Following are
the tests conducted on the system.
UNIT TESTING
During the implementation of the system each module of the system was tested
separately to uncover errors with in its boundaries. User interface was used as a guide
in the process.
MODULE TESTING
A module is composed of various programs related to that module. Module
testing is done to check the module functionality and interaction between
units within a module.

11
It checks the functionality of each program with relation to other programs
within the same module. It then tests the overall functionality of each
module.

INTEGRATION TESTING
Integration testing is a systematic technique for constructing the
program structure while conducting tests to uncover errors associated with
interfacing. The objective is to take unit-tested module and build a program
structure that has been dictated by design.

ACCEPTANCE TESTING
The software has been tested with the realistic data given by the client
and produced fruitful results. The client satisfying all the requirements
specified by them has also developed the software within the time limitation
specified. A demonstration has been given to the client and the end-user
giving all the operational features.

IMPLEMENTATION PHASE
The implementation is the final and important phase. It involves
User training, system testing and successful running of the developed
system. The users test the developed system when changes are made
according to the needs. The testing phase involves the testing of the
developed system using various kinds of data. An elaborate testing of data is
prepared and system is tested using the tests data.

Implementation is the stage where theoretical design turned into a

working system. Implementation is planed carefully to propose system to
avoid unanticipated problems. Many preparations involved before and during

12
the implementation of proposed system. The system needed to be plugged
in to the organization’s network then it could be accessed from anywhere,
after a user logins into the portal. The tasks that had to be done to
implement the system were to create the database tables in the organization
database domain. Then the administrator was granted his role so that the
system could be accessed.

The next phase in the implementation was to educate the system. A

demonstration of all the functions that can be carried out by the system was
given to examination department person, who will make extensive use of the
system.
An estimate says that 50% of whole software development process should be tested.
Errors may ruin the software from critical level to its own removal. Software testing is
done while coding by the developers and thorough testing is conducted by testing
experts at various levels of code such as module testing, program testing, product
testing, in-house testing and testing the product at user’s end. Early discovery of errors
and their remedy is the key to reliable software.

Maintenance

This phase confirms the software operation in terms of more efficiency and less errors.
If required, the users are trained on, or aided with the documentation on how to operate
the software and how to keep the software operational. The software is maintained
timely by updating the code according to the changes taking place in user end
environment or technology. This phase may face challenges from hidden bugs and real-
world unidentified problems.

Documentation

Software Requirement Specification

SRS is a document created by system analyst after the requirements are collected from
various stakeholders.

SRS defines how the intended software will interact with hardware, external interfaces,
speed of operation, response time of system, portability of software across various

13
platforms, maintainability, speed of recovery after crashing, Security, Quality,
Limitations etc.

The requirements received from client are written in natural language. It is the
responsibility of system analyst to document the requirements in technical language so
that they can be comprehended and useful by the software development team.

Feasibility Study

Technical Feasibility
The technical feasibility 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 need of the proposed system.

Operational Feasibility
Operational feasibility is a measure of how well a proposed system solves the problems,
and takes advantage of the opportunities identified during scope definition and how it
satisfies the requirements identified in the requirements analysis phase of system
development.

Economic Feasibility
The purpose of the economic feasibility assessment is to determine the positive
economic benefits to the organization that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This assessment typically
involves a cost/ benefits analysis.

Time Feasibility
A project will fail if it takes too long to be completed before it is useful. Typically this
means estimating how long the system will take to develop, and if it can be completed in
a given time period using some methods like payback period. Schedule feasibility is a
measure of how reasonable the project timetable is. Given our technical expertise, are
the project deadlines reasonable? Some projects are initiated with specific deadlines. It
is necessary to determine whether the deadlines are mandatory or desirable.

14
METHODOLOGY
In this project we are demonstrating the System on Asp.Net with C# language,
through which we are implementing such application which provide facility to
maintain large amount of data easily and calculate the Attendance, Leave
,Holiday, Working hours ,Shifts and Salary of Employees for Time
Management Module as well as for Students of ATS (Apprentice Student
Training). There are different types of methodologies i.e., Structured and Design
approach and Object Oriented approach. In our project Human Resource
Management System we have used Object Oriented approach.

Classes
The major driving force behind object-oriented programming is the use of Classes
that allows for writing of code that can be reused in multiple projects. Each of the
classes has a unique string identifier ID and defined properties based on specific
characteristics of the class
.
Modules
The modules which represent separate units of functionality are helper classes
which handle the utilities of the application. The HRM system includes the
following modules:
a) Time Management
b) Recruitment
c) Payroll
d) Performance

Interface
The Graphical User Interface (GUI) is closely tied to the HRM system classes and
is divided into three levels:
a) Form: the form is the base of the GUI. There is a home or parent form under
which all other forms fall (child forms) which handles the classes. A child form
contains a control, lists and menus.
b) Control: Every child form has a control which displays the class which the
form handles.
c) List: Every child form has a list which displays all instances of a particular class
as icons with an identifying text. The child form also contains another list showing
the dependent items of objects in the main list.

15
DATA FLOW DIAGRAMS

A graphical tool used to describe and analyze the moment of data through a
system manual or automated including the process, stores of data, and delays in the
system. Data Flow Diagrams are the central tool and the basis from which other
components are developed. The transformation of data from input to output, through
processes, may be described logically and independently of the physical components
associated with the system. The DFD is also know as a data flow graph or a bubble
chart.

CONTEXT DIAGRAM:

The top-level diagram is often called a “context diagram”. It contains a single process,
but it plays a very important role in studying the current system. The context diagram
defines the system that will be studied in the sense that it determines the boundaries.
Anything that is not inside the process identified in the context diagram will not be part
of the system study. It represents the entire software element as a single bubble with
input and output data indicated by incoming and outgoing arrows respectively.

TYPES OF DATA FLOW DIAGRAMS:

Data Flow Diagrams are of two types as follows:

(a) Physical DFD

(b) Logical DFD

1. PHYSICAL DFD:

Structured analysis states that the current system should be first understand
correctly. The physical DFD is the model of the current system and is used to ensure
that the current system has been clearly understood. Physical DFDs shows actual
devices, departments, and people etc., involved in the current system

16
2. LOGICAL DFD:

Logical DFDs are the model of the proposed system. They clearly should show
the requirements on which the new system should be built. Later during design
activity this is taken as the basis for drawing the system’s structure charts.

BASIC NOTATION:

The Basic Notation used to create a DFD’s are as follows:

DATAFLOW:

Data move in a specific direction from an origin to a destination.

PROCESS

People, procedures, or devices that use or produce (Transform) Data. The physical
component is not identified.

SOURCE:

External sources or destination of data, which may be People, programs,organizations

or other entities.

17
DATA STORE:

Here data are stored or referenced by a process in the System.

DESIGN:

Design is the first step in moving from problem domain to the solution domain. Design
is essentially the bridge between requirements specification and the final solution.

The goal of design process is to produce a model or representation of a system, which

can be used later to build that system. The produced model is called the “Design of the
System”. It is a plan for a solution for the system.

Data flow diagram is a pictorial representation of the system in which flow of data from
one process to another process is described. A Data Flow is composed of:

1. Data movement shown by arrows.

2. Transformation or process of data shown by named circle or rounded rectangle.
3. Sources and destination of data represented by named rectangle.
4. Static storage or data at rest denoted by an open rectangle that is name

18
Level0 DIAGRAM

It’s a diagram, which shows whole system at once. The sources in level0 diagram for
this system are admin and user who are linked to the Project Module. The level0
Diagram is shown in Fig (0):

19
LEVEL1 DIAGRAM:

User login process is the Level1 DFD shown in Fig (1). In this level, administrator or
the user has to give out the login details i.e. Employee id and password and then
only he can be logged on. The id and password given are checked from the data
stored in the database. The table that contains the login data is referred for checking
the details if the admin id and password given are correct then he can be logged on
to the site. Depending on the type of user i.e. either admin or a normal user, he is
provided with various privilege to work on the HRMS application.

user, he is provided with various privilege to work on the HRMS application.

Fig (1)

20
LEVEL 2 DIAGRAMS: The different processes done by user is shown in Level2 .

21
DATABASE
A database is a set of data, organized for easy access. The database is an
actual data; it is the database that you will be accessing when you need to retrieve data.
DATA DICTIONARY
The data dictionary is a set of tables Oracle uses to maintain
information about the database. The data dictionary contains information
about tables, indexes, clusters and so on.

DBA (DATABASE ADMINISTRATOR)

The DBA is the person responsible for the operation, configuration and
performance of the database. The DBA is charged with keeping the
database operating smoothly, ensuring that backups are done on regular
basis (and that backups work), and installing new software. Other
responsibilities might include planning for future expansion and disk space
needs, creating databases and table spaces, adding users and maintaining
security, and monitoring the database and retuning it as necessary. Large
installations might have teams of DBA’s to keep the system running
smoothly; alternatively, the task might be segmented among the DBA’s.

22
EXISTING SYSTEM
The Present system uses a very basic excel sheets, the decision for appraisal of
assigning next task are not properly projected.

 Need for extra effort

 Data maintenance may not be accurate

 Longer time to find a suitable employee

 No facility for employees to know their details

 Danger of losing files in some cases

 It is not User Friendly

PROPOSED SYSTEM
The two most important aspect of Human Resource Department are the
Recruitment system and the Performance management system

This system is designed to eliminate the drawbacks of the existing system and
provide permanent solution to existing problems

The competitive advantage in the organization can be sustained through these

modules:

 Recruitment ,employee management and administration

 Employee
 Job seeker
 User

23
SOFTWARE REQUIREMENTS
FRONT END TOOLS:

1. Microsoft Visual Studio 2008

2. C#

3. Asp.Net

BACK END TOOLS:

1. SQL Server 2005

OPERATING SYSTEM:

1. MICROSOFT WINDOWS 7

HARDWARE REQUIREMENTS
HARD DISK: 40 GB

RAM: 4 GB

PROCESSOR: INTEL ® CORE (TM) 2 DUO CPU

SYSTEM TYPE: 32 BIT OPERATING SYSTEM

24
ADVANTAGES
 It helps analyze the opportunities and threats that are crucial, from the point
of view of the company.
 It is possible to develop strategies and have a vision for the future.
 The need for competitive intelligence, which is of utmost importance in
strategic planning, is fulfilled by means of implementing strategic human
resource management.
 The attrition rate can be reduced, if strategic HRM is implemented properly.
It also performs the important task of motivating employees.
 Development and maintenance of competency among employees, is the
most important benefit offered by strategic HRM.
 It helps determine the weaknesses and strengths of the company, thereby
enabling the management to take appropriate measures.
 It helps keep a check whether the expectations of employees are addressed
properly.
 Business surplus is achieved by making the employees competent enough to
deliver the good

DISADVANTAGES
 Inability of the management in communicating the vision and mission of
Company clearly to the employees.
 Interdepartmental conflict and lack of vision among the senior management
in implementing the HR policies.
 The diversity of workforce that makes it difficult for the management to
handle them accordingly.
 Conflict among the employees over the issue of authority and the related
fear of victimization.

25
  The resistance from institutions such as the labor unions.
 Changes that take place in the organizational structure.

26
FRONT END:
INTRODUCTION TO VISUAL STUDIO 2008
Microsoft Visual Studio is an integrated development environment (IDE) from
Microsoft. It is used to develop computer programs for Microsoft Windows, as
well as web sites, web applications and web services. Visual Studio uses Microsoft
software development platforms such as Windows API, Windows Forms,
Windows Presentation Foundation, Windows Store and Microsoft Silver light. It
can produce both native code and managed code.

Visual Studio includes a code editor supporting IntelliSense (the code completion
component) as well as code refactoring. The integrated debugger works both as a
source-level debugger and a machine-level debugger. Other built-in tools include a
forms designer for building GUI applications, web designer, class designer, and
database schema designer. It accepts plug-ins that enhance the functionality at
almost every level—including adding support for source-control systems (like
Subversion) and adding new toolsets like editors and visual designers for domain-
specific languages or toolsets for other aspects of the software development
lifecycle (like the Team Foundation Server client: Team Explorer).

Visual Studio supports different programming languages and allows the code
editor and debugger to support (to varying degrees) nearly any programming
language, provided a language-specific service exists. Built-in languages include
C,C++ and C++/CLI (via Visual C++), VB.NET (via Visual Basic .NET), C# (via
Visual C#), and F# (as of Visual Studio 2010). Support for other languages such as
M, Python, and Ruby among others is available via language services installed
separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS.
Java (and J#) were supported in the past.

Microsoft provides "Community" editions of its Visual Studio at no cost.

Commercial versions of Visual Studio along with select past versions are available
for free to students via Microsoft's Dream Spark program.

Microsoft provides a preview of Visual Studio Code for free with a proprietary
license. It is a source code and text editor, along with other features, for Linux, OS
X, and Window. Features are code editor, debugger and designer.

27
INTRODUCTION TO C#
C# is an elegant and type-safe object-oriented language that enables developers to
build a variety of secure and robust applications that run on the .NET Framework.
You can use C# to create Windows client applications, XML Web services,
distributed components, client-server applications, database applications, and
much, much more. Visual C# provides an advanced code editor, convenient user
interface designers, integrated debugger, and many other tools to make it easier to
develop applications based on the C# language and the .NET Framework.

C# syntax is highly expressive, yet it is also simple and easy to learn. The curly-
brace syntax of C# will be instantly recognizable to anyone familiar with C, C++
or Java. Developers who know any of these languages are typically able to begin to
work productively in C# within a very short time. C# syntax simplifies many of the
complexities of C++ and provides powerful features such as nullable value types,
enumerations, delegates, lambda expressions and direct memory access, which are
not found in Java. C# supports generic methods and types, which provide increased
type safety and performance, and iterators, which enable implementers of
collection classes to define custom iteration behaviors that are simple to use by
client code. Language-Integrated Query (LINQ) expressions make the strongly-
typed query a first-class language construct.

As an object-oriented language, C# supports the concepts of encapsulation,

inheritance, and polymorphism. All variables and methods, including the Main
method, the application's entry point, are encapsulated within class definitions. A
class may inherit directly from one parent class, but it may implement any number
of interfaces. Methods that override virtual methods in a parent class require the
override keyword as a way to avoid accidental redefinition. In C#, a struct is like a
lightweight class; it is a stack-allocated type that can implement interfaces but does
not support inheritance.

In addition to these basic object-oriented principles, C# makes it easy to develop

software components through several innovative language constructs, including the
following:

28
  Encapsulated method signatures called delegates, which enable type-safe
event notifications.
 Properties, which serve as assessors for private member variables.
 Attributes, which provide declarative metadata about types at run time.
 Inline XML documentation comments.
 Language-Integrated Query (LINQ) which provides built-in query
capabilities across a variety of data sources.

If you have to interact with other Windows software such as COM objects or
native Win32 DLLs, you can do this in C# through a process called "Interop."
Interop enables C# programs to do almost anything that a native C++ application
can do. C# even supports pointers and the concept of "unsafe" code for those cases
in which direct memory access is absolutely critical.

The C# build process is simple compared to C and C++ and more flexible than in
Java. There are no separate header files, and no requirement that methods and
types be declared in a particular order. A C# source file may define any number of
classes, structs, interfaces, and events.

29
INTRODUCTION TO ASP.NET
ASP.NET is a web development platform, which provides a programming model, a
comprehensive software infrastructure and various services required to build up
robust web applications for PC, as well as mobile devices.

ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and
policies to set a browser-to-server bilateral communication and cooperation.

ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled

codes, written using the extensible and reusable components or objects present in
.Net framework. These codes can use the entire hierarchy of classes in .Net
framework.

The ASP.NET application codes can be written in any of the following languages:

 C#
 Visual Basic.Net
 Jscript
 J#

ASP.NET is used to produce interactive, data-driven web applications over the

internet. It consists of a large number of controls such as text boxes, buttons, and
labels for assembling, configuring, and manipulating code to create HTML pages.
Components of .Net Framework 3.5

Before going to the next session on Visual Studio.Net, let us go through at the
various components of the .Net framework 3.5. The following table describes the
components of the .Net framework 3.5 and the job they perform:

Components and their Description

30
(1) Common Language Runtime or CLR It performs memory management,
exception handling, debugging, security checking, thread execution, code
execution, code safety, verification, and compilation. The code that is directly
managed by the CLR is called the managed code. When the managed code is
compiled, the compiler converts the source code into a CPU independent
intermediate language (IL) code. A Just In Time(JIT) compiler compiles the IL
code into native code, which is CPU specific.

(2) .Net Framework Class Library

It contains a huge library of reusable types. classes, interfaces, structures, and

enumerated values, which are collectively called types.

(3) Common Language Specification

It contains the specifications for the .Net supported languages and implementation
of language integration.

(4) Common Type System

It provides guidelines for declaring, using, and managing types at runtime, and
cross-language communication.

(5) Metadata and Assemblies

Metadata is the binary information describing the program, which is either stored
in a portable executable file (PE) or in the memory. Assembly is a logical unit
consisting of the assembly manifest, type metadata, IL code, and a set of resources
like image files.

(6) Windows Forms

Windows Forms contain the graphical representation of any window displayed in

the application.

(7) ASP.NET and ASP.NET AJAX

ASP.NET is the web development model and AJAX is an extension of ASP.NET

for developing and implementing AJAX functionality. ASP.NET AJAX contains
the components that allow the developer to update data on a website without a
complete reload of the page.
31
(8) ADO.NET

It is the technology used for working with data and databases. It provides access to
data sources like SQL server, OLE DB, XML etc. The ADO.NET allows
connection to data sources for retrieving, manipulating, and updating data.

(9) Windows Workflow Foundation (WF)

It helps in building workflow-based applications in Windows. It contains activities,

workflow runtime, workflow designer, and a rules engine.

(10) Windows Presentation Foundation

It provides a separation between the user interface and the business logic. It helps
in developing visually stunning interfaces using documents, media, two and three
dimensional graphics, animations, and more.

(11) Windows Communication Foundation (WCF)

It is the technology used for building and executing connected systems.

(12) Windows CardSpace

It provides safety for accessing resources and sharing personal information on the
internet.

(13) LINQ

It imparts data querying capabilities to .Net languages using a syntax which is

similar to the tradition query language SQL.

32
BACKEND: SQL SERVER 2005
Microsoft SQL Server is a relational database management system developed by
Microsoft. As a database server, it is a software product with the primary function
of storing and retrieving data as requested by other software applications which
may run either on the same computer or on another computer across a network
(including the Internet).

Microsoft markets at least a dozen different editions of Microsoft SQL Server,

aimed at different audiences and for workloads ranging from small single-machine
applications to large Internet-facing applications with many concurrent users.

SQL Server uses as its primary query languages T-SQL and ANSI SQSQL Server
2005 (formerly codenamed "Yukon") released in October 2005. It included native
support for managing XML data, in addition to relational data. For this purpose, it
defined an xml data type that could be used either as a data type in database
columns or as literals in queries. XML columns can be associated with XSD
schemas; XML data being stored is verified against the schema. XML is converted
to an internal binary data type before being stored in the database. Specialized
indexing methods were made available for XML data. XML data is queried using
XQuery; SQL Server 2005 added some extensions to the T-SQL language to allow
embedding XQuery queries in T-SQL. In addition, it also defines a new extension
to XQuery, called XML DML, that allows query-based modifications to XML
data. SQL Server 2005 also allows a database server to be exposed over web
services using Tabular Data Stream (TDS) packets encapsulated within SOAP
(protocol) requests. When the data is accessed over web services, results are
returned as XML.

33
Common Language Runtime (CLR) integration was introduced with this version,
enabling one to write SQL code as Managed Code by the CLR. For relational data,
T-SQL has been augmented with error handling features (try/catch) and support for
recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has
also been enhanced with new indexing algorithms, syntax and better error recovery
systems. Data pages are check summed for better error resiliency, and optimistic
concurrency support has been added for better performance. Permissions and
access control have been made more granular and the query processor handles
concurrent execution of queries in a more efficient way. Partitions on tables and
indexes are supported natively, so scaling out a database onto a cluster is easier.
SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET
Framework.

SQL Server 2005 introduced Multi-Version Concurrency Control. User facing

features include new transaction isolation level called SNAPSHOT and a variation
of the READ COMMITTED isolation level based on statement-level data
snapshots.

SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of
allowing usage of database connections for multiple purposes.

SQL Server 2005 introduced DMVs (Dynamic Management Views), which are
specialized views and functions that return server state information that can be
used to monitor the health of a server instance, diagnose problems, and tune
performance.

Service Pack 1 (SP1) of SQL Server 2005 introduced Database Mirroring, a high
availability option that provides redundancy and failover capabilities at the
database level. Failover can be performed manually or can be configured for
automatic failover. Automatic failover requires a witness partner and an operating
mode of synchronous (also known as high-safety or full safety). Database
Mirroring was included in the first release of SQL Server 2005 for evaluation
purposes only. Prior to SP1, it was not enabled by default, and was not supported
by Microsoft.

34
35
 Human Resource Management

36
 Human Resource Management

37
 Human Resource Management

38
 Human Resource Management

39
 Human Resource Management

40
 Human Resource Management

41
 Human Resource Management

42
 Human Resource Management

43
 Human Resource Management

44
 Human Resource Management

45
 Human Resource Management

46
 Human Resource Management

47
 Human Resource Management

48
 Human Resource Management

49
 Human Resource Management

50
 Human Resource Management

51
 Human Resource Management

Future Scope
Future scope of the Application

The Human Resource Management System is an ambitious project. It can be various

other aspects of Human Resource System like training, recruitment etc. I am very
thankful for being provided this great opportunity to work on it. On the basis of the
Project work using Asp.net, I have successfully designed and implemented this HRMS
project.

Software scope
● Extensibility
● Reusability
● Understandability
● Cost Effectiveness

52