SYNOPSIS

This project entitled as “Resource Management System “(RMS) is

Developed using Microsoft Visual Basic 6.0 as Front end and Microsoft

SqlServer2000 as back end.

The ultimate aim of this project is to allocate the resources for the

organization. This project is mainly developed to automate the process between

the human resource manager and the project manager such as applying for

resource request, accepting the request or rejecting or holding the request,

applying request for relieving from the resource, entering, updating the details and

skills of the employee.

It contains an administrator login for the human resource manager in which

any new degree, domain and role for an employee can be updated. Several data

reports are created to display the current records.

This project is oriented with full user interface and easy to operate the

system. RMS is an automated process, so it reduces the paper works.

2.1 PROBLEM DEFINITION

The project is developed to automate the Resource Management System

(RMS). This project is mainly developed to automate the process between the

human resource manager and the project manager such as applying the resource

request, accepting the request or rejecting or holding the request, applying request

for reveling from the resource, entering updating the details and skills of the

employee.

METHODOLOGY

This project consists of three modules namely

HUMAN RESOURCE

PROJECT MANAGER

SKILL UPDATER

HUMAN RESOURCE:

This module consists of operations performed by the HR such as

adding new degree, role, and domain for the concern. It also acts as an indicator,

which indicates the message when a request is received from the project manager.

Here human resource manager acts as an Administrator. Human resource manager

can also perform the operation such as accepting, rejecting or holding the request

for the request made by the project manager. The HR enters the details such as

personal, educational, skill, project details and assigns unique id, unique username

and password for each employee who newly joins into the concern.

PROJECT MANAGER:

This module consists of the operations made by the project manager

such as requesting for resource; release the resource. After the allocation of the

resource by the human resource manager the project manager starts the project

work. Releasing of the resource is done after the completion of project or

allocation of resource to other project.

SKILL UPDATER:

This is a common module used by all such as human resource

managers, project manager, employees to update their skills during any period.

Each employee can alter and update their skills. In this module there is a provision

to change the password, which is used for login purpose HR can alter and update

the skills for all employees.

3.1 Requirement analysis & Specification

OPERATING ENVIRONMENT

3.1.1SOFTWARE ENVIRONMENT

Front End - Microsoft Visual Basic

Back End - SqlServer2000

3.1.2.HARDWARE ENVIRONMENT

Client Side

Operating System – Windows 95 & lateral

Processor - 200Mhz or faster processor

Primary - 64 or more MB RAM

Monitor - Monitor capable of 16-bit or better with

800 * 600 pixel setting.

Hard Disk - 10 GB or more.

Server Side

Windows 2000 NT .The server must be connected in good

condition.

Acronyms and Abbreviations

HR Human resource ManagerPM Project ManagerEMP Employee

3.1.4 DATA FLOW DIAGRAM

LEVEL –0

Login

Role based authentication

Report

EXISTINGUSER

RMS

REQUESTPROCESS

LEVEL -1

Storing employee details

Storing requestdetails

EXISTING USER

LOGIN ROLE BASED AUTHENTICATION

CHECK USER

EMPLOYEE

REQUESTPROCESS

RESOURCEREQUEST

ANALYSISSKILLUPDATER

Reports

1.1OBJECTIVES

The main objective of this project is to automate the things happens between Human Resource Manager and Project Manager.

• Only the HR can do new employee registration and provide the user id.

• After entering the data the save button is clicked to save the details into the database.

• Employee can login through given user id.• The user can also change the password.• PM can request the HR for the resources needed for a new

project.• HR will allocate the resource if it is available otherwise HR

can simply Hold or Reject the request.• Allocated resources are schedule in Man Power Allocation

Sheet. • Employers can view their own details.• HR is the only person can alter details of all employees.• The users easily store the inputs and view the details because

user interaction is provided throughout this project.

2.2 EXISTING SYSTEM

The existing system is a manual system in which the PM has to

inform about the request manually. The HR has to allocate the resources by

searching employees manually and to allocate to the resource, which was request.

