62261222 Employee Management System

8/3/2019 62261222 Employee Management System

1/121

Employee Management System

CHAPTER 1

1.1 Background of the Study

In terms of background the Employee Management System for Human Resource

Department of NCO is old and not that user friendly. NCO is an industry leader in

providing clients with successful business process outsourcing (BPO) solutions.

Our outsourcing portfolio includes accounts receivable management, customer

management services, and back office services for a diversified customer base.

Since NCO's inception in 1926, their goal has remained constant - to reduce client

operating expenses, increase cash flow, and improve their customers' experience.

The best-in-class, results-driven reputation, strong financial track record, and

proven business model makes NCO the choice for BPO solutions.

To meet and surpass the growing and complex needs of their clients, NCO's

services support essential functions across key portions of the customer lifecycle,

including acquisition, growth, care, resolution, and retention. NCO provides its

services through Customer Lifecycle Management, a unique customer-driven

model that delivers our optimal performance, leading-edge technology, proven

efficiency, and exceptional quality.

NCO operates a global network of over 100 operations centers running on a

centralized data platform with the flexibility to respond to a rapidly changing

marketplace, and to scale operations to meet client specifications. Their clients are

empowered to successfully address immediate business needs, while enabling long-

term growth across the entire customer lifecycle.

The application software takes care of database and day to day operations. For the

ease of the user the computer-based application is developed using VB.NET and MS

SQL/ACCESS server in the back.

1


2/121

1.2Statement of the Problem

General Problem

The problem is how to innovate, design, develop and implement a new computer-

based application which is the employee management system for the Human

Resource Department of NCO.

Specific Problems

Specifically the study aims to answer the following problem:

1. How to innovate and implement the current employee management system of

NCO that will monitor the employees quantity and personal information?

We would like to innovate the current employee management system of NCO

because we like to develop a more detailed, consistent and user friendly

computer based-application.

2. How to create a module that will add, edit, and delete query in the database of

the employees personal records.

1.3 Objectives of the Study

1.3.1 General Objectives

The main objective of the project is to innovate and develop a

computerized employee management system for NCO which could help

their Human Resource Department to be more efficient in their work and

to account their employees.

1.3.2 Specific Objectives

2


3/121

Specifically the study aims to:

Create a module that will add, edit, and delete employees personal and

working information to help the management trace their employees.

Create a module that will search employees data efficiently.

Help the Human Resource Department of NCO to work more efficient and

user friendly.

1.4 Significance of the Study

The function of the system will be managing Employees at various field offices from

the Head Quarter .It manages information about Employees of NCO at various Field

offices. It manages information regarding Human Resources through field offices. So,

that manpower can be monitored at Head Quarter.

1.5 Scope and Limitations

a. The system will cover only the employee management system which includes

record keeping of employees records

b. It will not cover the payroll system or the computation of employees salary

3


4/121

CHAPTER 2

PROBLEM FORMULATION

Introduction

Problem introduction or problem stating is the starting point of the software

development activity. The objective of this statement is to answer: Exactly what must

the system do? The software project is initiated by the clients need. In the beginning,

these needs are on the minds of various people in the clients organization. The

analyst has to identify the requirements by talking to the people and understanding totheir needs .it gores without saying that an accurate and through understanding of

Software requirements are essentials to the success of software development effort. all

further development like system analysis, System design and coding will depend on

how accurate and well understood the requirements are poorly analyzed and specified

software will disappoint the user and will bring brief to the developer. No matter how

well designed and well coded the software is. Software requirement appears to be a

relatively simple task, but appearances are often deceiving. Chances of misinterpretation are very high, ambiguity is probable and communication gap

between customer and developer is bound to bring confusions. Requirement

understanding begins with a clear and concise heading stating in a sentence the task to

be performed. Then Requirements are described in a technical manner in precise

statements.

2.1 DETAILED DESCRIPTION OF THE PROJECT

Labour Information Systems Division of NIC is actively involved in development of

the application for Directorate General of Labour Welfare. In all, application systems

were to be developed and implemented at CLC Division in Labour Ministry. System

maintains the information about the Employee records, it maintain the each and every

record about the employee regarding their posting, leave, vacancy position etc., it

maintains the details of all Employees located at various field offices. The application

software takes care of database and day-to-day operations. DGLW (Directorate

4


5/121

General of Labour Welfare) has its Headquarter in Delhi and its field offices are

spread across the country. This project will help in capturing information regarding

Human Resources through field offices. So, that manpower can be monitored at Head

Quarter. For the ease of the user and for the public the existing systems were migrated

to web-based applications.

2.1.1 Major Functions

1. Employee Management

The function of the system will be managing Employees at various field offices from

the Head Quarter .It manages information about Employees of DGLW at various

Field offices. It manages information regarding Human Resources through field

offices. So, that manpower can be monitored at Head Quarter.

2.2 METHODOLOGY TO BE USED CARRYING OUT THE STUDY

Studying the existing system. This will involve the

amount of information, the manpower equipment space

and other resources used for the information storage.

After analysing the existing setup this study would

suggest a new management setup. The benefits and

disadvantages of existing and new system would be

critically revised.

Cost Benefit Analysis study will done.

The database structure and information storage retrieval

process will also be studied and a new system for faster

response using operation research techniques will be

designed.

2.3 BUSINESS PROCESSES

2.4 Existing System

5


6/121

The existing system comprises of a system in which details are to be manually

handled. This is not user friendly.

2.5 The proposed system

It will be able to manage information about Employee in more user friendly way. This

system will manage Employees information at various field offices. User ID and

password has been given to all the field offices so that they can enter their employees

information into central database. Their access to the central database is restricted to

their information only. Various reports based on the data entered by employees at

field offices are generated at Head Quarter. These reports are helpful in Manpower

management decisions.

6


7/121

CHAPTER 3

SYSTEM ANALYSIS AND DESIGN

3.1Defining A System

Collections of components, which are interconnected, and work together to realize

some objective, form a system. There are three major components in every system,

namely input, processing and output.

Input Output

3.1.1 Systems Life Cycle

The sequencing of various activities required for developing and maintaining systems

in an ordered form is referred as Systems Life Cycle. It helps in establishing a system

project plan as it gives overall list of process and sub-processes required for

developing any system. Here, the systems life cycle will be discussed with reference

to the development of Employee Management System.

Broadly, following are the different activities to be considered while defining the

systems development cycle for the said project:

Problem Definition

Systems analysis

Study of existing system

Drawbacks of the existing system

7

Processing


8/121

Proposed system

Systems Requirement study

Data flow analysis

Feasibility study

Systems design

Input Design (Database & Forms)

Updation

Query /Report Design

Administration

Testing

Implementation

Maintenance

3.1.2 System Analysis

System analysis is a logical process; the objective of this phase is not actually to solve

the problem but to determine what must be done to solve the problem. The basic

objective of the analysis stage is to develop the logical model of the system using

tools such as the data flow diagram and elementary data description of the elementary

algorithm. The logical model is Subject to review by both the management and the

user who agree that the model does in fact reflect what should be done to solve the

problem.

System analysis is not a precise science. It is in fact more of an art, aided by scientific

