1

CHAPTER 1

INTRODUCTION

1.1 Company Profile

Powersoft Technology was started in 2000 to provide embedded and software

development solutions in the area of Application development, systems software, automotive
electronics, process controls and medical electronics. The Company has successfully completed
over 100 installations with as many clients worldwide.

Powersoft is currently engaged in the following activities.

• Manufactures digital energy meters, data loggers, 3 phase power meters, single phase
power meters, scrolling display, energy logger, 8051 & PIC microcontroller development
kits for embedded systems applications.
• Developing application software for embedded products, industrial process, automation
and systematic solution in the area of VB, .Net, C# and J2ME.
• Consulting services in the applications of microcontrollers for medical equipment,
automotive actuators, process control systems, radio frequency identification devices,
power electronics, motor controls.
• Training in embedded development in the areas of 8-bit microcontrollers (8051, PIC), 32-
bit microcontroller (ARM) and DSPs.

1.2 Objective

Web Power Data Mining is an excellent solution which provides an IT smart solution for
small to medium sized organizations. The final output could be organized in a table structure,
CSV or Web page like layout.

Internet users and analysts have long used slow manual methods to browse and collect
information on the Internet, clicking pages one after the other.
 2

Data sets have grown in volume and complexity and more sophisticated tools are
required to capture and sort large amounts of data. The concept of this solution is to automate the
process of looking up, extracting data and producing it in an ad -hoc format. The final output
could be organized in a table structure or Web page like layout.

For these reasons the software is a very efficient solution for these services:

Internet telemarketing

Internet Data mining

Web based emails

Anyone wants to collect data from single or multi pages web site

Major Features:

• Capture data/links from the Internet

• Can be authorized to access web based emails headers

• Store collected data in these formats: txt (Text file), Html (Hypertext Markup

• Language) and CSV (Comma-Separated Values)

• Easy extract data structured in table format

• Save configured jobs for later processing

• Schedule jobs to automate Internet data-mining

• Can be called from DOS prompt or batch files to enable programmers to integrate
application execution..net
 3

Due to the explosive growth of information available in databases, researchers have been
looking for ways to make use of data stored. Web Power Data Mining is the process of finding
useful information in a large database. Many algorithms have been suggested and used to find
useful data, and the activity is called data mining.

The purpose of Web Power Data mining is to find useful information in an ever growing
data set size in databases. Computer assisted transactions have generated mountains of data that
could be useful to maintain the competitive edge of a company. For instance, retailers such as
Wal-Mart have been making the best use of information from their several million point-of-sale
transactions of a day, to understand customer purchasing behavior and improve customer
service.
 4

CHAPTER 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

The existing system of this project only deals with old data mining algorithms such as
decision tree algorithm and clustering algorithm so that it cannot work more effectively to the
filtering.

The existing system of this project only worked with the job searching utility that is the users
cannot have the facility of entering their information into the web page so that they cannot
receive the mails regarding the job. The job seekers can only search the job in the web page
itself. The main problem of the existing system is the user cannot be informed when the
appropriate job suits to them. They will be known when they are use the web page again.

2.1.1 Drawbacks

• Users cannot upload their resumes they can only search the jobs

• Filtering the jobs according to the keyword is very low so that users need to spend more
time find their job

• Cannot find out the jobs exactly as their needs.

2.2 PROPOSED SYSTEM

The proposed system of this project has many advanced user friendly tasks such as job
seeking, profile registering, filtering, etc. so that the main objective the proposed system is to
maintain the user’s profile in the database and the users will receive the mail regarding the job
when appropriate job suits to them. And also the algorithm implemented in this proposed system
will precede the filtering and predicting the results.

2.2.1 Advantages
 5

• Job seekers and job providers have separate login.

• Job seekers can post their resumes so that they will be informed when the appropriate job
is posted.

2.3 FEASIBILITY STUDY

Feasibility analysis is helps the system to truly meet the user expectations.

Feasibility analysis involves

• Economic Feasibility

• Technical Feasibility

• Behavioral Feasibility.

2.3.1 Economic Feasibility

This has been undergone to determine benefits and saving that an expected from a
candidate system and compare them with cost with the project that has been developed, the
major benefits and savings are the time spent for search.

The project can be able to work with any type of system and need not to install any
special software. The objects using with this project is not more expensive and those can be
found easily at the market.

2.3.2 Technical Feasibility

Studying what all the technical needs of the system are of whether there are affordable to
this project needs picture microcontroller, vb.net, and sql. The software used in this project is
easy to use and portable.

2.3.3 Behavioral Feasibility

 6

This is an estimate of how strong a reaction the users staff is likely to have towards the
development of a computerize system. The users without much frustration accepted the system.
Users can use the project without any training because of the user friendliness.

CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENT

Processor : Pentium IV

Clock Speed : 2 GHz

RAM : 512 MB

Hard disk Capacity : 80 GB

Floppy disk Capacity : 1.44 MB

Keyboard : 101 Keys

Mouse : Optical Mouse

3.2 SOFTWARE REQUIREMENT

Platform : ASP. Net, VB Scripts

Database : SQL Server

 7

CHAPTER 4

SOFTWARE DESCRIPTION
4.1 FRONTEND

DOT.NET code us ASP.NET is a web application framework developed and marketed

by Microsoft to allow programmers to build dynamic web sites, web applications and web
services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is
the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the
Common Language Runtime (CLR), allowing programmers to write ASP in any supported .NET
language.

User controls

