HRM Project

HR Management System

INTRODUCTION

HR Management software is prepared for leading company. This company is

recruiting people every month. To match the resumes they required the software.

PURPOSE

The purpose of this document is to specify requirements and to give guidelines for

the development of above said project. In particular it gives guidelines on how to

prepare the above said project.

This document is intended to be a practical guide for people who developing this

software.

SCOPE

This software is very general purpose software. On completion of this software

will be useful for many companies

GOAL

The main goal of the application is to maintain the records of resumes, This

software is helpful to segregate the resumes based on the jobs.

KUVEMPU UNIVERSITY 1


ABOUT PROJECT

HR Management software is prepared for leading company. This company is

recruiting people every month. To match the resumes they required the software.

At present all HR work is managing manually. Each time job opening thousands

application will be coming, processing them is very tedious job. Also matching

with the particular job also very difficult. Preserving all the resumes for long time

is again one more tuff job.



OVERVIEW OF THE WORKING PLACE

Computer Lab

To provide excellent knowledge of the latest technology, Infysys Academy,

Koramangala has a well-equipped computer laboratory. It has got thirty Pentium

III Computers all networked using cat 5 cables. Also, the lab has server room

which contains one Windows NT Server, one Linux Server and one Backup

Domain Controller



SYNOPSIS

Title of the project: Human Resource Management

Object of the project:

HUMAN RESOURCE MANAGEMENT SYSTEM

The project has been developed using Visual Basic as Back End and MS-Access

and the front End. The project deals with Human Resource Management System

developed for RealVision Technologies, Bangalore.

This s/w manages to keep the complete records of students coming in the institute

for enquiry, takes admission, and till he/she is placed in some company for the job.



SYSTEM ANALYSIS AND DESIGN (SAD)

In business, SAD refers to the process of examining a business situation with the

intent of improving it through better procedures and methods.

OVERVIEW OF SAD:

System development mainly consists of two major components, “System analysis”

and “System design”. System Design is the process of planning a new business

system or one to replace the existing or a complement system.

But before planning is done, the process of understanding the old system and to

determine the best use of the computer is an exercise, which is available. System

analysis is the process of gathering interpreting facts, diagnosing the problem and

using information to recommend improvements to the system.

THE SYSTEM DEVELOPMENT LIFE CYCLE CONSISTS OF THE

FOLLOWING ACTIVITIES:

Preliminary investigation

Requirement determination

Feasibility study

Design of the system

Software development

Software testing

Implementation and evaluation





EXISTING SYSTEM

Place of Data collection:

RealVision Technologies

Jayanagar, Bangalore.

Date of Data Collection: 07-March-2008

Methods used for data collection

Interview and observations of existing system (manual system).

Observations made during problem analysis

We found that the records maintained contained redundant data, which could be

eliminated through computerized system.

Access to particular database is time consuming and difficult.

Updating any one database would have to be manually reflected in all other related

databases. So automatic updating was not possible throughout the database.

Report generation and querying is tedious and time consuming.

Security was not viable and safe i.e., high risk of manipulation by unauthorized

user existed.

Various objects/entities existing and their relationships were identified.



SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

Abstract

This document fully and formally describes the requirements of the proposed said

project system. It sets out the functional and non-functional requirements and

includes a description of the user interface and documentation and training

requirements.

An SRS is basically an organization's understanding (in writing) of a customer or

potential client's system requirements and dependencies at a particular point in

time (usually) prior to any actual design or development work. It's a two-way

insurance policy that assures that both the client and the organization understand

the other's requirements from that perspective at a given point in time.

The SRS document itself states in precise and explicit language those functions

and capabilities a software system must provide, as well as states any required

constraints by which the system must abide. The SRS also functions as a blueprint

for completing a project with as little cost growth as possible. The SRS is often

referred to as the "parent" document because all subsequent project

management documents, such as design specifications, statements of work,

software architecture specifications, testing and validation plans, and

documentation plans, are related to it.

It's important to note that an SRS contains functional and nonfunctional

requirements only; it doesn't offer design suggestions, possible solutions to

technology or business issues, or any other information other than what the

development team understands the customer's system requirements to be.

A well-designed, well-written SRS accomplishes four major goals:

It provides feedback to the customer. An SRS is the customer's assurance



that the development organization understands the issues or problems to be

solved and the software behavior necessary to address those problems.

Therefore, the SRS should be written in natural language, in an

unambiguous manner that may also include charts, tables, data flow

diagrams, decision tables, and so on.

It decomposes the problem into component parts. The simple act of writing

down software requirements in a well-designed format organizes

information, places borders around the problem, solidifies ideas, and helps

break down the problem into its component parts in an orderly fashion.

It serves as an input to the design specification. As mentioned previously,

the SRS serves as the parent document to subsequent documents, such as

the software design specification and statement of work. Therefore, the

SRS must contain sufficient detail in the functional system requirements

so that a design solution can be devised.

It serves as a product validation check. The SRS also serves as the parent

document for testing and validation strategies that will be applied to the

requirements for verification.

SRS are typically developed during the first stages of "Requirements

Development," which is the initial product development phase in which

information is gathered about what requirements are needed--and not. This

information-gathering stage can include onsite visits, questionnaires, surveys,

interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of

the customer or client's current business environment. The actual specification,

then, is written after the requirements have

been gathered and analyzed.

The National Bureau of Standards, IEEE (Standard No: 830-1984), and the

U.S Department of Defense have all proposed candidate formats for software

requirements specifications. The general structure is implemented with the related

software application.



REFERENCES

OVERVIEW

This software save lot of time compare to the manual searching of resumes. This

provide complete cycle of the recruiting.

PROPOSED SYSTEM

In the proposed system the software will be developed all the resumes can feed

into it. Later searching and matching will be very easier, even there thousand of

resumes searching will not take much time. Also all the information is available in

one place.

Each resume can match for different jobs. No need call advertisement each time.

With the existing resume only we can search for the suitable candidate.

At present all HR work is managing manually. Each time job opening thousands

application will be coming, processing them is very tidious job. Also matching

with the particular job also very difficult. Preserving all the resumes for long time

is again one more tuff job.



HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS

Processor : Pentium III 400MHz and Above

RAM : 128MB RAM

Monitor : 15” Color Monitor

Keyboard

Mouse

Software Requirements

Operating System. : Windows 2000/XP

Developing Tool : Visual Basic 6.0

Database : MS Access

HARDWARE AND SOFTWARE REQUIREMENTS

The Functional Specification is created after the Software Requirements

Document. It provides more detail on selected items originally described in the

Software Requirements Document.

Some software development organizations combine these two documents into a

single document. The Functional Specification describes the features of the

software product. It describes the product's behavior as seen by an external

observer, and contains the technical information and data needed for the design.

The Functional Specification defines what the functionality will be, but not how