approach to find definition and recording data, gathering traditional structures is only

one part of the system analysis, the next step is to examine the data, assess the

situation and looking at the alternatives.

3.2 Analysis and development of the actual solution

8


9/121

A complete understanding of the requirement for the new system is very important for

the successful development of a software product. Requirement Specification is the

foundation in the process of software development .All further developments like

system analysis; designing and coding will depend on how accurate and well

documented the Requirement Specification is.

Requirement specification appears to be a relatively simple task, but appearance is

often deceiving. There is always a chance of wrong specification because of

communication gap between the user and the Developer. Requirement Specification

begins with a clear statement of the problem and the task to be performed. Then the

requirement is described in a technical manner in precise statements. After the initial

specification reports are received, they are analyzed and redefined through customer

interaction.

3.3 Project Overview

3.3.1 Product prospective

It will be able to manage information about Employee in more user friendly way. This

system will manage Employees information at various field offices. User ID and

password has been given to all the field offices so that they can enter their employees

information into central database. Their access to the central database is restricted to

their information only. Various reports based on the data entered by employees at

field offices are generated at Head Quarter. These reports are helpful in Manpower

management decisions.

3.3.2 User Interface

The system will be having user privileges based menu.

User will have to select the options form the given

menu.

The system will be entering the information into the

database to generate reports.

The forms will be designed to enter the data.

9


10/121

Buttons will be used to insert, retrieve or modify the

data.

Links will be provided to shift from one form to

another.

3.3.3 Hardware Software Interface

An Internet Web Server, running IIS, in this case Windows 2000 advanced server is

used to host the application. The application software, Employee Management, is

developed in ASP, JavaScript, and HTML. The backend database is MS SQL Server

2000. The Client systems with internet facility equipped with web browser will be

able to access the system

3.3.4 Memory Constraints

No memory constraints are applicable. A normal memory configuration is more than

sufficient.

3.3.5 Product Function

It is advisable to have weekly data backups. The system administrator will do the data

recovery. Selection of panel is user-initiated operation, while indent handling is client

initiated

3.4 Constraints

3.4.1 General Constraints

1) This system will not take care of any virus problem,

which might occur either on the client or the server

system. Avoiding the use of pirated software and

ensuring that floppies and other removable media are

scanned for viruses before use could minimize the

possibility of viral infection.

10


11/121

2) Recovery of data after a system crash will be possible

only if backups are taken at regular intervals.

3) Manual interfaces cannot be fully avoided. Documented

proofs like dates etc. will have to be verified by theconcerned staff before entering it into the computerized

system

3.4.2 Hardware Constraints

Constraints of the Internet & Intranet will be applicable to the system. The

performance of the system will be dependent on the network conditions like network

congestion, bandwidth etc. The primary memory (RAM) and the secondary memory

(Hard Disk Space) requirement of the system at the client end will be the same as that

required by the web browser and the operating system. At the server end memory

requirements will be that of the server software (Operating system, Database

Software, etc) and the space required to store the data. The space required to store the

data would increase as more and more records are added to the system.

3.4.3 Security Constraints

User will be authenticated by the use of username and passwords. This does not

Provide complete security and the system could be hacked into. Use of secure SocketLayer (SSL) is recommended. Use of SSL prevents any unauthorized access as all

communications are encrypted. Valid Digital Certificates are required for this at the

server end and the client web browser should have support for SSL.

3.4.4 Assumptions and Dependencies

11


12/121

1. It is assumed that the user is

familiar with the basic computer

fundamentals.

2. Timely backup of data should betaken to avoid data loss in case of

system crash.

3. The use of pirated software

should be avoided as it may lead

to data loss and system crashes

due to viral infections.

4. Floppies and other removable

media should be scanned for

viruses before use.

5. Proper configuration of the client,

database server and network is

necessary for the system to

function as intended.

6. It is assumed that the

maintenance of the database will

be assigned to the authorized

person only.

7. Only authorized persons will be

allowed inside the server room.

3.5 Feasibility Study

The main objective of the feasibility study is to treat the technical, Operational,

logical and economic feasibility of developing the computerized system. All systems

are feasible, given unlimited resources and infinite time. It is both necessary and

prudent to evaluate the feasibility of the project at System study phase itself. The

feasibility study to be conduced for this project Involves.

1. Technical Feasibility

12


13/121

2. Operational Feasibility

3. Economic Feasibility

4. Logical Feasibility

3.5.1 Technical Feasibility

Technical feasibility includes Risk Resources availability and technologies. The

management provides latest hardware and software facilities for the successful

completion of the projects. With these latest hardware and software support the

system will perform extremely well. The system is available through Internet.

3.5.2 Operational Feasibility

In the existing manual system it is very difficult to maintain and update huge amount

of information. The development of the system was started because of the

requirement put forward by the management of the concerned department. This

system, will handles the request in a better way and make the process easier thus, it is

sure that the system developed is operationally feasible.

3.5.3 Economic Feasibility

In the economic feasibility the development cost of the system is evaluated weighing

it against the ultimate benefit derived from the new system. It is found that the

benefit, from the new system would be more than the cost and time involved in its

development.

3.5.4 Legal Feasibility

In the legal feasibility it is necessary to check that the software we are going to

develop is legally correct which means that the ideas which we have taken for the

proposed system will be legally implemented or not. So, it is also an important step in

feasibility study.

3.6 Information Gathering

13


14/121

We have taken an approach of gathering information with sensitivity and precautions.

3.6.1 Information about project:

During the analysis, we collected whole information from Mr. Alok Roy, Scientist

D, NIC, and staff members of the DGLW, Labour ministry, New Delhi.

3.6.2 Information Sources:

We have collected the information about the current system from:

1. Reports

2. Personal staff

3. System Documentation

4. Trainees

5. Existing System

14


15/121

3.7 DFD

Login form

loginform

user

Username,password

Verifyinguser

usertable

Allocating particular menu

menutable

Username,password

userlevel

userlevel

Menuorder,menugroup,menutitle,menulink,itemorder

15


16/121

DFD of Transfer

ListingLeaveDetails

Finding particular entry

Updatingentry

Adding newentry

Employee

Emp_name,Emp_ID

Emp_name,Emp_ID

Emp_name,Emp_ID

Type,from,to,Remarks,Date

Type, From, To,Reason


User


DFD of Leaveform

16


17/121

Dfd of form Employee

17

SelectRegion

Finding particular entry

Updatingentry

Adding newentry

Region,prev_Region,prev_statn,

Employee_ID

Emp_ID

Prev_regn,Prev_statn

RegionEmployee Posting

User

1

1

1.Emp_name,Prev_Region,Prev_station,new_Region,new_designation,Date


18/121

DFD of EmployeeCR

ListingDesignation

Find particular entry

Update particular entry

GnrlCode Employee

Adding newentry

Region,Designation

Designation,Region

Region,Designation

1

1.Emp_ID,name,seniority,dob,Desig,post,

basic.file_no,category,station,dt_posting,dt_presentstn,dt_entry,postname,qualification,description,remarks,increment,perm/temp,dt_comfirmation,dt_leaving,reason_leaving