ASP.NET supports creating reusable components through the creation of User Controls.
A User Control follows the same structure as a Web Form, except that such controls are derived
from the System .Web .UI .User Control class, and are stored in ASCX files. Like ASPX files,
an ASCX file contains static HTML or XHTML markup, as well as markup defining web control
and other User Controls. The code-behind model can be used.

Programmers can add their own properties, methods,[9] and event handlers.[10] An event
bubbling mechanism provides the ability to pass an event fired by a user control up to its
containing page.

User can also build Custom Controls for Asp.Net application. Where controls are in
compiled DLL file. And by using Register directive user can use control from DLL.
 8

Rendering technique compilation, the template (.aspx) file is compiled into initialization
code which builds a control tree (the composite) representing the original template. Literal text
goes into instances ASP.NET uses a visited composites rendering technique. During of the
Literal control class, and server controls are represented by instances of a specific control class.
The initialization code is combined with user-written code (usually by the assembly of multiple
partial classes) and results in a class specific for the page. The page doubles as the root of the
control tree.

Actual requests for the page are processed through a number of steps. First, during the
initialization steps, an instance of the page class is created and the initialization code is executed.
This produces the initial control tree, which is now typically manipulated by the methods of the
page in the following steps.

As each node in the tree is a control represented as an instance of a class, the code may
change the tree structure as well as manipulate the properties/methods of the individual nodes.
Finally, during the rendering step a visitor is used to visit every node in the tree, asking each
node to render itself using the methods of the visitor. The resulting HTML output is sent to the
client.After the request has been processed, the instance of the page class is discarded and with it
the entire control tree.

State management

ASP.NET applications are hosted in a web server and are accessed over the stateless
HTTP protocol. As such, if the application uses stateful interaction, it has to implement state
management on its own. ASP.NET provides various functionality for state management in
ASP.NET applications.

Application state

Application state is a collection of user-defined variables that are shared by an ASP.NET

application. These are set and initialized when the Application_OnStart event fires on the loading
of the first instance of the applications and are available till the last instance exits. Application
state variables are accessed using the Applications collection, which provides a wrapper for the
application state variables. Application state variables are identified by names.
 9

Session State

Session state is a collection of user-defined session variables, which are persisted during
a user session. These variables are unique to different instances of a user session, and are
accessed using the Session collection. Session variables can be set to be automatically destroyed
after a defined time of inactivity, even if the session does not end. At the client end, a user
session is identified either by a cookie or by encoding the session ID in the URL itself.

ASP.NET supports three modes of persistence for session variables:

In Process Mode

The session variables are maintained within the ASP.NET process. This is the fastest
way, however, in this mode the variables are destroyed when the ASP.NET process is recycled
or shut down. Since the application is recycled from time to time this mode is not recommended
for critical applications.

ASP State Mode

In this mode, ASP.NET runs a separate Windows service that maintains the state
variables. Because the state management happens outside the ASP.NET process, this has a
negative impact on performance, but it allows multiple ASP.NET instances to share the same
state server, thus allowing an ASP.NET application to be load-balanced and scaled across
multiple servers. Also, since the state management service runs independent of ASP.NET,
variables can persist across ASP.NET process shutdowns.

SQLServer Mode

Using SQL. Session variables can be persisted across ASP.NET process shutdowns in
this mode as well. The main advantage of this mode is it would allow in this mode, the state
variables are stored in a database server, accessible the application to balance load on a server
cluster while sharing sessions between servers.

View state
 10

View state refers to the page-level state management mechanism, which is utilized by the
HTML pages emitted by ASP.NET applications to maintain the state of the web form controls
and widgets. The state of the controls are encoded and sent to the server at every form
submission in a hidden field known as __VIEWSTATE. The server sends back the variable so
that when the page is re-rendered, the controls render at their last state.

At the server side, the application might change the view state, if the processing results in
updating the state of any control. The states of individual controls are decoded at the server, and
are available for use in ASP.NET pages using the View State collection.

When first released, ASP.NET lacked a template engine. Because the . NET framework
is object-oriented and allows for inheritance, many developers would define a new base class
that inherits from "System.Web.UI.Page", write methods here that render HTML, and then make
the pages in their application inherit from this new class. While this allows for common elements
to be reused across a site, it adds complexity and mixes source code with markup. Furthermore,
this method can only be visually tested by running the application - not while designing it. Other
developers have used include files and other tricks to avoid having to implement the same
navigation and other elements in every page.

ASP.NET 2.0 introduced the concept of "master pages", which allow for template-based
page development. A web application can have one or more master pages, which can be nested.
Master templates have place-holder controls, called Content Placeholders to denote where the
dynamic content goes, as well as HTML and JavaScript shared across child pages.

Child pages use those Content Placeholder controls, which must be mapped to the
placeholder of the master page that the content page is populating. The rest of the page is defined
by the shared parts of the master page, much like a mail merge in a word processor. All markup
and server controls in the content page must be placed within the Content Placeholder control.

When a request is made for a content page, ASP.NET merges the output of the content
page with the output of the master page, and sends the output to the user. The master page
remains fully accessible to the content page. This means that the content page may still
manipulate headers, change title, configure caching etc. If the master page exposes public
properties or methods (e.g. for setting copyright notices) the content page can use these as well.
 11

Other means of state management that are supported by ASP.NET are cookies, caching, and
using the query string.

Template engine

When first released, ASP.NET lacked a template engine. Because the .NET framework is
object-oriented and allows for inheritance, many developers would define a new base class that
inherits from "System.Web.UI.Page", write methods here that render HTML, and then make the
pages in their application inherit from this new class. While this allows for common elements to
be reused across a site, it adds complexity and mixes source code with markup. Furthermore, this
method can only be visually tested by running the application - not while designing it. Other
developers have used include files and other tricks to avoid having to implement the same
navigation and other elements in every page.