that functionality will be implemented.

The software engineer uses the Functional Specification document to create a

detailed design document that explains in detail how the software will be designed

and developed. The detailed design work may further decompose and translate the

functional requirements into pseudocode, and from there into a computer module

or program.



The functional specification translates the Software Requirements Document into

a technical description that:

Ensures that the product feature requirements are correctly understood before

moving into the next step, the software design process.

Clearly and unambiguously provides all the information necessary to design the

software.



DEVELOPING FUNCTIONAL SPECIFICATION CONTENTS

The Functional Specification contents are determined by the project manager, the

software developer, and typical end-users.

The end-users are important members of this team, because they will help ensure

the software will meet the business and engineering needs of those who will use

the software. The project's user group is a good source for information and review.

For guidance on drafting a functional specification, please see the links in the

Background Material and Examples section below.

FUNCTIONAL SPECIFICATION SCOPE

The Functional Specification includes specific information about each functional

requirement of the software. The Functional Specification should describe, for

each functional requirement:

Purpose - What the function is intended to accomplish.

Input - What inputs will be accepted, in what format the inputs arrive, sources for

the inputs, and other input characteristics.

Process -The steps to be performed, algorithms, formulas, or techniques to be

used. Software implementation details are not included, however.

Output - Desired outcomes such as the output form (e.g. report layout), the

destination of the output, output volume and timing, error handling procedures,

and units of measure.

Usability items need to be included in the Functional Specification. These are

features that ensure user friendliness of the software. Examples include clear error

messages, input range checking as soon as entries are made, and order of choices

and screens corresponding to user preferences.



FUNCTIONAL SPECIFICATION

The problem under study is being divided into several modules/functions

discussed below to understand the approach to the solution in the broader way:

FUNCTIONAL DESCRIPTION

1. Employee Training Selection

2. Employee Recruiting

3. Interview marks entry form

4. Interview Letter Form

5. Resume Matching Form

6. Job opening Entry form

7. Experience Details entry screen

8. Education Entry Screen

9. Resume Entry Screen

10. Subject Name Entry Screen

11. Main Screen and login Screen

EXTERNAL INTERFACES

The interfaces in this section are specified by documenting: the name and

description of each item, source or input, destination or output, ranges, accuracy

and tolerances, units of measure, timing, display formats and organization, and

data formats.

User Interfaces:

Describes all major forms, screens, or web pages, including any complex dialog

boxes. This is usually best done via simulated, non-functioning screen shots (such

as PowerPoint slides), and may take the form of a separate document.

The navigation flow of the windows, menus, and options is described, along with

the expected content of each window. Examples of items included are screen

resolutions, color scheme, primary font type and size. Discussion also



includes how input validation will be done, and how data will be protected from

accidental changes.

Specific items are described for each screen such as input fields, control buttons,

sizing options, and menus.

Hardware Interfaces:

Describes the equipment needed to run the software, and also other output or input

devices such as printers or handheld devices.

Pentium III or above, 128MB RAM or above

Windows Operating system.

Performance

Program is written such way that it gives ultimate performance for user. And it is a

single user. So there is not much complexity in the project. Normally database will

grow slowly. If the performance is not up to the mark, and it take long time then,

Open MS Access database run repair database tool.

Design Constraints

Examples of constraints that affect software design choices are items such as

memory constraints involving minimum and maximum RAM and hard disk space,

and limitations arising from hardware, software or communications standards.

Attributes

Security:

Project level security is set. User need to login when they start the program, option

is also provided to create the additional user and also the user level security.

Presently user level security is not set but can be implemented with few

modifications.



Reliability, Availability, Maintainability:

It is very user friendly software, Data is secured, There is not much maintenance.

Project can be upgraded as per the requirement step by step.

Configuration and Compatibility:

Describes requirements such as those connected with individual customization or

operation in specific computing environments.

Installation:

Provided with the set files. User can easily install to the system. Describes the

planned method for installation: done by the user independently, done by customer

company internal IT services, done by an external contractor. Specifies the

handling of such items as data transfer from prior releases, and the presence of

software elements from prior releases.

Usability:

Describes items that will ensure the user-friendliness of the software. Examples

include error messages that direct the user to a solution, input range checking as

soon as entries are made, and order of choices and screens corresponding to user

preferences. More ideas on software usability elements are found in:

The Software Design Specification (SDS) given in this outline are guidelines to

the contents of your SDS. The document should present the conceptual and

detailed technical design of the software/module that you are developing.

Purpose of this Document

This Software Design Specification (SDS) document contains a statement of the

design of the above title project. In an SDS, the designers are supposed to provide

an unambiguous design of the product. The design should contain an explanation

of a way to carry out each of the product specifications written in the Software



REQUIREMENTS SPECIFICATION (SRS)

The design then serves as a guide to the developers who write the code and

actually create the product. The SDS discusses how the program is separated into

modules, how the modules interact with each other, and how users see the

program. The SDS also looks into several design considerations, including design

tradeoffs and code reusability.

Scope of the Development Project

The project Tool is a new project which creates an interactive and easy program.

The package serve to the end user customers. Eventually, we hope to reach a

broader audience.

Definitions, Acronyms, and Abbreviations

ActionScript –

ActionScript is a tool used to write the code that controls the actions in animated

Flash presentations.

· Asp.net Microsoft web based project development tool

· C, C++ - The names of two object oriented programming languages commonly

used in industry.

· CEO - Chief Executive Officer.

· Form is object holder in Visual Basic Language. Defines single screen.

· HTML - Hypertext Markup Language. A language used to create Web

documents.

· IIS Internet Information Server 5.0

· Internet Explorer Microsoft Internet Browser version 6.0

· MS Access Microsoft developed Database Program.

· Oracle Oracle Corporation RDBMS database program.

· SDS - Software Design Specification document.

· SQL Server Microsoft RDBMS software.

· SRS - Software Requirements Specification document.



· Visual Basic 6.0 Programming Language

· VB.net Microsoft dot net Programming tool

Software Design Specification

Major Screens

System architecture description

Employee Training Selection

Employee Recruiting

Interview marks entry form

Interview Letter Form

Resume Matching Form

Job opening Entry form

Experience Details entry screen

Education Entry Screen

Resume Entry Screen

Subject Name Entry Screen

Main Screen and login Screen

Detailed description of components



SCREENS

MAIN SCREEN AND LOGIN SCREEN

This is main login screen employees as to login from this point based on

their provision corresponding form will be opened.


This is a master form to enter the subjects. Same there are other master

screen where all master entry need to be entered. Provide new, save, modify

and delete options. Also display in a flexgrid all entered information.



Resume Entry Screen

This is the main part of the project here all the collected resumes will be

entered. Collect all necessary information here. Make very use friendly so

user can easily entered the data here.




This is part of the resume here enter all education details. These fields very