User

1

18

ListingStation

FindingParticular entries

Adding new entry

Updating an entry

Station VacancyPosition

User

Region,Station

Region,Station,Designation

1.Date,Sanction_perm,Sanctioned_temp,fillperm_R,fillperm_T,fillperm_A, fillperm_C ,filltemp_C,filltemp_A,Remarks

DFD of Vacancyposition

1

1

Region,Station,Designation


19/121

3.8 Processing Logic

The Employee Management System has been designed and developed for variousfield offices of DGLW to capture the information about human resources. Various

19

Add newentry of EmployeeCR

Find particular EmployeeCR entry

EmployeeCR

UpdateEmployeeCR

entry

Region,Station,Emp_name

,Emp_ID

User

Region,Station,Emp_name,Emp_ID

Emp_ID,Cryear,Received,remarks

ListingEmployees

Emp_ID,Emp_name

Employee

Emp_ID,Cryear,Received,remarks


20/121

details about the Employee is entered in the system with all details like Employee

name, Designation, Date of birth, Station, Region, seniority, etc. There are some

major activities which is taking care by the Employee Management System.

Employee Management System

All of the Employee record such as his name, designation, Region of posting,

station of posting, his salary detail, seniority level, date of joining, qualification etc.,

is entered into the computerized system by the Employees at various Regional

Offices.

DGLW Vacancy Position Information

This file contains the information regarding Vacancy Position at various regional

offices. Such as station, sanctioned strength, number of permanent filled posts,

number of temporary filled posts etc,

DGLW Employee detail

This file stores multiple information of Employee. Each employee has a separaterecord regarding his basic information such as his designation, region of posting

,basic salary, seniority level, DOB, date of joining, date of retirement, qualification

etc.,.

DGLW Employee Posting/Transfer detail

After some certain specified time employees are Posted/Transferred to different

Stations of different Regions this file keep track of Posting/Transfer record of theEmployees.

On giving these details, some reports and queries are generated by the system.

3.8.1 Reports Generated by the System

(a) List of Vacancy Detail designation wise

(b) List of Vacancy Detail Region wise

20


21/121

(c) List of Vacancy Detail Region and Designation wise

(d) Vacancy Position Report for a particular Region, Station, Designation

(e) Vacancy Position Report for a particular Region

(f) Vacancy Position Report for a particular Designation

3.8.4 Data Structures

The Database DGLW contains the tables that contain the information related to

system and the data needed to run the software. The tables are discussed in detail:

Directorate General of Labour Welfare (DGLW)

1. BalanceLeave :Table contains the information of balance leaves of the

Employee

2. Payscale :Table contains information of Employees basic salary,

increment

3. Defaults : Table contains default information about Employee

4. EmpAddress : It contains the Address of all Employee

5. Employee : contains all the information about employee regarding his date

of joining, seniority, posting region and all other

6. EmployeeCR : Table contains information about Employees CR

7. GnrlCode : Code directory of Designation

8. GnrlDir :Table contains of code directory

9. Leave : Table contains information about leave

10. LeaveApplication : Table contains record of the application

applied for leave

11. Leo : Table contains basic information about

Employee

12. Menutable : Table contains the Menu item for dynamic

generation

21


22/121

13. Posting : Table contains information about

Employees posting at various Regions

14. Region : Region code directory

15. SectionPosting : Division code directory

16. Station : Station code directory

17. StatusLeave : Table contains information about status of the

leave taken

18. UserTable : Table contains the information of

various users of the Software

19. VacancyPosition : Table contains information about vacancy

position at various Regions

3.9 Application Architecture

Most of the users database system today is not present at user premises, but clients

connect to it through a network. We can therefore differentiate between client and

server machine. In our system the information about personnel and post exist in the

central database. But it need to be accessed from DGLW offices all over India so that

employees can view, enter or modifies their personal information through their user-id

and password. This can be done only through web based application architecture, as

shown in the next page.

22


23/121

Fig: 3.0 Three tier Architecture

User

ApplicationClient (Employees)

Application Server

Database System

23


24/121

Tables used:

3.10 Database Architecture

Fig: 3.1 Table: BalanceLeave

Fig: 3.2 Table: Paysclale

24


25/121

Fig: 3.3 Table: Defaults

Fig: 3.4 Table: EmpAddress

25


26/121

Fig: 3.5 Table: Employee

Fig: 3.6 Table: EmployeeCR

26


27/121

Fig: 3.7 Table: GnrlCode

Fig: 3.8 Table: GnrlDir

27


28/121

Fig: 3.9 Table: Leave

Fig: 3.10 Table: LeaveApplication

28


29/121

Fig: 3.11 Table:LEO

Fig: 3.12 Table: MenuTable

29


30/121

Fig: 3.13 Table:Posting

Fig: 3.14 Table: Region

30


31/121

Fig: 3.15 Table: SectionPosting

Fig: 3.16 Table: Station

31


32/121


33/121

Fig: 3.19 Table: VacancyPosition

33


34/121

34


35/121

35


36/121

3.11 Input / Output Specification

3.11.1 Screen Layouts

For Screen layouts refer annexure Forms Layouts.

3.11.2 Report Layout

For report layout refer annexure Report Layouts.

3.11.3 Navigation (Menu Description)

From the DGLW Portal the user will login by given userID and password in the login

dialogue box. After user validation the system will display the customized home page

and menu options depending upon user roles and access permissions.

3.11.4 Help Facilities

Document has user manual to the user separately. On line User Manual has not been planned yet.

3.11.5Error Messages

Suitable error messages should be flashed on error arising from Data inputs, which is

easily understood by the user.

3.12 Choice of Tools and Technologies

Introduction

Technologies and tools are strongly related to the approach of software development.

What the tools can or cannot do significantly impact what principles that can be used,

as well as what objectives that can be fulfilled. While selection of a particular

methodology may imply use of certain tools, the tools themselves often leavesignificant room for developers to choose how to use them. The selection has

36


37/121

therefore been based mainly on the objectives of the project, while the methodologies

were selected after the tools were selected, due to the fact that technologies and tools

poses certain restrictions of how development can be done.

3.12.1 ASP

ASP stands for Active Server Pages, and it is Microsoft's implementation of server-

side scripting. In short, this server-site scripting basically means that a script is parsed

and executed by the server. When a user requests a web-page containing ASP, the

web-server will parse code and send the result to the user, so the ASP code will never

reach the user's browser. This is the exact opposite of JavaScript.

You don't need to be a programmer to understand ASP, but you should have some

HTML knowledge, as the actual design of the web page will require it.

To use ASP scripts, you must have installed Microsoft's IIS (Internet Information

Services), which is a web-server included in Windows 2000 and Windows XP

Professional. It is also a part of the Windows NT 4.0 Option Pack, which can be

downloaded from Microsoft's web-site. If IIS is not already installed on your

computer, you can install it using the Add/Remove Programs section within the

Windows Control Panel. The ASP engine is included within IIS, so you won't have to

download it and install it separately. You must have Windows NT 4.0 or later to run

IIS, so if you use Windows 98 you should install PWS (Personal Web Server), which