ASP.NET 2.0 introduced the concept of "master pages", which allow for template-based
page development. A web application can have one or more master pages, which can be nested.
Master templates have place-holder controls, called Content Placeholders to denote where the
dynamic content goes, as well as HTML and JavaScript shared across child pages.

Child pages use those Content Placeholder controls, which must be mapped to the
placeholder of the master page that the content page is populating. The rest of the page is defined
by the shared parts of the master page, much like a mail merge in a word processor. All markup
and server controls in the content page must be placed within the Content Placeholder control.

When a request is made for a content page, ASP.NET merges the output of the content
page with the output of the master page, and sends the output to the user.

The master page remains fully accessible to the content page. This means that the content
page may still manipulate headers, change title, configure caching etc. If the master page exposes
public properties or methods (e.g. for setting copyright notices) the content page can use these as
well.
 12

CHAPTER 5

PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION

Data Mining is the process of extraction of interesting (non-trivial, implicit, previously

unknown and potentially useful) information or patterns from data in large databases. Search
engines provide multiple options according to the key word for our search. The options may
include both necessary and unnecessary data. So that the user has to spend more time with it in
order to find the data needed.

But the data mining provide the technique to filter needed data from large database so
that it can be very useful to the user to find the data very easily. And also the data mining
technique finds the necessary data in less time.

Many algorithms are available to implement the data mining into the programming code
and every algorithm does a different task in order to make use of the data mining concept.

Classification algorithms rely on human supervision to train it self to classify data into
pre-defined categorical classes. The following list shows some of the categories of classification
algorithms generally used in data mining applications.

> Nearest Neighbor algorithm

> Decision Tree
> DNF Rules
> Neural networks
> Genetic algorithms
> Bayesian networks
> Rough and Fuzzy Sets
 13

Neural Network based Classification algorithms has some shortcomings. They are not
scalable. Further, if there are so many classes of data in the data under consideration, then the
dimensionality of the data makes the situation more complex and the system will give
unpredictable results. So in this research a neural network based data classification system is
under examination. For this, a multi-layer neural network will be created and its classification
performance with multi-dimensional data will be evaluated.

In the training phase, the correct class for each record is known (this is termed supervised
training), and the output nodes can therefore be assigned "correct" values — "1" for the node
corresponding to the correct class, and "0" for the others. (In practice it has been found better to
use values of 0.9 and 0.1, respectively.) It is thus possible to compare the network's calculated
values for the output nodes to these "correct" values, and calculate an error term for each node
(the "Delta" rule). These error terms are then used to adjust the weights in the hidden layers so
that, hopefully, the next time around the output values will be closer to the "correct" values.

A key feature of neural networks is an iterative learning process in which data cases
(rows) are presented to the network one at a time, and the weights associated with the input
values are adjusted each time. After all cases are presented, the process often starts over again.
During this learning phase, the network learns by adjusting the weights so as to be able to predict
the correct class label of input samples. Neural network learning is also referred to as
"connectionist learning," due to connections between the units.

Advantages of neural networks include their high tolerance to noisy data, as well as their
ability to classify patterns on which they have not been trained. The most popular neural
network algorithm is back-propagation algorithm proposed in the 1980's.

Once a network has been structured for a particular application, that network is ready to be
trained. To start this process, the initial weights (described in the next section) are chosen
randomly. Then the training, or learning, begins.
 14

The network processes the records in the training data one at a time, using the weights
and functions in the hidden layers and then compares the resulting outputs against the desired
outputs. Errors are then propagated back through the system, causing the system to adjust the
weights for application to the next record to be processed. This process occurs over and over as
the weights are continually tweaked. During the training of a network the same set of data is
processed many times as the connection weights are continually refined.

Note that some networks never learn. This could be because the input data do not contain
the specific information from which the desired output is derived. Networks also don't converge
if there is not enough data to enable complete learning. Ideally, there should be enough data so
that part of the data can be held back as a validation set.

5.2 OVERVIEW OF THE PROJECT

The project web power data mining is to implement the concept of data mining in the job
seeking website that is to filter the jobs according to the need of job seekers. And also the
project is to filter job opportunities given by many companies. So the project is mainly designed
like a website and it can be accessed by both job seekers and job providers.

Based on the data collected, priori algorithm is used to either produce a description of the
data stored, or predict an outcome. Different kinds of algorithms are used to achieve either one
of these tasks. However, in the overall web power data mining process, any mixture of these tasks
may be called upon to achieve the desired results. The Steps involved in web power data mining
are:

1. Description tasks: These tasks describe the data being mined and they are:

• Summarization: To extract compact patterns that describes subsets of data. The methods
used to achieve this task are Association Rule algorithms.

• Segmentation or Clustering: To separate data items into subsets that is similar to each
other. Partition-based clustering algorithms are used to achieve this task.
 15

• Change and Deviation Detection: To detect changes in sequential data (such as protein
sequencing, behavioral sequences, etc.).

• Dependency Modeling: To construct models of causality within the data.

2 Prediction tasks: To predict some fields in a database based on information in other fields.

• Classification: To predict the most likely state of a categorical variable (its class).

• Regression: To predict results that is numeric continuous variables.

The above tasks are implemented in this project by using the ‘priori’ algorithm. The algorithm
is used to filter the related data from large database. The priori algorithm can be implemented in
following ways.

Critical Level

The critical level type of searching is the most useful and accurate searching used to find the
very particular type of sentence. That is the critical level type gives the exact solution and displays the
output of what the user exactly needed.