2.3 LIMITATIONS OF EXISTING SYSTEM

Since the current system is the manual, it suffers mainly in the way

that information is organized, stored and later presented in the form of reports and

queries.

In the existing system the time consumption is high.

Large number of Files to be maintained for storing the details.

Lot of paper works is needed for requesting for resources.

It is tedious to search for the resources manually.

NEED FOR COMPUTRIZATION

With the technology being enhanced new provisions are added to

people. To cite an example, RMS is the best resource that the people avail of it.

PM in any corner of the world can access the system and request for the resource

needed. This system will attract the people because of reducing their precious

time. Thus the need for computerization comes into the picture.

2.4 PROPOSED SYSTEM

This system RMS has been specially developed to overcome the

problems faced in the existing system. The proposed system does not require any

manual processing. This system has the feature to store all the request details that

are made by the PM. It also features the search for the resource in a easy way.

Since, the propose system involves the automation of the existing

system, the functional aspects logically follow the existing system. The proposed

system aims to overcome the disadvantages of the current manual system

satisfying the specification requirements.

ADVANTAGES OF PROPOSED SYSTEM

Increasing the time efficiency reduces human factor to a bigger

extent.

The system is developed after considering the user’s needs and

analyzing as to how fat it is feasible.

This system focuses on the user interaction and the periodic reports

that have to be generated to satisfy user reports.

3.1.3 DATA DICTIONARYThe dictionary contains the data about data i.e. metadata. The

following tables clearly explain the fields used in this project with their type and description.

Table Name EMPPER

Field Name Data Type Size DescriptionEid Varchar 10 To store the

employee idUname Varchar 30 To store the

user namePass Varchar 30 To store the

passwordEmpFirst Varchar 30 To store the

first nameEmpLast Varchar 30 To store the last

nameAddress Varchar 50 To store the

addressCity Varchar 25 To store the

cityPhone Number 15 To store the

phone numberMobile Number 15 To store the

mobile numberAge Number 3 To view the ageBlood group Varchar 10 To store the

blood groupMail Varchar 25 To store the

Email idState Varchar 40 To store the

stateDdate Number 2 To store the

dateDmon Varchar 5 To store the

monthDyear Varchar 4 To store the date

Table Name LOGIN

Field Name Data Type Size DescriptionUname Varchar 30 To store the

user namePass Varchar 30 To store the

password

Table Name EMPEDU

Field Name Data Type Size DescriptionEid Varchar 10 To store the

employee idDegree Varchar 10 To select the

degreeSpecial Varchar 20 To enter the

specializationPercent Number 2 To enter the

percentageDurfrm Number 4 To select the

from durationDurto Number 5 To select the to

duration

Table Name SKILL_MAS

Field Name Data Type Size DescriptionEid Varchar 10 To store the

employee idSkill name Varchar 30 To store the skill

nameSkill type Varchar 30 To store the typeProficiency Varchar 30 To store the

proficiency

Table Name EDU_MAS

Field Name Data Type Size DescriptionDegree Varchar 30 To store the

degreeDomain Varchar 50 To store the type

of domainRole Varchar 50 To store the role

Table Name EMPPROJ

Field Name Data Type Size DescriptionEid Varchar 10 To store the

employee idDomain Varchar 50 To store the

domainTitle Varchar 50 To store the

title of the project

Role Varchar 50 To store the role in the project

Descry Varchar 50 To store the description of the project

Styr Int 4 To store the starting year

Endyr Int 4 To store the ending year

Soft Varchar 50 To store the software environment

Hardware Varchar 50 To store the hardware environment

Table Name RESREQ

s

Thus the above are the tables and data used in the database.

Field Name Data Type Size DescriptionResource id Varchar 30 To store the

resource idPtitle Varchar 50 To store the

project titleReqname Varchar 50 To store the

requested person name

Datereq Date 8 To store the date of request

Stat Varchar 15 To store the status of the request

3.2. SYSTEM DESIGN

3.2.1. DATABASE DESIGN