is the smaller brother of IIS.

You can use ASP code to do a lot of things: dynamically edit, change or add any

content to a web-page, access and query databases, read or write files, connect to

remote computers, create images - the only limit is your imagination. The most

obvious difference from HTML files is that ASP files have the extension ".asp", but

this doesn't mean that you need to separate the ASP code from the HTML code in

different files; you can use one file which will include both HTML and ASP code.

The web-server won't mind at all, it will parse the ASP code and forget about the

HTML code. Depending on your ASP code, the web-server will output some HTML

instead of the ASP code, so the web-browser will only see HTML.

This provides a higher level of security, because nobody will be able to view your ASP code, and copy it and use it on their own web-page. Furthermore, you don't need

37


38/121

any extra components for your web-browser, because the ASP files are returned in

plain HTML, so they can be viewed in any web-browser.

In case you don't have Windows, you should know that some companies also didn't

like the fact the ASP was only available for Windows platforms, so they decided toadapt ASP to other operating systems. So they created technologies like Chili ASP

and iASP, which allow you to take advantage of the ASP technology while using

other web-servers, not just IIS. And because other web-servers run on many operating

systems - like Apache web-server - this extends the ASP technology too, so it can run

on other operating systems.

Active Server Pages or ASP, as it is more commonly known, is a technology that

enables you to make dynamic and interactive web pages. ASP uses server-sidescripting to dynamically produce web pages that are not affected by the type of

browser the web site visitor is using. The default scripting language used for writing

ASP is VBScript, although you can use other scripting languages like JScript

(Microsoft's version of JavaScript). ASP pages have the extension .asp instead of

.htm, when a page with the extension .asp is requested by a browser the web server

knows to interpret any ASP contained within the web page before sending the HTML

produced to the browser. This way all the ASP is run on the web server and no ASPwill ever be passed to the web browser. Just simply just simply opening the page in a

web browser cannot run any web pages containing ASP. The page must be requested

through a web server that supports ASP, this is why ASP stands for Active Server

Pages, no server, and no active pages. As ASP was first introduced by Microsoft on

its web server, Internet Information Services (IIS) that runs on Windows 2000/XP

Pro/NT4, it is this web server that ASP pages usually run best on. For those of you

running Windows and wish to play around with ASP on your own system you willneed to install Microsoft's Internet Information Services (IIS). Lucky IIS or its micro

version Personal Web Server (PWS) comes free with Windows. For Windows users

you can find Internet Information Services (IIS) or Personal Web Server (PWS) in the

following places: -

Windows 2000/XP Pro - IIS can be found in 'Add/Remove Programs' in the

'Control Panel'.

Windows 98 - PWS can be found under 'add-ons' on the Windows 98 CD.

38


39/121

Windows NT4/95 -You can get hold of IIS by downloading the NT4 Option

Pack from Microsoft (don't be fooled by the name as it also runs on Windows

95).

Windows ME - IIS and PWS are not supported on this operating system.

Windows XP Home Edition - IIS and PWS are not supported on this

3.12.2 ASP Programming

Active Server Pages ( ASP ) programming is writing code to facilitate ASP functionality

on websites. Such functionality includes the delivery of dynamic, database-driven

content to website viewers without taxing the server-side system. ASP programming

involves writing ASP files and HTML files. The ASP code is placed within the HTML

pages, enclosed in special tags. When you need to make changes in the ASP

programming code, you need change only the ASP files; the HTML files, which do

nothing but go and get the ASP files' coding, need not be changed.

ASP files have a file extension of .asp, much like HTML files have file extensions of

either .htm or .html. The HTML files that contain the ASP instructions enclose those

instructions within tags that look like this: Notice that unlike HTML, the ASP endingtag does not include a slash. To send the results of an ASP instruction directly to a

browser, you add an equals sign:


40/121

Written data isnt the only thing that can be uploaded to your website using ASP

programming. You can design forms that allow users to upload image files to your

site as well. Real estate websites are perfect examples of sites that can take advantage

of this functionality.

ASP programming also comes in handy when your HTML pages and what they

display involve accessing large databases containing tons of data. In this case, you

will really appreciate the benefits of not having to change HTML files when you

update the parameters of your databases. ASP programming makes this process

simple.

3.12.3 Parsing ASP Code

In order to correctly parse (process) a selection of ASP code, no matter how long and

complex, you need a HTTP web server.

Generally, ASP pages run under Microsofts Internet Information Server (IIS), which

comes as an optional installation from the Windows 2000 and XP Professional CD's.

Windows 98 includes a cut down version of IIS called Personal web server (PWS)

The ASP parsing is enabled via the ASP DLL . This enables any piece of codeencased within the ASP tags () to be parsed as ASP. The rest of the

HTML page will be untouched and processed by the web browser client side.

ASP can be embedded within HTML. The example below shows how you would

create a table and place a simple date function to return the current date and time.

The date/time is

The process of embedding ASP within HTML is known as "spaghetti coding".

40


41/121

3.12.4 Connecting to a Database

One of the major features of ASP is database connectivity. ASP can be used to

connect primarily to Microsoft Access or SQL Server database. an ASP script can

contain Structured query language (SQL) statements to insert , delete and update

records within a database (to name just a few) For example :

SELECT * FROM myTable WHERE myValue = 'myValue'

INSERT INTO myTable (value1) VALUES ("myValue")

A database connection is done via a connection string in the ASP source code. There

are two ways this is generally done, one is using a data source name (DSN) and the

other is using a DSN-Less connection string, which instead can use the

Server.MapPath method or physical pathname to locate the database.

An example connection string using a DSN:

DSN's are created using the ODBC data source administrator. This can be found in

your system32 folder or within control panel. When you set up a data source name

you are required to input the data source name, plus the database that it connects to

and the path of that database. A user ID and password are also necessary, which is

what will be within the two "", "" parameters in the dbase.Open line.

Example of a dsn-less connection, using Server.MapPath:

41


42/121

42


43/121

CHAPTER 4

TESTING AND IMPLEMENTATION

4.1 Objectives of Testing:

This section introduces the concept of testing and how important is, for the successful

implementation of the project. Different phases of testing are described along with the

level of testing incorporated in this particular project.

Testing is vital to the success of any system. Testing is done at different stages within

the phase. System testing makes a logical assumption that if all phases of the system

are correct, the goals will be achieved successfully. Inadequate testing at all leads to

errors that may come up after a long time when correction would be extremely

difficult. Another objective of testing is its utility as a user-oriented vehicle before

implementation. The testing of the system was done on both artificial and live data.

Testing involves operation of a system or application under controlled conditions and

evaluating the results (e.g., if the user is in interface A of the application while using

hardware B and does C, then D should not happen). The controlled conditions should

include both normal and abnormal conditions.

Typically, the project team includes a mix of testers and developers who work closely

together, with the overall QA processes being monitored by the project managers.

4.2 Types of Testing

4.2.1 Black Box Testing

Also known as functional testing, this is a software testing technique whereby the

tester does not know the internal working of the item being tested. Black-box test

design treats the system as a black-box, so it does not explicitly use knowledge of

the internal structure. Black-box test design is usually described as focusing on testing

functional requirements. Synonyms for black-box includes: behavioral, functional,opaque-box and closed-box.

43


44/121

4.2.2 White Box Testing

White box test design allows one to peek inside the box, and it focuses specifically

on using internal knowledge of the software to guide the selection of test data.

Synonyms for white-box include: structural, glass-box and clear-box.

4.2.3 Condition Testing

An improvement over White-box testing, the process of condition testing ensures that

a controlling expression has been adequately exercised whist the software is under test

by constructing a constraint set for every expression and then ensuring that every

member on the constraint set is included in the values whish are presented to theexpression

4.2.4 Data Life-Cycle Testing

It is based upon the consideration that in the software code, a variable is at some stage

created, and subsequently may have its value changed or used in a controlling

expression several times before being destroyed. If only locally declared Boolean

used in control conditions are considered then an examination of the sources code will

indicate the place in the source code where the variable is created, places where it is

given a value is used as a part of a control expression and the place where it is

destroyed.

This approach to testing requires all possible feasible lifecycles of the variable to be

covered whilst the module is under test.

4.2.5 Unit Testing

The purpose of this phase is to test the individual units of the developing software

component. This phase is recursive and is to be repeated, as many as there are, levels

of testing. In the DGLW project, each individual form has been tested using

techniques of testing namely: Client side testing using JavaScript.

Each individual form has been validated so that user enters only valid data at every

time.

44


45/121

4.2.6 Functional Testing:

This is done for each module / sub module of the system. Functional testing serve as a

means of validating whether the functionality of the system Confers the original user

requirement i.e. does the module do what it was supposed to do? Separate schedules

were made for functional testing. It involves preparation of the test data, writing of

test cases, testing for conformance to test cases and preparation of bugs listing for

non-conformities.

4.2.7 System Testing:

System testing is done when the entire system has been fully integrated. The purposeof the system testing is to test how the different modules interact with each other and

whether the entire system provides the functionality that was expected.

System testing consists of the following steps:

a) Program Testing

