theoretical background of the project

Introduction

1. INTRODUCTION

1.1. Aim of the Project

ENTERPRISE RESOURCE INFORMATION SYSTEM(ERIS) is a compurised solution for recruiting angencies and software consultants. The objective of the project is to design and develop Integration of Resume, which is a place for Job Seekers and Job Providers to meet. The Database should collect also the minute details about the Job Seeker and Provider.

Integration of Recruitment Process is designed to collect multiple resumes from the Job Seeker. Integration of Recruitment Process aim is to provide Job Provider with enormous amount of data.

1.2. Problem Statement

Software consultants and recruiting agencies conduct a test to the candidates applying for the job. They, then select the candidates who passed the test and make arrangements after their interviews; fix the date and other formalities. This is then informated to the candidates. Interview is conducted and the candidates passing the interview are recruited as employees in their own firm.

The organization maintains data about the recruited employees; their personal details, skills, experience etc.,. it also maintains information about the firms outsourcing the recruitment. It maintains all the details about the vacancies in firms and their requirements.

The organization then matches the requirements of the firms with that of the skills of its employees and assigns them to the concerned firms. It still maintains the details of the assigned employees; because these are the hired employees directly under the control of the organization, and it is the organization who pays salaries to them.

The organization does all these manually. It writes down the data about the applicants, employees and clients in the records. All this is a very tedious job requiring everything to be done manually.

ENTERPRISE RESOURCE INFORMATION SYSTEM

1

Introduction

Enterprise Resource Information System addresses all these by automating many of the tasks of the organization. It relieves the employees by letting them do all the tedious jobs electronically.

1.3. Project ObjectiveDesigning and Implementing Job Seekers & Job Providers:

The aim of this module is to collect data from the user; he may a job seeker or a job provider. Both of them are potential clients to our Resume Art. A user should be registered regardless of whether he is a job seeker or a provider. In this moduleweregister the user and grab as many details as possible about the user.

Designing and implementing Resume Database, job database

The aim of the module is to create a resume for all his job seekers asking the details about the experience, education, skills, affiliations and references for the project.

Designing a resume search engine

The aim of the module is to design a dynamic search engine for the Resume atdatabase, which can provide data for the job seekers and job providers.


2

Theoretical Background of the Project

2. THEORETICAL BACKGROUND OF THE PROJECT

2.1. HARDWARE CONFIGURATION

This system is developed on the following hardware configuration.

Pentium IV processor

128 MB Ram

Hard disk 80 GB

Microsoft Compatible Key Board

Scroll Mouse

2.2. DESCRIPTION OF SOFTWARE

This system is developed using the following software.

Operating System: Windows XP

Technology: ASP.NET

Data Access Component ADO.NET

Back End: MS Access 2003

Overview of the .NET Framework

Web services

Web services provide a web-enabled user interface with tools that include various

hypertext markup language (HTML) controls and web controls. Web services also handle

various web protocols, security, when code is targeted for .NET, it is called managed

code, which means that the code automatically runs under a “contract of cooperation”

with the CLR. Managed code supplies the information necessary for the runtime to

provide services such as memory management, cross-language integration, code access

security, and the automatic lifetime control of all of our objects.



3

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET Framework

is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or

executed remotely.

To provide a code-execution environment that minimizes software deployment and

versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance problems

of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on

the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and

the .NET Framework class library. The common language runtime is the foundation of

the .NET Framework. You can think of the runtime as an agent that manages code at

execution time, providing core services such as memory management, thread

management, and remoting, while also enforcing strict type safety and other forms of

code accuracy that ensure security and robustness. In fact, the concept of code

management is a fundamental principle of the runtime. Code that targets the runtime is

known as managed code, while code that does not target the runtime is known as

unmanaged code. The class library, the other main component of the .NET Framework, is



4

a comprehensive, object-oriented collection of reusable types that you can use to develop

applications ranging from traditional command-line or graphical user interface (GUI)

applications to applications based on the latest innovations provided by ASP.NET, such

as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common

language runtime into their processes and initiate the execution of managed code,

thereby creating a software environment that can exploit both managed and unmanaged

features. The .NET Framework not only provides several runtime hosts, but also

supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment

for managed code. ASP.NET works directly with the runtime to enable Web Forms

applications and XML Web services, both of which are discussed later in this topic.

Fig 1: .NET ARCHITECTURE



5

The above illustration shows the relationship of the common language runtime and the

class library to your applications and to the overall system. The illustration also shows

how managed code operates within a larger architecture.

The following sections describe the main components and features of the .NET

Framework in greater detail.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution, code

safety verification, compilation, and other system services. These features are intrinsic to

the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,

depending on a number of factors that include their origin (such as the Internet, enterprise

network, or local computer). This means that a managed component might or might not

be able to perform file-access operations, registry-access operations, or other sensitive

functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an

executable embedded in a Web page can play an animation on screen or sing a song, but

cannot access their personal data, file system, or network. The security features of the

runtime thus enable legitimate Internet-deployed software to be exceptionally feature

rich.

The runtime also enforces code robustness by implementing a strict type- and code-

verification infrastructure called the common type system (CTS). The CTS ensures that

all managed code is self-describing. The various Microsoft and third-party language

compilers generate managed code that conforms to the CTS. This means that managed

code can consume other managed types and instances, while strictly enforcing type

fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common software

issues. For example, the runtime automatically handles object layout and manages

Theoretical Background Of The Project


6

references to objects, releasing them when they are no longer being used. This automatic

memory management resolves the two most common application errors, memory leaks

and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can

write applications in their development language of choice, yet take full advantage of the

runtime, the class library, and components written in other languages by other

developers. Any compiler vendor who chooses to target the runtime can do so. Language

compilers that target the .NET Framework make the features of the .NET Framework

available to existing code written in that language, greatly easing the migration process

for existing applications.

While the runtime is designed for the software of the future, it also supports software of

today and yesterday. Interoperability between managed and unmanaged code enables

developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A

feature called just-in-time (JIT) compiling enables all managed code to run in the native

machine language of the system on which it is executing. Meanwhile, the memory

manager removes the possibilities of fragmented memory and increases memory locality-

of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such as

Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure

enables you to use managed code to write your business logic, while still enjoying the

superior performance of the industry's best enterprise servers that support runtime

hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate

with the common language runtime. The class library is object oriented, providing types