useful in selection procedure. Therefore collection all education details in

detail.




This information is linked to the main resume. Based resume id experience

will be entered this will be help ful in the selection time.

Collect the complete experience details.




In this form all the openings in the company are entered. Company require

new employees time to time. Here job name, required qualification.

Experience will be entered, based on this resume matching will done.




Based on the job opening form entry on the required parameter this search

will be done. There based on the job all the possible qualifying resumes will

be displayed.




Who ever resumes are matching for the job, for them we need to send the

letter. For the same this form is provided here select the list and prepare the

letter and generate the letters. Take a print out of the generated letters send

them to the applicants.




After conducting the interview the marks can be entered here. To enter the

marks for each applicant options are provided here. Based on this the

selection list can be prepared.



Employee Recruiting

Once the applicant successfully selected to job then he became the employee

of the company. In this form what job assigned to the employee will be

specified. And also all other necessary information will be entered here.




Employee who are selected for the job will put for the training. In this for all

the training related information will entered.



Training Test



SOFTWARE ENVIRONMENT

The proposed system is developed using Visual Basic as the front end and MS

Access as the back end.

Visual Basic

A very user friendly very robust application to build the customized applications.

It can support various other platforms also.

It encompasses object oriented programming that creates and use the object

as a fundamental part of development process.

Object is a basic element, which helps to build the application.

Standard database formats for many applications are in built.

Database creation is very simple and is done in a GUI environment.

Modifications can be easily done to the created database.

design description of an object in Visual Basic has a protocol description

that establishes the interface of an object by defining each event that the

object can receive and the related operation that the object can perform

when the particular event is fired.

It has an implementation description that shows implementation details for

each operation implied by an event that is processed to an object. That

implementation details about the objects private part i.e., the internal details

about the data structure and procedural, functional details that describe the

operations.

FEATURES

The following are the various features of Visual Basic that made to select this

software for the project.



IMPROVED RELIABILITY:

The Visual Basic takes the core achievements originally made in Windows 2000

and brings them to new levels. With advanced ways of monitoring the health of

running applications, as well as isolating applications from each other,

applications built using the Visual Basic stay up-and-running longer than ever

before.

Developer Productivity:

Developers of all backgrounds are finding that they can rapidly get up to speed on

the Visual Basic. The intuitiveness of the programming model, the amount of code

already provided in the class libraries, and the amount of work that the Visual

Basic handles behind the scenes in areas such as memory management have

enabled Visual Basic developers to reap huge productivity gains.

Powerful, Granular Security:

The code access security technology in the Visual Basic was designed for today's

Internet environments. The Visual Basic can collect evidence about the origin and

author of an application. The Visual Basic run-time environment can then

combine that evidence with administrator-set or default security policies to make

fine-grained decisions about whether to run that application or enable it to access a

particular resource. It can even "negotiate" with the application, for example,

denying it the permission to write to a protected directory and enabling the

application to choose whether it will run, given that it has been denied that

permission.

Support for Other Programming Languages:

The Visual Basic supports the integration of over other programming languages in

a way unimagined previously, enabling developers to choose the right

programming language for the task at hand. All programming languages target a

single, extensive, and extensible set of class libraries. Components written in



different languages supported by the Visual Basic can interact seamlessly, with no

COM plumbing required.

FLEXIBLE DATA ACCESS:

The Visual Basic technology for interacting with data, ADO (ActiveX Data

Object), is designed for today's Web-based style of data access. Using ADO,

developers have the option of working with a platform-neutral, XML-based cache

of the requested data, instead of directly manipulating the database. This approach

to data access frees up database connections and results in significantly greater

scalability.

MS Access

Microsoft Access is a relational database management system from Microsoft,

packaged with Microsoft Office Professional which combines the relational

Microsoft Jet Database Engine with a graphical user interface. It can use data

stored in Access/Jet, SQL Server, Oracle, or any ODBC-compliant data container.

Skilled software developers and data architects use it to develop powerful,

complex applications.

Relatively unskilled programmers and non-programmer "power users" can use it

to build simple applications without having to deal with features they don't

understand. It supports substantial object-oriented (OO) techniques but falls short

of being a fully OO development tool. Microsoft Access was also the name of a

communications program from Microsoft, meant to compete with ProComm and

other programs. It proved a failure and was dropped. Years later they reused the

name for their database software.

Few Terms

These words are used often in Access so you will want to become familiar with

them before using the program and this tutorial.



A database is a collection of related information.

An object is a competition in the database such as a table, query, form, or

macro.

A table is a grouping of related data organized in fields (columns) and

records (rows) on a datasheet. By using a common field in two tables, the

data can be combined. Many tables can be stored in a single database.

A field is a column on a datasheet and defines a data type for a set of values

in a table. For a mailing list table might include fields for first name, last

name, address, city, state, zip code, and telephone number.

A record in a row on a datasheet and is a set of values defined by fields. In

a mailing list table, each record would contain the data for one person as

specified by the intersecting fields.

Design View provides the tools for creating fields in a table.

Datasheet View allows you to update, edit, and delete in formation from a

table.

Queries

Queries select records from one or more tables in a database so they can be

viewed, analyzed, and sorted on a common datasheet. The resulting collection of

records, called a dynaset (short for dynamic subset), is saved as a database object

and can therefore be easily used in the future. The query will be updated whenever

the original tables are updated. Types of queries are select queries that extract data

from tables based on specified values, find duplicate queries that display records

with duplicate values for one or more of the specified fields, and find unmatched

queries display records from one table that do not have corresponding values in a

second table.



TABLE RELATIONSHIPS

To prevent the duplication of information in a database by repeating fields in more

than one table, table relationships can be established to link fields of tables

together. Feasibility study is a test of a system proposal according to its

workability, impact on the organization, ability to meet user needs, and effective

use of resources. The feasibility study is to serve as a decision document; it must

answer the following questions.

1) What are the user's demonstrable needs?

2) Is the problem worth solving?

3) How can the problem be solved?

All the successful projects are not necessarily the biggest but rather those that truly

meet the user expectations. Three key considerations involved in the feasibility

analysis are economic, operational and technical.

















ECONOMIC FEASIBILITY

Economic feasibility is the most frequently used method for evaluating the

effectiveness of a candidate system. The procedure is to determine the savings and

the benefits from the candidate system and compare with costs. If the benefits

outweigh the costs then it is decided to go ahead with the projects. Otherwise,

further justification or alterations in the proposed system will have to be made if it

is to have a chance of being approved. This is an on-going effort that improves in

accuracy at each phase of the system life cycle.

OPERATIONAL FEASIBILITY:

People are resistant to change and computers have been known to facilitate

change. An estimate should be made of how strong a reaction of the user staff is

likely to have an impact towards the development of a computer system. It is

common knowledge that computer installations have a lot to do with turnovers,