b) String Testing

c) System Testing

d) System Documentation

e) User Acceptance Testing

4.3 Various Levels Of Testing

Before implementation the system is tested at two levels:

Level 1

Level 2

4.3.1 Level 1 Testing (Alpha Testing)

At this level a test data is prepared for testing. Project leaders test the system on this

test data keeping the following points into consideration:

Proper error handling

45


46/121

Exit Pints in code

Exception handling

Input / Output format

Glass box testing

Black box testing

If the system is through with testing phase at LEVEL 1 then it is passed on to

LEVEL 2.

4.3.2 Level 2 Testing (Beta Testing)

Here the testing is done on the live database. If errors are detected then it is sent back

to LEVEL 1 for modification otherwise it is passed on to LEVEL 3.

This is the level at which the system actually becomes live and implemented for the

use of END USERS.

We have also checked the proposed system for :

Recovery & Security

A forced system failure is induced to test a backup recovery procedure for file

integrity. Inaccurate data are entered to see how the system responds in terms of error

detection and protection. Related to file integrity is a test to demonstrate that data and

programs are secure from unauthorized access.

Usability Documentation & Procedure :

The usability test verifies the user-friendly nature of the system. This relates to normal

operating and error-handling procedures.

4.4 Quality Assurance

Proper documentation is must for mainframe of any software. Apart from In-line

documentation while coding. Help coding, help files corresponding to each program

were prepared so as to tackle the person-dependency of the existing system.

46


47/121

4.5 System Implementation

During the implementation stage the system is physically created. Necessary

programs are coded, debugged and documented. A new hardware is selected, ordered

and installed.

4.6 System Specification

Every computer system consists of three major elements.

1. The Hardware

2. Application Software such as visual studio.

3. Operating system

For successful operation of the package following must be kept in mind:

Too many packages should not be used, as very few systems may have all those

packages installed due to memory problem. Thus, the compatibility of the system

developed will get reduced.

4.6.1 Hardware Requirements

Intel Pentium processor at 500 MHz or faster, minimum of 364 MB available disk

space for installation (including IBM SDK), minimum of 256 MB memory,512 MB

recommended, CD-ROM drive.

4.6.2 Software Requirements

The application software is hosted on the MOLDB (Ministry of Labour &

Employment Database server) web server located at NIC Computer Cell, Ministry of

Labour, Shram Shakti Bhawan, Rafi Marg, New Delhi. The application software is

developed in ASP, JavaScript, and HTML. The central database is based on MS SQL

Server 2000. The system can be accessed over the Internet connecting all the Internet

of Ministry of Labour & Employment nodes. Clients equipped with web-browsers can

access the system from any of the Intranet Nodes.

47


48/121

4.7 Installation

The Application installation scripts have to be generated from the current server

where the application source code is saved and installed in the main server from

where the application is to be run. This was done using a special code, which

generates all SQL-Statements to insert preliminary data (like menu entries, code in

code directories etc) at server and the operational modules of the application made

available to the end users successfully.

4.8 Implementation

The system is still under construction few reports are yet to me made after that thissystem will be implanted at client side. Users will be given a training to use the

package and special workshops are conducted by the NIC for the purpose. And

according to their feedback the changes are implanted in the software.

48


49/121

CHAPTER 5

RESULT AND CONCLUSION

This section discuses the result of the work done in this project And also mentions the

future scope for improvement.

Conclusion

Today we are at the cross roads of innovation. The right direction to take will only

evolve with time, but effort has to be taken seriously by everyone involved in

education; the school/University, administration, faulty, students and parents.

By designing the Directorate General of Labour Welfare through ASP server side

technology, we are able to provide the basic functionality related to the submission

activities with great ease. The use of ASP technology has made it easier to design and

develop the n-tired architecture of this application. We were using the Microsoft

Software Development Platform for the development of this project, which had given

a complete, tight and integrated approach for the process of design and development

of this project.

Hence we may conclude that the application system being developed helps a great

deal in modifying the computerized DGLW.

Future Scope of Improvement

The Employee Management System for DGLW is a big and ambitious project. I am

thankful for being provided this great opportunity to work on it. As already

mentioned, this project has gone through extensive research work. On the basis of the

research work, we have successfully designed and implemented Employee

Management System. This system is based upon 3-tier client server architecture. The

tools used for development were as follows.

49


50/121

Front-end-----ASP, JavaScript, VBScript, HTML, DHTML

Back-end----MS SQL Server 2004

Query Language----PL/SQL

Annexure A Sample forms

Fig: 5.1 This is login form

50


51/121

Fig: 5.2 After login this form will be shown from where we will have to choose

from the menu.

51


52/121

Fig: 5.3 After login this form will be shown from where we will have to choose

from the menu.

Fig: 5.4 On clicking on Employee form these designation will be listed and on

choosing a particular designation all the employees at that designation on the regionthrough which a person has entered will be listed

52


53/121

Fig: 5.5 On choosing a designation a employee record at the designation will be

listed like this also mentioning the total number of person at that designtion

53


54/121

Fig: 5.6 On clicking the New Information on the top and bottom of the State

