5 job adda doc 2

CHAPTER I

INTRODUCTION

1.1 Overview

This project is aimed at developing an online search Portal for the Placement Details

for job seekers. The system is an online application that can be accessed throughout the

organization and outside as well with proper login provided. This system can be used as an

Online Job Portal for job seekers. Job Seekers logging should be able to upload their

information in the form of a CV. Visitors/Company representatives logging in may also

access/search any information put up by Job aspirants.

1.2 Purpose

This system can be used as an Online Job Portal for the Placements providing to the

unemployed who are seeking for a job placement. Job Seeker logging into the system and

he can should be able to upload their information in the form of a CV. Visitors/Company

representatives logging in may also access/search any information put up by Job Seeker.

The purpose of designing the online job portal is to give the job seekers a platform for

finding a right and a satisfactory job according to their qualification. It also connects the

job seekers with the major agencies.

It also provides Jobs portal for Job Seekers to submit their CV and apply for job

posting and Employer can select best Employees from Available CV based on their

payment option selection. This is basically a Job portal where job Seeker applies for jobs

and employer post jobs and select prospective applicant.

1.3 Objectives

The objective of the application is to develop a system using which job applicants and

recruiters can communicate with each other. An Online Job Portal is an application where

the job seekers can register themselves at the website and search jobs which are suitable

for them where as the employers register with the website and put up jobs which are vacant

at their company.

1 | P a g e

The Online Job Portal System is a package to be used by agencies to improve the

efficiency of business. The Online Job Portal System to be developed benefits greatly the

members. The system provides jobs catalogue and information to members and helps them

decide on the jobs to apply. The Admin and employers can keep the jobs catalogue updated

all the time so that the Job seekers get the updated information all the time.

The Objective of the system can be as follows:-

Maintain Job Seeker and Employer records

Maintain uploaded Resumes

Provide Customized Job Postings

Maintain Job Posting details and generate various reports

To help the client in retrieving the information fastly.

To develop a user friendly project.

1.4 Project Significance

Job portal is prepared for provide all categories of job and help to get various type of

job. The main purpose of job portal is to provide the facility to job seekers for getting the

quick job.So; it enables applicants to search for jobs in a convenient manner and to enable

employers to find suitable candidates.

1.5 Limitations

There is no any online Payment gateway provided in this portal. So, any company which would register would not be able to pay online. Payment would be done by check/case.

There are no banners for advertisement on the site.

This system can run only on Windows platform.

Supported only in My SQL database.

No security of data.

No N-level category.

Supportive language is only English.

2 | P a g e

CHAPTER II

REVIEW AND METHODOLOGY

2.1 Introduction

This chapter defines facts and finding on Job Portal after read some articles, books,

websites or journals that are related to the system, decide, describe methodology that are

used to develop the system, state out project requirements, explain action plan prior to the

end of the project and attach Gantt chart.

2.2 Facts and Finding on Job Portal

In this section, all the information related to the online job portal system can be

found by surfing the Internet and go to the library. Literature review is done and findings

are come out after read through all the information. This section discusses about the

research that have been done for this courseware. The research includes the entire

information that is related on the system proposed which focused on the research of e-

management system. E-management is a quite big field to do research.

2.3 Existing System

The existing system is doing all the processes manually. The personnel should refer

all the records kept for years ago to simply know details. This so tedious and time

consuming. This process is so difficult when the number of users increases.

2.3.1 Drawbacks of Existing System

There are a lot of limitations for the existing systems

Time consuming

Not accurate

Error prone

Large amounts of records are to be kept

3 | P a g e

Complicated procedure

May not complete in time

Paper work is very tedious

Report production is very slow

All the registers are kept for a long period

Searching for a file or record is very difficult

Due to all this reasons we are moving for the proposed system.

2.4 Proposed System

The proposed system is a web based application which allows applicants and

employers to register their details. Applicants can browse through the vacancy details that

are posted and can apply for the jobs online. Employers can browse through the posted

resumes and select suitable candidates.

2.4.1 Advantages of proposed system

The proposed system is intended to avoid all the drawbacks of existing system. It will

add some more features than the existing system. The proposed system is a cost effective

way of doing the manual processes done in the existing system. This helps the organization

to win the war in the existing competitive world. The proposed system is intended to do the

following:

Enable to meet challenges

Prepare and produce accurate outputs

Reduce the time needed

Reduce the expenses

Make information flow efficient

Easy report generation

Attractive user interface.

2.5 Research

4 | P a g e

Communicated Requirements

Requirements Specification

Design Specification

Executable Software Modules

Integrated Software Product

Delivered Software Product

Changed Requirements

Requirements Engineering

Design

Programming

Integration

Delivery

Maintenance

Product Product

Input Output

Process

A useful fact and finding is to research the application and problem. Computer

trade journals, reference books and the Internet are good sources of information. They can

provide information on how others have solved similar problems, plus can learn whether or

not software packages exist to solve the problem.

2.6 Project Methodology

The project methodology that used in the development of the system is the System

Development Life Cycle (SDLC). SDLC is the process of understanding how an

Information System (IS) can support business needs, designing the system, building it and

delivering it to users. The SDLC is composing of four phases:

Figure 1-The Waterfall Development Methodology

5 | P a g e

The approach that used in the system development methodology is the Iterated Waterfall

Design. This is the implementation of SDLC step by step into the system development

methodology.

Planning-In planning phase, to develop a new system which is a first step is to identify

need for the "Job Portal", and also plan how to develop the functional requirements of a

system. This will include determining whether a business problem or opportunity exists,

conducting a feasibility study to determine the developing a project plan.