7

from which your own managed code can derive functionality. This not only makes

the .NET Framework types easy to use, but also reduces the time associated with learning

new features of the .NET Framework. In addition, third-party components can integrate

seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that

you can use to develop your own collection classes. Your collection classes will blend

seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types

enable you to accomplish a range of common programming tasks, including tasks such as

string management, data collection, database connectivity, and file access. In addition to

these common tasks, the class library includes types that support a variety of specialized

development scenarios. For example, you can use the .NET Framework to develop the

following types of applications and services:

Console applications.

Scripted or hosted applications.

Windows GUI applications (Windows Forms).

ASP.NET applications.

XML Web services.

Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that

vastly simplify Windows GUI development. If you write an ASP.NET Web Form

application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the

desktop, enabling a user to perform a task. Client applications include applications such

as word processors and spreadsheets, as well as custom business applications such as

data-entry tools, reporting tools, and so on. Client applications usually employ windows,



8

menus, buttons, and other GUI elements, and they likely access local resources such as

the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the

managed Windows Forms control) deployed over the Internet as a Web page. This

application is much like other client applications: it is executed natively, has access to

local resources, and includes graphical elements.

Server Application Development

Server-side applications in the managed world are implemented through runtime hosts.

Unmanaged applications host the common language runtime, which allows your custom

managed code to control the behavior of the server. This model provides you with all the

features of the common language runtime and class library while gaining the performance

and scalability of the host server.

The following illustration shows a basic network schema with managed code running in

different server environments. Servers such as IIS and SQL Server can perform standard

operations while your application logic executes through the managed code.

Fig 2: Server-side managed code

ASP.NET is the hosting environment that enables developers to use the .NET Framework

to target Web-based applications. However, ASP.NET is more than just a runtime host; it

is a complete architecture for developing Web sites and Internet-distributed objects using

managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the



9

publishing mechanism for applications, and both have a collection of supporting classes

in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are distributed,

server-side application components similar to common Web sites. However, unlike Web-

based applications, XML Web services components have no UI and are not targeted for

browsers such as Internet Explorer and Netscape Navigator. Instead, XML Web services

consist of reusable software components designed to be consumed by other applications,

such as traditional client applications, Web-based applications, or even other XML Web

services. As a result, XML Web services technology is rapidly moving application

development and deployment into the highly distributed environment of the Internet.

The .NET Framework also provides a collection of classes and tools to aid in

development and consumption of XML Web services applications. XML Web services

are built on standards such as SOAP (a remote procedure-call protocol), XML (an

extensible data format), and WSDL (the Web Services Description Language). The .NET

Framework is built on these standards to promote interoperability with non-Microsoft

solutions.

Active Server Pages.NET

ASP.NET is a programming framework built on the common language runtime that can

be used on a server to build powerful Web applications. ASP.NET offers several

important advantages over previous Web development models:

Enhanced Performance. ASP.NET is compiled common language runtime code

running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage

of early binding, just-in-time compilation, native optimization, and caching services right

out of the box. This amounts to dramatically better performance before you ever write a

line of code.

World-Class Tool Support. The ASP.NET framework is complemented by a rich

toolbox and designer in the Visual Studio integrated development environment.



10

WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a

few of the features this powerful tool provides.

Power and Flexibility. Because ASP.NET is based on the common language

runtime, the power and flexibility of that entire platform is available to Web application

developers. The .NET Framework class library, Messaging, and Data Access solutions

are all seamlessly accessible from the Web. ASP.NET is also language-independent, so

you can choose the language that best applies to your application or partition your

application across many languages. Further, common language runtime interoperability

guarantees that your existing investment in COM-based development is preserved when

migrating to ASP.NET.

Simplicity. ASP.NET makes it easy to perform common tasks, from simple form

submission and client authentication to deployment and site configuration. For example,

the ASP.NET page framework allows you to build user interfaces that cleanly separate

application logic from presentation code and to handle events in a simple, Visual Basic -

like forms processing model. Additionally, the common language runtime simplifies

development, with managed code services such as automatic reference counting and

garbage collection.

Manageability. ASP.NET employs a text-based, hierarchical configuration system,

which simplifies applying settings to your server environment and Web applications.

Because configuration information is stored as plain text, new settings may be applied

without the aid of local administration tools. This "zero local administration" philosophy

extends to deploying ASP.NET Framework applications as well. An ASP.NET

Framework application is deployed to a server simply by copying the necessary files to

the server. No server restart is required, even to deploy or replace running compiled code.



11

Scalability and Availability. ASP.NET has been designed with scalability in mind,

with features specifically tailored to improve performance in clustered and

multiprocessor environments. Further, processes are closely monitored and managed by

the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be

created in its place, which helps keep your application constantly available to handle

requests.

Customizability and Extensibility. ASP.NET delivers a well-factored architecture

that allows developers to "plug-in" their code at the appropriate level. In fact, it is

possible to extend or replace any subcomponent of the ASP.NET runtime with your own

custom-written component. Implementing custom authentication or state services has

never been easier.

Security. With built in Windows authentication and per-application configuration,

you can be assured that your applications are secure.

Language Support

The Microsoft .NET Platform currently offers built-in support for three languages: C#,

Visual Basic, and JScript.

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with

existing pages), the ASP.NET Web Forms framework has been specifically designed to

address a number of key deficiencies in the previous model. In particular, it provides:

The ability to create and use reusable UI controls that can encapsulate common

functionality and thus reduce the amount of code that a page developer has to write.



12

the ability for developers to cleanly structure their page logic in an orderly fashion (not

"spaghetti code").

The ability for development tools to provide strong WYSIWYG design support

for pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be

deployed throughout an IIS virtual root directory tree. When a browser client

requests .aspx resources, the ASP.NET runtime parses and compiles the target file into

a .NET Framework class. This class can then be used to dynamically process incoming