Wise Employee Information Employee form will be loaded

54


55/121

Fig: 5.7 While on clicking on the information in the Station Wise Employee

Information list then the Employee form will be loaded taking all the information

from the Table Employee

Fig: 5.8 On clicking on the Posting Button this list of Postings at various

station will appear if it already have, also on clicking on the New Information link

on the left side of for posting to the New Region can be assigned to the employee

through whose record we have entered

55


56/121

Fig: 5.9 This will make one select the particular Region for the Posting

56


57/121

Fig: 5.10 On selecting the Region the above form will be loaded, now thestation, designation, and duration of the position will be chosen through this form

57


58/121

Fig: 5.11 Now when the new posting has been assigned to the person that data

will be inserted and form will be closed

58


59/121

Fig: 5.12 The record inserted above is listed here in the posting information form

59


60/121

Fig: 5.13 On clicking on the Transfer Button in the Employee form this page

will be loaded giving information about his previous station and allowing the user to

assign him new Region and Station and the date for the Transfer

60


61/121

Fig: 5.14 After inserting the Region for the Transfer this form will be loaded

listing Employees previous Region, Station and Region selected through previous

form, then through this form Station for the Employee for the Transfer will be

selected

61


62/121

Fig: 5.15 On clicking the Leave Button on Employee form this form will be

loaded listing all the leaves taken by Employee their type and duration

62


63/121

Fig: 5.16 On clicking on New Information on the left of the Leave Information

form this form will be loaded where leave record can be entered

63


64/121

Fig: 5.17 On clicking on the Vacancy Position form this form will be loaded

listing particular station for the Region through which user has login

64


65/121

Fig: 5.18 Now allowing user to select the particular station

65


66/121

Fig: 5.19 On selection the Station all the designation on that station will be listed

from the table Vacancy Position

66


67/121

Fig: 5.19 Each designation has a link containing information about the

Employee at that designation

67


68/121

Fig: 5.20 On clicking the particular designation this form will be loaded bringing

all the information regarding Vacancy Position about the Employee at designation

68


69/121

Fig: 5.21 On clicking on the New Button this form will be loaded

69


70/121

Fig: 5.22

70


71/121

Fig: 5.23 On clicking the New Information link this page will be loaded with

Region and Station fixed

71


72/121

Fig: 5.24 New form allow user to insert a new information on the particular

Region and station

72


73/121

Fig: 5.25 On inserting the above information this form will be loaded like this

i.e., the designation inserted will be printed now and editing on the other field can be

performed

73


74/121

Fig: 5.26 This is a login form, if user is not from regional area but is from

Administration he will have User ID and Password other than that of user from

Regional areas

74


75/121

Fig: 5.27 After this login this page will be loaded here the user will have both

Region and Station to select, user can access any region and station

75


76/121

Fig: 5.28 Now again after entering the Region and Station this form will be

loaded

76


77/121

Fig: 5.29 User can access other Region and Station as well

77


78/121

Fig: 5.30 After selecting the Region and Station this page will be loaded listing

all the designation at that station

78


79/121

Fig: 5.31 On clicking the EmloyeeCR form from the menu this form will be

loaded listing all the station of the Region through which User has login

79


80/121

Fig: 5.32 On selecting the Station this page will be loaded bringing name and

designation of all the Employees at the station

80


81/121

Fig: 5.33 On clicking the Employees Name this page will be loaded listing

information about his CR year and whether it is received or not

81


82/121

Fig: 5.34 On clicking the New Information on the left this form will be loaded

with the Employees name

82


83/121

Fig: 5.35 On clicking the Employees name in the list above this form will be

loaded with the information about Employees CR year this info can be edited and

saved

83


84/121

Fig: 5.35 On clicking on the Leave on the Menu this form will be loaded letting

to choose the designation, for the designation entered here the leave information will

be listed

84


85/121

Fig: 5.36 On selecting designation through previous form this form will be

loaded listing Balance leaves of the employee

85


86/121

Annexure B: Reports

Fig: 5.37 On clicking on the List Region Repots in the menu this page will be

loaded, select the region through this list

86


87/121

Fig: 5.37 For the Region entered above report listing all the data in table

VacancyPosition will listed regarding sanctioned strength for various designation at

various Region and Station

87


88/121

Fig: 5.38 On selecting list Designation from the Menu this page will be loaded,

select the Designation through this list

88


89/121

Fig: 5.39 All the information as entered in the table Vacancy Position for the

selected designation will be listed

89


90/121

Fig: 5.40 On selecting list vacancy Region from the menu this page will be

loaded

90


91/121

Fig: 5.41 Then for the selected Region, list of all the vacancy position for the

various designation at the various station of the selected Region will be listed

91


92/121

Fig: 5.42 On selecting vacancy Region from the menu this page will be loaded

92


93/121

Fig: 5.43 This page will list vacancy position for the various designation at each

Region and Station

93


94/121

Fig: 5.44 On selecting list VacancyRegionDesign this page will be loaded

94


95/121

Fig: 5.45 This page asks the user to select the Region from the list

95


96/121

Fig: 5.46 For the selected Region, Designation record at the region will be listed

96


97/121

Fig: 5.47 On choosing particular Designation all the information regarding

vacancy position for that designation at selected Region will be listed

97


98/121

Annexure C- Sample code:

frmEmployee.asp


99/121

Response.Write "New Form"

cRegion=Request.Form("Region")

case "Insert"

GetValuesFrom "Form"

frmInsert()

Case "Save"


frmUpdate()

case "Delete"


frmDelete()

case "Search"GetValuesFrom "Form"

frmSearch()

case "Refresh"


frmFind()

case "Close"

frmClose()

case else

select case cstr(Request.QueryString("frmAction"))

case "Find"

cID = Request("ID")

frmFind()

case else

frmMode="New"

GetValuesFrom "Default"Response.Write "New Form"

cRegion=Request.QueryString("Region")

cDesignation=Request.QueryString("Designation")

end select

end select

sub frmInsert()

insert=True

99


100/121

if (Not checkdate(cDOB)) then

insert=False

Response.Write "Wrong Date of Birth"

frmMode="New"

cDOB=""

else

strSql = "Insert into Employee (Name, "

if (len(trim(cSeniority))>0) thenstrSql = strSql & " Seniority, "

end if

strSql = strSql & " Region, "

if (len(trim(cStation))>0) then

strSql = strSql & "Station, "

end if

strSql=strSql & " Sex, DOB, Designation, "

if (isNumeric(cBasicPay)) then

strSql= strSql & " BasicPay, "

end if

strSql= strSql & " PerFileNo, Category, "

if (len(trim(cDtGovt))>0) then

strSql= strSql & "DtGovt,"

end if

if (len(trim(cDtService))>0) then

strSql = strSql & " DtService,"

100


101/121

end if

if (len(trim(cDtPost))>0) then

strSql= strSql & " DtPost,"

end if

if (len(trim(cIncrYear))>0) then

strSql = strSql & " IncrYear, "

end if

if (len(trim(cIncrMonth))>0) then

strSql = strSql & " IncrMonth, "end if

strSql=strSql & " Qualification, QualificationDesc,"