Analysis-In this phase, analysis of the current systems and investigates any problems

associated with it is found. Other sources of information about system and the new

requirements would also be investigated at this time. The output from this stage would

probably be no more than a set of notes.

Design-After the requirements have been determined, the necessary specifications for the

hardware, software, people, and data resources, and the information products that will

satisfy the requirements of the proposed system can be determined. The design will serve

as a blueprint for the system and helps detect problems before these errors or problems are

built into the final system

Implementation-The implementation phase is described as those activities that begin

when the system design has been completed. Coding and debugging is the act of creating

the final system.

System-Last phase is system which is when development is complete and the system is in

daily use. It is the longest life-cycle phase. System involves correcting errors which were

not discovered in earlier stages of life cycle; improving the implementation of system units

and enhancing the Bus Ticket Reservation System services as new requirement are

discovered

6 | P a g e

CHAPTER III

REQUIREMENT ANALYSIS

3.1 Introduction

This chapter aims to describe the problem analysis for the existing system and the

requirement analysis for the purpose system, Job Portal. This chapter is about analysis

phase. Analysis phase is the step that is concern with first studying the existing system,

then using the information gathered to define the requirements for a new system. There are

many fact-gathering techniques that can use in gathering the information such as interview,

observation, questionnaires and other method. Analysis follows the problem recognition

and feasibility phases and must be completed before the design phase can begin.

System analysis is a detailed study of various operation performed by a system and

the relationship within and outside of the system. One aspect of analysis is defining the

boundaries of a system and determining whether or not a candidate system should consider

other related system. Analysis begins when a user or manager begins a study of the

programs using an existing system.

During analysis data is collected on the various files, decision points and

transactions handled by the present systems. This means that to do system works, one is to

understand the system concepts and how the organizations operate as a system and the

design appropriate computer based system and that will make the organization

requirements. It is actually customized approach to the use of computer problem solving.

Analysis can be defined as the separation of a substance into parts for study an

interpretation, detailed examination. System development revolves around a life cycle that

being with the recognition of user names. The critical phase of managing system project is

planning. To launch a system investigation, we need a master plan detailing steps taken,

the people to be questioned and outcome expected. System analysis can be categorized into

four parts:

System planning and initial investigation

Information gathering

Analyzing tools for structured analysis

Feasibility study

Cost Benefit Analysis

7 | P a g e

System study or system analysis is the first among the four life cycle phases of a

system. System analysis begins when a user or manager request a studying of a program in

either an existing system or a project one. It involves studying the base of the organization

currently operating, retrieving and processing data to produce information with goal of

determining how to make it work better. System analysis itself breaks down into stages

preliminary and detailed. During preliminary analysis, the analyst and the user list the

objectives of the system. To arrive at a preliminary report, the analyst interviews key

personnel in the organization and scheduling meetings with the users and management.

The objective of analysis phase of the system analysis and design exercise is the

establishment of the requirement for the system to be acquired, developed and installed. In

brief analysis of the system helps an analyst to make a clear view of an existing system and

thereby give suggestions for the improvement of the new system information about the

organizations, policies, goals, objectives and structure explains the kind of environment

that promotes the introduction of the computer based system. It is necessary that the

analyst must be familiar with the objectives, activities and functions of the organizations.

3.2 Problem Analysis

Problem analysis will be discussed in term of background of current system and problem

statements.

3.2.1 Principles of System Analysis:

Understand the problem before you begin to create the analysis model.

Develop prototypes that enable a user to understand how human machine

interaction will occur.

Record the origin of and the reason for every requirement.

Use multiple views of requirements like building data, function and behavioral

models.

Work to eliminate ambiguity

System Analysis is a separation of a substance into parts for study and their

implementation and detailed examination.

8 | P a g e

Before designing any system it is important that the nature of the business and the

way it currently operates are clearly understood. The detailed examination provides the

specific data required during designing in order to ensure that all the client's requirements

are fulfilled. The investigation or the study conducted during the analysis phase is largely

based on the feasibility study. Rather it would not be wrong to say that the analysis and

feasibility phases overlap. High-level analysis begins during the feasibility study.

Though analysis is represented as one phase of the system development life cycle

(SDLC), this is not true. Analysis begins with system initialization and continues until its

maintenance. Even after successful implementation of the system, analysis may play its

role for periodic maintenance and up gradation of the system. One of the main causes of

project failures is inadequate understanding, and one of the main causes of inadequate

understanding of the requirements is the poor planning of system analysis.

3.3 Feasibility Study

Once you define a problem you have to analyze whether this is feasible or not,

because all possible solutions are not feasible and feasible one is not always possible. The

detailed studies carried out to check the work ability of proposed system. A feasibility

study is a test of system proposal regarding to its work ability, impact on the organization

ability to meet user needs an effective use of resources. Thus when a new application is

proposed it normally goes through a feasibility study before it is approved for deployment.

Thus during feasibility analysis for this project, following primary areas of interest

are to be considered. Investigating the existing system in the area under investigation and

generating ideas about a new system does this :

1. Economic Feasibility: An evaluation of development cost weighed against the

ultimate income of benefit derived from the development system of product. In

economic feasibility, cost benefit analysis is done in which expected cost and

benefits are evaluated.

2. Technical Feasibility: The technical issue usually raised during the feasibility

stage of the investigation includes the following:

9 | P a g e

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required

to use the new system?

Will the proposed system provide adequate response to inquiries, regardless of

the number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data

security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure

Implementation System’. The current system developed is technically feasible.

Thus it provides an easy access to the users. The database’s purpose is to create,

establish and maintain a workflow among various entities in order to facilitate all

concerned users in their various capacities or roles.