transfers, retaining and changes to employee job status. Therefore it's

understandable that the production of the candidate system requires special effort

to educate and train the staff on the new way of doing the job. But since ultimately

the introduction of a new system will only reduce the staff's workload, they may

have no objection to install a computerized system, and of course will be eager to

extend their cooperation.

Feasibility Study

Behavioral Feasibility:

It relates human behavior in the organization and political aspects. Here we focus

on:

1) What changes will be brought with the system

2) What organizational structures are disturbed

3) What new skills will be required

Do the existing members have these skills? If not can they be trained in due course

of time. It also includes social and managerial aspects that is whether the proposed

project will be acceptable to the customer and the management, along with the



determination of whether the proposed project considers Act, Status as well as

pending Legislations as a part of the legal feasibility

TECHNICAL FEASIBILITY:

Technical feasibility centers on the existing system and to what extent it can

support the proposed system. This involves financial considerations to

accommodate technical enhancements. If the budget is a serious constraint, then

the project is judged not feasible. Now considering the proposed system, our client

has been maintaining the records manually at the present. So he has to purchase

new computer systems for the automation of the concern. The owner having

realized the advantages, benefits and economic feasibility of the new system is

ready to afford the expenses for the satisfaction of all the hardware and software

requirements. Therefore the project, in question, is technically feasible as well.



CONCLUSION

This system developed for RealVision Technologies aims at maintaining the

records of the camps that have been held, dates of the camp, number of patients

treated, number of people operated upon, number of patients given free spectacles,

money spent, transport details, number of doctors who attended the camp, details

of the camp and follow up dates.

It increases the efficiency of the voluntary camp and also reduces the workload, as

there is no need to maintain the records manually.

This project is designed using very carefully and a lot of thought has been put into

the making of the system. It has been developed using VB 6.0 an approved front-

end tool that is a very efficient graphical user interface.

This system automates the entire process and will surely serve its purpose for

many years to come.

A computer procedure is a series of operations designed to manipulate data to

produce outputs from a computer system. The procedure may be a single program

or a series of programs. The detail design of the computer procedure follows

acceptance by management of an outline design proposal. The aim now is to

design procedures at lower levels of detail, which will define the detailed steps to

be taken to produce the specified computer output. When complete, these

procedure definitions together with data specifications are organized for

programmers from which the required programs can be written.

DESIGN TOOLS:

Various tools are being used by system analysis to specify computer procedures.

Not all of them are used here to design this project. Some of the important tools

that have been made use of are:

1. Entity relationship Diagram.

2. Input design.

3. Output Design.



4. Database Design.

INPUT DESIGN:

Input design is a part of overall system design, which requires very careful

attention. Often the collection of input data is the most expensive process of the

system.

In terms of both the equipment used and the number of people involved, it is the

point of most contact for the users with the computer system; and it is prone to

error. If data going into the system is incorrect, then the processing and output will

magnify their errors.

One of the early activities of input design is to determine the nature of the input

data. This is done partially in logical system design but it now needs to be made

more explicit.

ERROR AVOIDANCE AND DETECTION:

Every effort must be made to ensure that input data remains accurate from the

stage at which it is recorded and documented to the stage at which the customer

accepts it. While every effort is made to avoid errors during the preparation of

input data, a proportion of errors are likely to be present.

The user is free from the anxiety of keeping the uniqueness of the primary key

since the system itself generates the primary key for the user.

As soon as the user keys erroneous data in, the system just will not accept the data

and provides appropriate messages.



SYSTEM DESIGN

Data validation:

Computer input procedures must also be designed to detect errors in the data at a

lower level of detail which is beyond the capability of the control procedures.

These are combined with the design of the input process itself.

The validation procedure must be designed to check each record, data item, field

against certain criteria specified by the system analyst or the programmer.

Output design:

The specification of user requirements is the starting point for the appraisal and

the detailed physical design must be done in the light of this and with continuing

user involvement. The normal procedure is to design the outputs in detail first and

then to work back to the inputs. The outputs can be in the form of operational

documents, lengthy reports, and replies to queries or summarizing graphs.

Outputs from computer systems are required primarily to provide a permanent

copy of the results for later consultation. Any data item not yet defined must be

identified and recorded before output design can proceed. There is often a need at

output to provide totals at various levels. It is not always desirable to print or

display data as it is held on a computer. The system analyst must ensure whether

the form in which it is stored in the system is suitable for the output.

In proposed system the users have been provided with many outputs in the form of

messages and alerts so as to help the user enter the correct data.

REPORTS:

Reports enhance the application programmer's effort to output the formatted data

in a manner practical for the user. This also helps to create hard copy of the valid

information.



ARCHITECTURAL DESIGN

Architectural design represents the structure of data and program components that

are required to build a computer based system. It considers the architectural style

that a system will take, the structure and properties of the component that

constitute the system, and the inter relationships that occur among all architectural

components of a system.

Although a software engineer can design both data and architecture, the job is

often allocated to specialists when large, complex systems are to be built. A

database or a data warehouse designer creates the data architecture of a system.

The system architect selects an appropriate architectural style for the requirements

derived during system

ENGINEERING AND SOFTWARE REQUIREMENTS ANALYSIS.

Architectural design begins with data design and then proceeds to the derivation of

one or more representations of the architectural structural of the system.

Alternative architectural style or patterns are analyzed to derive the structure that

is best suited to customer requirements and quality attributes. Once an alternative

has been selected, the architecture is elaborated using an architectural design

method.

An architectural model encompassing data architecture and program structure is

created during architectural design. In addition, component properties and

relationships are described.

A Dataflow Diagram also known as “Bubble Chart” is used to clarify System

requirements and identifying major transformations that all become programs in

System Design

SYMBOLS

Data Source/Destination

Process

Data Storage



Flow of data

Data Flow Diagram

Interview test

Candidate

Job Matching

Interview

Data Flow Diagram

Selection

Employee

ENTITY RELATIONSHIP DIAGRAM

Entity

Relationship

Attribute

Key Attribute

Entity Relationship Diagram

Employee

EmpNO

Name

Date

Job

Candidate

Rno

Name

Address

Course

Job Experience

Matching

Data Dictionary

AppEd

RNo Byte

RName Text



SlNo Integer

Course Text

Branch Text

SC Text

Year Text

Per Text

AppEx

RNo Byte

RName Text

slno Integer

yearFrom Text

yearTo Text

JTitle Text

JExp Text

AppSkill

RNo Byte

RName Text

slno Integer

Sk Text

Desc Text

Education

RNo Integer

RName Text

SSLC Text

PUC Text

Degree Text

PG Text

Others Text

Interview

jNo Integer

jtitle Text

aNo Integer

aName Text

intDate Date



intTime Text

remark Text

totMarks Integer

scoMarks Integer

JobOpen

RNo Byte

jTitle Text

Nopost Integer