In this type of searching for particular keyword we have to implement the very exact solution
for particular keywords. It can be specified by the algorithm.

High Level

It is something less priority than the critical level that is the high level provides some additional
information than the exact solution. So that this level is little time consuming than the critical level. In
this searching the filtering will be implemented only to particular keywords.

Low level

In this level the searching finds all solution to the keywords and it is worst than other two type
of searching. Because in this type of searching keyword will not be filtered most accurately so that
more number of output is possible, the user cannot find the exact output what they needed.

There is no theoretical limit on the number of hidden layers but typically there are just one
or two. Some work has been done which indicates that a maximum of five layers (one input
 16

layer, three hidden layers and an output layer) are required to solve problems of any complexity.
Each layer is fully connected to the succeeding layer.

The complex part of this learning mechanism is for the system to determine which input
contributed the most to an incorrect output and how does that element get changed to correct the
error. An inactive node would not contribute to the error and would have no need to change its
weights. To solve this problem, training inputs are applied to the input layer of the network, and
desired outputs are compared at the output layer.

In the self-organization process the input vectors are presented to the network, and the cluster
unit whose weight vector is closest (usually in terms of Euclidean distance) is chosen as the
winner. The next step is to update the value of the winning unit and neighboring units, this will
approximate

The values of the units to the one of the input vector. This can be viewed as a motion of the
units in the direction of the input vector, the magnitude of this movement depends on the learning
rate, which decreases along the process in order to obtain convergence.

5.3 MODULE DESCRIPTION

The project has been separated into number of phases called modules and each module
perform particular tasks. And the module can be easily implemented and tested rather than
testing the entire project.

5.3.1 Modules

Login

In this module new user can register their profile into the website or else the registered users
can directly login to the website.

Job Seeker

Job Seeker will be the one of two type of users available in this project , job seekers has
separate login and registration to access the website.
 17

The job seekers can access the website by posting resumes, searching the jobs according
to the company and also they can check the companies available and the opportunities given by
the companies.

Employee (Job Provider)

The job provider module is developed for the companies which has to provide jobs that is
the companies can upload the job requirement and the can check the posted resumes and can
select the candidates according to their needs.

In this module there will be a form used to register the company profile and the job
requirement. After registering the company profile they can view the resumes posted by number
of candidates.

Priori Algorithm Implementation

The following phases explain how the algorithms working with this project.

• Understand the business: This phase is used to identify the domain, objectives,
requirements, and feasibility of the data mining project.

• Understand data: This phase is based on data mining objectives identified in the previous
stage. It is used to analyze and document available data and knowledge sources in the business,
and to study characteristics of the data.

• Prepare data: Format or transform data to suitable media, clean or eliminate missing
tuples, and focus the data for data mining. This step is usually the most time consuming part of
the WPD project.

• Explore data: This phase is used to explore interesting insights into the data, so that initial
hypotheses and models of data can be evaluated and developed.

• Data mining: Select and apply modeling and discovery algorithms to find patterns of
interest in the data. This is accomplished by using different algorithms, which is the subject of
 18

this paper.

• Evaluate results: Interpret and evaluate data mining results in business terms, and initiate
new experiments if necessary.

• Deploy results: Implement results obtained by the data mining process. Maintenance and
monitoring data mining results are also part of this phase.

• Document experience: This phase is really done throughout all phases of KDD projects,
and documents aspects of the project and deployment of data mining results. This stage
enables future projects to be more efficient and effective.
 19

5.4 Data flow diagram

start

New User Register Login

password

invalid valid

Db
Try again Job details

Select
proces
s

Job seeker Job provider

Allocate
Resume jobs
submissio Searching
n
Db

db

Filter
 20

5.5 INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-based

format input data are collected and organized into group of similar data. Once identified,
appropriate input media are selected for processing.
Objectives of Input Design
The quality of input determines the quality of system processing. Input specifications
describe the manner in which data enter the system process. Input design features can ensure the
reliability of the system and procedure results from accurate data, or they can result in the
production or erroneous information. The input design also determines whether the user can
interact efficiently with the system. The input design of this project has login, registration,
resume posting, searching resumes and searching company profiles forms.

5.6 OUTPUT DESIGN

Computer output is the most important and direct source of information to the user.
Efficient, intelligible output design should improve the system’s relationships with the user and
help in decision making. A major form of output is the hardcopy from the printer.

Output requirements are designed during system analysis. A good starting point for the
output design is the data flow diagram (DFD). Human factors educe issues for design involves
addressing internal controls to ensure readability. The output design of this project has job
searching results, resume searching results forms.
 21

CHAPTER 6
SYSTEM TESTING

6.1 SYSTEM DEVELOPMENT

The system is developed to satisfy the users need. In this, the system is studied first.
System design is to be done after study and analysis. After the successful completion of the
design phase the next important step which comes into account, is the development of the system
according to the specified design.

The main procedure of this phase is the coding of the input/output, text manipulation,
logic comparison and storage/retrieval operation during system analysis stage provide the input
for program preparation. Coding was carried out in a step-by-step manner. One or more
programmers convert these operations into a program of instructions written in a language and
from acceptable to the computer hardware. User inter-activeness was given stress and the
system gives maximum flexibility. Proper validation is done for every user-defined function.

A rough interface of the system is given to the users for their feedback and suggestions.
Then the modifications are done. But as the system evolved and after a series of interactions and
demonstrations, the user felt comfortable with the newly developed system.

• The software request is evaluated

• Product requirements are collected

• Design specification for the prototype is prepared

• Prototype software is developed, tested and refined

• Prototype is given to the user, who tested the system any gave suggestions for
further refinement
 22