Permission to the users would be granted based on the roles specified.

Therefore, it provides the technical guarantee of accuracy, reliability and security.

The work for the project is done with the current equipment and existing software

technology. Necessary bandwidth exists for providing a fast feedback to the users

irrespective of the number of users using the system.

3. Operational Feasibility: Operational feasibility is mainly concerned with issues

like whether the system will be used if it is developed and implemented. Whether

there will be resistance from users that will affect the possible application benefits?

The essential questions that help in testing the technical feasibility of a system are

following:

Does management support the project?

Are the users not happy with current business practices? Will it reduce the time

considerably? If yes, then they will welcome the change and the new system.

Have the users involved in the planning and development of the project? Early

involvement reduced the probability of resistance towards the new system.

Will the proposed system really benefit the organization? Does the overall response

increase? Will accessibility of information be lost? Will the system affect the

customers in considerable way?

10 | P a g e

4. Legal Feasibility: A determination of any infringement, violation, or liability that

could result from development of the system. Legal feasibility tells that the

software used in the project should be original purchased from the legal authorities

and they have the license to use it or the software are pirated.

3.4 Object Oriented Analysis

Object-oriented analysis and design (OOAD) is a software engineering approach

that models a system as a group of interacting objects. Each object represents some entity

of interest in the system being modeled, and is characterized by its class, its state (data

elements), and its behavior. Various models can be created to show the static structure,

dynamic behavior, and run-time deployment of these collaborating objects. There are a

number of different notations for representing these models, such as the Unified Modeling

Language (UML).

Object-oriented analysis (OOA) applies object-modelling techniques to analyze the

functional requirements for a system. Object-oriented design (OOD) elaborates the

analysis models to produce implementation specifications. OOA focuses on what the

system does, OOD on how the system does it.

An object-oriented system is composed of objects. The behavior of the system

results from the collaboration of those objects. Collaboration between objects involves

them sending messages to each other. Sending a message differs from calling a function in

that when a target object receives a message, it itself decides what function to carry out to

service that message. The same message may be implemented by many different functions,

the one selected depending on the state of the target object.

The implementation of "message sending" varies depending on the architecture of

the system being modeled, and the location of the objects being communicated with.

3.5 Architectural Specification

Three tier architecture, also referred to as multi tier architecture as the middle tier

may consists of several tiers by itself, emerged in 1990’s to overcome the limitations of the

two tier architecture.

11 | P a g e

The third tier architecture is between the user and the interface run on client and the

database management system run on the server. This middle tier provides process

management where business logic and rules are executed and can accommodate hundreds

of users, as compared to two tiered architecture. This architecture is the evolution of two

tier applications. Logically the application is divided into three constituent layers:

User services:

Presentation layer: provides services such as the graphical user interface and other

automation task that the application has to perform.

Business services:

Business layer: implements business rules. This layer encapsulates the business

logic from user such that they need not know how business logic is applied. When project

is upgraded only the business layer is affected and must be upgraded, the rest of

application services can remain untouched.

Data services:

Data layer: provides data availability and integrity. It is responsible for adding

modifying and deleting data from database.

The middle tier is basically application code, which a user invokes via the

presentation layer to validate/insert/update/delete and retrieve business data from viewing.

The presentation layer then receives the data and formats it for display. The separation of

application logic from the user interface adds enormous flexibility to the design of an

application.

The thid tier contains the business data required by the application. This business

data can be held within an enterprise database such as SQL Server or a set of XML

documents i.e. data that has been stored in a well formed document conforming to XML

specifications.

12 | P a g e

3.6 Input Design

The input design is the link that ties information system into the world of its users.

Input design consist of developing specific procedures for data preparation, steps necessary

to put the transaction data in the form that is usable for computer processing. Main

objectives that guides in the input design stages are:

Controlling the amount of Inputs

Avoiding inordinate delay

Controlling errors

The accuracy of the output depends on the accuracy of the input and its processing.

Thus, for this proposed system, the input design is in the format of web pages for the user

in format of form for the administrator.

Validation checks are to be built in the system to avoid any error entries from the users.

Hence the input design is the process of converting user-oriented inputs to a computer

based format. So, input interface design takes an important role in controlling the errors

Customized messages are given in place of system messages, while the data

manipulation is being carried out. There for, the input interface design should be made in

such a way that it can be easily understandable to the user by using meaningful and

appropriate words.

3.7 Output Design

Computer output is the most important and direct source of information to the

administrator. Efficient, intelligible output design should improve the systems relationship

with the appraisal. A major form output, reports, is a hard copy from printer. When

designing output, system analyst must accomplish the following.

Determine what information should be present

Decide whether to display, print the information and select the output medium

Arrange the presentation of information in an acceptable format

Decide how to distributes the outputs

13 | P a g e

3.8 Database Design

Database is designed to manage large bodies of information. The management of data

involves both the definitions of structures for the storage of information. In addition the

data base system must provide for the safety of the information solved, despite system

crashes or due to attempts at unauthorized access. For developing an efficient database we

have to fulfill certain conditions such as controlled redundancy.

Defining the data

Inputting the data

Locating the data

Accessing the data

Communicating the data

Revising the data

3.8.1 Objectives of Database design

In this data base design several objectives are designed such as :

Ease of use

Control of data integrity

Control of redundancy

Control of security

Data independence (logical & physical)

3.9 Software & Hardware Requirements:

HARDWARE

Processor : Pentium 2.4 GHz or above

Memory : 256 MB RAM or above

Cache Memory : 128 KB or above

Hard Disk : 3 GB or above [at least 3 MB free space required]

14 | P a g e

SOFTWARE