if (len(trim(cDtLeaving))>0) then

strSql=strSql & " DtLeaving, "

end if

strSql = strSql & " TypeLeaving, Remarks, Post, PostType,"

if (len(trim(cDtPostHeld))>0) then

strSql = strSql & " DtPostHeld,"

end if

if (len(trim(cUPSCDt))>0) thenstrSql = strSql & " UPSCDt,"

end if

strSql= strSql & " UPSCNo1, UPSCNo2, EntryMode, HomeTown, PresentStatus)VALUES ("

strSql = strSql & "'" & cName & "', "

101


102/121

if (len(trim(cSeniority))>0) then

strSql = strSql & cSeniority & ", "

end if

strSql = strSql & cRegion & ", "

if (len(trim(cStation))>0) then

strSql = strSql & cStation & ", "

end if

strSql = strSql & "'" & cSex & "', "

if (len(trim(cDOB))>0) thenstrSql = strSql & "'" & DateMMDDYYYY(cDOB) & "', "

end if

strSql = strSql & "'" & cDesignation & "', "

if (IsNumeric(cBasicPay)) then

strSql = strSql & "" & cBasicPay & ", "

end if

strSql = strSql & "'" & cPerFileNo & "', "

strSql = strSql & "'" & cCategory & "', "


strSql = strSql & "'" & DateMMDDYYYY(cDtGovt) & "', "

end if


strSql = strSql & "'" & DateMMDDYYYY(cDtService) & "', "

end if


strSql = strSql & "'" & DateMMDDYYYY(cDtPost) & "', "

end if

102


103/121


strSql = strSql & "'" & cIncrYear & "', "

end if


strSql = strSql & "'" & cIncrMonth & "', "

end if

strSql = strSql & "'" & cQualification & "', "

strSql = strSql & "'" & cQualDesc & "', "


strSql = strSql & "'" & DateMMDDYYYY(cDtLeaving) & "', "

end if

strSql = strSql & "'" & cTypeLeaving & "', "

strSql = strSql & "'" & cRemarks & "', "

strSql = strSql & "'" & cPost & "', "

strSql = strSql & "'" & cPostType & "', "


strSql = strSql & "'" & DateMMDDYYYY(cDtPostHeld) & "', "

end if

if (len(trim(cUPSCDt))>0) then

strSql = strSql & "'" & DateMMDDYYYY(cUPSCDt) & "', "end if

strSql = strSql & "'" & cUPSCNo1 & "', "

strSql = strSql & "'" & cUPSCNo2 & "', "

strSql = strSql & "'" & cEntryMode & "', "

strSql = strSql & "'" & cHomeTown & "', "

strSql = strSql & "'" & cPresentStatus & "'"

strSql = strSql & ")"

103


104/121

set rsFrm = Server.CreateObject("ADODB.Recordset")

Response.Write strSql

rsFrm.open strSql, EmployeeConn

Response.Redirect "Region=" & cRegion & "&Designation=" & cDesignation

end if

end sub

sub frmUpdate()

strSql ="Update Employee set "

strSql = strSql & "Name = '" & cName & "', "if (len(trim(cSeniority))>0) then

strSql = strSql & "Seniority =" & cSeniority & ", "

end if

strSql = strSql & "Region =" & cRegion & ", "

strsql = strSql & "Station =" & cStation & ", "

strSql = strSql & "Sex = '" & cSex & "', "

if (len(trim(cDOB))>0) then

strSql = strSql & "DOB = '" & DateMMDDYYYY(cDOB) & "', "

end if

strSql = strSql & "Designation = '" & cDesignation & "', "

if (isNumeric(cBasicPay)) then

strSql = strSql & "BasicPay = " & cBasicPay & ", "end if

strSql = strSql & "PerFileNo = '" & cPerFileNo & "', "

strSql = strSql & "Category = '" & cCategory & "', "


strSql = strSql & "DtGovt = '" & DateMMDDYYYY(cDtGovt) & "', "

end if

104


105/121


strSql = strSql & "DtService = '" & DateMMDDYYYY(cDtService) & "', "

end if


strSql = strSql & "DtPost = '" & DateMMDDYYYY(cDtPost) & "', "

end if

if (len(trim(cIncrAmount))>0) then

strSql = strSql & "IncrYear = '" & cIncrYear & "', "

end if


strSql = strSql & "IncrMonth = '" & cIncrMonth & "', "

end if


strSql = strSql & "IncrYear = '" & cIncrYear & "', "

else

strSql=strSql & "IncrYear='', "

end if

strSql = strSql & "PostType = '" & cPostType & "', "

strSql = strSql & "Qualification = '" & cQualification & "', "

strSql = strSql & "QualDesc = '" & cQualDesc & "', "


strSql = strSql & "DtLeaving = '" & DateMMDDYYYY(cDtLeaving) & "', "

end if

strSql = strSql & "TypeLeaving = '" & cTypeLeaving & "', "

strSql = strSql & "Remarks = '" & cRemarks & "', "

strSql = strSql & "Post = '" & cPost & "', "

105


106/121


strSql = strSql & "DtPostHeld = '" & DateMMDDYYYY(cDtPostHeld) & "', "

end if

if (len(trim(cUPSCDt))>0) then

strSql = strSql & "UPSCDt= '" & DateMMDDYYYY(cUPSCDt) & "', "

end if

strSql = strSql & "UPSCNo1= '" & cUPSCNo1 & "', "

strSql = strSql & "UPSCNo2= '" & cUPSCNo2 & "', "

strSql = strSql & "EntryMode= '" & cEntryMode & "', "strSql = strSql & "HomeTown= '" & cHomeTown & "', "

strSql = strSql & "PresentStatus= '" & cPresentStatus & "'"

strSql = strSql & " where Id = " & cID


'Response.Write strSql


Response.Redirect "frmEmployee.asp?frmAction=Find&ID=" & cID & "&Region="& cRegion

end sub

sub frmDelete()

strSql = "Delete from Employee where ID =" & cID



'Response.Redirect "frmEmployee.asp?frmAction=New" & "&Region=" & cRegionResponse.Redirect "Region=" & cRegion & "&Designation=" & cDesignation

end sub

sub frmClose()

Response.Redirect RedirectURL & "?userName=" & session("gUserId")

end sub

106


107/121

sub frmTransfer()

Response.Redirect "frmRegion.asp?ID=" & cID & "&Region=" & cRegion &"&Station=" & cStation & "&Designation=" & cDesignation

end sub

sub frmPosting()

Response.Redirect "../List/lstPosting.asp?ID=" & cID & "&Region=" & cRegion &"&Station=" & cStation

end sub

sub frmLeave()

Response.Redirect "../List/lstLeave.asp?ID=" & cID & "&Region=" & cRegion &"&Station=" & cStation

end sub

sub frmFind()


strSql = "Select * from Employee where ID=" & cID

rsFrm.Open strsql, EmployeeConn

GetValuesFrom "Table"

rsFrm.close

end sub

sub GetValuesFrom(ByVal Src)

select case cstr(Src)

case "Form"

cId = Request.Form("ID")cName = Request.Form("Name")