requests. (Note that the .aspx file is compiled only the first time it is accessed; the

compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and changing

its file name extension to .aspx (no modification of code is required). For example, the

following sample demonstrates a simple HTML page that collects a user's name and

category preference and then performs a form pushback to the originating page when a

button is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This includes support

for <% %> code render blocks that can be intermixed with HTML content within

an .aspx file. These code blocks execute in a top-down manner at page render time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is the method

shown in the preceding samples, where the page code is physically declared within the

originating .aspx file. An alternative approach--known as the code-behind method—


enables the page code to be more cleanly separated from the HTML content into an

entirely separate file.


13

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program dynamic content,

ASP.NET page developers can use ASP.NET server controls to program Web pages.

Server controls are declared within an .aspx file using custom tags or intrinsic HTML

tags that contain a runat="server" attribute value. Intrinsic HTML tags are handled by

one of the controls in the System.Web.UI.HtmlControls namespace. Any tag that

doesn't explicitly map to one of the controls is assigned the type of

System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between round trips to

the server. This control state is not stored on the server (it is instead stored within an

<input type="hidden"> form field that is round-tripped between requests). Note also

that no client-side script is required.

In addition to supporting standard HTML input controls, ASP.NET enables developers to

utilize richer custom controls on their pages. For example, the following sample

demonstrates how the <asp:adrotator> control can be used to dynamically display

rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.

2. ASP.NET Web Forms pages can target any browser client (there are no script

library or cookie requirements).

3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.

4. ASP.NET server controls provide an easy way to encapsulate common

functionality.


5. ASP.NET ships with 45 built-in server controls. Developers can also use controls

built by third parties.


14

6. ASP.NET server controls can automatically project both uplevel and downlevel

HTML.

7. ASP.NET templates provide an easy way to customize the look and feel of list

server controls.

8. ASP.NET validation controls provide an easy way to do declarative client or server

data validation.

ACTIVE X DATA OBJECTS.NET

ADO.NET Overview

ADO.NET is an evolution of the ADO data access model that directly addresses user

requirements for developing scalable applications. It was designed specifically for the

web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Commandobjects, and also introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous data

architectures is that there exists an object -- the DataSet -- that is separate and distinct

from any data stores. Because of that, the DataSet functions as a standalone entity. You

can think of the DataSet as an always disconnected recordset that knows nothing about

the source or destination of the data it contains. Inside a DataSet, much like in a

database, there are tables, columns, relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then, it

connects back to the database to update the data there, based on operations performed

while the DataSet held the data. In the past, data processing has been primarily

connection-based. Now, in an effort to make multi-tiered apps more efficient, data

processing is turning to a message-based approach that revolves around chunks of



15

information. At the center of this approach is the DataAdapter, which provides a bridge

to retrieve and save data between a DataSet and its source data store. It accomplishes this

by means of requests to the appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model that works

with all models of data storage: flat, relational, and hierarchical. It does this by having no

'knowledge' of the source of its data, and by representing the data that it holds as

collections and data types. No matter what the source of the data within the DataSet is, it

is manipulated through the same set of standard APIs exposed through the DataSet and

its subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed provider has

detailed and specific information. The role of the managed provider is to connect, fill,

and persist the DataSet to and from data stores. The OLE DB and SQL Server .NET Data

Providers (System.Data.OleDb and System.Data.SqlClient) that are part of the .Net

Framework provide four basic objects: the Command, Connection, DataReader and

DataAdapter. In the remaining sections of this document, we'll walk through each part

of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they

are, and how to program against them.

The following sections will introduce you to some objects that have evolved, and some

that are new. These objects are:

Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database.

DataReaders. For reading a forward-only stream of data records from a SQL



16

Server data source. DataSets. For storing, remoting and programming against flat data,

XML data and relational data.

DataAdapters. For pushing data into a DataSet, and reconciling data against a

database.

When dealing with connections to a database, there are two different options: SQL Server

.NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider

(System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider.

These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data

Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).

Connections

Connections are used to 'talk to' databases, and are represented by provider-specific

classes such as SQLConnection. Commands travel over connections and resultsets are

returned in the form of streams which can be read by a DataReader object, or pushed

into a DataSet object.

Commands

Commands contain the information that is submitted to a database, and are represented by

provider-specific classes such as SQLCommand. A command can be a stored procedure

call, an UPDATE statement, or a statement that returns results. You can also use input

and output parameters, and return values as part of your command syntax. The example

below shows how to issue an INSERT statement against the Northwind database.

DataReaders

The DataReader object is somewhat synonymous with a read-only/forward-only cursor

over data. The DataReader API supports flat as well as hierarchical data. A DataReader

object is returned after executing a command against a database. The format of the



17

returned DataReader object is different from a recordset. For example, you might use

the DataReader to show the results of a search list in a web page.

DataSets and DataAdapters

DataSets

The DataSet object is similar to the ADO Recordset object, but more powerful, and with

one other important distinction: the DataSet is always disconnected. The DataSet object

represents a cache of data, with database-like structures such as tables, columns,

relationships, and constraints. However, though a DataSet can and does behave much

like a database, it is important to remember that DataSet objects do not interact directly

with databases, or other source data. This allows the developer to work with a

programming model that is always consistent, regardless of where the source data resides.

Data coming from a database, an XML file, from code, or user input can all be placed

into DataSet objects. Then, as changes are made to the DataSet they can be tracked and

verified before updating the source data. The GetChanges method of the DataSet object

actually creates a second DatSet that contains only the changes to the data. This DataSet

is then used by a DataAdapter (or other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to produce and

consume XML data and XML schemas. XML schemas can be used to describe schemas

interchanged via WebServices. In fact, a DataSet with a schema can actually be

compiled for type safety and statement completion.

DataAdapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source data.

Using the provider-specific SqlDataAdapter (along with its associated SqlCommand

and SqlConnection) can increase overall performance when working with a Microsoft

SQL Server databases. For other OLE DB-supported databases, you would use the



18

OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection

objects.

The DataAdapter object uses commands to update the data source after changes have

been made to the DataSet. Using the Fill method of the DataAdapter calls the SELECT

command; using the Update method calls the INSERT, UPDATE or DELETE command

for each changed row. You can explicitly set these commands in order to control the

statements used at runtime to resolve changes, including the use of stored procedures. For

ad-hoc scenarios, a CommandBuilder object can generate these at run-time based upon

a select statement. However, this run-time generation requires an extra round-trip to the

server in order to gather required metadata, so explicitly providing the INSERT,

UPDATE, and DELETE commands at design time will result in better run-time

performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new

objects, the DataSet and DataAdapter, are provided for these scenarios.

3. ADO.NET can be used to get data from a stream, or to store data in a cache for

updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order to do

inserts, updates, and deletes. You don't need to first put data into a DataSet in order to

insert, update, or delete it.

6. Also, you can use a DataSet to bind to the data, move through the data, and navigate

data relationships

Overview of ADO.NET

ADO.NET provides consistent access to data sources such as Microsoft SQL Server, as

well as data sources exposed via OLE DB and XML. Data-sharing consumer applications

can use ADO.NET to connect to these data sources and retrieve, manipulate, and update



19

ADO.NET cleanly factors data access from data manipulation into discrete components

that can be used separately or in tandem. ADO.NET includes .NET data providers for

connecting to a database, executing commands, and retrieving results. Those results are

either processed directly, or placed in an ADO.NET DataSet object in order to be

exposed to the user in an ad-hoc manner, combined with data from multiple sources, or

remoted between tiers. The ADO.NET DataSet object can also be used independently of

a .NET data provider to manage data local to the application or sourced from XML.

The ADO.NET classes are found in System.Data.dll, and are integrated with the XML

classes found in System.XML.dll. When compiling code that uses the System.Data

namespace, reference both System.Data.dll and System.XML.dll. For an example of

compiling an ADO.NET application using a command line compiler, ADO.NET provides

functionality to developers writing managed code similar to the functionality provided to

native COM developers by ADO.

Design Goals for ADO.NET

As application development has evolved, new applications have become loosely coupled

based on the Web application model. More and more of today's applications use XML to

encode data to be passed over network connections. Web applications use HTTP as the

fabric for communication between tiers, and therefore must explicitly handle maintaining

state between requests. This new model is very different from the connected, tightly

coupled style of programming that characterized the client/server era, where a connection

was held open for the duration of the program's lifetime and no special handling of state

was required.

ADO.NET was designed to meet the needs of this new programming model:

disconnected data architecture, tight integration with XML, common data representation

with the ability to combine data from multiple and varied data sources, and optimized

facilities for interacting with a database, all native to the .NET Framework.

In creating ADO.NET, Microsoft embraced the following design goals.



20

Leverage Current ADO Knowledge

The design for ADO.NET addresses many of the requirements of today's application

development model. At the same time, the programming model stays as similar as

possible to ADO, so current ADO developers do not have to start from the beginning in

learning a brand new data access technology. ADO.NET is an intrinsic part of the .NET

Framework without seeming completely foreign to the ADO programmer.

ADO.NET coexists with ADO. While most new .NET-based applications will be written

using ADO.NET, ADO remains available to the .NET programmer through .NET COM

interoperability services.

Support the N-Tier Programming Model

ADO.NET provides first-class support for the disconnected, n-tier programming

environment for which many new applications are written. The concept of working with a

solution for n-tier programming is the DataSet.

Integrate XML Support

XML and data access are intimately tied — XML is all about encoding data, and data

access is increasingly becoming all about XML. The .NET Framework does not just

disconnected set of data has become a focal point in the programming model. The

ADO.NET support Web standards — it is built entirely on top of them.

XML support is built into ADO.NET at a very fundamental level. The XML classes in

the .NET Framework and ADO.NET are part of the same architecture — they integrate at

many different levels. You no longer have to choose between the data access set of

services and their XML counterparts; the ability to cross over from one to the other is

inherent in the design of both.

ADO.NET Architecture

Data processing has traditionally relied primarily on a connection-based, two-tier model.

As data processing increasingly uses multi-tier architectures, programmers are switching

to a disconnected approach to provide better scalability for their applications.



21

XML and ADO.NET

ADO.NET leverages the power of XML to provide disconnected access to data.

ADO.NET was designed hand-in-hand with the XML classes in the .NET Framework —

both are components of a single architecture.

ADO.NET and the XML classes in the .NET Framework converge in the DataSet object.

The DataSet can be populated with data from an XML source, whether it is a file or an

XML stream. The DataSet can be written as World Wide Web Consortium (W3C)

compliant XML, including its schema as XML Schema definition language (XSD)

schema, regardless of the source of the data in the DataSet. Because the native

serialization format of the DataSet is XML, it is an excellent medium for moving data

between tiers making the DataSet an optimal choice for remoting data and schema

context to and from an XML Web service.

The DataSet can also be synchronized with an XMLDataDocument to provide relational

and hierarchical access to data in real time

Fig 2.ADO.NET architecture

Fig 2.ADO.NET architecture

Remoting or Marshaling Data between Tiers and Clients

The design of the DataSet enables you to easily transport data to clients over the Web



22

using XML Web services, as well as allowing you to marshal data between .NET

components using .NET Remoting services. DataTable objects can also be used with

remoting services, but cannot be transported via an XML Web service.

Architectural Overview of XML in the .NET Framework

This section provides an architectural overview of XML in the .NET Framework. The

design goals for the XML classes in the .NET Framework are:

High-productivity.

Standards-based.

Multilingual support.

Extensible.

Pluggable architecture.

Focused on performance, reliability, and scalability.

Integration with ADO.NET.

Design Goals for XML in the .NET Framework.

The goals of XML in .NET Framework are:

Compliance with the W3C standards.

Extensibility.

Pluggable architecture.

Performance.

Tight integration with ADO.NET.

XML Integration with Relational Data and ADO.NET

When using previous versions of ActiveX Data Objects (ADO), the code written when

working with relational data was different than the code written to work with hierarchical

data. Today, the .NET architecture integrates several classes in XML with several classes

in the ADO.NET architecture to unify the two programming models. This gives you an

object model to use regardless of the structure of the data.



23

The XML in the .NET Framework and ADO.NET provide a unified programming model

to access data represented as both XML data, text delimited by tags that structure the

data, and relational data, tables consisting of rows, columns, and constraints. The XML

reads XML data from any data stream into DOM node trees, where data can be accessed

programmatically, while ADO.NET provides the means to access and manipulate

relational data within a DataSet object.

Of the classes that comprise XML in the .NET Framework and ADO.NET, the DataSet

represents a relational data source in the ADO.NET, the XMLDocument implements the

DOM in XML, and the XMLDataDocument unifies the ADO.NET and XML by

representing relational data from a DataSet and synchronizing it with the XML document

model.

The XML integration with relational data occurs with the XMLDataDocument, a class

derived from the XMLDocument. The XMLDataDocument maps XML to relational data

in an ADO.NET DataSet.

Reading XML with the XMLReader

The XMLReader class is an abstract base class that provides non-cached, forward-only,

read-only access. The XMLReader class checks that the XML is well-formed, and throws

XMLExceptions if an error is encountered. It can read a stream or a document, and it

implements the namespace requirements outlined in the recommendation provided by the

W3C located at www.w3.org/TR/REC-XML-names.

A database typically has two components: the files holding the physical database and the

database management system (DBMS) software that applications use to access data.

The DBMS is responsible for enforcing the database structure, including:

Maintaining the relationships between data in the database.

Ensuring that data is stored correctly, and that the rules defining data relationships

are not violated.

Recovering all data to a point of known consistency in case of system failures.



24

Database Objects

The database window has six object types.

a. Tables: stores data. Columns are fields and rows are records. Accessis

A relational database in that it allows data to be stored in multiple tables, and the

Data in one table can be related to another table by a single field.

b. Queries : Used to select specific data from the tables. A query could be

used to select only students who are in a specific department or only students

Who have attended a certain year.

c. Forms: Used to enter and display data in the tables. Used to make data

Entry easier and to customize the way the data is viewed.

d. Reports: Used to output the data from tables and queries.

e. Macros: Automate tasks within the database.

f. Modules: Program code (Visual Basic)

Tips on creating a database

1. Plan your database on paper.

2. Tables should share a common field.

3. Organize data into its smallest unit. Ex. Fame and lname instead of

full name

4. Give the file a real name. Don’t use db1….db2 etc.

5. (Cold Fusion) Field names should be alpha characters. If numbers are used

they should be at the end. Underscores and dashes are acceptable. Try to

avoid using spaces.

Table Relationships

One-To-Many: Each value in the primary table field is unique. Each value in the related

table field matches a value in the primary table field, but can appear more

than once in the related field table. In a one-to-many relationship, the

primary table field must be a key field, yet the related field does not have



25

to be a primary key.

One-To-One: Each value in the primary table field is unique. Each value in the related

table field is also unique, both fields must be primary keys.

32

Table Design

1. Create tables in design view.

2. Toggle to the field properties by pressing F6.

Datasheet View

An efficient way to work with more than 1 record on the screen. Use the arrow-head

buttons on the status bar to scroll through records.

Primary Key Field

The primary key is a field or combination of fields that uniquely identify each

record in a table. It speeds retrieval of data from large tables. A primary key field can

not contain duplicate values or null values.

Examples:

a. AutoNumber

b. Single Field – unique value

c. Multiple Field- combination of 2 or more fields.

d. Ex. SS number, employee ID, student ID#

Form Design

The form design window displays labels and fields for the form. The form contains 2

sections, the Form Header and Detail.

Report Design

Report Header

Includes data to be printed at the top of the first page of the report.



26

Page Header

Includes data to be printed at the top of each page of the report.

Detail

Display the fields for the report.

Page Footer

At the bottom of each page of the report.

Report Footer

Data to be printed at the bottom of the last page of the report.

Creating a Database Table

Data Types:

Text:

Maximum length of 255 characters

Number:

Numeric data used in calculations

Date/Time:

Dates and Times

Yes/No:

Fields that will contain either a yes or no entry.

33

Memo

More Tips

1. If there is not a unique field don't let Access primary key.

2. Index Fields sort faster.

3. Open a file by shift-clicking on the filename if you need to get passed a form.

4. Don't turn off the wizard button when using Tools.

Entering Records

1. Tab key or arrow keys to advance from column to column. Shift tab to go

Project backwards.



27

2. After leaving a record or row, data is automatically saved in the table.

3. F2 edit mode

4. Column width can be changed in the datasheet view.

Tables – Design View

Can be used to add, delete or rename fields. Fields can also be moved by clicking the

field’s row selector and dragging the triangular arrow head up or down.

Summary Query

1. Create a query

2. Choose View Totals or click the Totals button

3. Click the Total row of the field you want to summarize

4. On the Total row choose the function

5. Run button

Append Query

1. Create a query that retrieves the records you want to copy into a table

2. Run the query to test it

3. Click the View button to return to Design View

4. Choose Append Query

5. Choose the name of the table that the records will be copied to

6. Append to: If the field names are different use the drop down list and choose the

appropriate field. (Data types must be the same)

7. Run Query

Creating a Form

1. Forms Tab

2. Click on New

3. Choose Form Wizard

4. My favorite is: AutoForm: Columnar 34

5. Tables/Queries drop-down list, choose the first table or query

6. Choose the fields.

Requirement Gathering


28

3. REQUIREMENT GATHERING

In this chapter we first design the UML Diagrams (UNIFIED MODELLING

DIAGRAMS) which gives a brief idea of how the project handled. It mainly

focus on identifying the use cases which are important for any project

UML is the Standard Language for visualizing, specifying, constructing and

Documenting the artifacts of a software-intensive system

Use Case diagrams are the central for modeling the behavior of a system, a

subsystem, or a class.

Class diagram is the most common diagram found in the modeling object oriented

systems

It address the static design view of a system

A Sequence diagrams is the interaction diagram that emphasizes the time ordering

of messages

It is made up of objects and messages

An ERIS has UML diagrams representing the over Use case of the system, User level use

case, sequence diagram.

UML diagrams


29

3.1 UML DIAGRAMS

Use Case of Job Seeker


30

UML diagrams

Use Case Of Job Provider


31

UML diagrams

Use Case of Administrator


32

UML diagrams

Use Case of Outside User


33

UML diagrams

Job Providers Sequence Diagram


34

UML diagrams

Job seekers sequence diagram


35

UML diagrams

Administrator sequence diagram


36

Modeling Requirements through use cases

3.2 Modeling Requirements through use cases Job Providers

Brief Description:This is use case is used to add a new recruiter, modify the details of existing recruiter Flow Of Events:Basic Flow

1. User enters the recruiter details2. If the recruiter information does not exist, a new instance will be created; otherwise the information about the recruiter will be modified

Alternative FlowNone

Special Requirements NonePre Conditions

Recruiter should log on to the systemPost Conditions

If the use case is successful a new recruiter is added or existing recruiter information is modified ore deleted.

Job Seeker

Brief Description: This use case is used to add a new client, modify the details of existing clients

Flow Of Events:Basic Flow1. System asks the client information from the user2. User enters the client details3. If the client information does not exist a new instance will be created; otherwise

the information about the client will be modifiedAlternative FlowNoneSpecial RequirementsNonePre ConditionsJob Seeker should log on to the system.


37


Post ConditionsIf the use case is successful a new client is added or existing clients information is modified.

POST JOB

Brief Description:This describes the jobs available with the clients and their requirements and modify and maintain the information pertaining to the job

Flow Of Events: Basic Flow1. The System asks the user to enter the Job code other related information about the job(like the job title, description etc)2. The user enters the required details about the job3. The system then creates the new job order and stores all the details about it in the databaseAlternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the system

Post ConditionsIf the use case is successful, the new job is added or the existing jobs information is modified and stored in the databaseUPDATE JOB ORDER

Brief Description: This deals with updating job ordersFlow Of Events:Basic Flow1. The system asks the user about information regarding the updations2. The user enters the required details3. The System then updates the details of the existing job orders, if it already exists

in the systemAlternative FlowNoneSpecial RequirementsNone


38


Pre ConditionsUser should log on to the systemPost ConditionsIf the use case is successful, the updation will generated in the database.

SKILL SET

Brief Description:This is used to add skills of the applicants and also helps in its modificationFlow Of Events:Basic Flow

1. The system asks the user to enter the skills of an applicant along with their id and other related details

2. The user enters the required details about the applicant3. The system then add skills of applicant and stores all the details about it in the

databaseAlternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the systemPost Conditions If the use case is successful, the skills of applicant is added and the information is stored in the database

ADD NEW SKILLBrief Description:This is used to add new skills of the existing applicants Flow Of Events:Basic Flow

1. The system asks the user to enter the skills of an applicant along with their id and other related details

2. The user enters the required details about the applicant3. The system then add skills of applicant and stores all the details about it in the

databaseAlternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the systemPost Conditions


39


If the use case is successful, the skills of applicant is added and the information is stored in the database

UPDATE SKILLS

Brief Description:This use case deals with updating skills of existing applicants.Flow Of Events:Basic Flow

1. The system asks the user about information regarding the uploads2. The user enters the required details 3. The system then add skills if it already exists in the system

Alternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the systemPost ConditionsIf the use case is successful, the updation will generated in the database

SEARCH CANDIDATESBrief Description:This is used to search or fetch job Seekers according to a skillsFlow Of Events:Basic Flow

1. The system asks the user to enter the skill for which it wants to perform the search of applicants

2. The user enters the required skill3. The system then displays all the applicants with the skill u entered

Alternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the systemPost ConditionsIf the use case is successful, applicants with the required skill are displayed else it displays the message saying ‘no subjects of said skills’


40


AdministratorThis use case is used to generate reports based on the criteria mentioned by the userFlow Of Events:

Basic Flow1. The system asks the user to select any of the following reports based on their

authorizationsa. Client Reportsb. Application Reportsc. Job Order Reportsd. Skill set Reports

2. The user selects the option3. The system performs the search based on the option selected by the user and

gives the search results in a formatted way as a reportAlternative FlowNoneSpecial RequirementsNonePre ConditionsUser should log on to the systemPost ConditionsIf the use case is successful, the search result is given to the user in a formatted form of a report. Otherwise, the use case terminates.


41

Analysis

4. ANALYSIS

4.1. USER CHARACTERISTICS:

The “ERIS” project meant for consultancy activities to provide environment to

participate in the placement activities of different organizations. This project has to

provide such facilities that it has more user interface and make it cover all the

requirements of people who want to register for job and who want man power in their

organization.

4.2. USER SPECIFICATION OF SYSTEM:

Each user is having a particular USER ID and it is not similar with any other ID even it

his or her is same.

The administrator of the consultancy can access the data of Users. The administrator

maintains the database consisting of tables, which stores the information about various

fields. The user can insert the information needed by the consultancy for the recurtment

process.

4.3. FUNCTIONAL REQUIREMENTS:

The applicant can communicate with the consultancy. This makes the user to post his

resume from the net, as well as easy to search for the job in various companies which are

providing the vacancies and the user can also specify his skills set along with his

resumes. This information will be carried to recruiter to maintain the details of different

applicants to search for the vacancies.


42

Analysis

4.4. PROPOSED SYSTEM:

Enterprise Resource Information System is mainly divided into three modules.

1.job seeker2.job provider3.job search/applicant search4.administrator

Job Seeker:

Applicants : These are the ones who apply for the jobs.the applicant can get registered

and login with his id and password.He can give his details like personal data, skills and

resume. The job seeker has got privlages to update his personal details,educational

details,skill details and aslo can perform job search.

Job Provider:

Job Provider is the one who conducts the tests to the applicants and interviews to the

selected candidates.The recruiter once registered can post job and can give details of job

like job title,description,skills required ,The Job Provider has got privilages to update his

personal details,update job order and can perform resume search.

Job search/applicant search

Here in search we can perform two types of searchs,one is used to search for jobs

available and other is used to search the jobseekers.For performing the Job search by

entering the skills and experience in specified text boxes and the matching jobs with

entered fields will be displayed


43

Design

5. DESIGN

5.1. INPUT DESIGN:

The input design is the link that ties the information System into the real world of its users. The inputs, which are given by the user, will form the core of the processes. So the inputs have to be care fully analyzed and care has to be taken to avoid in correct inputs.

The guidelines that have been followed in designing the input forms are., Minimizing the number of input by collecting only required Data and grouping similar or related data.

Maintain consistently between information display and input.Providing help facilities those are context sensitive.The format of the same data in different screens must be same.Consistent terminology’s are to be used throughout the system.

5.2. OUTPUT DESIGN:

Computer out put is the most important and direct source of information to user. Efficient, intelligible output design should provide user with systems relationships and help in decision making.

The major form of output is hard copy from the printer, printouts are to be designed around the out put requirements of the user. The output devices to be considered depends on factors such as compatibility of the device with the system, response time requirements, expected print quality and number of copies needed.

The output design was carried out in consultation with the user reports, which have many columns, are printed n compressor mode, which can be printed on laser printers and others in uncompressed mode so as to facilitate its usage online printers.


44

Design

5.3 DATABASE DESIGN

Desc Jobprovider details

Name Type

----------------------------------------- -------- ----------------------

Username TEXT (20) (primary key)

Pwd TEXT (20)

Email NUMBER (9)

Company name VARCHAR2 (8)

Contact person TEXT

Com type TEXT

Indus type TEXT

Address TEXT

Mobile TEXT

Desc Jobseekers details

Name Type

----------------------------------------- -------- ----------------------

Username TEXT (20) (primary key)

Pwd TEXT (20)

changePwd TEXT (20)

Email VARCHAR(50)

Country TEXT

Location TEXT

Address TEXT

Mobile TEXT


45

Design

Desc Jobeduc details

Name Type

----------------------------------------- -------- ----------------------

Basicquali TEXT (20)

postgrad TEXT (20)

doctorate TEXT (20)

experiencel VARCHAR(50)

industry TEXT

keyskills TEXT

resumetitle TEXT

uploadresume TEXT

Desc postjob details

Name Type

----------------------------------------- -------- ----------------------

jobcode TEXT (20) (primary key)

jobtitle TEXT (20)

description TEXT (20)

skills VARCHAR(50)

exp TEXT

email TEXT

Desc compose

Name Type

----------------------------------------- -------- ----------------------

to TEXT

from TEXT

subject TEXT

attachfiles TEXT

message TEXT


46

Development

6. DEVELOPMENT

6.1SAMPLE CODE

Inserting Data

Imports System.Data.OleDbImports system.Data.OleDb.OleDbExceptionPartial Class jobseekersRegistration Inherits System.Web.UI.Page Dim con As New OleDbConnection("provider=microsoft.jet.oledb.4.0;data source=c:\erisdatabase.mdb") Dim cmd As New OleDbCommand Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click con.Open() cmd.Connection = con cmd.CommandText = "insert into jsr values('" & TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" & TextBox5.Text & "','" & DropDownList1.SelectedItem.Text & "','" & TextBox6.Text & "'," & TextBox7.Text & ")" cmd.ExecuteNonQuery() Response.Redirect("loginsucc.aspx")

con.Close() End Sub

Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton1.Click Response.Redirect("home.aspx") End SubEnd Class


47

Development

LINK BETWEEN ONE WEB PAGE TO OTHER WEB PAGE

Partial Class home Inherits System.Web.UI.Page

Protected Sub LinkButton2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton2.Click Response.Redirect("searchjobs.aspx") End Sub

Protected Sub LinkButton4_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton4.Click Response.Redirect("jobseekerslogin.aspx") End Sub

Protected Sub LinkButton5_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton5.Click Response.Redirect("jobproviderlogin.aspx") End Sub

Protected Sub LinkButton6_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton6.Click Response.Redirect("adminstratorlogin.aspx") End Sub

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

End Sub

Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton1.Click

End Sub

Protected Sub LinkButton3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton3.Click Response.Redirect("contact.aspx") End SubEnd Class


48

Development

SEARCH ENGINE CODE

Imports System.Data.OleDbPartial Class searchjobs Inherits System.Web.UI.Page Dim con As New OleDbConnection("provider=microsoft.jet.oledb.4.0;data source=c:\erisdatabase.mdb") Dim cmd As New OleDbCommand()

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click con.Open() cmd.Connection = con cmd.CommandText = "select jobcode,jobtitle,description,exp,email from postjob where skills='" & TextBox1.Text & "' " Dim dr As OleDbDataReader dr = cmd.ExecuteReader Label2.Text = " " If dr.HasRows Then If GridView1.Visible = False Then GridView1.Visible = True GridView1.DataSource = dr GridView1.DataBind() Else Label2.Text = "No jobs are found " GridView1.Visible = False End If con.Close() End Sub

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

End Sub

Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton1.Click Response.Redirect("home.aspx") End SubEnd Class


49

Development

FOR DELETING THE DATA

Imports System.Data.OleDbPartial Class Default14Inherits System.Web.UI.PageDim varun As New OleDbConnection("provider=microsoft.jet.oledb.4.0;datasource=e:\enterprise.mdb")Dim varun1 As New OleDbCommand()Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)Handles Button1.Clickenterprise.Open()enterprise.Connection = enterpriseenterprise.CommandText = "delect from jpdetails values('" & TextBox1.Text& "','" & TextBox2.Text & "','" & TextBox3.Text & "'," & TextBox4.Text & ",'" &TextBox5.Text & "','" & TextBox6.Text & "','" & TextBox7.Text & "'," & TextBox8.Text& ",'" & TextBox9.Text & "'," & TextBox10.Text & ")"enterprise.ExecuteNonQuery()MsgBox("Delection is Ok")varun.Close()TextBox1.Text = " "TextBox2.Text = " "TextBox3.Text = " "TextBox4.Text = " "TextBox5.Text = " "TextBox6.Text = " "TextBox7.Text = " "TextBox8.Text = " "TextBox9.Text = " "TextBox10.Text = " "End SubEnd Class


50

Testing

7. TESTING

TEST PLAN

The importance of software testing and its implications cannot be overemphasized.

Software testing is a critical element of Software Quality Assurance and represents the

ultimate review of the specifications, design and coding.

TESTING OBJECTIVES:

The main objective of testing is to uncover a host of errors, systematically and with

minimum effort and time. Stating formally, we can say,

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

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it exists.

But there is one thing that testing cannot do (just to quote a very famous sentence)

“Testing cannot show the absence of defects, it can only show that software defects are

presents.”

As the test results are gathered and evaluated they begin to give a qualitative indication of

the reliability of the software. If severe errors are detected, the overall quality of the

software is a natural suspect. If, on the other hand, all the errors, which are encountered,

are easily modifiable, then one of the two conclusions can be made:


51

Testing

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable standards.

For the purpose of the current project we are assuming that in the event that errors

that are easily modifiable points to the latter possibility, since repeating the entire testing

routine can be very time consuming. What we propose to do instead is to get it tested by

one or more persons who are not a part of the development team but is well versed with

the subject and with the concept of software testing (alpha testing). If he can detect no

serious errors, it will enable us to state with more confidence that the software does

actually conform to the expected standards.

TESTING STRATEGY:

A testing strategy is a roadway, giving there how-to conducting a test. Our testing

strategy is flexible enough to promote customization that may be necessary in due course

of development process. For instance during coding we find that a change in design (E.g.

Z de normalized table makes certain query easy to process), we maintain a change log

and refer to it at appropriate time during the testing. Software can be tested in one of the

following ways:

Knowing the specific functions that the Software is expected to perform, tests can

be conducted to perform that all functions are fully operational.

Knowing the internal workings of the product, tests can be conducted to show that

internal operations of the system perform according to the specifications and all

internal components are adequately exercised.


52

Testing

The first approach is what is known as Black box testing and the second is called White

box testing. We will be using a mixed approach, more popularly known as sandwich

testing. We apply white box testing techniques to ascertain the functionalities top-down

and then we use black box testing to demonstrate that everything runs as expected.

7.1 UNIT TESTING:

Unit testing focuses verification effort on the smallest unit of software i.e. the module.

Using the detailed design and the process specifications testing is done to uncover errors

within the boundary of the module. All nodules must be successful in the unit test before

the start of the integrat6ion testing begins.

7.2 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while

conducting tests at the same time to uncover errors associated with interfacing. We have

used incremental integration testing for this project.

7.3 VALIDATION TESTING

At the culmination of integration testing the software is complete as a package and the

interfacing errors have been uncovered and fixed, final tests- validation testing- may

begin. Validation tests succeed when the software performs exactly in the manner as

expected by the user.

Software validation is done by a series of Black box tests that demonstrate the

conformance with requirements. Alpha and bets testing fall in this category. We will not

do beta testing but alpha testing will certainly will certainly be done.


53

Testing

7.4 TEST CASE DESIGN

The techniques that are used in deriving the test cases are explained below.

7.5 CONDITION TESTING

Condition Testing is a test case design method that exercises the logical conditions

contained in the program. The possible components in a condition statement are : a

Boolean operator, a Boolean variable, a relational operator, arithmetic expression and

parenthesis around simple or compound conditions. The condition testing method focuses

on testing each condition in the program.

It has two advantages over the pure white box testing:

Measurement of test coverage is straightforward.

The test coverage of conditions in a program provides guidance for generation of

additional tests for the program.

We have used a special condition testing method called the Domain Testing

where the condition in a form lie E1 < Relational Operator> E2 will the tested for

three conditions E1 > E2, E1 equal to E2 and E1 les than E2.

BOUNDARY VALUE ANALYSIS:

Boundary value analysis leads to a selection of test cases that exercise the boundary

conditions or bounding values. It has been observed that a large number of errors tend to

appear at the boundaries of the input domain than in the center. The guidelines for

developing the test cases in BVA are given below:


54

Testing

If the input condition has a low and high range then tests should be done at the

low and high boundaries. Values above and below these extremes should be

tested.

Apply the same principle to output conditions. E.g.: Test cases should be designed

to generate the maximum and minimum no of entries in a report that is generated

by the program.

EQUIVALENCE PARTITIONING:

Equivalence partitioning is a black box testing method that divides the input domain of a

program into classes of data from which test cases can be derived. A typical test case

uncovers a class of errors that might otherwise require many more test cases before the

error is observed.

Equivalence classes for input determine the valid and invalid inputs for the program.

Equivalence class test cases are generated using the following guidelines:

If an input class specifies a range then one valid and two invalid equivalence

classes are defined.

If an input class specifies a value then one valid and one invalid equivalence


If an input class specifies a member of a set then one valid and one invalid

equivalence classes are defined.


55

If an input class specifies a Boolean then one valid and two invalid equivalence


Test cases should be selected so that the largest number of attributes of an equivalence

class is exercised at once.


56

Sample Screens

8. SAMPLE SCREENS

HOME PAGE


57

Sample Screens

SEARCH PAGE


58

Sample Screens

JOBSEEKERS LOGIN PAGE


59

Sample Screens

JOBSEEKERS REGISTRATION


60

Sample Screens

JOB SEEKERS HOMEPAGE


61

Sample Screens

POST RESUME


62

Sample Screens

JOB PROVIDERS REGISTRATION


63

Sample Screens

JOB PROVIDERS LOGIN


64

Sample Screens

ADMINISTRATOR PAGE


65

Sample Screens

JOB PROVIDERS HOMEPAGE


66

Sample Screens

POST A JOB PAGE


67

Sample Screens

UPDATE JOB


68

Sample Screens

SEARCH PAGE


69

Sample Screens

SEARCH JOB


70

Sample Screens

UPDATE DETAILS PAGE


71

Sample Screens

CONTACT PAGE


72

Sample Screens

JOBSEEKERS DETAILS


73

Sample Screens

RESUMES POSTED


74

Conclusion

9.CONCLUSION

The task given to us performed by keeping in mind the goals we have to achieve, these

are to provide user-friendliness. This project ERIS is mainly useful for software

consultants.

The ERIS is excepted to function as per the requirements and we expect that it will

satisfy the users. Working on such a project in the organization provided the professional

attitude and fuel needed to prepare for further hobs. The encounter with real life

professionals will surely pave the way towards a more successful illustrious career.


75

Future Scope

10. FUTURE SCOPE OF THE PROJECT

The current system is susceptible to handle the situation that, even the organization grows

and establishes various branches at various places in the world.

The Database maintained here grows, as time passes by thus it has to be cleaned up in

frequent intervals so as to save memory. There are no special provisions designed in the

system. If the user wants an option of backing of data in frequent intervals, it could be

added to the present system.

The information of the Employee's working in the organization, like payroll

(remuneration's), details of their work, are not incorporated in the system as it does not

fall under the scope of this project. If Payroll management is to be included it can be

easily coupled with the present modules.

Frequently enough the system should be reviewed for updating as we know that

maintenance is rather difficult than developing a system so there should be proper

feedback about the usefulness of the system, otherwise the basic purpose of automation

would not achieved.


76

BIBLIOGRAPHY

Database Management System by Henry F.Korth Abraham Silberschatz

Software Engineering by --Presily

An Introduction

To Database Systems by --C J Date

System Analysis and Design by --James Senn

Software Engineering,

A Practitioner’s approach by --Roger.S.Pressman

Database Management by --George Diehr

Fundamentals of Database Systems by --Elmasri Navathe

System Analysis And Design by --Elias M.Awad

An Integrated Approach

To software Engineering by --Pankaj Jalote

Microsoft Developer Network-MSDN library.

Software Engineering by -- Bernd Bruegge and Allen

H.Dutoit.

ASP.Net Programming by -- Steven Holtzner.

System Analysis And Design by --Lee

MS-SQL Server 2000 online reference

MSDN 2003

www.microsort.com


77

theoretical background of the project

Documents

encapsulate common functionality

modified alternative flow

pre conditions user

black box testing

common language runtime

invalid equivalence classes

input class specifies

highly distributed environment