Operating System : Windows XP (Professional).

Font-End Tool : Visual Studio 2010 (Professional).

Back-End : Sql Server 2008 Express

3.10 Software Descriptions

Introduction to .NET Framework

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

15 | P a g e

ensure security and robustness. The class library, the other main component of the .NET

Framework, is 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.

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.

3.11. ASP.NET

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

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

16 | P a g e

ASP.NET as the 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.

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.

If you develop and publish your own XML Web service, the .NET Framework

provides a set of classes that conform to all the underlying communication standards, such

as SOAP, WSDL, and XML. Using those classes enables you to focus on the logic of your

service, without concerning yourself with the communications infrastructure required by

distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web

service will run with the speed of native machine language using the scalable

communication of IIS.

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

World-Class Tool Support

Power and Flexibility

Simplicity

Manageability

Scalability and Availability

Customizability and Extensibility

Security

17 | P a g e

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.

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).

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.

18 | P a g e

Introduction to asp.net server controls

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.

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.

3.12. C#.NET

3.12.1. 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.

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 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

19 | P a g e

(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).

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

3.13. Sql server

A database management, or DBMS, gives the user access to their data and helps

them transform the data into information. Such database management systems include

dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create,

update and extract information from their database.

SQL Server stores each data item in its own fields. In SQL Server, the fields

relating to a particular person, thing or event are bundled together to form a single

complete unit of data, called a record (it can also be referred to as raw or an occurrence).

Each record is made up of a number of fields. No two fields in a record can have the same

field name..

3.13.1. Advantages of RDBMS

Redundancy can be avoided

Inconsistency can be eliminated

Data can be Shared

Standards can be enforced

Security restrictions ca be applied

20 | P a g e

Integrity can be maintained

Conflicting requirements can be balanced

Data independence can be achieved.

3.13.2. Disadvantages of DBMS

A significant disadvantage of the DBMS system is cost. In addition to the cost of

purchasing of developing the software, the hardware has to be upgraded to allow for the

extensive programs and the workspace required for their execution and storage. While

centralization reduces duplication, the lack of duplication requires that the database be

adequately backed up so that in case of failure the data can be recovered.

3.13.3. Features of sql server (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS)

because it is the only Database that meets the uncompromising requirements of today’s

most demanding information systems. From complex decision support systems (DSS) to

the most rigorous online transaction processing (OLTP) application, even application that

require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the

industry in both performance and capability

SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched

performance, continuous operation and support for every database.

SQL SERVER with transactions processing option offers two features which contribute to

very high level of transaction processing throughput, which are:

The row level lock manager

Enterprise wide data sharing

Portability

Open systems

Distributed data sharing

Unmatched performance

Sophisticated concurrency control

21 | P a g e

CHAPTER IV

SYSTEM DESIGN

4.1 Introduction

The design document that we will develop during this phase is the blueprint of the

software. It describes how the solution to the customer problem is to be built. Since

solution to complex problems isn’t usually found in the first try, iterations are most likely

required. This is true for software design as well. For this reason, any design strategy,

design method, or design language must be flexible and must easily accommodate changes

due to iterations in the design. Any technique or design needs to support and guide the

partitioning process in such a way that the resulting sub-problems are as independent as

possible from each other and can be combined easily for the solution to the overall

problem. Sub-problem independence and easy combination of their solutions reduces the

complexity of the problem.

4.2 Modules

Below are the different modules used in the project. It contains different features a

particular module support. All these modules are independently developed and are

integrated later. Administrator roles are developed after all the forms are developed so that

back end word can be seen easily various modules used are:

There are following modules in the systems:

Job Seeker Module

Employer Module

Administration Module

The application comprises the following major modules:

4.2.1. Job Seeker Module

This module provides functionalities for job seekers. Applicants can post their resumes

with personal and professional details. They can also update the resume as frequently as

22 | P a g e

required. The applicant can also browse through the present vacancies available. Job

seekers can also get mail alerts when their resumes are selected by employers.

4.2.2. Employer Module

This module provides functionalities related to employers. Employers can post vacancy

details and update the details as and when necessary. Employers can search through

applicant resumes based on different criteria.

4.2.3. Administration Module:

This module provides administrator related functionalities. Administrator manages entire

application and maintains the profiles of applicants and employers.

4.3 Context diagram

The highest level data flow diagram is the context diagram.

• The context diagram shows the interaction of the system with its environment in terms

of data flows

• The context diagram defines the boundary of the system (the scope of the system)

• Only the data flows which leave the system and the data flows which come from

outside the system are shown.

23 | P a g e

Figure 2-Context Diagram

24 | P a g e

4.4 Sequence Diagram

Sequence diagram is an interaction diagram that shows how processes operate with one

another and what is their order. It is a construct of a Message Sequence Chart. A sequence

diagram shows object interactions arranged in time sequence. It depicts the objects and

classes involved in the scenario and the sequence of messages exchanged between the

objects needed to carry out the functionality of the scenario. Sequence diagrams are

typically associated with use of case realizations in the logical view of the system under

development. Sequence diagrams are sometimes called event diagrams o event scenarios.

Admin Login Bal : AdminLogin Dal : SqlHelper DataBase

1 : Login()

2 : CheckUser()

3 : Execute NonQuery()

4 : Exeute NonQuery()

5 : Response to ExecuteNonQuery()

6 : Get Response()

7 : Show Result()

Figure 3-Sequence Diagram for Admin

25 | P a g e

J obSeeker Update J obseeker Profile BAL : clsUpdateJ obSeekerProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()

3 : ExecuteNonQuery()


5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

Figure 4-Sequence Diagram for Jobseeker