Database management system defines a file a database and calls it as

a collection of interrelated records. A table is a collection of data about a specific

topic. The information can be stored in a single database file. Within the file, the

data can be divided into separate storage containers called tables, view, add and

update table data by using online forms; find and retrieve just a data want by

using queries; and analysis and print data in a specific layout by using reports.

Users are allowed to view, update or analyze the databases data from the file

Internet or an intranet by creating data access pages.

The basic steps in designing a database

Determine the purpose of database

Determine the tables needed in databases

Determine the fields needed in the tables

Identify fields with unique values in each record

Refine the design

Store data and create other database objects

Tables used in this project are

EMPPER:

To store the personal details of the employee

EMPEDU:

To store the educational details of the employee

EMPSKILL:

To store the skills and their corresponding proficiency of the

employee

EMPPROJ:

To store the project details of the employee

RESREQ:

To store the status and the resource details for a project

SKILL_MAS:

To store the skills newly add to the software field.

EDU_MAS:

To store the new degree, domain, Role in the environment

LOGIN:

To Store The Login Details

3.2.2.INPUT DESIGN

As per the theories of system analysis and design the reliability of a user

about a system is increased only through the proper design of the input and output

forms.

• Only the HR can do new employee registration and provide the user id.

• Storing the details and checking the save button user details into the database.

• Employee can login through given user id.• PM can request the HR for the resources needed for a new

project.• HR will allocate the resource if it is available otherwise HR

can simply Hold or Reject the request.• Allocate resources are schedule in Man Power Allocation

Sheet. • Employers can view their own details.• HR is the only person can alter details of all employees.• The users easily store the inputs and view the details because

user interaction is provided throughout this project.

Suppose for example

While Not RS1.EOFIf Trim (UNAME.Text) = RS1 (0) And PASS.Text = "" Then

Set MYOLAPP = Create Object ("Outlook.Application") Set MYITEM = MYOLAPP.CreateItem (olMailItem) MYITEM.To = RS (0) MYITEM.Subject = " PASSWORD REMEMEBERANCE" MYITEM.Body = "Your password is " & RS1 (0) &

MsgBox " Password Send To Your Mail Box " Rs1.close Exit sub

End ifWend

USER NAME

PASSWORD

FORGET PASSWORD

CANCELOK

In the above example user can retrieve the password by just entering the user name

and checks the forget password check box then user can receive the password

through mail.

Suppose for example

If OLDPASS.Text = pas ThenRS.Open " UPDATE LOGIN SET PASS = '" & CPASS.Text & "‘ where UNAME = '" & LOGIN.UNAME.Text & "' ", CON, 1, 2RS1.Open "UPDATE EMPPER SET PASS = '" & CPASS.Text & "‘ UNAME = '" & LOGIN.UNAME.Text & "' ", CON, 1, 2MsgBox " Password Changed ", vbInformation

ElseMsgBox " Incorrect Old Password ", vbCriticalOLDPASS.SelStart = 0OLDPASS.SelLength = Len (OLDPASS.Text)OLDPASS.SetFocusNEWPASS.Text = ""CPASS = ""

End If

In the above example the user have the provision to change the password. In the

example the user has to enter the old password, then the new password and retype

the password so as to confirm the password for their login.

Change passw

Old Password

New Password

Confirm

Save

3.2.3 OUTPUT DESIGN

One of the most important features of any information system for

users is the output it produces. The right output must developed while ensure that

each output element is designed so that people will find the system easy to use

efficiently.

RESULT REPORT

This will be provided immediately after the allocation of resources

for a project that is requested by PM.

These following types of reports can be generated in this project. They are

SKILL WISE

This type of reports is used to generate the details of the employee using

skill wise.

EMPLOYEE WISE

This type of reports is used to generate the details of a particular employee.

PROJECT WISE

This type of reports is used to generate the details of the employee through

project work done by the employee.

YEAR WISE

This type of reports is used to generate the details of a particular employee

about the performance throughout the year.

3.4. TESTING