Ed Text

NoYear Integer

MasBr

cName Text

years Text

MasEd

cName Text

years Text

MasPg

cName Text

years Text

MasSkill

cName Text

Det Text

Resume

RNo Integer

RName Text

PName Text

Add1 Text

Add2 Text

Add3 Text

Pin Text

phone Text

EMail Text

Gender Text

DOB Date



Lang Text

Ed Text

Ex Integer

SelList

jNo Integer

jtitle Text

aNo Integer

aName Text

intDate Date

intTime Text

letsend Text

SkillTab

RNo Byte

RName Text

SS Text

Desc Text

TempTab

T1 Text

T2 Text

T3 Text

T4 Text

T5 Text

T6 Text

T7 Text

T8 Text

T9 Text

T10 Text

Training

tName Text

tDays Integer

det Text

trainingSel

batchNo Text

EmpNo Integer



eName Text

job Text

tName Text

fromdate Date

todate Date

scoMarks Integer

remark Text

Users

RNo Byte

userName Text

PWord Text



DEFINITIONS

In relational database design, the process of organizing data to minimize

redundancy is called normalization. Normalization usually involves dividing a

database into two or more tables and defining relationships between the tables.

The objective is to isolate data so that additions, deletions, and modifications of a

field can be made in just one table and then propagated through the rest of the

database via the defined relationships. There are three main normal forms, each

with increasing levels of normalization:

1. First Normal Form

First Normal Form (1NF): Every cell I the table must have only one value i.e. it

should not have multiple values.

2. Second Normal Form

Second Normal Form (2NF): All non-key attributes must be fully functionally

dependent on the primary key and not just the part of the key.

3. Third Normal Form

Third Normal Form (3NF): The database must be in the second normal form and no

nonprime attribute should be transitively dependent on the primary key.

4. Fourth Normal Form

It deals with multiple valued dependencies

5. Fifth Normal Form

It deals with joined dependencies

6. Boyce Codd Normal Form

It states that no inverse partial dependencies should exist in the database The

Inventory Management System of a Music Store is developed using the second



normal form where the primary key of one table acts as a foreign of another table

and all the attributes of the table are dependent on the primary key and not the part

of the key.

NORMALIZATION

Introduction

This document is intended to be used throughout the coding and testing phases of

the project. It outlines the procedures used for testing and verification of the code.

The document also describes the integration procedures and the order in which

modules will be coded, and describes the test procedures and results of testing.

This section deals with the details of the classes of tests which must be conducted

to validate the functions, performance, and the constraints. This is achieved

basically by the means of testing which plays a vital role in the development of the

software. The various low level testing which can be grouped on a broader sense

are discussed as below:

There are three levels of testing:

1. Unit Testing -- Each module will be tested separately to ensure that it is

working before being combined with other modules.

2. Integration Testing -- Related modules will be integrated and tested together

before being placed into the system.

3. System Testing -- The entire system will be tested together after integration is

complete. System testing includes function, acceptance, installation and regression

testing. System testing will involve some beta

testing by the client.



TESTING

UNIT TESTING

The purpose of unit testing is to uncover errors in the smallest software unit the

routine. Each routine will be tested individually using black box-oriented tests.

The programmer of each module will design a set of test cases for that module and

ensure that the module is fully tested. Important or complex routines will also be

tested by at least one other person.

Testing

The following Forms are tested for the functionality

Selected candidate list

Resume Complete List

Interview letter format

The following Reports are tested for their functionality


Employee Recruiting







Resume Entry Screen



INTEGRATION TESTING

This section describes the integration strategy and procedures for the system. It

gives the order in which modules will be developed and how they will be



integrated. It also describes the specific tests that will be performed on integrated

sets of modules.

Note: It is important that each module be thoroughly tested as a unit before being

integrated with other modules.

Integration testing of unit tested modules is necessary to ensure that:

modules interface correctly with each other;

one module does not have inadvertent, undesirable effects on another

module;

submodules (routines) combine to produce the desired functions of the

major module;

interfaces to, and use of global data structures are consistent.

SYSTEM TESTING

Functional Requirements Testing

The functionality tests should be performed by the application representatives and

treat the whole system as a black box using the actual applications or middleware.

The aim of these tests is to verify the overall functionality of the system. This will

be performed by a section by section walkthrough of the SRS functional

requirements section. All functional requirements in the SRS must be fulfilled.

BETA TESTING

Method

This will be performed by the client, and by potential users of the system at the

Bureau of Meteorology. Users will be given a copy of the system to try out. Any

problems with the system will be reported back to the group.

BETA TESTING

To help us achieve the best possible result with our project, we have decided to get

as much input as possible from potential users of our system.



BUGS

If unexpected events happen while using project,

ALTERATIONS

If there is anything missing from the system, that you would like to see there, we would

also like to know about it. Most likely we will not be able to implement the changes to

the current system (due to time restraints), but when the full system is written next year,

it will most likely be present.

All Comments... Can be sent to us in various ways.

Please include your name and email address in any correspondence.

RESULTS

Comments received from the customers:

Alpha testing - prototype 2 of system

Performance and Stress Testing

A set of tests have been developed for performance and stress testing.

Performance tests will ensure that the system responds in a reasonable time to user

input (as defined in the SRS). The aim of stress testing is to try to break the

program by giving it abnormal or extreme input quantity, frequency or volume.

Performance testing will be performed at the client's site after installation.

According to the SRS:

The system must respond to all reports within 10 seconds on an Pentium IV

computer with a load average less than 1.

PERFORMANCE CRITERIA SATISFIED.

Stress testing with extreme and abnormal input cases has been been performed

where necessary on individual routines in the Unit Testing section.

STRESS TESTING SATISFIED.

Acceptance Testing



Acceptance testing consists of a suite of tests to be performed in the presence of

the client before he accepts the system. It will consist of the function tests,