cSex = Request.Form("Sex")

cDOB = Request.Form("DOB")

cDesignation = Request.Form("Designation")

cPayScale = Request.Form("BasicPay")

cPerFileNo = Trim(Request.Form("PerFileNo"))

cCategory = Request.Form("Category")

cDtGovt = Request.Form("DtGovt")

107


108/121

cDtService = Request.Form("DtService")

cDtSection = Request.Form("DtPost")

cPost = Request.Form("Post")

cPostType = Request.Form("PostType")

cDtPostHeld=Request.Form("DtPostHeld")

cPlacePosting = Request.Form("PlacePosting")

cQualification = Request.Form("Qualification")

cQualDesc = Request.Form("QualDesc")

cHomeTown = Request.Form("HomeTown")

cDtLeaving = Request.Form("DtLeaving")

cTypeLeaving = Request.Form("TypeLeaving")

cRemarks = Request.Form("Remarks")cRegion = Request.Form("Region")

cStation= Request.Form("Station")

cSeniority = Request.Form("Seniority")

cBasicPay=Request.Form("BasicPay")

cDtPost=Request.Form("DtPost")

cUPSCDt=Request.Form("UPSCDt")

cUPSCNo1=Request.Form("UPSCNo1")

cUPSCNo2=Request.Form("UPSCNo2")

cEntryMode=Request.Form("EntryMode")

cPresentStatus=Request.Form("PresentStatus")

cIncrMonth = Request.Form("IncrMonth")

cIncrYear=Request.Form("IncrYear")

case "Table"

cId = rsFrm("Id")

cName = rsFrm("Name")cSex = rsFrm("Sex")

cDOB = rsFrm("DOB")

cDesignation = rsFrm("Designation")

cBasicPay = rsFrm("BasicPay")

cPerFileNo = Trim(rsFrm("PerFileNo"))

cCategory = rsFrm("Category")

cDtGovt = rsFrm("DtGovt")

cDtService = rsFrm("DtService")

108


109/121

cDtSection = rsFrm("DtPost")

cPost = rsFrm("Post")

cDtPostHeld=rsFrm("DtPostHeld")

cPostType = rsFrm("PostType")

cQualification = rsFrm("Qualification")

cQualificationDesc = rsFrm("QualificationDesc")

cHomeTown = rsFrm("HomeTown")

cDtLeaving = rsFrm("DtLeaving")

cTypeLeaving = rsFrm("TypeLeaving")

cRemarks = rsFrm("Remarks")

cRegion = rsFrm("Region")

cStation= rsFrm("Station")cSeniority = rsFrm("Seniority")

cDtPost=rsFrm("DtPost")

cUPSCDt=rsFrm("UPSCDt")

cUPSCNo1=rsFrm("UPSCNo1")

cUPSCNo2=rsFrm("UPSCNo2")

cEntryMode=rsFrm("EntryMode")

cPresentStatus=rsFrm("PresentStatus")

cIncrMonth=rsFrm("IncrMonth")

cIncrYear= rsFrm("IncrYear")

case else

cName = ""

cSex = ""

cDOB = ""

cDesignation = ""

cPayScale = ""cPerFileNo = ""

cCategory = ""

cDtGovt = ""

cDtService = ""

cDtSection = ""

cPost=""

cPlacePosting = ""

cPostType = ""

109


110/121

cQualification = ""

cQualDesc = ""

cHomeTown = ""

cDtLeaving = ""

cTypeLeaving = ""

cRemarks = ""

cRegion=Request.QueryString("Region")

cIncrMonth=""

cIncrYear=""

end select

end sub

%>

Employee Details


111/121

alert("Blank Date!, Date format is 'DD/MM/YYYY'");

//document.frmName.CGITReceivedDate.focus();

}

else {

if(!DateValid(document.frmName.DtService.value)) {


}

}

}

function checkDtGovt()

{

if (document.frmName.DtGovt.value == "") {alert("Blank Date!, Date format is 'DD/MM/YYYY'");


}

else {

if(!DateValid(document.frmName.DtGovt.value)) {


}

}

}

function checkDtPost()

{

if (document.frmName.DtPost.value == "") {



}else {

if(!DateValid(document.frmName.DtPost.value)) {


}

}

}

function checkDtPostHeld()

{

111


112/121

if (document.frmName.DtPostHeld.value == "") {



}

else {

if(!DateValid(document.frmName.DtPostHeld.value)) {


}

}

}

function checkUPSCDt()

{if (document.frmName.UPSCDt.value == "") {



}

else {

if(!DateValid(document.frmName.UPSCDt.value)) {


}

}

}

function checkDtLeaving()

{

if (document.frmName.DtLeaving.value == "") {


//document.frmName.CGITReceivedDate.focus();}

else {

if(!DateValid(document.frmName.DtLeaving.value)) {


}

}

}

112


113/121

function checkBP()

{

if (document.frmName.BasicPay.value == "") {

alert("Blank Basic Pay!");

}

else {

if(!is_int(document.frmName.BasicPay)) {

alert("'" + document.frmName.BasicPay.value + "' is not a valid BasicPay!");

//alert(document.frmName.BasicPay.value);

document.frmName.BasicPay.value=""

}}

}

//-->

Name/Seniority

/

Sex

Male

Female

113


114/121

*DoB

Designation

Basic

File No.

Category

General

Schedule Cast

Schedule Tribe

OBC

Station

*Dt.of Posting(Prsnt. Desg.)

Dt. of Entry(Govt.)

Dt.Present Station

114


115/121

Increment Month

Incr.added upto Year

Permanent / Temporary Employee Info.

Post Name

Perm./Temp.

Dt. of Confirmation

Qualification

10th

12th

Graduate

Post Graduate

Description

115


116/121

Home Town

Dt. of Leaving

Reason of Leaving

Remarks

116


117/121

*These fields are mandatory


118/121

end sub

sub btnPosting_OnClick()

frmName.SubmitAction.value="Posting"

frmName.submit

end sub

sub btnLeave_OnClick()

frmName.SubmitAction.value="Leave"

frmName.submit

end sub

sub btnInsert_OnClick()frmName.SubmitAction.value="New"

frmName.submit

end sub

118


119/121

Annexure D - List of Common Validations

1. No field in a form should be left blank.

2. The name of a person cannot be numeric value. It has to be in alphabets

3. Data has to be entered in a valid format.

4. Data of birth has to be a date previous than the current date.

5. Time has to be entered in valid format.

6. In any form, only one option can be selected from the given number of options

7. Email address should be entered in a valid format.

119


120/121

Annexure E - Definition/Glossary

Data describe the numbers, text, graphics, image, and voice stored in this form that

can be used by a computer.

Record A set of related data items treated as a unit.

File Set of record is termed as storage of files, and records in computer.

LAN Based Application an application which run on internet or intranet.

Project Life Cycle (PLC) Describe a way to make a successful project.

Configuration status reporting (CSR) an activity that help software Developer to

understanding what changes have been made and why.

Validation Test to ensure that the software confirms to its requirement.

Prototyping Creating a mock up of an application.

120


121/121

62261222 Employee Management System

Documents