6.2 TESTING

Test Plan
The system testing deals with process of testing the system as a whole. This is done after the
integration process. The entire system tested by moving through each module from top to bottom. The
verification and validation process are then carried out. The errors the testing phase are eliminated and
well functioning system is developed.

Test case design focuses on a set of techniques, which meets all the testing objectives, which are
mentioned below.

• Testing is a process of executing a program with the indent of finding an error.

• A successful test is one that uncovers as yet undiscovered errors

Software Testing

A test procedure is a formal specification of test cases to be applied to one or more target
program modules. Test procedures are executable. A process called the VERIFIER applies a test
procedure to its target modules and produces an exception report indicating which test cases, if any,
failed. Test procedures facilitate thorough software testing by allowing individual modules or arbitrary
groups of modules to be thoroughly tested outside the environment in which they will eventually reside.
Test procedures are complete, self-contained, self-validating and execute automatically. Test procedures
are a deliverable product of the software development process and are used for both initial checkout and
subsequent regression testing of target program modifications.

Some of the common issues experienced with the access control reader with host software are given
below.

If reader does not function with software, verify the power supply is properly connected with reader
or not. Disconnect the power and reapply power to readerIf PC does not recognize reader, verify the
power is properly connected or disconnect the power and reapply power to reader.
Verify serial cable is properly connected to RS 232 computer COM port. Select the COM port in
software to which the reader is connected. Sequentially select the available baud rates in software until
 23

reader responds, then select desired baud rate or click the reset button in the software the repeat the above
baud rate setting process.

Testing Objectives

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

• A good test has a high probability of finding an as yet undiscovered error.
• A successful test is one that uncovers an as yet undiscovered error.
• The objective is to design tests that systematically uncover different classes of errors and do so with a
minimum amount of time and effort. Testing cannot show the absence of defects, it can only show that
software defects are present.

UNIT TESTING

The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code, and determine whether it behaves exactly
as you expect. Each unit is tested separately before integrating them into modules to test the
interfaces between modules. Unit testing has proven its value in that a large percentage of defects
are identified during its use.

The most common approach to unit testing requires drivers and stubs to be written. The
driver simulates a calling unit and the stub simulates a called unit. The investment of developer
time in this activity sometimes results in demoting unit testing to a lower level of priority and
that is almost always a mistake. Even though the drivers and stubs cost time and money, unit
testing provides some undeniable advantages. It allows for automation of the testing process,
reduces difficulties of discovering errors contained in more complex pieces of the application,
and test coverage is often enhanced because attention is given to each unit.

During unit testing the following tasks must be done.

• Number of input parameters should be equal to number of arguments.

• Parameter and argument attributes must match.
• Parameters passed should be in correct order.
• Global variable definitions consistent across modules.
 24

Integration Testing

Top down integration

Modules decision points early in design process. Top-level structure tested most. Depth first
implementation integrated by moving down the program design hierarchy. Can use depth first or
breadth first top down integration

Verifies major control and allows a complete function to be implemented, tested and
demonstrated. Can do depth first implementation of critical functions early. Top down integration
forced (to some extent) by some development tools in programs with graphical user interfaces.

Bottom up Integration

In bottom up integration testing, module at the lowest level are developed first and other
modules which go towards the 'main' program are integrated and tested one at a time. Bottom up
integration also uses test drivers to drive and pass appropriate data to the lower level modules. As
and when code for other module gets ready, these drivers are replaced with the actual module. In
this approach, lower level modules are tested extensively thus make sure that highest used module is
tested properly.

VALIDATION TESTING

Validation testing is aims to demonstrate that the software functions in a manner that can be
reasonably expected by the customer. This tests conformance the software to the Software
Requirements Specification.
 25

Test Validation

Test validation is a procedure that demonstrates that a test is job-related and correlates to on-the-
job performance. There are three main types of validation:

1. Content Validation - is a procedure where the content of the job in question is analyzed,
matched and compared, (function by function) to the abilities measured by the test. This
shows that the test is related to the job.

2. Concurrent Validation - is a procedure which tests individuals currently in the position,

and then statistically compares their test results with their current performance.

3. Predictive Validation - is a procedure which tests individuals when they are hired, and
then statistically compares the test results, after a certain time, to on-the-job performance.
A successful comparison or correlation suggests that the test is predictive of on-the-job
success. For a good predictive study, a large application pool and considerable time and
effort are required. A suggested scenario would be to test all applicants as they are hired
but not use the test results for selection. At the end of a period, say one year, a
comparison is made between the test results and on-the-job performance criteria.

TEST CASES

A test case in project is a set of conditions or variables under which a tester will determine
whether an application or software system is working correctly or not. The mechanism for
determining whether a software program or system has passed or failed such a test is known as a test
oracle.

In some settings, an oracle could be a requirement or use case, while in others it could be a
heuristic. It may take many test cases to determine that a software program or system is considered
sufficiently scrutinized to be released. Test cases are often referred to as test scripts, particularly
when written. Written test cases are usually collected into test suites.
 26

Formal test cases

In order to fully test that all the requirements of an application are met, there must be at
least two test cases for each requirement: one positive test and one negative test; unless a
requirement has sub-requirements. In that situation, each sub-requirement must have at least two
test cases. Keeping track of the link between the requirement and the test is frequently done
using a traceability matrix. Written test cases should include a description of the functionality to
be tested, and the preparation required to ensure that the test can be conducted.

A formal written test-case is characterized by a known input and by an expected output,

which is worked out before the test is executed. The known input should test a precondition and
the expected output should test a postcondition.

Informal test cases