performance tests (at the client's site), a walk-through of the user manual and the

final demonstration.

Function tests accepted.

Performance tests accepted.

User manual walkthrough accepted. Will be held performed along with

Installation Testing.

Final demonstration accepted.

INSTALLATION TESTING

Installation tests will check the installation and configuration procedure as well as

any missing dependencies. Installation tests test the installation and configuration

procedures. These tests are a set of scripts that automatically download all

necessary packages and install them.

Acceptance testing will be repeated after installation of the system at the Customer

Place. This is to ensure that the system works correctly in the Customer Place.

Note: System has not been installed for the client yet. Will be installed this week.

Some specific points that also need to be tested are:

1. Directory paths for data and help files are set up correctly and can be found by

the system.

2. Check for necessary third party controls.

3. All IDL library functions can be found by the system.

4. All fonts for the text tool can be found and loaded -- beta testing uncovered

some problems loading some fonts.

5. Check Printer drivers are installed properly.



REGRESSION TESTING

The selective retesting of a software system that has been modified to ensure that

any bugs have been fixed and that no other previously working functions have

failed as a result of the reparations and that newly added features have not created

problems with previous versions of the software. Also referred to as verification

testing, regression testing is initiated after a programmer has attempted to fix a

recognized problem or has added source code to a program that may have

inadvertently introduced errors. It is a quality control measure to ensure that the

newly modified code still complies with its specified requirements and that

unmodified code has not been affected by the maintenance activity.

Regression testing was not usually necesary, because most of the errors detected

were very localised, and did not affect other functions in an adverse manner.

User Manual

Screen Shots

And



1

2

3 6 7

5

8

4

Follow the below steps enter the Data

1. Click on New button to enter the new record

2. Enter details in each box.

3. To save the record click on Save Button

4. Click on Display button to see the complete list of records in the flexgrid

5. Double click on the record to view the details of the record



6. If any changes need to be done then make changes and then click Modify button

7. If you want to delete the record then click on Delete button

8. To close the form click on Close button.

The same method is applicable to all other forms.

Resume Entry Screen







Employee Recruiting




CODINGDim DbPath, GetConn As String

Private Sub BrMenu_Click()

MasBrForm.Show

End Sub

Private Sub CouMenu_Click()

MasEdForm.Show

End Sub

Private Sub EducationMenu_Click()

EdForm.Show

End Sub

Private Sub edDetMenu_Click()

EdForm.Show

End Sub

Private Sub empTrainMenu_Click()

TrainingForm.Show

End Sub

Private Sub ExDetMenu_Click()

ExpForm.Show

End Sub

Private Sub ExitMenu_Click()

End

End Sub

Private Sub ExperienceMenu_Click()

ExpForm.Show

End Sub

Private Sub IntViewLetMenu_Click()

IntViewLetForm.Show

End Sub

Private Sub IntViewMenu_Click()



IntViewForm.Show

End Sub

Private Sub JobOpeningsMenu_Click()

JobOpenForm.Show

End Sub

Private Sub MDIForm_Load()

DatabasePath = App.Path & "\MainData.mdb"

Conn = "Provider=Microsoft.Jet.OLEDB.4.0;Persist Security Info = False; Data Source=" & DatabasePath

& ""

Conn.Open Conn, "Admin"

'With Conn

' .CursorLocation = adUseClient

' .ConnectionString = "Provider=MSDAORA.1;Password=tiger;User ID=scott;data source=;Persist

Security Info=True"

' .Open

'End With

End Sub

Private Sub PgMenu_Click()

MasPgForm.Show

End Sub

Private Sub RecruitMenu_Click()

RecruitForm.Show

End Sub

Private Sub ResDetMenu_Click()

ResumeForm.Show

End Sub

Private Sub ResMatMenu_Click()

MatchForm.Show

End Sub

Private Sub skillMenu_Click()

MasSkillForm.Show



End Sub

Private Sub SkillsMenu_Click()

SkillForm.Show

End Sub

Private Sub TrainSelMenu_Click()

TrainingSelForm.Show

End Sub

Private Sub TrainyTestmenu_Click()

TrainytestForm.Show

End Sub

Dim LNo As Byte

Private Sub butAdmin_Click()

LNo = 2

If TempRS.State = 1 Then TempRS.Close

TempRS.Open "select * from users where UserName = 'ADMIN' and pword = '" & Text2 & "' and rno=0",

Conn

If TempRS.EOF = True Then

MsgBox ("The entered UserName or Password is not Correct")

Text1.SetFocus

LNo = 1

Else

UserNameVar = "ADMIN"

LoginAdmin.Show

End If

End Sub

Private Sub butCancel_Click()

LNo = 1

End

End Sub

Private Sub butLogin_Click()

LNo = 2




TempRS.Open "select * from users where username='" & UCase(Text1) & "' and pword = '" & Text2 &

"'", Conn


MsgBox ("The entered UserName or Password is not Correct")

Text1.SetFocus

LNo = 1

Else


TempRS.Open "select * from users where username='ADMIN' and pword = '" & Text2 & "'", Conn

If Not TempRS.EOF = True Then

UserNameVar = "ADMIN"

End If

Unload Me

End If

End Sub

Private Sub Command1_Click()

End Sub

Private Sub Form_Activate()

Me.Height = 2740

Me.Width = 5000

Me.Left = 3500

Me.Top = 2500

LNo = 1

End Sub

Private Sub Form_Unload(Cancel As Integer)

If LNo = 1 Then End

End Sub

Private Sub Text1_GotFocus()

Text1.SelStart = 0

Text1.SelLength = Len(Text1)

End Sub



Private Sub Text1_KeyPress(KeyAscii As Integer)

If KeyAscii = 13 Then Text2.SetFocus

End Sub

Private Sub Text2_GotFocus()

Text1.SelStart = 0

Text1.SelLength = Len(Text1)

End Sub

Private Sub MSF_DblClick()


TempRS.Open "select * from Resume where RName='" & MSF.TextMatrix(MSF.Row, 0) & "'", Conn

If Not TempRS.EOF Then

Text1 = TempRS(1) & ""








If TempRS(9) = "Male" Then

Option1.Value = True

Else


End If

DOB = TempRS(10)


Combo1 = TempRS(12) & ""


End If

Button(0).Enabled = False


Button(2).Enabled = True


End Sub


If KeyAscii = 13 Then

Text2.SetFocus

End If



End Sub

Private Sub Text1_LostFocus()

Text1 = UCase(Text1)

End Sub



Text3.SetFocus

End If

End Sub



End Sub



Text4.SetFocus

End If

End Sub



Text5.SetFocus

End If

End Sub



Text6.SetFocus

End If

End Sub



Text7.SetFocus

End If

End Sub



Text8.SetFocus

End If

End Sub





DOB.SetFocus

End If

End Sub



If Button(1).Enabled = True Then

Button(1).SetFocus

End If

End If

End Sub



End Sub

Sub NameDis()


TempRS.Open "select RName from Resume ", Conn

K = 1

Do While Not TempRS.EOF

MSF.TextMatrix(K, 0) = TempRS(0)

TempRS.MoveNext

K = K + 1

Loop

End Sub

Sub opt()

If Option1.Value = True Then

OpVar = "Male"

Else

OpVar = "Female"

End If

End Sub

Dim Num As Long

Private Sub Button_Click(Index As Integer)

Select Case Index

Case 0

Num = 1

ClearTxtControls Me, TextBox





Case 1


TempRS.Open "select * from jobopen where rno=" & Val(Text1) & "", Conn


StrSql = "insert into JobOpen(Rno,jTitle,NoPost,ed,Noyear) values "

StrSql = StrSql & " (" & Val(Text1) & ",'" & Text2 & "'," & Val(Text3) & ",'" & Text4 & "'," &

Val(Text5) & ")"

Conn.Execute StrSql



DisRec

Else

MsgBox "This JobNo is already present please check"

End If

Case 2

If vbYes = MsgBox("Do you want to Modify this Record", vbYesNo) Then

Conn.Execute "update jobOpen set jtitle='" & Text2 & "',NoPost=" & Val(Text3) & ",ed='" & Text4 &

"',noyear=" & Val(Text5) & " where rNo=" & AppNo & ""

DisRec

End If

Case 3

If vbYes = MsgBox("Do you want to delete this Record", vbYesNo) Then

Conn.Execute "delete from jobOpen where rno=" & AppNo & ""

DisRec

End If

Case 4

Unload Me

End Select

End Sub


MSF1.TextMatrix(Num, 0) = Num

MSF1.TextMatrix(Num, 1) = Text2






Num = Num + 1


End Sub

Private Sub Form_Load()

Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100

DisRec

DisRecEd

End Sub

Sub MSFInit()

MSF.Clear

MSF.ColWidth(0) = 1600


MSF.TextMatrix(0, 0) = "Name"

MSF.TextMatrix(0, 1) = "App No"

End Sub

Sub DisRec()


TempRS.Open "select jtitle,rno from jobOpen order by jTitle"

MSFInit

I = 1


MSF.TextMatrix(I, 0) = TempRS(0)


I = I + 1

TempRS.MoveNext

Loop

End Sub

Sub DisRecEd()


TempRS.Open "select cName from MasEd "

Text4.Clear


Text4.AddItem TempRS(0)

TempRS.MoveNext



Loop

End Sub


If MSF.TextMatrix(MSF.Row, 0) = "" Then Exit Sub

LblNo = MSF.TextMatrix(MSF.Row, 1)

AppNo = MSF.TextMatrix(MSF.Row, 1)

LblName = MSF.TextMatrix(MSF.Row, 0)


TempRS.Open "select * from jobOpen where rno=" & AppNo & " ", Conn

Text1 = TempRS(0)

Text2 = TempRS(1)

Text3 = TempRS(2)

Text4 = TempRS(3)

Text5 = TempRS(4)



End Sub

Dim Num As Long

Dim tNameVar As String


Select Case Index

Case 0

Num = 1




Case 1

StrSql = "insert into Training(tName,tDays) values "

StrSql = StrSql & " ('" & Text1 & "','" & Text2 & "')"

Conn.Execute StrSql



DisRec

Case 2


Conn.Execute "update Training set tName='" & Text1 & "',tDays='" & Text2 & "' where tName='" &

tNameVar & "'"



DisRec

End If

Case 3


Conn.Execute "delete from Training where tName='" & tNameVar & "'"

DisRec

End If

Case 4

Unload Me

End Select

End Sub


MSF1.TextMatrix(Num, 0) = Num





Num = Num + 1


End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100

DisRec

End Sub

Sub MSFInit()

MSF.Clear





End Sub



Sub DisRec()


TempRS.Open "select tName,tDays from Training order by tName"

MSFInit

I = 1




I = I + 1

TempRS.MoveNext

Loop

End Sub



tNameVar = MSF.TextMatrix(MSF.Row, 0)


TempRS.Open "select * from Training where tName='" & tNameVar & "' ", Conn

Text1 = TempRS(0)

Text2 = TempRS(1)



End Sub

Dim Num As Long

Dim cNameVar As String


Select Case Index

Case 0

Num = 1




Case 1

StrSql = "insert into MasBr(cName,Years) values "

StrSql = StrSql & " ('" & Text1 & "','" & Text2 & "')"

Conn.Execute StrSql





DisRec

Case 2


Conn.Execute "update MasBr set cName='" & Text1 & "',Years='" & Text2 & "' where cName='" &

cNameVar & "'"

DisRec

End If

Case 3


Conn.Execute "delete from MasBr where CName='" & cNameVar & "'"

DisRec

End If

Case 4

Unload Me

End Select

End Sub

Private Sub butSend_Click()


TempRS.Open "select * from dual", Conn

Set DataReport2.DataSource = TempRS

DataReport2.Sections("section1").Controls("L1").Caption = Text2


DataReport2.Sections("section1").Controls("L3").Caption = ""





DataReport2.Sections("section1").Controls("L8").Caption = DateFormat(DTPicker1.Value)

DataReport2.Sections("section1").Controls("L9").Caption = Format(DTPicker2.Value, "HH:MM PM")

DataReport2.Show

End Sub





TempRS.Open "Select aNo,aName from selList where jNo=" & Val(Combo1) & " order by aName", Conn

I = 1

MSF.Clear


MSF.TextMatrix(0, 1) = "App Name"




TempRS.MoveNext

I = I + 1

Loop

End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100


TempRS.Open "select distinct jno from selList order by jNo", Conn

Combo1.Clear


Combo1.AddItem TempRS(0)

TempRS.MoveNext

Loop

End Sub

Sub MSFInit()

MSF.Clear






MSF.TextMatrix(0, 0) = "Job No"

MSF.TextMatrix(0, 1) = "Post"

MSF.TextMatrix(0, 2) = "No of Post"

MSF.TextMatrix(0, 3) = "Education"

MSF.TextMatrix(0, 4) = "Experience"

End Sub



Sub DisRec()


TempRS.Open "select rName,rno from Resume order by rName"

MSFInit

I = 1




I = I + 1

TempRS.MoveNext

Loop

End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100

DisRec

RVar = 1

Fromdate.Value = Date

toDate.Value = Date


TempRS.Open "select tName from Training order by tName"

Combo1.Clear


Combo1.AddItem (TempRS(0))

TempRS.MoveNext

Loop

MSF1Init

End Sub

Sub MSFInit()

MSF.Clear






MSF.TextMatrix(0, 0) = "Emp No"




MSF.TextMatrix(0, 2) = "Job"

End Sub

Sub MSF1Init()

MSF1.Clear

MSF1.ColWidth(0) = 600





MSF1.TextMatrix(0, 0) = "SlNo"

MSF1.TextMatrix(0, 1) = "Emp No"

MSF1.TextMatrix(0, 2) = "Name"

MSF1.TextMatrix(0, 3) = "Job"

MSF1.TextMatrix(0, 4) = "program"

End Sub

Sub DisRec()


TempRS.Open "select empNo,eName,Job from Employee order by eName"

MSFInit

I = 1





I = I + 1

TempRS.MoveNext

Loop

End Sub



MSF1.TextMatrix(RVar, 0) = RVar

MSF1.TextMatrix(RVar, 1) = MSF.TextMatrix(MSF.Row, 0)



MSF1.TextMatrix(RVar, 4) = Combo1

RVar = RVar + 1

End Sub

Private Sub ButClose_Click()



Unload Me

End Sub


StrSql = "insert into Employee values(" & Val(Text1) & ",'" & UCase(Text2) & "','" & Var1 & "','" &

DateFormat(DOB) & "','" & Combo2 & "','" & Combo3 & "','" & Val(Text3) & "','" & DateFormat(Jdate)

& "')"

Conn.Execute StrSql

MsgBox "This record is saved successfully"

End Sub



TempRS.Open "Select aNo,aName,totMarks,ScoMarks,Remark from Interview where jNo=" &

Val(Combo1) & " order by totMarks,ScoMarks", Conn

I = 1

MSF.Clear


MSF.TextMatrix(0, 1) = "App Name"

MSF.TextMatrix(0, 2) = "Tot Marks"

MSF.TextMatrix(0, 3) = "Sco Marks"

MSF.TextMatrix(0, 4) = "Remark"








TempRS.MoveNext

I = I + 1

Loop

End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100



Me.Top = 100


TempRS.Open "select Cname from MasEd order by cName"

Combo2.Clear



TempRS.MoveNext

Loop


TempRS.Open "select jTitle from jobOpen order by jtitle"

Combo3.Clear



TempRS.MoveNext

Loop


TempRS.Open "select distinct jno from selList order by jNo", Conn

Combo1.Clear



TempRS.MoveNext

Loop

End Sub



TempRS.Open "select * from Resume where RName='" & MSF.TextMatrix(MSF.Row, 1) & "'", Conn

If Not TempRS.EOF Then



If TempRS(9) = "Male" Then


Else


End If

DOB = TempRS(10)

Combo2 = TempRS(12)



End If

End Sub

Dim Num, YVar, N1, R1 As Long

Dim EdVar, JName As String


Unload Me

End Sub

Private Sub butSave_Click()

If Combo1 = "" Then

MsgBox "Please select the Batch No "

Exit Sub

End If

If Text2 = "" Then

MsgBox "Please enter the employee"

Exit Sub

End If

StrSql = "update TrainingSel set scoMarks=" & Val(Text5) & ",remark='" & Text1 & "' where empno=" &

Text2 & " and batchno='" & Combo1 & "'"

Conn.Execute StrSql

End Sub



TempRS.Open "Select empNo,eName from TrainingSel where batchNo='" & Combo1 & "' order by

eName", Conn

I = 1

MSF.Clear

MSF.TextMatrix(0, 0) = "empNo No"





TempRS.MoveNext

I = I + 1

Loop



End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100


TempRS.Open "select distinct batchNo from trainingSel order by batchNo", Conn

Combo1.Clear



TempRS.MoveNext

Loop

End Sub


If Not MSF.TextMatrix(MSF.Row, 0) = "" Then

Text2 = MSF.TextMatrix(MSF.Row, 0)

Text3 = MSF.TextMatrix(MSF.Row, 1)

End If

End Sub

Dim Num, YVar, N1, R1 As Long

Dim EdVar, JName As String


Unload Me

End Sub

Private Sub butSave_Click()

If L1.Caption = "" Then

MsgBox "Please select the Job "

Exit Sub

End If

Conn.Execute "delete from selList where jNo=" & Val(L1.Caption) & ""

For I = 1 To R1

If Not MSF1.TextMatrix(I, 0) = "" Then

StrSql = "insert into selList(jNo,jtitle,aNo,aName) values(" & Val(Right(L1.Caption, 4)) & ",'" &

L2.Caption & "'," & MSF1.TextMatrix(I, 0) & ",'" & MSF1.TextMatrix(I, 1) & "')"

Conn.Execute StrSql

End If



Next

End Sub


If EdVar = "" Then

MsgBox "Please select the Job"

Exit Sub

End If


TempRS.Open "Select rno,rName,Ed,Ex from Resume where ed='" & Trim(EdVar) & "' and ex >= " &

YVar & "", Conn

MSF1Init

I = 1


MSF1.TextMatrix(I, 0) = TempRS(0)




'MSF1.TextMatrix(I, 4) = TempRS(4)

TempRS.MoveNext

I = I + 1

Loop

R1 = I

End Sub

Sub MSF1Init()

MSF1.Clear





'MSF1.ColWidth(4) = 2000

MSF1.TextMatrix(0, 0) = "App No"

MSF1.TextMatrix(0, 1) = "Name"

MSF1.TextMatrix(0, 2) = "Education"

MSF1.TextMatrix(0, 3) = "Experience"

End Sub



TempRS.Open "select rNO,jTitle,NoPost,Ed,NoYear from JobOpen order by rNo", Conn

I = 1



MSFInit





MSF.TextMatrix(I, 3) = TempRS(3) & ""


TempRS.MoveNext

I = I + 1

Loop

End Sub



TempRS.Open "Select rno,rName,Ed,Ex from Resume where ed='" & Trim(EdVar) & "' and ex >= " &

YVar & "", Conn

Set DataReport1.DataSource = TempRS

DataReport1.Sections("section4").Controls("L1").Caption = JName

DataReport1.Sections("section4").Controls("L2").Caption = N1

DataReport1.Show

End Sub


Me.Width = 10230

Me.Height = 6975

Me.Left = 100

Me.Top = 100

Command2_Click

End Sub

Sub MSFInit()

MSF.Clear






MSF.TextMatrix(0, 0) = "Job No"

MSF.TextMatrix(0, 1) = "Post"

MSF.TextMatrix(0, 2) = "No of Post"

MSF.TextMatrix(0, 3) = "Education"

MSF.TextMatrix(0, 4) = "Experience"

End Sub



Sub DisRec()


TempRS.Open "select rName,rno from Resume order by rName"

MSFInit

I = 1




I = I + 1

TempRS.MoveNext

Loop

End Sub



L1 = MSF.TextMatrix(MSF.Row, 0)

N1 = Val(MSF.TextMatrix(MSF.Row, 0))

L2 = "Post Name : " & MSF.TextMatrix(MSF.Row, 1)

JName = MSF.TextMatrix(MSF.Row, 1)

L3 = "Post Nos : " & MSF.TextMatrix(MSF.Row, 2)

L4 = "Qualification : " & MSF.TextMatrix(MSF.Row, 3)

L5 = "Experience : " & MSF.TextMatrix(MSF.Row, 4)

EdVar = MSF.TextMatrix(MSF.Row, 3)

YVar = Val(MSF.TextMatrix(MSF.Row, 4))

End Sub



BIBLIOGRAPHY

1. Visual basic Complete Reference :

Author: Tony Stevenson

2. Programming Microsoft Visual Basic 6.0, Edition: 2005

Author: Francesco Balena

Publisher: Microsoft Press, Edition:2007

3. MS-Access-Complete Reference

Author: Virginia Andersen, Virginia Andersen,

Edition:2006


http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author=Virginia%20Andersen/104-9993770-8514364

http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author=Virginia%20%20Andersen/104-9993770-8514364

Documents

HRM Project