Testing is a process of executing a program with the intent of finding an

error. This process also ensures that defined input will produce actual results that

agree with required results. The amount of testing required is related to the size

and complexity of the application. A good test is one that has to high probability

of finding an undiscovered error.

UNIT TESTING

This test checks each individual module ensure that it functions properly as

a unit. Unit test exercise specific path in a module to ensure complete coverage

and maximum error detection.

All independent paths in a module through the control structure to

ensure that all statements in the module are executed at least once.

All loops have been executed at their boundaries with their

operational bounds.

All logical decisions have been exercised on their side.

For example the user name is HR and password is secretly want to

be checked. At the start “ If Statement “is used to check the above

constraint.

If the condition goes true the required menus will be displayed

Otherwise, it will display an error message.

From this, it is confirmed, if condition functions correctly.

Suppose for example

If Trim (UCase (UNAME.Text)) = "HR" And PASS.Text = RS (1) ThenMDIForm1.MM_PM.Enabled = FalseMDIForm1.ShowMe.Hide

ElseMsgbox “Invalid user name “, vbcritical

end if

Here if condition checks for the user name and password are equal to the database field name in some table.

If the condition is true then it will show the Mdiform with respected menus.

Otherwise it will display a message box.

Various tests can be generated to uncover the errors in the following categories.

Improper or inconsistent of default values

Inconsistent data types

Underflow or overflow

All error-handling paths were tested.

INTEGRATION TEST

Integration test is the systematic technique or constructing this

program structure while at the same time conducting test to uncover errors

associated build a program structure that has been dictated by design.

The modules are integrated to from the compute software package. It

addresses the issues associated with dual problems of verification and program

construction. It mainly deals with testing whether the links are passed between

modules without any error.

In this project the integration testing is done to check whether the links

between the forms are passing correctly.

For example, suppose the user forget the password then he can retrieve it using

RS1.MoveFirst

While Not RS1.EOF

If Trim(UNAME.Text) = RS1(0) And PASS.Text = "" Then

Me.Hide

FORGET.Show

Exit Sub

End If

RS1.MoveNext

Wend

Suppose in the above coding if the state mention is true then the

forget form will be shown.

Other wise the existing form will be hided and the Mdiform is

displayed.

Similarly ever passing is tested and corrected when error occurred.

WHITE BOX TEST

White box testing, sometimes called glass box testing, is a test case design

method that uses the control structure of the procedural design that uses the control

structure of the procedural design to derive test cases. Using the white box testing

methods, the software engineer can derive test cases that

1. Guarantee that all independent paths within a module have been

exercised once

2. Exercise all logical decisions on their true or false sides.

3. Execute all loops at their boundaries and within their operational

bounds

4. Exercise internal data structure to assure their validity.

Suppose for example

With vas1Do While Not rs.EOF

vas1.MaxRows = vas1.MaxRows + 1vas1.Row = vas1.MaxRows .Col = 1 .Text = rs(0) .Col = 2 .Text = rs(1) .Col = 3 .Text = rs(2) .Col = 4 .Text = rs(3) .Col = 5 .Text = rs(4) .Col = 6 .Text = rs(5)

loopend with

This routine is used to store the data to the spreadsheet from the database. So that he routine is used.

BLACK BOX TEST

It focuses on the functional requirements of the software. That is, black box

testing enables the software engineer to derive of input conditions that fully

exercise all functional requirements for a program. Black box testing is not an

alternative to white box techniques. Rather, it is a complementary approach that is

likely to uncover a different classes of errors that white box method.

Black box testing attempts to find errors in the following categories

1. Incorrect or missing functions

2. Interface errors

3. Error in data structure or external data ware access

4. Performance Errors

5. Initialization and termination errors

Suppose for example

Private Sub SETLENTGH()TXT_ID.MaxLength = 20txt_first.MaxLength = 30txt_last.MaxLength = 30txt_add.MaxLength = 50txt_ph.MaxLength = 15txt_mob.MaxLength = 15TXT_MAIL.MaxLength = 30TXT_BG.MaxLength = 15End Sub