J obRecuriter Update J obRecuriter Profile BAL : clsJ obrecuriterProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()



5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

Figure 5-Sequence Diagram for Recruiter

26 | P a g e

4.5 Data Flow Diagrams (DFD)

Data flow diagram is a graphical technique that depicts information flow and

transforms that are applied as data move from input to output. The DFD is also known

as Data Flow Graphs or Bubble Chart. The DFD is used to represent increasing

information flow and functional details. Also DFD can be states as the starting point of

the design phase that functionally decomposes the requirements specifications down to

the lowest level of detail.

A level zero also called the fundamental system model or a context level DFD that

represent the entire software elements as a single bubble with input and output data

indicated by incoming and outgoing arrows, respectively. Additional process and

information flow parts are represented in the next level, i.e., level 1 DFD. Each of the

processes represented at level 1 are sub functions of overall system depicted in the

context model. Any processes that at\re complex in level 1 will be further represented

into sub functions in the next level, i.e., level 2.

Data Flow Diagram is a means of representing a system at any level of detail with a

graphic network of symbols showing data flows, data stores, data processes and data

sources. The purpose of data flow diagram is to provide a semantic bridge between

users and system developers. The diagram is the basis of structured system analysis. A

DFD describes what data flows rather than how they are processed, so it does not

depend on hardware, software, data structure or file organization.

4.5.1 Components of Data Flow Diagram

There are four symbols that are used in the drawing of data flow diagrams

Entities

External entities represent the sources of data that enter the system or the recipients

of data that leave the system

27 | P a g e

Process

Processes represent activities in which data is manipulated by being stored or retrieved or

transformed in some way. A circle represents it. The process will show the data

transformation or change.

Database

Databases represent storage of data within the system

Data Flow

A data flow shows a flow of information from its source to its destination. A line

represents a data flow, with arrow heads showing the direction of flow.

4.5.2. Silent features of DFD’s

1. The DFD shows flow of data, not of control loops and decision are controlled

considerations do not appear on a DFD.

2. The DFD does not indicate the time factor involved in any process whether the

dataflow take place daily, weekly, monthly or yearly.

28 | P a g e

3. The sequence of events is not brought out on the DFD.

LEVEL 0 DFD:

The level zero data flow diagram is the diagram at the level immediately below

the context diagram.

It "expands" the single process on the context diagram to show the major, high-

level processes (or functions) within the system

Figure 6-Level 0 DFD

29 | P a g e

LEVEL: 1 DFD


30 | P a g e

LEVEL: 2 DFD


31 | P a g e

4.6 ER Diagram

Peter Chen originally proposed Entity- Relationship Diagram (ERD) for the design of

relational data base system. The E-R Database model is based on a perception of real world

that consist of a set of basic objects called entities and relationships among these objects.

Sets of primary components identified for the ERD ; Data objects, attributes, relationships

and various type indicators. The ERD enables us to identify data entity and relationships

using a graphical notation. This model consist of three interrelated pieces of information.

Entity (Data Object)

A Data Object is a representation of any composite information that must be understood by

software

Attributes

It defines the properties of an entity and takes on one of three different characteristics.

They can be used to name an instance of the data object, describe the instance and make

references to another instance in another table.

Relationships

Entities are connected to one another in a variety of different ways

Cardinality

Modality

An entity–relationship model (ER model) is a data model for describing the data or

information aspects of a business domain or its process requirements, in an abstract way

that lends itself to ultimately being implemented in a database such as a relational

database. The main components of ER models are entities (things) and the relationships

that can exist among them, and databases. An entity may be defined as a thing capable of

an independent existence that can be uniquely identified. An entity is an abstraction from

the complexities of a domain. When we speak of an entity, we normally speak of some

aspect of the real world that can be distinguished from other aspects of the real world.

32 | P a g e

http://en.wikipedia.org/wiki/Entity

http://en.wikipedia.org/wiki/Entities

http://en.wikipedia.org/wiki/Relational_database

http://en.wikipedia.org/wiki/Relational_database

http://en.wikipedia.org/wiki/Database

http://en.wikipedia.org/wiki/Data_modeling

Figure 9- E-R diagram of job portal

33 | P a g e

4.7 Tables

1. Login

Field name Data type Constraint Description

Username char(20) Primary key Name of user

Password varchar2(12) - Password of user

Role char(10) - Admin/ HR /Candidate

2. Candidate_basic


candidate_id Number Primary key ID of Candidate

Username char(15) Foreign key Username

que_id Number Foreign key ID of Question

Ans varchar2(15) - Answer

profile_date Date - Date of Profile

first_name char(15) - First name of user

middle_name char(15) - Middle name of user

last_name char(15) - Last name of user

Gender char(6) - Gender

Dob Date - Date of birth

contact_no number(15) - Contact no

email_id varchar2(30) - Email ID

profile_status char(5) - Active / Inactive

3. Candidate education



perc11 number(4,2) - 11th Percentage

34 | P a g e

perc12 number(4,2) - 12th Percentage

graduation varchar2(10) - Graduation

institute_grad varchar2(25) - Institute of Graduation

perc_grad number(4,2) - Graduation %

post_grad varchar2(10) - Post-graduation

institute_post_grad varchar2(25) - Institute of Post-grad

perc_post_grad number(4,2) - Post-graduation %

dr_phd varchar2(10) - Doctorate / PhD

institute_dr_phd varchar2(25) - Dr. / PhD Institute

perc_dr_phd number(4,2) - Dr. / PhD %

certification varchar2(10) - Certification Course

4. Candidate professional



candidate_prof_id Number - ID of Professional

area_id Number Foreign key ID of area