In scenario testing, hypothetical stories are used to help the tester think through a
complex problem or system. These scenarios are usually not written down in any detail. They
can be as simple as a diagram for a testing environment or they could be a description written in
prose. The ideal scenario test is a story that is motivating, credible, complex, and easy to
evaluate. They are usually different from test cases in that test cases are single steps while
scenarios cover a number of steps.
 27

CHAPTER 7

SYSTEM IMPLEMENTATION

Implementation is the stage of the project where the theoretical design is turned into a
working system. At this stage the main work load and the major impact on the existing system
shifts to the user department. If the implementation is not carefully planned and controlled, it can
cause chaos and confusion.

Implementation includes all those activities that take place to convert from the old system
to the new one. The new system may be totally new, replacing an existing manual or automated
system or it may be a major modification to an existing system. Proper implementation is
essential to provide a reliable system to meet the organization requirements.

The process of putting the developed system in actual use is called system
implementation. The system can be implemented only after thorough testing is done and it is
found to be working according to the specifications. The system personnel check the feasibility
of the system. The most crucial stage is achieving a new successful system and giving
confidence on the new system for the user that it will work efficiently and effectively. It involves
careful planning, investigation of the current system and its constraints on implementation. The
system implementation has three main aspects. They are education and training, system testing
and changeover.

The implementation stage involves following tasks

• Careful planning

• Investigation of system and constraints

• Design of methods to achieve the changeover.

• Training of the staff in the changeover phase

• Evaluation of the changeover method

 28

Implementation Procedures

Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system. The people
are not sure that the software is meant to make their job easier.

In the initial stage they doubt about the software but we have to ensure that the resistance
does not build up as one has to make sure that. The active user must be aware of the benefits of
using the system Their confidence in the software built up Proper guidance is impaired to the
user so that he is comfortable in using the application Before going ahead and viewing the
system, the user must know that for viewing the result, the server program should be running in
the server. If the server object is not running on the server, the actual processes will not take
place.

User Training

To achieve the objectives and benefits expected from the proposed system it is essential
for the people who will be involved to be confident of their role in the new system. As system
becomes more complex, the need for education and training is more and more important.

Education is complementary to training. It brings life to formal training by explaining the

background to the resources for them. Education involves creating the right atmosphere and
motivating user staff. Education information can make training more interesting and more
understandable.

Training on the Application Software

After providing the necessary basic training on the computer awareness, the users will
have to be trained on the new application software. This will give the underlying philosophy of
the use of the new system such as the screen flow, screen design, type of help on the screen, type
of errors while entering the data, the corresponding validation check at each entry and the ways
to correct the data entered. This training may be different across different user groups and across
different levels of hierarchy.
 29

Operational Documentation

Once the implementation plan is decided, it is essential that the user of the system is
made familiar and comfortable with the environment. A documentation providing the whole
operations of the system is being developed.

Useful tips and guidance is given inside the application itself to the user. The system is
developed user friendly so that the user can work the system from the tips given in the
application itself.

A company's reputation is only as good as its last customer interaction. That's the reality
in which customer service centers operate today customer satisfaction is hard to win and easy to
lose. To avoid eroding your customer base as the availability of skilled personnel and budget
dollars shrink, you need an integrated customer service solution.

The unique features of this system are case capture, auto response and case escalation
cum notification. Using built-in workflow engine, you can automatically route cases to the right
person or team and escalate cases that are not promptly resolved, allowing you to deliver better
service, faster.
 30

CHAPTER 8

CONCLUSION AND FUTURE ENHANCEMENT

This project is used as a tool to perform data mining under large database especially job
seeking and job providing, so the users can access the website in two ways, and the project is
working like a website that is it can be useful for both job seekers and job providers.

It is the software utility to install at the computer system and can search jobs from the
home or office and also can access the company profiles. The software can be used to filter the
accurate job as their need from number of job opportunities.

Data mining technique has been implemented in this project to filter the searching
according to the keyword so that it is less time consuming. Users can easily find their data from
large database.

Project can be used over the internet to make use of this tool as software to the user to
improve the performance level of the neural network and the number of layers will be increased
as per the requirement.
 31

CHAPTER 9

APPENDIX
9.1 SOURCE CODE

Login

<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"

CodeFile="login.aspx.vb" Inherits="login" title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">
<div align=center>
<asp:Label ID="Label1" Runat="server" Text="Already Registered? Login here!"
SkinID="FormHeading"></asp:Label>
<br />
<br />
<asp:Login ID="Login1" Runat="server" OnAuthenticate="Login1_Authenticate">
</asp:Login><br />
<asp:HyperLink ID="HyperLink1" Runat="server" NavigateUrl="~/register.aspx">New
user? Register here!</asp:HyperLink>
<br />
<br />
<asp:PasswordRecovery ID="PasswordRecovery1" Runat="server">
</asp:PasswordRecovery>&nbsp;</div>
</asp:Content>

Masterpage

<%@ Master Language="VB" CodeFile="MasterPage.master.vb" Inherits="MasterPage" %>

<%@ Register TagPrefix="uc3" TagName="LatestJobs" Src="UserControls/LatestJobs.ascx"

%>
 32

<%@ Register TagPrefix="uc2" TagName="Statistics" Src="UserControls/Statistics.ascx" %>

<%@ Register TagPrefix="uc1" TagName="NavigationTree"
Src="UserControls/NavigationTree.ascx" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head id="Head1" runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">

<table width="100%" border=0 cellpadding=0 cellspacing=0>