In the above coding function SETLENTGH sets the maximum length for each

textboxes. Hence it has been tested using the black box text.

NORMALIZATION

Normalization procedure involves breaking down or decomposing the

given table into other table. The decomposition is required to be reversible. So that

no information is lost in the process.

NORMAL FORM

Table name empedu

Uname Pass Degree Special Percent Dur frm Dur toPran Pran MCA Computer

applications75 2001 2004

DIL DIL M.Sc IT&M 72 2002 2004Pran Pran Mtech VLSI 78 2004 2006

First Normal Form

A relation scheme is said to be in first normal form (1 NF) if the

values in the domain of each attribute of the relation are atomic. In other words

only one value is associated with each attribute. From the above example the table

gives atomic values.

Second Normal FormA second normal form doesn’t permit partial dependency between a

non-prime attribute and the relation keys.

Definition A relation scheme is in second normal form (2 NF) if it is in 1 NF

and if all non-prime attributes are fully functionally dependent on the relation

keys.

ExampleIn this project the pass details are kept in 2 NF.

Parsing of empedu

Table name login

Uname pass

pran pran

DIL DIL

Uname Degree Special Percent Dur frm Dur toPran MCA Computer

applications75 2001 2004

DIL M.Sc IT&M 72 2002 2004Pran Mtech VLSI 78 2004 2006

Thus the tables are partitioned into login, empedu, skillmas, empproj, resreq and

empper table.

3.3. IMPLEMENTATION

Implementation is the conversion of logical design into source code.

The implementation phase of software developed is concerned with translated

design specification into source code. Source code clarity is enhanced by

structured coding techniques, by supporting documents and by good internal

comments.

During the implementation stages the client will never leave the

existing system until the client is fully satisfied with the proposed system. Unit,

integration, black and white box tests test this project.

In this project the server is implemented in one place and the client

systems are also implemented in various places. This server system should be in

well configured to meet the constraints. This project is implemented in the intranet

environment.

The server must be in running and the client pulls the information to

the server and in turn the server responds to the client. For this purpose data

streaming concept is used.

Less time consumption and more efficient.

Information required is obtained very quickly.

Less expensive

In this project several components are used but there are some special controls

used for some specific purpose they will be as follows

1.MAPI control

This control is Mail Access Programming Interface. This control is

used to send mails to the users for the purpose as incase of the user has forget the

password. The password will be send to the mail using this control for the

particular employee requested for the remembrance of password.

2.FAR POINT SPREAD SHEET

In spite of using Grid controls for viewing any type of details here

the spreadsheet control is used for viewing or displaying the details. Using this

control the user can edit the details and update into the database.

For the database connectivity ADODB control is used so that the

backend process is done easily.

3.5. MAINTENANCE ISSUES

The software maintenance is the important phase in the software

development and requires more effort. The software maintenance means to

improve our software quality according to current positions.

This software uses reverse engineering to develop this software from

scratch, because existing system is done by manually. This is more expensive and

non-reliability so this software makes the capability of online process by the client.

So it is possible to cover lot of customer more than the existing system.

Developing the software is characterized by the following activity

Adaptive Maintenance

This maintenance means changing the software to some new

environment such as different hardware platform or for use with a different

operating system. The software functionality does not radically change. This

software can be run under minimum configuration as Windows 95 and lateral

operating system. Processor can be 200 MHz or faster processor. The primary

memory will be 64 or more MB RAM. The hard disk with minimum of 10 GB or

more the monitor capable of 16-bit or better with 800 * 600 pixel setting is a

minimum requirement

4. CONCLUSION.

The main objective of this project is to automate the things happens

between Human Resource Manager and Project Manager. They are by making

way for complete paperless working environment. Various helpdesk services that

ware handled manually are now managed at never impact pace. The increased

standard of the services will definitely have an impact on the efficiency of the

system. In future many additional task such as, analyzing the project duration for

each phase in the software development life cycle (SDLC) through the system. It