Expr varchar2(15) - How much Experience

Salary varchar2(20) - Salary

Industry varchar2(25) - Work Industry

ind_role varchar2(25) - Role in industry

Skills varchar2(50) - Key Skills

35 | P a g e

5. Candidate Address


candidate_id Number Foreign key ID of Candidate

candidate_addrs_id Number Primary key ID of Address

candidate_addrs varchar2(50) - Local address

city_id Number Foreign key ID of City

6. Company


company_id Number Primary key ID of Company

company_name varchar2(20) - Name of Company

contact_person varchar2(25) - Contact-person Name

company_contact number(15) - Contact number

company_email_id varchar2(30) - Company email id

company_details varchar2(200) - Details of Company

company_status char(10) - Active / Inactive

7. Company Branch Address


company_id Number Foreign key ID of Company

branch_id Number Primary key ID of Branch

area_id Number Foreign key ID of Area

branch_address varchar2(50) - Local address

city_id Number Foreign key ID of City

36 | P a g e

8. Package


package_id Number Primary key ID of Package

package_cost Number - Total or Per-resume

no_jobpost Number - No. of Job-postings

9. Company Package


company_package_id Number Primary key ID-Company package


package_id Number Foreign key ID of Package

package_date Date - Date of selection

10. Job Applied


applied_id Number Primary key ID of Applied job


jobpost_id Number Foreign key ID of Vacancy

resume_id Number Foreign key ID of Resume

applied_date Date - Date when applied

11. Job Post


jobpost_id Number Primary key ID-Company package


job_title varchar2(20) - Title of Job

37 | P a g e


branch_id Number Foreign key ID of Branch

post_id Number Foreign key ID of Post

no_vacancy Number - Number of vacancy

start_date Date - Starting date

end_date Date - Ending date

expr_req varchar2(15) - Experience Requirement

skills_req varchar2(30) - Skills Requirement

edu_req varchar2(10) - Education Requirement

basic_req varchar2(30) - Basic Requirement

salary_given varchar2(20) - Salary Given

jobpost_status char(10) - Active/ Outdate / Full

12. Company Block


ccb_id Number Primary key ID of Blocking



block_date Date - Date when blocked

block_status char(10) - Active / Inactive

13. Post


post_id Number Primary key ID of Area


post_name char(10) - Name of the Post

38 | P a g e

14. Category


category_id Number Primary key ID of Category

category_name char(10) - Name of Category

category_status char(10) - Active / Inactive

15. Area


area_id Number Primary key ID of Area

category_id Number Foreign key ID of Category

area_name varchar2(10) - Name of the area

16. Question


que_id Number Primary key ID of Question

Que varchar2(50) Full Question

17. Country


country_id Number Primary key ID of Country

country_name char(20) - Name of the Country

country_status char(10) - Active / Inactive

39 | P a g e

18. State


state_id Number Primary key ID of State

state_name char(20) - Name of the State

country_id Number Foreign key ID of the Country

state_status char(10) - Active / Inactive

19. City


city_id Number Primary key ID of City

city name char(20) - Name of the City

state_id Number Foreign key ID of the State

dist_status varchar2(10) - Active / Inactive

20. Resume


resume_id Number Primary key ID of Resume

resume headline varchar2(30) - Headline of Resume


CHAPTER V

40 | P a g e

FORM LAYOUT

5.1 Home page

Description: This is the Home Page of website.

7.2. Jobseeker’s Login Page

41 | P a g e

Description: This is the Jobseeker’s Login Page with forgot password and registration link.

7.3. New Jobseeker Registration:

42 | P a g e

Personal Details

Description: This page is used to fill personal details of new jobseeker.

Education Details

43 | P a g e

Description: This page is used to fill Educational detail of new jobseeker.

Professional Details

44 | P a g e

Description: This page is used to fill professional detail of new jobseeker.

7.4. Active Profile

45 | P a g e

Description: This page is used to view active profile of jobseeker.

46 | P a g e

7.5. Forgot Password

Description: This page is used to get new password for jobseeker.

47 | P a g e

7.6. Search jobs

Description: This page is used to search jobs by using different options.

48 | P a g e

7.7. Recruiter Login

Description: This page is used for Recruiter login and Registration.

49 | P a g e

7.8. Recruiter Profile

Description: This page displays the profile of recruiters.

50 | P a g e

7.9. Administrator Login

Description: This page used by admin for Login .

51 | P a g e

7.10. User Names & Passwords

Description: This page used by admin to view all usernames and password and also to edit or delete them.

52 | P a g e

7.11. Employer’s Profile

Description: This page displays the Employer’s Profile.

53 | P a g e

7.12. Post Jobs

Description: This page is used for job posting.

54 | P a g e

7.13. Admin Area

Description: This Page displays all the options that Admin Can perform.

55 | P a g e

7.14. Add Package

Description: This page is used by Admin for posting of Package provided by Companies.

56 | P a g e

7.15. Posted Job

Description: This page displays the posted jobs to admin.

57 | P a g e

7.16. Security Question

Description: This page asks is used to recover password by asking security question.

58 | P a g e

7.17. Company Package

Description: This page displays Package provided by Company,

59 | P a g e

CHAPTER VI

TESTING

6.1 Introduction

Testing should be done through the implementation process. Even before and

application is installed; it makes sense to verify that the basic platform is capable of

achieving its design capabilities. System testing is a critical process. Testing is a process of

executing a program with the explicit intention of finding errors that is making the program

fail. This helps in finding the bottle neck in the system. Executing a program in a

stimulated environment performs testing. The feedback from testing phase generally

produces changes in the software to deal with errors and failures that are uncovered.