<tr>
<td colspan=3 class="pagetop">
<table width=100% border=0>
<tr>
<td><asp:HyperLink ID="HyperLink1" Runat="server" ImageUrl="~/Images/logo.gif"
NavigateUrl="~/default.aspx"></asp:HyperLink></td>
<td valign="bottom" align="right">
&nbsp;<asp:LoginName ID="LoginName1" Runat="server" SkinID="FormLabel"
FormatString="Welcome {0} !" />
[
<asp:LoginStatus ID="LoginStatus1" Runat="server" LogoutPageUrl="~/default.aspx"
LogoutAction="Redirect" />
]
</td>
</tr>
</table>
 33

</td>
</tr>
<tr>
<td valign="top" class="pageleft" height="600px" style="width: 20%">
<uc1:NavigationTree ID="NavigationTree1" Runat="server" />
</td>
<td valign="top" width="60%">
<asp:contentplaceholder id="ContentPlaceHolder1" runat="server"><br />
</asp:contentplaceholder>
</td>
<td valign="top" width="20%" class="pageright">&nbsp;<uc2:statistics id="Statistics1"
runat="server"></uc2:statistics>
<br />
<uc3:LatestJobs ID="LatestJobs1" Runat="server" />
</td>
</tr>
<tr>
<td colspan=3 class="pagebottom" align="center">
&nbsp;<br />
Copyright (C) your copyright here.<br />
<br />
<asp:HyperLink ID="lnkAds" Runat="server">Want to advertise with us?
</asp:HyperLink>
|
<asp:HyperLink ID="lnkWebmaster" Runat="server">Problems with the site?
</asp:HyperLink>
<br />
<br />
</td>
</tr>
</table></form></body></html>
 34

Change Password

<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"

CodeFile="changepassword.aspx.vb" Inherits="changepassword" title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">
<div align=center>
<asp:Label ID="Label1" Runat="server" Text="Change your password!"
SkinID="FormHeading"></asp:Label>
<br /><br />
<asp:ChangePassword ID="ChangePassword1" Runat="server"
OnContinueClick="ChangePassword1_ContinueClick"
ContinueDestinationPageUrl="~/default.aspx">
</asp:ChangePassword>
</div>
</asp:Content>

Customer Error Page

<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"

CodeFile="customerrorpage.aspx.vb" Inherits="customerrorpage" title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">
<div align=center>
<br />
<asp:Label ID="Label1" Runat="server" Text="Unexpected Error!"
CssClass="dataentryformerrormsg"></asp:Label>
</div>
</asp:Content>

Default

<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"

CodeFile="Default.aspx.vb" Inherits="_Default" title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">
 35

<div align=center>
<asp:Label ID="Label1" Runat="server" Text="Welcome !!!"
SkinID="FormHeading"></asp:Label>
<br />
<br />
<p>
<asp:Label CssClass="marketingtext" ID="Label2" runat="server" Text="Search for job
openings, post resume, search resumes, post job openings and more..."></asp:Label>
&nbsp;</p>
<p>
&nbsp;&nbsp;</p>
<p>
&nbsp;&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
</div>
</asp:Content>

Register

<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"

CodeFile="register.aspx.vb" Inherits="register" title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">

<div align=center>
<asp:Label ID="Label2" Runat="server" Text="Employees/ Employers! Register here!!"
SkinID="FormHeading"></asp:Label>
</div>
<br />
 36

Registration is a two step process:<br />

<ol>
<li>Choose a user name and password</li><li>Choose whether you would like to register
as an "Employee" or "Employer".</li></ol>

<p>
Once you register with us you can access respective secured areas for posting resumes
or posting jobs.</p>

<div align=center>
<asp:CreateUserWizard ID="CreateUserWizard1" Runat="server"
CreateUserButtonText="Register Me"
OnContinueButtonClick="CreateUserWizard1_ContinueButtonClick"
OnNextButtonClick="CreateUserWizard1_NextButtonClick"
OnActiveStepChanged="CreateUserWizard1_ActiveStepChanged">
<WizardSteps>
<asp:WizardStep Runat="server" ID="WizardStep2" Title="Please tell us about
yourself"><table style="width: 100%"><tr><td contenteditable="true" align="right"><asp:Label
Runat="server" Text="First Name :" SkinID="FormLabel" ID="Label3"></asp:Label>
</td><td align="left"><asp:TextBox Runat="server" ID="TextBox1"></asp:TextBox>
<asp:RequiredFieldValidator Runat="server" ControlToValidate="TextBox1"
Display="Dynamic"
ErrorMessage="Please enter first name" ID="RequiredFieldValidator1">
</asp:RequiredFieldValidator>
</td></tr><tr><td contenteditable="true" align="right"><asp:Label Runat="server" Text="Last
Name :" SkinID="FormLabel" ID="Label4"></asp:Label>
</td><td align="left"><asp:TextBox Runat="server" ID="TextBox2"></asp:TextBox>
<asp:RequiredFieldValidator Runat="server" ControlToValidate="TextBox2"
Display="Dynamic"
ErrorMessage="Please enter last name" ID="RequiredFieldValidator2">
</asp:RequiredFieldValidator>
 37

</td></tr></table></asp:WizardStep>
<asp:CreateUserWizardStep ID="CreateUserWizardStep1" Runat="server" Title="Sign Up for
Your New Account"></asp:CreateUserWizardStep>
<asp:WizardStep ID="WizardStep1" Runat="server" Title="Choose your role" StepType=Step>
<table width="100%">
<tr>
<td style="width: 100px">
<asp:Label Runat="server" Text="Register As :" ID="Label1"></asp:Label>
</td>
</tr>
<tr>
<td style="width: 100px">
<asp:DropDownList Runat="server" Height="22px" Width="135px"
ID="DropDownList1">
</asp:DropDownList>
</td>
</tr>
</table>
</asp:WizardStep>
<asp:CompleteWizardStep ID="CompleteWizardStep1" Runat="server"
Title="Complete"></asp:CompleteWizardStep>
</WizardSteps><StartNavigationTemplate>
<asp:Button Runat="server" Text="Next" CommandName="MoveNext"
ID="StartNextButton" />