can be improved as per user’s requirement by getting their suggestions. This will

surely help the people who are in software concerns.

5 BIBLIOGRAPHY

1. Mastering Visual Basic 6.0

• Evangeous Petroutsos

2.Using Visual Basic 6.0

• Mike Mickly, Brain Siley

3.Visual Basic 6.0

• Noel Jerke

4.Beginning Sql Server 2000 For VB Developers

• Thearon Willis

5.Data Base Management System

• C.J. Date

6.Software Engineering

• Roger.S.Pressman

7.System Analysis And Design

• Elias.M.Awards

B.Lakshmi, M.C.A.,Lecturer,Department of Computer Science,Nehru Memorial College,Puthanampatti – 621 007.

CERTIFICATE

This is to certify that the project titled “ RESOURCE MANAGEMENT

SYSTEM (RMS)” is a bonafide work done

By

P.R.PRANESH

Register Number: 01280128

during the 6th semester in partial fulfillment of the award of the Master of

Computer Applications of Bharathidasan University, Tiruchirappalli.

I certify that the project work carried out by him is an independent

work done under my supervision and guidance.

HEAD OF THE DEPARTMENT PROJECT ADVISOR (M.MURALIDHARAN) (B.LAKSHMI)

EXAMINERS

1.____________________

2.____________________

ACKNOWLEDGEMENT

I am very happy to reward my sincere thanks to Mr.M.Ponnambalam,M.A.,M.Sc., Secretary and Dr.S.Ramalingam,M.A.,PhD., principal, Nehru Memorial College, Puthanampatti for the encouragement during the course of my study.

I express my sincere thanks to Mr.M.Muralidaran,M.Sc.,PGDCA , Head, Department of Computer Science , Nehru Memorial College, Puthanampatti for making all necessary arrangements for the successful completion of this project work.

I am greatly indebted to my project guide Mrs.B.Lakshmi, M.C.A Lecturer, Department Of Computer Science for her thought provoking lectures and invaluable guidance.

I am greatly indebted to the company Take Solutions for providing me this great opportunity to do the project in their concern. I greatly express my thanks to Mrs.R.Shanthi process consultant of the concern for her thought provoking lectures and invaluable guidance.

I am very much thankful to Mrs.B.Neera HR of the concern for her thought provoking lectures and invaluable guidance. I am very much thankful to Mr.Sathish Krishnan Project Manager of the concern who has given his provoking invaluable guidance throughout this project. I express my hearty and special thanks to Mr.B.Soundara Rajan for his guidance throughout this project.

I express my heartily and special thanks to my parents, friends and all staff members who helped me a lot in various way directly or indirectly throughout this project work.

PRANESH.P.R

TABLE OF CONTENTS

S.No Content Page. No.

1. Introduction 1.1 Objectives

1.2 Organization Profile 2. Problem Definition and Methodology

2.1 Definition 2.2. Existing System

2.3 Limitation of Existing System 2.4. Proposed System

3. Developmental Process and Documentation 3.1 Requirement analysis & Specification

3.1.1 Software Requirements3.1.2 Hardware Requirements3.1.3 Data Dictionary3.1.4 Data Flow Diagram

3.2 System Design 3.2.1. Database Design

3.2.2 Input Design 3.2.3 Output Design

3.3 Implementation 3.4 Testing

3.5 Maintenance Issues

4. Conclusion

5. Bibliography

6. Appendix6.1 Software Profile6.2. Source code6.3 Table Structure6.4 Screen Layout

6.5 Reports

6.4. SCREEN LAYOUT

Form Name Login

Form Name Admin

Form Name Empper

Form Name Empedu

Form Name Empskill

Form Name Empproj

Form Name HR_REQ

Form Name HR_SER

Form Name REQ_SEND

Form Name HR_MPRA

Form Name pass_chan

Form Name PM_REQ

Form Name REQ_STAT

Form Name PM_RLF

6.5 REPORTS

Report Name EMPREP

Report Name MPRA

Report Name PDREP

Report Name SKILLREP