6.2 Types of Testing

6.2.1 Unit Testing:

Here we test each module individually and integrate the overall system. Unit testing

focuses verification effort even in the smallest unit of software development in each

module. This is also known as module testing. The modules of the system are tested

separately. This testing is carried out in the programming style itself. In this testing, each

module is focused to work satisfactorily as regard to expect output from the module.

6.2.2 Integration Testing:

Data can be lost across on an interface, one module have an adverse effect on the

other sub-functions, when combined may not produce the desired functions. Integrated

testing is the systematic testing to uncover the error within the interface. The testing is

done with simple data and the developed system can run successfully with this simple data.

Here the major intention is to find the overall system performance.

6.2.3 Blackbox Testing:

This is a software testing approach in which the tester doesn’t know the internal

working of the item being tested. For example in a Black box test, on software design the

60 | P a g e

tester only knows the input and the expected outputs. He doesn’t know how the program

derives the output. He doesn’t even imagine as to how, the coding is done. He need know

only the specifications.

The advantages of this testing approach are-

The test is unbiased because the designer and the tester is independent of each

other

The tester needs no specific knowledge on any programming language

The test is done from the point of view of the user, not the designer.

The test can be designed as soon as the specifications are complete

The disadvantages of this testing approach are

The test can be redundant if the software designer has already run a test case.

The test can be difficult to design

Testing every possible input stream is unrealistic.

6.2.4 Validation Testing:

At the culmination of Black box testing the software is completely assembled as a

whole package. Interfacing error have been uncovered and corrected and the final series of

tests, that is validation begins. The validation test can be defined by the following simple

definition that validation succeeds when the software functions in a manner that can be

reasonably accepted by the customer.

6.2.5 Output Testing:

After performing validation testing the next step is the output testing. The system

cannot be useful if it does not produce the required output. Asking the user about the

format in which the system is required, test the output that is displayed or generated by the

system under consideration. Here the output format is considered in two way. One is on

screen format and the other is the printed format. The output format on the screen is found

to be correct as the format was designed in the system phase according to user names. As

for hard copy, the output comes according to the specification requested by the user. Here

the output testing doesn’t result in any correction in the system.

6.2.6 User Acceptance Testing:

61 | P a g e

User acceptance testing of the system is the key factor of the success of any system.

The system under consideration is tested for user acceptance by constantly keeping in

touch with the prospective system at the time of development and making change

whenever required. This is done with regard to input-output screen designs.

.

6.2.7 White Box Testing:

The White box testing or structural testing performs close operation of procedural

details. They test the software logical path by having test cases exercising specific sets of

condition and loops.

White box testing is done in theproject to remove the errors:

All modules path have been exercised at least once.

Exercised on logical decisions.

Executed all loops at their boundaries and within their operational bounds.

Exercised internal data structure to ensure their validity.

6.2.8 Stress Testing:

This testing is done to tackle problems of interface that is putting all interfaces

together. When the separate modules are put together in an integrated manner, this

testing is performed. This testing is systematic technique. This testing is performed to

check the data should not be lost across an interface. The objective is to take an unit

tested module and build a program structure that has been dedicated by design.

6.2.9 System Testing:

System testing is done when the entire system has been fully integrated. The

purpose of the system testing is to test how the different modules interact with each other

and whether the system provides the functionality that was expected.

Software testing is an investigation conducted to provide stakeholders with

information about the quality of the product or service under test.Software testing also

provides an objective, independent view of the software to allow the business to appreciate

62 | P a g e

and understand the risks of software implementation. Test techniques include, but are not

limited to, the process of executing a program or application with the intent of

finding software bugs (errors or other defects).

Software testing can also be stated as the process of validating and verifying that a

software program/application/product:

meets the business and technical requirements that guided its design and

development;

works as expected; and

can be implemented with the same characteristics.

6.2.10 Component Testing:

It focuses on verification efforts of the smallest grid of software designing that is a

software component or module is tested. This testing is done at the coding phase. This

testing uses procedural design as guide to test major control path and uncovers errors

within the module boundary. Following test were performed during component test:

Module Interface Test: Module interface was tested to ensure information flow in

and out of the program unit.

Local Data Structure Testing: Local data structures were tested to make surety

that data store temporarily maintained their integrity during all steps in algorithm

execution.

Boundary Condition Testing: Boundary conditions were tested to make sure that

the modules operate properly at boundaries.

Independent Path Testing: All independent paths through control structure were

checked to make sure that all statements in a module have been executed.

Error Handling Path Test: This is performed to handle exception.

6.3 System Security

Security is a critical stage in system development. Even candidate system must

provide built-in features for security and integrity of data. Without safe guards against

63 | P a g e

unauthorized access, fraud, embezzlement, fire and natural disaster, a system could be so

vulnerable as to threaten the survival of the organizations.

To do an adequate job on security, the risk, exposure, cost and specific measures

such as password should be analyzed to provide protection. In addition, back up of copies

of software and recovery restart procedures must be available when needed.

The amount of protection depends on the sensitivity of data, the reliability of the

user and the complexity of the system. The motive behind security is to keep the

organization running, protect data as an asset and seek management support for more

installations.

6.4 Threats To System Security

The lists of potential threats are :

Errors and Omissions

Disgruntled and Dishonest Employees

Fire

Natural Disaster

External Attack

6.5 System Security Measures

After system security risk has been evaluated, the next step is to select security measures.

the measures are

Identification

Access Control

Audit Control

System Integrity

6.5.1 Identification

64 | P a g e

It is the scheme of identifying person to the system based on “ Something you know” such

as a password or a picture badge, “Something you are” such as finger print or voice print or