</StartNavigationTemplate>
</asp:CreateUserWizard>
</div>
</asp:Content>
 38

Education Level
<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"
CodeFile="EducationLevelsManager.aspx.vb" Inherits="EducationLevelsManager"
title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">
<div align="center">
<asp:Label ID="Label14" Runat="server" SkinID="FormHeading" Text="Education Levels
Manager"></asp:Label>
<br />
<br />
<asp:DetailsView ID="DetailsView1" Runat="server" DataSourceID="ObjectDataSource1"
AllowPaging="True" AutoGenerateRows="False" DataKeyNames="EducationLevelID"
GridLines="None" CellPadding="5" SkinID="AdminEntry">
<PagerSettings Mode="NumericFirstLast"></PagerSettings>
<CommandRowStyle HorizontalAlign="Left"></CommandRowStyle>
<Fields>
<asp:CommandField ButtonType="Button" ShowDeleteButton="True"
ShowInsertButton="True"
ShowEditButton="True"></asp:CommandField>
<asp:BoundField HeaderText="Education Level ID :" DataField="educationlevelid"
ReadOnly="True" InsertVisible="False">
<ItemStyle HorizontalAlign="Left"></ItemStyle>
<HeaderStyle CssClass="dataentryformlabel"></HeaderStyle>
</asp:BoundField>
<asp:BoundField HeaderText="Education Level Name :"
DataField="educationlevelname">
<HeaderStyle CssClass="dataentryformlabel"></HeaderStyle>
</asp:BoundField>
</Fields>
<FieldHeaderStyle HorizontalAlign="Right"></FieldHeaderStyle>
 39

<HeaderStyle HorizontalAlign="Right"></HeaderStyle>
<EditRowStyle HorizontalAlign="Left"></EditRowStyle>
</asp:DetailsView><br />
<asp:ObjectDataSource ID="ObjectDataSource1" Runat="server"
TypeName="JobSiteStarterKit.BOL.EducationLevel"
DataObjectTypeName="JobSiteStarterKit.BOL.EducationLevel"
DeleteMethod="Delete" InsertMethod="Insert" SelectMethod="GetEducationLevels"
UpdateMethod="Update">
</asp:ObjectDataSource>
</div>
</asp:Content>

Experience Level
<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false"
CodeFile="ExperienceLevelManager.aspx.vb" Inherits="ExperienceLevelManager_aspx"
title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="server">

<div align=center>
<asp:Label ID="Label14" Runat="server" SkinID="FormHeading" Text="Experience Levels
Manager"></asp:Label><br />
<br />
<asp:DetailsView ID="DetailsView1" Runat="server" DataSourceID="ObjectDataSource1"
AllowPaging="True" AutoGenerateRows="False" GridLines="None" CellPadding="5"
DataKeyNames="ExperienceLevelID" SkinID="AdminEntry"
OnDataBound="DetailsView1_DataBound" OnDataBinding="DetailsView1_DataBinding">
<PagerSettings Mode="NumericFirstLast"></PagerSettings>
<CommandRowStyle HorizontalAlign="Left"></CommandRowStyle>
<Fields>
<asp:CommandField ButtonType="Button" ShowDeleteButton="True"
ShowInsertButton="True"
 40

ShowEditButton="True"></asp:CommandField>
<asp:BoundField ReadOnly="True" HeaderText="Experience Level ID :"
InsertVisible="False"
DataField="experiencelevelid">
<ItemStyle HorizontalAlign="Left"></ItemStyle>
</asp:BoundField>
<asp:BoundField HeaderText="Experience Level Name :"
DataField="experiencelevelname">
<ItemStyle HorizontalAlign="Left"></ItemStyle>
</asp:BoundField>
</Fields>
<FieldHeaderStyle HorizontalAlign="Right"></FieldHeaderStyle>
<HeaderStyle HorizontalAlign="Right"></HeaderStyle>
<EditRowStyle HorizontalAlign="Left"></EditRowStyle>
</asp:DetailsView><br />
<asp:ObjectDataSource ID="ObjectDataSource1" Runat="server"
TypeName="JobSiteStarterKit.BOL.ExperienceLevel"
DataObjectTypeName="JobSiteStarterKit.BOL.ExperienceLevel"
DeleteMethod="Delete" InsertMethod="Insert" SelectMethod="GetExperienceLevels"
UpdateMethod="Update" OnSelected="ObjectDataSource1_Selected">
</asp:ObjectDataSource>

</div>

</asp:Content>
 41

9.2 SCREEN SHOTS

1. Login
 42

2. Register
 43

3. Registration form
44
 45

4. User Selection
 46

5. User
47
 48

6. Search Job
 49

7. Post Resume
50
 51

8. Company Profile
 52

9. Company
53
 54

10. My Favorites form

 55

CHAPTER 10
REFERENCES

Websites

1. www.thearling.com

2. www.edataindia.com

3. www.cs.umbc.edu

4. www-ai.cs.uni-dortmund.de

5. www.cs.fit.edu

Books

Longbing Cao 'Data mining and multi-agent integration’

Data mining : concepts and techniques by Jiawei Han, Micheline Kamber

1. Agent intelligence through data mining by Andreas L. Symeonidis, Pericles A. Mitkas