“Something you have” such as credit card, key or special terminal.

6.5.2 Access Control

Controlling the access to the computer facility is secured through encoded cards or similar

devices. Encryption prevents intruders from accessing data by scrambling messages across

telephones to the destination.

6.5.3 Audit Control

Auditing must be supported at all levels of management. Audit control protects a system

from external security breaches and internal fraud or embezzlement. Various software

programs are available to help in audit function.

6.5.4 System Integrity

This line of different safeguards the functioning of hardware, software and physical

security and operating procedure. Proper back of hardware and software are extremely

important.

CHAPTER VII

65 | P a g e

SYSTEM IMPLEMENTATION

As we know, creating software is one thing and the implementation of the created

software is another. The process of implementing software is much difficult as compared

to the task of creating the project. First we have to implement the software on a small scale

for removing the bugs and other errors in the project and after removing them we can

implement the software on a large scale. Before we think in terms of implementing the

Software on a large basis, we must consider the Hardware requirements.

The term Implementation has different meanings ranging from the conversation of

a basic application to a complete replacement of a computer system. The procedures

however, are virtually the same. Implementation includes all those activities that take place

to convert from old systems to new.

The new system may be totally new replacing an existing manual or automated

system or it may be major modification to an existing system. The method of

implementation and time scale to be adopted is found out initially. Neat the system is test

properly and at the same time the users are trained in the new procedure. Proper

implementation is essential to provide a reliable system to meet organization requirement.

Successful and efficient utilization in the system can be achieved only through

proper implementation of the system in the organization. So implementation phase is also

important like other phases such as analysis, design, coding and testing.

Careful planning

Investigation of the system and its constraints

Design the methods to achieve the change over

Training the staff in the changed phase

Ensuring the user has understood and accepted the changes

66 | P a g e

Getting complete feedback during test run and ensuring everything in perfect for the final change over

Whenever we develop software or project a certain hardware and software is being

used by the programmer for developing the project. The hardware and software to be used

by the programmer for developing the project should be such that it would result in the

development of a project, which would satisfy all the basic needs for which the project has

been created by the programmer. The Hardware should be such that cost constraints of the

Client should also be taken into account without affecting the performance.

67 | P a g e

CHAPTER VIII

FURTHER SCOPE OF THE APPLICATION

This System being web-based and an undertaking of Cyber Security Division,

needs to be thoroughly tested to find out any security gaps.

A console for the data centre may be made available to allow the personnel to

monitor on the sites which were cleared for hosting during a particular period.

Moreover, it is just a beginning; further the system may be utilized in various other

types of auditing operation viz. Network auditing or similar process/workflow

based applications.

Though maximum efforts have been put in to make this report authentic in all

aspects and to take all necessary presentation to ensure that the information

gathered is true, some uncomfortable factors may have crept in.

Some of the respondents were reluctant to part with certain information on the

pretext of the sensitivity of the information. Also some facts of figures were not

divulged as the company policy came in the way for free revelation of the desired

input.

An element of bias might have crept in from the side of the official interviewed.

This could also have resulted in some kind of modification of the information

divulged.

Through an attempt was make to collect information from the best possible source

in the company, it was difficult to meet the top officials due to their busy schedules.

Most of the analysis and interpretations, made for this report, are based on

secondary data obtained. This data could have some inherent mistakes and errors.

Finally, although due care has been taken those can be typing and compilation

errors in the report itself.

68 | P a g e

CHAPTER IX

CONCLUSION

At last it can be concluded that the Job Portal System was a real learning experience.

The principles of software production were well implemented throughout the system. The

whole project undergoes with full of enthusiasm and with full of joyous moments. The

project has been made as per as the given specification. The system has been made as user

friendly as possible by the use of principals. That is why Management holds an important

place in the software production.

Working on the Project was really a learning experience and we have come a long

way in building our concepts of Software engineering. The “Job Portal System “developed

by us is purely based on ASP.net platform. The overall purpose of this system is to

computerized the whole process and thus prevent the intervening errors. We also tried to

follow the holistic design principle so that the interface of the system is simple.

During the course of this assignment we have gone through many obstacles which

made us to research and though increased our knowledge. After applying all the data

modeling, object modeling and process modeling techniques now we are very well clear

with all these concepts and fundamentals which will be going to help us in the future.

69 | P a g e

BIBLIOGRAPHY

BOOK REFERENCING

Stephen walther (2008). ASP.NET 3.5 Unleashed. India: Dorling Kindersley.1797

Chris Payne(2002).ASP.NET in 21 days: G.C. Jain for Techmedia.939

Ian Sommerville (2008). Software Engineering. 7th ed. Delhi: Pearson Education

Ltd.

S.Valacich, Joseph, F.George, Joey, and A. offer, Jeffery, 2005. Essentials of

System Analysis and Design. 2nd Ed. New Delhi: Prentice-Hall of India Private

Limited.

WEB SITE REFERENCING

(1995). Asp tutorials. Available: http://w3schools.com/asp/default.asp.

(2004). ASp.net and sql.

Available:http://www.tutorialized.com/tutorial/Connecting-to-a-SQL-database-

from-ASP-.NET-II/5745.

De Montfort University. 2010. Purpose of WISDM. [ONLINE] Available

at:http://www.ccsr.cse.dmu.ac.uk/conferences/ethicomp/ethicomp2010/abstracts/

ethicomp2010_ramrattan_ramrattan_patel_hussain.php. [Accessed 13 March 13].

http://www.google.co.in

http://www.wikipedia.org

70 | P a g e

http://www.google.co.in/

5 job adda doc 2

Engineering

Transcript of 5 job adda doc 2