You are on page 1of 154

INDIRA GANDHI NATIONAL

OPEN UNIVERSITY
MCSP - 060

Job portal
By

Submitted to the School of Computer and Information Sciences, IGNOU


in partial fulfilment of the requirements
for the award of the degree
Master of Computer Applications (MCA)
Year of Submission
2017-18

Indira Gandhi National Open University


MaidanGarhi
New Delhi – 110068.

Table of Content
S NO Topic Description Page No
1. Original Copy of the Approved Performa 3

1|Page
2. Certificate of Originality duly signed by Guide 4

3. Bio-data of the Guide with signature and Date 5-12

4. Synopsis 13-37

5. Title of the Project 38

6. Introduction 39

7. Objective of the project 40-41

8. System Analysis 42-47

9. Feasibility Study 48-52

10. Hardware & Software Requirement Specification 53-57

11. Software Engineering Paradigm Applied 58-63

12. System design 64-70

13. Data Flow Diagram (DFD) 71-76

14. E-R Diagram 77

15. Data Structure of Table 78-82

16. Coding 83-115

17. Output Screen 116-135

18. Testing 136-148

19. Charts 149-152

20. Cost Estimation of the Project 153-155

21. Future Scope of the Project 156

22. Bibliography 157

23. Glossary 158-159

2|Page
24. Finish 160

3|Page
4|Page
CERTIFICATE OF ORIGINALITY
This is to certify that the project report entitled ____________________________________

submitted to Indira Gandhi National Open University in partialfulfilment of the requirement

for the award of the degree of MASTER OF COMPUTER APPLICATIONS (MCA), is

an authentic and original work carried out by Mr./Ms.________________________________

with enrolment no. _______________________under my guidance.

The matter embodied in this project is genuine work done by the student and has not been

submitted whether to this University or to any other University / Institute for the fulfilment of the
requirements of any course of study.

………………………. ...…………………….

Signature of the Student: Signature of the Guide

Date: ……………….. Date: …………………

Name and Address Name, Designation


of the student and Address of the Guide:
……………………….. ………………………..
……………………….. ………………………..
……………………….. ………………………..
……………………….. ………………………..

Enrolment No…………

5|Page
Submitted By:
Deepak joshi
117587080

6|Page
CONTENTS
SL NO. Title Page No.
1. INTRODUCTION 15
2. OBJECTIVE 16
3. EVALUATION OF EXISTING SYSTEM 17
4. BENEFITS OF WEB SYSTEM 18-19
5. SOFTWARE REQUIREMENTS 20
6. TOOLS AND TECHNOLOGY 21-22
7. PROCESS FLOW 23
8. LIST OF INPUT FORMS 24
9. LIST OF REPORTS 25
10. ER-DIAGRAM 26
11. DATA FLOW DIAGRAM 27-31
12. DATA STRUCTURE 32-34
13. FUTURE SCOPE 35
14 LIMITATIONS 36
15 BIBLOGRAPHY 37

7|Page
INTRODUCTION
 This project is aimed at developing an 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 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.

 It provides the candidates ability to register to this application and


search for jobs, manage their accounts. Each candidate will have their
own account with their own home page.

 On the other hand companies that are willing to publish the jobs for
their company to candidates can register to the job portal and get their
own account created and can post jobs to portal‘s database.

 Registered companies can add or remove jobs and these jobs can be
seen by various candidates and they can contact the company person for
the job.

 Main aim of this web application is to make a good web application that
can make this job search option easy and accessible to everyone who
are interested.
OBJECTIVE

8|Page
 Objective of this project is to develop a Computerized on Line Job
Search System to facilitate the General administration system to
manage the various information of the Job Seeker and Recruiter’s and
the processes involved in a placement company. So, that organization
can access accurate information quickly and easily as and when
required, thereby improving its operational efficiency & effectiveness.

 Some of the client requirement and objectives of this site is as under: -

• To increase the business of Client.

• To make it Global.

• To facilitate job search.

• To facilitate company so that it can search for best candidates


available.

• To help candidates to fetch a right job.

• To act as a middle men connecting Job seeker and Provider

• User can search for different options available.

• User can do on-line resume posting etc.

• User can do apply for job on-line.

• User can download different forms etc.

So these are some of the objectives which we have to accomplish.

EVALUATION OF EXISTING
SYSTEM

9|Page
3.1 Problem in Existing System: -

 Cannot Upload and Download the latest updates.


 No use of Web Services and Remoting.
 Risk of mismanagement and of data when the project is under
development.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users - Friendly.

3.2. Solution of These Problems: -


The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.
 User friendliness is provided in the application with various controls.
 The system makes the overall project management much easier and
flexible.
 Readily upload the latest updates, allows user to download the alerts by
clicking the URL.
 There is no risk of data mismanagement at any level while the project
development is under process.
 It provides high level of security with different level of authentication.

Benefits of using A Web Service/System

10 | P a g e
 Exposing the function on to network: Web services allow you to
expose the functionality of your existing code over the network. Once
it is exposed on the network, other applications can us the existing
functionality of your program.

 Connecting Different Applications: Web Services allows different


applications to talk to each other and share data and services among
themselves. Other applications can also use the services of the web
services.

 Standardized Protocol: Web Services uses standardized industry


standard protocol for the communication. This standardization of
protocol stack gives the business many advantages like wide range of
choices, reduction in the cost due to competition and increase in the
quality.

 Low Cost of communication: Web services use SOAP over HTTP


for communication, so you can use your existing low cost internet for
implementing web services. This solution is much less costly
compared to proprietary solutions like EDI/B2B.

 Support for Other communication means: Beside SOAP over


HTTP, Web Services can also be implemented on other reliable
transport mechanisms. So, it gives flexibility use the communication
means of your requirement and choice.

 Loosely Coupled Applications: Web Services are self-describing


software modules which encapsulates discrete functionality. Web

11 | P a g e
Services are accessible via standard Internet communication protocols
like XML and SOAP. These Web Services can be developed in many
technologies (like C++, Java, .NET, PHP, Perl etc.) and any
application or Web Services can access these services. So, the Web
Services are loosely coupled application and can be used by
applications developed in any technologies

 Web Services Sharing: Web Services supports different technologies


like EAI, EDI, B2B, Portals etc. which are being used by
organizations for distributing computing.

 Web Services are Self Describing: Web Services are self-describing


applications which reduces the software development time. This helps
the other business partners to quickly develop application and start
doing business.

 Automatic Discovery: Web Services automatic discovery mechanism


helps the business to easy find the Service Providers. This also helps
the customer to find the services easily.

 Business Opportunity: Web Services has opened the door to new


business opportunities by making it easy to connect with partners.

SOFTWARE REQUIREMENTS

12 | P a g e
1. Hardware Requirement are:
 Pentium IV 1.8 GHz and Above
 512 MB DDR2 RAM or More
 40 GB HDD or more
 Printer
 Power Backup
 Microsoft Mouse or compatible pointing device.
 Standard Windows Keyboard
 Internet Connection

2. Software Requirement are:


 Windows XP/Wins 2000 Professional or More.
 Microsoft Visual Studio 2010-Asp.Net(C#).
 MS SQL Server 2008.
 Internet Explorer, Google Chrome and Mozilla Firefox.

TOOLS & TECHNOLOGY

13 | P a g e
1. Microsoft Visual Studio 2010:

 Visual Studio includes a code editor supporting


IntelliSense as well as code refactoring.

 The integrated debugger works both as a source-level


debugger and a machine-level debugger. Other built-in
tools include a forms designer for building GUI
applications, web designer, class designer, and database
schema designer.
 Visual Studio supports different programming languages
by means of language services, which allow the code
editor and debugger to support (to varying degrees)
nearly any programming language, provided a language-
specific service exists. Built-in languages include C/C++
(via Visual C++, VB.NET (via Visual Basic .NET, C#
(via Visual C# and F#(as of Visual Studio 2010).

2. ABOUT C#
 C# is intended to be a simple, modern, general-purpose,
object-oriented programming language.

 Object-oriented programming was, and still is, a widely


accepted proven technique to master complexity in
worlds where tons of software components need to work
together seamlessly. No wonder the CLI and C# embrace
it.

 Type safety is a big thing in the CLI. It eliminates whole


classes of bugs and security headaches that
plaguelanguages like C and C++. This said, C# still
allows type unsafe code in regions explicitly marked as
such.

3. ABOUT ASP.NET

14 | P a g e
 ASP.NET is built on the Common Language Runtime
(CLR), allowing programmers to write ASP.NET code using
any supported .NET language.

 ASP.NET 4 is the latest iteration in the .NET framework,


introducing many new features that build upon its
predecessor to improve performance, security, and
interoperability with the latest browsers.

4. ABOUT MS SQL

 As a database, it is a software product whose primary


function is to store and retrieve data as requested by other
software applications, be it those on the same computer or
those running on another computer across a network.

 Its primary query languages are T-SQL.

 SQL Server includes a cost-based query optimizer which


tries to optimize on the cost, in terms of the resources it will
take to execute the query.

PROCESS FLOW

15 | P a g e
1. Login: Login and Sign-up module includes user security management, login
security.
 Login: Checks the jobseekers or recruiters by user name and password.
Any jobseekers or recruiters will be asked to enter a valid user name and
password to access the application features. Application checks the
validation by matching the username and password from database on
server.

2. Registration: This module deals with all operations related to entity –


Jobseeker.
 Add New: This sub module adds new jobseeker details to the System
and Database for job information.
 Update Jobseeker’s data: This sub module responsible to update the
Jobseeker’s data i.e. address working or non-working status.
 Jobseeker’s Report: This module generates the Jobseeker’s report. This
report displays Jobseeker’s all details.
 Jobseeker’s Record: This module displays Jobseeker’s record with
respect to their qualification.

3. Employer: This module deals with all operations related to entity –


Employer.
 Add New: This sub module adds new Employer to the System and
Database.
 Update Employer data: This sub module responsible to update the
Employer Date i.e. name of the employer with their jobs.
 Employer Report: This module generates the Employer report. This
report displays all details of Employer with their jobs.
 Employer Record: This module displays Employer record with respect
to their jobs available for job seeker to apply online using job portal.

4. Administrator: This module handles the Jobseeker, employer details and


job search for job portal. This module is used by Administrator which can be
resources manager.

LIST OF INPUT FORMS

16 | P a g e
A) JOBSEEKER:

This form gets the input from jobseekers about his/her details like First
Name, Last Name, Date of Birth, Age, Address, Mobile Number, Email-
ID, college, institute, session, password etc that help the administrator to
maintain the jobseekers record.

B) EMPLOYER FORM:

This form gets the input from employers about company details like
Company Name, Location, Email-ID, Address, Mobile Number, Fax
Number, password etc that help the administrator to maintain the
Employer record.

C) JOBS POSTING FORM:

This form gets the input from employer to add and update the vacancy of
jobs, which will be help to the jobseekers to check the time to time for
applying jobs in job portal.

D) JOB SEARCH FORM:


This form gets the input from jobseeker to search the information of jobs
according to his qualification.

17 | P a g e
LIST OF REPORTS
* Report generation is an important part of the job portal.

* It provides the detailed information about all the modules. With the help of
reports the important decisions can be taken at ease.

* Following are the reports that will be generated by the system:

 Jobseekers Reports
i. Reports by qualification.
ii. Reports by experience.
iii. Brief summary about jobseeker.
iv. Job apply by jobseekers.
v. Sort according to ascending or descending order.

 Employer Reports
i. Employer complete name with address.
ii. Contact info of Employer.
iii. Requirement of Employer.
iv. Nature of Jobs.

 Jobs Search Report


i. Name of the Job.
ii. Name of the Employer(Company).
iii. Criteria for Job Vacancy.
iv. Location.
v. Salary
vi. Experience.

18 | P a g e
E-R DIAGARAM

19 | P a g e
DATA FLOW DIAGARAM
0 Level DFD’s

20 | P a g e
1st Level DFD’s
DFD For New Job Seeker Creation

Job Seeker Registratio


Details n Details

Insert New Check for


Job Seeker Verify Data Registration Verify Data
Details

Insert

Job
Seeker

21 | P a g e
DFD For New Job Seeker Creation

Job Provider Registratio


Details n Details

Insert New Check for


Job Provider Verify Data Registration Verify Data
Details

Insert

Job
Provider

22 | P a g e
DFD For New Job Search Creation

Registration
Job Seeker Details
Search
Details Job
Details

Check for
Insert New Verify Data Check For
Verify Data Registration Verify Data
Job Seeker Job

Insert

Job Seeker
Details

2nd Level DFD’s

23 | P a g e
DFD For New Recruitment Creation

Designation Job Provider


Job Seeker Type Details
Details Details

Insert New Verify Data


Check
Job Seeker for Verify Data Verify Data
Designa

Check for
Job Provider

Check for Job


Seeker Info

Check for Type Check for


Verify Data Verify Data Status Verify Data

Job Provider Job Seeker


Job Seeker Details
Details Status Details

Insert

Job Seeker
Details

24 | P a g e
DATA STURCTURE
 Usually, a collection of interrelated data is referring to as database. The
database contains information about one particular enterprise.

 Database system is designed to shear and manage large volume of


information.

 The management of data involves both the manipulation of information.

 In addition, the database system must provide for safety information


storage in the database, despite system crashes or unauthorized access.

1. Table Name Jobseeker:

Field Name Data Size Constraints Description


Type
JS_ID int 10 Primary Key Jobseeker ID
UserID Varchar 50 Jobseeker UserID
First_Name Varchar 50 Jobseeker First Name
Last_Name Varchar 50 Jobseeker Last Name
Sex Char 2 Jobseeker sex details
DOB Varchar 30 Jobseeker date of birth
Father_Name Varchar 100 Jobseeker Father
Name
Qualification Varchar 50 Jobseeker
Qualification
Skills Varchar 200 Jobseeker Skills
Address Varchar2 200 Jobseeker Address
Email_ID Varchar2 100 Jobseeker Email ID
Contact_Number Int 10 Student contact
number
Password Varchar 50 Jobseeker Password
Confirm_Passwor Varchar 50 Jobseeker Confrim
d Password

25 | P a g e
2. Table Name Employer:

Field Name Data Size Constraints Description


Type
COMP_ID Int 10 Primary Key Employer ID
EmpID Varchar 50 Employer User ID
EMP_Name Varchar 50 Employer Name
Contact_Person Varchar 50 Contact Person of
Company
Address Varchar2 200 Employer Address
Email_ID Varchar2 100 Employer Email ID
Phone_Number Int 10 Employer phone
number
Mobile_Number Int 10 Employer mobile
number
Password Varchar 50 Employer Password
Confirm_Password Varchar 50 Employer Confirm
Password

3. Table Name FEEDBACK:

Field Name Data Size Constraints Description


Type
SLNO Int 10 Serial Number
JS_ID Varchar 50 Foreign Key Jobseeker ID
Feedback Varchar2 500 Jobseeker
Feedback

26 | P a g e
4. Table Name JOB_VACCANCY:

Field Name Data Size Constraints Description


Type
JPID Int 10 Primary Key JOB POST ID
COMP_ID Varchar 50 Foreign Key Employer ID
JOB_Name Varchar 50 Job Name
JOB_Category Varchar 50 Job Category
JOB_Experience Varchar 20 Job Experience
JOB_Qualificatio Varchar 20 Job Qualification
n
Salary Varchar 20 Salary for Job
JOB_Location Varchar 50 Location for job

5. Table Name ADMIN:

Field Name Data Size Constraints Description


Type
ADMIN_ID Varchar 30 Primary Key Admin User ID
PASSWORD Varchar 50 Admin password
Confirm_Passwor Varchar 50 Admin confirm
d password

27 | P a g e
FUTURE SCOPE & LIMITATIONS
 Since Object Oriented programming is used here for developing this system,
there are every chances of reusability of the codes in other environment even
in different platforms.

 Also its present features can be enhanced by some simple modification in


the codes so as to reuse it in the changing scenario.

 With a little bit of modification, the System can be modified to a generic


System. The generic system can be used for a wide variety of other
applications having the problem nature similar to this application.

 Our project has to be deployed on server and operate from each standalone
computers which is makes it easier to reach to maximum number of people.

 Job Portal can be conducted through internet or in an intranet. It can be


conducted at anytime and anywhere.

 Job Portal will help in reducing cost and time. More securities for all
important data will be maintained confidentially

28 | P a g e
LIMITATIONS

 Sever goes down during when no. of people trying to access the same site,
so job employer/jobseeker face difficulty to update the data.
 Technical difficulties could delay the process.
 If you are living in a rural area where online services are not up to the mark,
then you would face difficulty in accessing the application.
 It is not mobile based application.
 It allows maximum 32,767 users to access the online application at same
time.

29 | P a g e
BIBLIOGRAPHY

 Jason Price, Mike gunderloy," Mastering visual C#.net "BPB Pub.


1999.

 Herbert Schildt," C#.net" TATA McGraw-Hill edition 2002.

 www.google.com

 www.codeproject.com

 Beginning ASP.NET 3.5 in C# 2008 Second Edition Matthew


MacDonald.

 SQL Tutorial - tutorialspoint.com

 www.library.co.in

 www.stackoverflow.com

 www.wikipedia.org

30 | P a g e
PROJECT REPORT
MCA 6TH SEMESTER

MCSP-060(Project)
(2017)

Job Portal

:
An application developed by DEEPAK JOSHI
Enrollment no: 117587080
Programme code: MCA(6 th Semester)
Course code: MCSP-060(Project)

31 | P a g e
Chapter 1

INTRODUCTION
The project (Job portal) would help in effective and systematic record
keeping that is storing and retrieving of useful data. Project will be able to
give the report so that management can make decisions on the basis of
those reports.

The project should contain all the information of Company and Vacancy
which is registered in this site. It also contains all the information of Job
Seeker like Personal Detail, Professional Detail, and Educational Detail etc. It
should process and evaluate jobs registered by companies.

Project should also contain information related to Job expiry or re


registration. It should inform both Job Seeker and Recruiter’s when the
appropriate person is found for a job.It should maintain proper financial
records.

The project should have Administrator for scheduling administrative work of


site.

I tried my best to make it general-purpose web application so that most of


the companies and jobseeker can use it to automate their routine work.

32 | P a g e
Chapter 2
OBJECTIVE
Objective of this project is to develop a Computerized on Line Job portal to
facilitate the General administration system to manage the various
information of the Job Seeker and Recruiter’s and the processes involved in
a placement company. So, that organization can access accurate information
quickly and easily as and when required, thereby improving its operational
efficiency & effectiveness.

In today’s competitive environment, where everybody wants to be on the


top, Information plays very crucial role. As fast as information is accessed
and processed, it can give good results. Today Internet is the fast way of
transferring Data and Information over wide area, hence I have used
internet as a way for exchanging information.

Computerized system helps to fulfill these goals. Computerization of the


official works will help in doing lot of manual work quickly. It will help in easy
storage and access of all information, in short period of time.

We proposing a centralized system with one server maintaining high level of


security.

33 | P a g e
Specific Objective of the site:

Objective of doing this project is to enhance my knowledge in the field of E-


com technology using ASP.net as a language. Some of the client
requirement and objectives of this site is as under:-

•To increase the business of Client.

• To make it Global.

• To facilitate job search.

• To facilitate company so that it can search for best candidates available.

• To help candidates to fetch a right job.

• To act as a middle men connecting Job seeker and Provider

• User can search for different options available.

• User can do on-line resume posting etc.

• User can use search engine to look for different vacancies, facilities
available etc.

• User can do apply for job on-line.

• User can download different forms etc.

So these are some of the objectives which we have to accomplish.

34 | P a g e
Chapter 3
SYSTEM ANALYSIS
IDENTIFICATION OF NEED

Draw back in existing system


The current system have all the problems which generally in count in the
manual system such as wastage of time, wastage of money, more efforts to
work etc. if the responsible person wants the full information of the total sale
of various models of the vehicles at various center at the evening then
he/she can not get it. Because the current system work manually and it is
very slow same as if he/she wants the total production then it take time. The
current system can not give the fast response as needed. It also does not
keep records of grievances of the faults in the vehicles in various parts of the
country. If he/she wants the information regarding the total stock at various
warehouses at his\her office then using current system he\she can not get
it.

He\she can not get the full information on time. It may be late and this
process is time consuming and generally the administrators receive the
relevant information next day which is the major limitation of existing
system.

35 | P a g e
SYSTEM ANALYSIS
OVERVIEW OF SYSTEM ANALYSIS

System analysis is the process of gathering and interpreting


the facts, diagnosing problems and using the information to
recommend a new system. System Analysis phase is
considered one of the most important phase in SDLC
(System Development Life Cycle). System Analysis is done
in order to understand the problem which the system to
solve. It is extremely important for the developer that he
has studied the existing system thoroughly otherwise it is
impossible to satisfy the need of user. This study will
enable the developer to know the disadvantage of existing
system and bring out their hidden mysteries to the light so
that they know exactly what to do and not to do while
building the system. It is a management technique that
helps in designing a new system. Analysis phase is the
bridge between system engineering and software design.

System Analysis and design refers to the process of examining a


business situation with the intent of improving it through better
procedures and methods. System Analysis is a process of
gathering and interpreting facts, diagnosing problems and using
the information to recommend improvement to the system. In
brief we can as Analysis specifies that system should do.
System Analysis is a management technique, which helps us in
designing a new system or improving an existing system.

System
Engineering

Analysis

Design

36 | P a g e
System Analysis may be divided into five areas of
effect:-
1 Problem recognition
2 Evaluation and synthesis
3 Modeling
4 Specification
5 Review

Problem Recognition:-

The first step of analysis is important to


understand the time factor which make the work correctly and
efficiently because it is the main goal of analysis. The
system designed by me is a new system, which is based
on operations done by the company.

The system that was followed by the company includes


following defects:-

Lack of security.
Inability to obtain the information of members rapidly
Difficulty in maintaining the information of each user
details.
Difficulty in maintain every user details of works

Evaluation and Solution Synthesis :-


Evaluation and solution synthesis is the next major area of
analysis , as it define all externally observable data objects
evaluate the flow and content of information define and
elaborate all functions, establish system interface
characteristics understand software behavior in the context
of events that affect the system and uncover addition
design constraints. Software created by me is not going to
be affected by the behavior in the context of events that
affect the system.

37 | P a g e
Modeling : -

It creates functional modes to gain a better understanding


of an actual entity to be built. It begins with a single
context level model and then moving towards the detail of
behavioral model or Data flow model. Various models and
tools are used in system analysis, which mainly involves
data flow diagram, interview, on-site observations and
questionnaires, etc. These models help the analyst
understand information function, behavior of system thereby
making the analyst task easier and more systematic.
Further the models become the foundation for design,
providing the design with an essential representation of
software that can be mapped into an implementation
context. In modeling there are various context level
diagrams. DFD’s are created by me who shows the
modeling.

Specificatio n:-
Specification on partitioning which decomposes a problem
into various parts and then establishing a hierarchical
representation of information exposing increasing detail by
moving vertically on functionally decomposing the problem
by moving horizontally.

Review : -
Review is like an assurance activity performed by the
analyst to go through the problem and requirements of
solving the problem. Further to uncover all the errors for
any representation of the software. Thus, System analysis is
the direction of system into its component pieces to study
how those component pieces interact and work. One aspect
of analysis is defining the boundaries of the system that
are assumed by me while implementing the software.

38 | P a g e
SOFTWARE REQUIREMENT SPECIFICATION
The Software Requirement Specification(SRS) is very
important part of the software building process, which describes the actual
user level requirement from technical point of view. I.e. what the user
exactly wants? The objective of preparing the software requirement
specification is to represent the requirements of the software in such a
manner that ultimately leads to successful software implementation. It is the
result of the analysis process of the software development. It should contain
all the data the software is going to process, the function it will provide, and
the behavior it will exhibit. This Software Requirements Specifications (SRS)
is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software
Requirements Specifications. The synopsis is prepared in the way to fulfill
almost all the points needed in S.R.S.

Analysis Report:

System analysis is the first step towards the software building process.
The purpose of system analysis is to understand the system requirements,
identify the data, functional and behavioral requirements and building the
models of the system for better understanding of the system.
In the process of system analysis one should first understand that,
what the present system, what it does, is how it works (i.e. processes). After
analyzing these points we become able to identify the problems the present
system is facing. Upon evaluating current problems and desired information
(input and output to the system), the analyst looks towards one or more
solutions. To begin with, the data objects, processing functions, and
behavior of the system are defined in detail. After this, a models from three
different aspects of the system-data, function and behavior. The models
created during the system analysis process helps in better understanding of
data and control flow, functional processing, operational behavioral and
information content.

39 | P a g e
SOFTWARE ENGINEERING PARADIGM
There are numerous life cycle models which are available to software
developers. One of the renowned and probably the oldest S.D.L.C model is
Water Fall Model. This model as the name implies, is a phased model. Each
phase has well defined starting and ending boundaries. One phase cannot
begin unless it’s previous phase is completed.

WATERFALL MODEL
In our case, we have decided to use waterfall model because the
requirements have been well defined and stable which is the prime criteria
for applicability of waterfall model. Also, the time allowed for the project is
limited; there is no scope for applying an evolutionary model. Activities have
to be distributed throughout the life cycle effectively. This model is easy to
understand and easy to explain to the customer. With a small team size of
two persons only, this model seems appropriate to us.

The following diagram depicts the various phases of the waterfall model: -

Requirements
analysis and
specification

Design and
specification

Coding and
module testing

Integration and
Implementation

Delivery and
maintenance
40 | P a g e
Chapter 4

FEASIBILITY
STYUDY
FEASIBILTY STUDY

“Feasibility study” is the determination of whether or not a project is


worth doing the process followed making this determination is called
feasibility study. This of determines if a project can and should be taken.
Once it has been determined that a project is feasible, the analyst can go
ahead and prepare the project specification which finalizes project
requirements. Generally, feasibility studies are undertaken within right time
constraints and normally culminate in a written and oral feasibility report.
The contents and recommendations of such a study will be used as a sound
basis for deciding whether to proceed, postpone or cancel the project. Thus,
since the feasibility study may lead to the commitment of large resources, it
becomes necessary that it should be conducted competently and that no
fundamental errors of judgment are made.

41 | P a g e
Different Type of Feasibility Study:-

TECHNICAL FEASIBILITY
This is concerned with specifying equipment and software and hardware that
will successfully satisfy the user requirement. The technical needs off the
system may vary considerably, but might include:
 The facility to produce output in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a
particular speed.
 Facility to communicate data to distant location.

In examining technical feasibility, configuration of the system is given more


importance than the actual make of hardware. The configuration should
give the complete picture about the system requirements. What speeds of
input and output should be achieved at particular quality of
printing.According to the definition of technical feasibility the compatibility
between front-end and back-end is very important. In our project the
compatibility of both is very good. The degree of compatibility of JSP and
SQL Sever 2000 is very good. The speed of out put is very good when we
enter the data and click button then the response time is very fast and give
result very quickset. I never find difficulty when we use complex query or
heavy transaction. The speed of transaction is always smooth and constant.
This software provides facility to communicate data to distant location.

We use Java Server Pages and Java Script. The designing of front-end of any
project is very important so we select Java Server Pages,Java Script as
front-end due to following reason:

42 | P a g e
 Easy implementation of code.
 Well define interface with database.
 Well define hand shaking of SQL Server 2000.
 Easy debugging.

At present scenario the no of backend are available but I have selected SQL
Server 2000 because of the following number of reasons.
 Able to handle large data.
 Security.
 Robust RDBMS.
 Backup & recovery.

With the help of above support we remove defect of existing software. In


future we can easily switch over any plate form. To ensure that system does
not halt in case of undesired situation or events. Problem effected of any
module does not effect any module of the system. A change of hardware
does not produce problem.

ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used technique for
evaluating the effectiveness of a proposed system. More
commonly known as cost/benefit analysis: the procedure is to
determine the benefits and saving that are expected from a
proposed system and compare them with cost. if benefits
outweighs cost ,a decision is taken to design and implement the
system. Otherwise, further justification or alternative in the
proposed system will have to be made if it is to have a chance of

43 | P a g e
being approved. This is an ongoing effort that improves in
accuracy at each phase of the system life cycle.

At present Company has ten systems with following configuration:

o Ram 32 MB or above for fast execution and reliability


o P-III 100MHz or above
o MOTHER Board 810
o Color Monitor 14” and 17”
o Hard Disk 10 / 40 GB
Hence the economical feasibility is very good.

OPERATIONAL FEASIBILITY

It is mainly related to human organizational and political aspects. The points


to be considered are:

 What changes will be brought with the system?


 What organization structures are disturbed?
 What new skills will be required? Do the existing staff
members have these skills? If not, can they be trained in
due course of time?

At present stage all the work is done manually. So, throughput and response
time is too much. Major problem is lack of security check that should have
been applied. Finding out the detail regarding customer’s transaction was
very difficult, because data store was in different books and different places.

44 | P a g e
In case of any problem, no one can solve the problem until the person
responsible is not present.

Current communication is entirely on telephonic conversation or personal


meetings. Post computerization staff can interact using internet.

Now, we will explain the last point of operational feasibility


i.e. handling and keeping of software , at every point of designing
I will take care that menu options are not too complex and can be
easily learned and required least amount of technical skills as
operators are going to be from non computers back ground.

45 | P a g e
Chapter 5
HARDWARE AND SOFTWARE
REQUIREMENTS
SPECIFICATION

HARDWARE REQUIREMENT
Altogether a Personal Computer with following Components:-

 Intel Pentium-IV Processor.


 Min Memory(512 MB RAM)
 Hard Disk 80GB
 Color Monitor
 Keyboard
 Mouse
 Printer

46 | P a g e
SOFTWARE REQUIREMENT
The Software Requirements Specification is produced at the culmination
of the analysis task. The function and performance allocated to software
as a part of system engineering are refined by establishing a complete
information description, a detailed functional description, a representation
of system behavior, an indication of performance requirements and
design constraints, appropriate validation criteria.

The introduction of software requirement specification states the


goal and objectives of the software, describing it in the context of
computer-based system. Actually the introduction may be nothing more
than the software scope of the planning document. Hardware, Software
and Human interfaces are designed for the external system elements and
internal software functions.

Thefollowing are the software requirements:-


Software : C# .net 4.5 FrameWork,Asp.net
PLATFORM:Windows 9x,Windows NT, indows XP,Window 7,
Window 8.1 & Window 10.
Database Server: Microsoft SQL Server2012.

47 | P a g e
ABOUT TECHNOLOGY

WHY .NET
ASP.NET is a unified Web development model that
includes the services necessary for you to build enterprise-
class Web applications with a minimum of coding. ASP.NET is
part of the .NET Framework, and when coding ASP.NET
applications you have access to classes in the .NET
Framework. You can code your applications in any language
compatible with the common language runtime (CLR),
including Microsoft Visual Basic, C#, JScript .NET, and J#.
These languages enable you to develop ASP.NET applications
that benefit from the common language runtime, type safety,
inheritance, and so on.

Client Side Interface:

In client side interface we are using:-

 ASP.NET-for internet based application

ASP.NET is middle-ware technology which are used in web


based projects because they use

 HTTP protocol which is the granting protocol to handle the


Request and Response

 They are invoked through Browser

 They give output in HTML format

 They need Browser Support

48 | P a g e
The choice of JSP was based mainly because enables rapid
development of Web-based applications that are platform
independent. JSP technology separates the user interface from
content generation, enabling designers to change the overall page
layout without altering the underlying dynamic content.

WHY SQL SERVER

Merits of using Sql Server 2012(RDBMS) are as under:

 Centralization of database

 Client Server Technology

 Normalization of database

 Transaction processor

 Security

 Gives internet related feature Relationship

Hence, due to these feature of the Sql Server 2012(RDBMS) we are


using it as a back-end technology.

Weather you are working on LAN projects or Distributed projects, there are
two sides:

 Front end

 Back end

49 | P a g e
Front end remains on client side. Front end is made for end user who uses
our application .basically in front end, our input-output forms reside which
takes the input from the client and gives output back to client.

Backend remains on the server side and has two component

 Server side programs

 Database

Database is the most important thing that gives identity to a thing. It


provides us a repository where we can store large amount of data, at one
place. Without a database, existence of thing is impossible.

While working on project first step is to design a database.

 What is database?

Database is a collection of coherent meaningful data. And it is a


collection of tables and tables is a collection of records in a tabular form i.e.
in row and columns format.

Database can be divided in to two parts:-

 RDBMS

 DBMS

We will be using RDBMS (Relational Database Management System) in our


project i.e. Sql Server 2012 Enterprise Edition.

50 | P a g e
Chapter 6
SOFTWARE ENGINEERING

PARADIGM APPLIED
LINEAR SEQUENTIAL MODEL

The basic objective of Software engineering is to: develop methods and


procedure for software development that can scale up for large system and
that can be used to consistently produces high quality software at low cost
and with a small cycle time. That is, the key objectives are consistency, low-
cost, high quality, small cycle time, and scalability.
The basic approach that software engineering takes is to separate the
development process from the software. The premise is that the
development process control the quality, scalability, consistency, and
productivity. Hence to satisfy the objectives, one must focus on the
development process. Hence to satisfy the objectives, one must focus on the
development process. Design of proper development process and their
control is the primary goal of the software engineering. It is this focus on the
process that distinguishes it from most other computing disciplines. Most
other computing disciplines focus on some other type of the product-
algorithms, operating systems, databases etc. while software engineering
focuses on the process for producing products.

51 | P a g e
The software-engineering paradigm applied for of all the analyst
group things about the model which is used in the development part of the
software. There are mainly some common models. The linear sequential
model. The Linear sequential model called the life cycle or water fall model,
the linear sequential suggests a systematic approach to software
development that begins at system level and progress through the analysis,
design, testing and the support. The linear sequential model for software
engineering model after engineering cycle, the linear sequential model
compasses.

ANALYSIS DESIGN CODE TEST

LINEAR SEQUENTIAL MODEL

The Linear Sequential Model is the oldest and the most widely
used paradigm for software engineering. However, a critic of the paradigm
has caused even active supporters to questions its efficiency.
Among the problems that are something encountered when Linear
sequential model is applied for:-
1) Real Project rarely follows the sequential flow that the model
progress. Although the Linear Model can accommodate iteration, it
dies too indirectly. As a result, Changes can cause confusion as the
project teams proceed.

52 | P a g e
2) It is often difficult for the customer to state all the requirements
explicitly. The Linear Sequential Model requires this and has difficulty
in accommodation the natural uncertainty that exists at the beginning
of the many projects.
3) The customer have patience working version of the program will not
available until in the project will not available in the time span. A
major blunder if undetected until working is reviewed, can be
disastrous.

SYSTEM/INFORMATION ENGINEERING MODELING

Because Software is always the part of a larger system ,work


begins by establishing the requirements for all the system elements

and then allocating some subset of these requirements to software.

SOFTWARE REQUIREMENTS ANALYSIS

The requirement gathering process in itself focused specifically on the


software. To understand the nature of the program to be built, the software
engineer (analyst) must understand the information domain for the software
as well as required functions behaviour performance. Requirement analysis
is done in order to understand the problem the software system is to solve.
The problem could be automating an existing manual process, developing a
new automated system, or a combination of the two. The emphasis in
requirements analysis is on identifying what is needed from the system, not
how the system will achieve the goals. There are at least two parties
involved in the software development –a client and the developer. The

53 | P a g e
developer has to develop the system to satisfy the needs of the client. The
developer does not understand the client’s problem domain, and the client
does not understand the issue involved in the software systems. This causes
a communication gap, which has to be adequately bridged during a
requirement analysis.

DESIGN
Software design is actually the multi step process that focuses on the
distinct attribute of the program: data structure, software architecture,
interface representation, and procedural design. The design process
translates the requirements into the representation of the software that can
be assessed for quality before the coding begins. Like requirements, the
design is documented and becomes the important part of the software
configuration.
The purpose of the design phase is to plan a solution of the
problem specified by the requirements documents. This phase is the first
step in moving from the problems domain to the solution domain. Starting
with what is needed; design takes us towards how to satisfy the needs. The
design of a system is perhaps the most critical factor affecting the quality of
the software. It has major impact on the later phases, particularly testing
and maintenance.
The design activity is divided into two phases: System Design
and Detailed Design. In System Design the focus is on identifying the
modules whereas during the Detailed Design the focus
is on designing the logic of each of the module.

54 | P a g e
CODE GENERATION
The Design must be then translated into a machine readable form the code
generation step performs this task. If design is performed in a detailed
manner, code generation can be accomplished mechanistically.

TESTING
Testing is the major quality control measure used during the software
development. Its basic function is to detect the errors in the software.
Testing not only uncover errors introduced during coding, but also errors
introduced during the previous phase. Thus, the goal of the testing is to
uncover requirements, design and coding errors in the program. Therefore,
different levels of testing are testing are used. Testing is an extremely
critical and time consuming activity. It requires proper planning of the
overall testing process. The output of the Testing phase is the test Reports
and the error report. Test report contains the set of the test cases and the
result of executing the code with the test cases. The error report describes the

error encountered and the action taken to remove these errors.

There are different levels of Testing used, these are as follows:-


1) Black Box Testing.
2) White Box Testing.
3) Unit Testing.
4) System Testing.
5) Validation Testing.
6) Special Test cases.

55 | P a g e
SUPPORT

Software will undoubtedly changes after it is delivered to the customers.


Change will occur because error have been encountered, because the
software must be adapted to the accommodate changes in its external
environment (e.g a change required because of a new operating system or
peripherial device)

56 | P a g e
Chapter 7

SYSTEM DESIGN
OVERVIEW OF SYSTEM DESIGN

The design of the information system produce the detail


that state how a system will meet the requirement identified
during system analysis often refer to this stage as logical
design, in contrast to the process of developing program
software, which is referred to as physical design.

System analysts being the process by identifying


reports, the requirement and output need by the system.
Then the specific data on each are pinpointed. Usually,
designers sketch the form or displays they expect from the
system. This can also be done on a paper or on the computer
display with the help of automated system tools available.
The system design also describes the date to be
input, calculated, or stored. Individual date items and
calculation procedures are written in detail. The procedures
tell how to process the data and produce the output.

57 | P a g e
Designers are responsible for providing
programmers with complete and clearly outlined software
specification. As programming starts, designers are able to
answer questions, clarify fuzzy areas, and handle problems
that confront the programmers when using the design
specifications.
As the software is to be designed in ASP .NET
PAGES and C# and back-end SQL Server2012, the concept of
database is must for quantity designing. It will be designed of
the database, designing of forms, designing of reports .
Unlikely the existing system, separate table have
been created for specific details. In order to make the
response time negligible; all the tables have been created in
the memory file system (MFS). Moreover, indexes have been
created on the tables in which the number of records is very
large. Therefore, in the proposed system, search for a value
has been made direct. This is contrast to the sequential
search being done in the existing system have been taken
care of in the system.

The design stage takes the final specification of the system


from analysis and finds the best way of fulfilling them, give
the technical environment and previous decision on required
level of automation.

58 | P a g e
The system design is carried out in two phase:

i) Architectural design (high level design).

ii) Detailed design (low level design).

HIGH LEVELDESIGN

The high-level design maps the business system described in


the program requirement specification to logical data
structure. It involves:

Identifying the entities


All the entities related to the
module were identified, checked and consolidated.
i) Identifying the relationship:
The relationships between
entities, within and outside the system were identified.
ii) Attribute definition:
The pertaining to the entities was
identified and their field characteristics were specified.

iii) N or m a l i z a t i o n :
The entities were normalized. After first
and second normalization go to bcnf was achieved for all the
entities of systems.
i v ) I n t e r fa c e :
Interfacing with other system was done and
attributes related to external entities were identified.
Once the entities and their attributes were defined, entity
relationship diagrams.

59 | P a g e
LOW LEVELDESIGN

Default database design:


This utility create column and constraint
definitions form the entity model and the table / entity
mapping entered in CASE* dictionary. This database design
can be refined according to your application regarding using
can be refined according to your application regarding using
the tables, columns sand key constraint definition screen to
make amendments.
The step involved here were:
i) Generation of table.
ii) Check constraint.
iii) Primary key.
iv) Unique key.
v) Foreign key.

Module design:
This screen is used to enter module information
during the design stage of business system development. The
application systems, function, tables and columns must
already exist in CASE* dictionary before being referenced.

60 | P a g e
User preferences :
Based on user preference like form
name, validation of primary key, layout of forms, layout of
fields. Creating title for forms, mandatory input field prompts
etc. was incorporated here.
Generate the program:

The program was generated based on the


relationship specified and according to the user preferences .
Program specification:
The program specifications were
written for the master, transaction, report, and queries. The
logic for each fields, from were so that anyone who does not
know system will be able to code the logic. Field validations
and user-friendly error message were written as a part of the
program specification.
This is done mainly for two reasons:
1) Saving the development time
As the procedures will be common to many
programs, the development time be saved substantially by
keeping.
2) Testing become easier
As the procedures become an independent
entity, it can be easily tested.

61 | P a g e
DESIGN OBJECTIVE

The following goals were kept in mind while designing


the new system:

i) To reduce the manual works required to be done in the


existing system.
ii) To avoid errors inherent in the manual works and hence
make the output consistent and correct.
iii) To improve the management of permanent information of
the company by keeping it is properly structured tables
and to provide facilities to update this information as
efficient as possible.
iv) To make the system complete menu-driven and hence
user-friendly. This is necessary so that even non-
programmers could use the system effectively and
system could act as catalyst in achieving objective.
v) To make the systems compatibility i.e. it should “fit in”
in the total, integrated system.
vi) To design the system in such a way that reduces feature
maintenance and enhancement times and efforts.
vii) To make the system reliable, understandable and cost
effective.

62 | P a g e
PROJECT MODULES

System has several modules namely:


Module 1:

Registration module, which is further sub-divided into:-

• Job Seeker Registration.

• Recruiter’s Registration.

• Change Password Job Seeker.

• Change Password Recruiter’s.

• Login for both Job Seeker and Recruiter’s.

Module 2:
Job Seeker Administration section, which is further sub-divided into –

• Resume Registration under Vacancy Category.

• Resume Updating

• Search for Job according to his skill set.

• Schedule interview

• Feedback

Module 3:
Recruiter’s Administration section, which is further sub-divided into four
subs-Sections: -

•Register Vacancy.

•Update Vacancy.

63 | P a g e
Chapter 8
Data Flow Diagram

0th Level DFD’s


DFD For Job Portal

2. Admin

Login Process
1. Job Seeker

3. Employer

64 | P a g e
1st Level DFD’s
DFD For New Job Seeker Creation

Job Seeker Registration


Details Details

Insert New Check for


Job Seeker Verify Data Registration Verify Data
Details

Insert

Job
Seeker

65 | P a g e
DFD For New Job Seeker Creation

Job Provider Registration


Details Details

Insert New Check for


Job Provider Verify Data Registration Verify Data
Details

Insert

Job
Provider

66 | P a g e
DFD For New Job Search and Book Schedule

Registration Search
Job Seeker Details
Details Job
Details

Check for
Insert New Verify Data Check For
Verify Data Registration Verify Data
Job Seeker Job

Check For
Interview Scheduling

edule
Time

Schedule

Verify Data

Job Seeker
Insert Details

67 | P a g e
2nd Level DFD’s
DFD For New Recruitment Creation

Designation Job Provider


Job Seeker Type Details
Details Details

Insert New Verify Data


Check
Job Seeker for Verify Data Verify Data
Designa

Check for
Job Provider

Check for Job


Seeker Info

Check for Type Check for


Verify Data Verify Data Status Verify Data

Job Provider Job Seeker


Job Seeker Details
Details Status Details

Insert

68 | P a g e
Job Seeker
Details

69 | P a g e
3rd Level DFD’S

DFD For New Recruitment Creation


Job Provider Details
Job Seeker Details Designation Type
Details

Request for new Validate Prod-


Job Seeker Generate Emp-Id Validate Desg-Id
() () Id ()

Validate Prod- Validate Job-Seek-Id ()


Commit () Status-ID ()

Database
Updated
Job Provider Status Details Job Seeker status Details
Job Seeker Details

70 | P a g e
Chapter 9
ER-DIAGRAM
Entity Relationship Diagram

71 | P a g e
Chapter 10
Data Structure of
Table
TABLES
USER LOGIN TABLE

72 | P a g e
FEEDBACK TABLE

USER QUALIFICATION TABLE

73 | P a g e
USER RESUME TABLE

JOBSEEKER TABLE

74 | P a g e
KEY SKILL TABLE

POSTED JOB TABLE

75 | P a g e
SCIDULING INTERVIEW

76 | P a g e
CHAPTER 11
CODING
CODE EFFICIENCCY

In an effort tomaintain computational efficiency and to allow


the eventual adaptation of the algorithm to face tracking
applications intense optimization of the code has been
performed. Although further developmentis in progress,
the algorithm is currently fast and compact enough to
run interactively on most generic platforms.
Additionally, we utilized special programming techniques
to reduce the run-time. For instance, repeaters and
data grids are used to bind information retrieved from
database in a fast and accurate manner.
The efficiency of the code allows a company details to
be found within one second. Thus, it can be
determined that coding done in this project is very
efficient.

OPTIMISATION OF CODE
Optimization refers to increase in the throughput of the
system with minimal use of effort and system
resources. It also includes faster response through
better system design practices including optimal

77 | P a g e
utilization of code, normalized database structures and
their use in the code.
The very first instance that stands for optimization of
this application is that it would prove to be most
favorable and best possible for the progress in the
working of the company.
This system is optimized because all the modules are
more cohesive that the connectivity among the modules
is less. So that it will take less time to complete any
process. As the modules are less dependent on each
other so in future if we want to make any changes in
our system then it will be very easy to
change system and we have to make changes only on
those modules that we have to change. If our system
will not be cohesive then in this case it
will take more time to complete any process and the
efficiency of the system to do work will be poor.
The other criteria that ensure the optimization of this
software application are enlisted as under:-
Use of modular design structure of application
development.
Use of Normalized Database Structures-Database
Optimization.
Use of code modules extensively-Code Optimization.
Use of minimum number of code lines for maximum
processing of input data.
We find optimal solution of a project that is cost
effective as well as time effective. Both are equally
important for a project we divide the project into
modules so that we can easily understand the project.
And also it will take less time to solve the problems.
Modularity is the single attribute of software that
allows a program to be intellectually manageable.

CODING
--------------------------------------------------------------------------------------------------------------------------
HOME PAGE-FRONT PAGE
--------------------------------------------------------------------------------------------------------------------------

78 | P a g e
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Index.aspx.cs"
Inherits="_Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"


"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

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


<head runat="server">
<title>Job Portal</title>
<style type="text/css">
.style1
{
height: 14px;
width: 111px;
}
.style2
{
width: 111px;
}
.style3
{
width: 90px;
}
</style>
</head>
<body >
<form id="form1" runat="server">
<div style=" background-color: #00475D" >
<TABLE WIDTH=957 BORDER=0 align="center" CELLPADDING=0 CELLSPACING=0 >
<TR>
<TD COLSPAN=26>
<IMG SRC="images/Job-Portal-link_01.jpg" WIDTH=957 HEIGHT=18
ALT=""></TD>
</TR>
<TR>
<TD COLSPAN=12 ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_02.jpg" WIDTH=533 HEIGHT=49
ALT=""></TD>

<TD COLSPAN=5 style="height: 14px"><a href="EmpLogin.aspx"><IMG SRC="images/Job-Portal-


link_03.jpg" ALT="" WIDTH=139 HEIGHT=14 border="0"></a></TD>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_04.jpg" WIDTH=12 HEIGHT=49
ALT=""></TD>

<TD COLSPAN=4 style="height: 14px"><a href="Login.aspx"><IMG SRC="images/Job-Portal-


link_05.jpg" ALT="" WIDTH=155 HEIGHT=14 border="0"></a></TD>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_06.jpg" WIDTH=12 HEIGHT=49
ALT=""></TD>

<TD class="style1">
<a href="AdminLogin.aspx"><b style="color: #FFFFFF">Admin login </b></a></TD>

79 | P a g e
<TD COLSPAN=2 ROWSPAN=4>
<IMG SRC="images/Job-Portal-link_08.jpg" WIDTH=20 HEIGHT=91
ALT=""></TD>
</TR>
<TR>
<TD COLSPAN=5>
<IMG SRC="images/Job-Portal-link_09.jpg" WIDTH=139 HEIGHT=35
ALT=""></TD>
<TD COLSPAN=4>
<IMG SRC="images/Job-Portal-link_10.jpg" WIDTH=155 HEIGHT=35
ALT=""></TD>
<TD class="style2">
<IMG SRC="images/Job-Portal-link_11.jpg" WIDTH=86 HEIGHT=35
ALT=""></TD>
</TR>
<TR>
<TD ROWSPAN=7>
<IMG SRC="images/Job-Portal-link_12.jpg" WIDTH=280 HEIGHT=570
ALT=""></TD>

<TD COLSPAN=5 style="height: 22px"><a href="JobSearch.aspx"><IMG SRC="images/Job-Portal-


link_15.jpg" ALT="" WIDTH=120 HEIGHT=22 border="0"></a></TD>
<TD COLSPAN=2 ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_14.jpg" WIDTH=45 HEIGHT=42
ALT=""></TD>

<TD COLSPAN=5 style="height: 22px">&nbsp;</TD>


<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_16.jpg" WIDTH=36 HEIGHT=42
ALT=""></TD>

<TD COLSPAN=6 style="height: 22px">&nbsp;</TD>


<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_18.jpg" WIDTH=30 HEIGHT=42
ALT=""></TD>

<TD COLSPAN=3 style="height: 22px">&nbsp;</TD>


</TR>
<TR>
<TD COLSPAN=5>
<IMG SRC="images/Job-Portal-link_20.jpg" WIDTH=118 HEIGHT=20
ALT=""></TD>
<TD COLSPAN=5>
<IMG SRC="images/Job-Portal-link_21.jpg" WIDTH=120 HEIGHT=20
ALT=""></TD>
<TD COLSPAN=6>
<IMG SRC="images/Job-Portal-link_22.jpg" WIDTH=188 HEIGHT=20
ALT=""></TD>
<TD COLSPAN=3>
<IMG SRC="images/Job-Portal-link_23.jpg" WIDTH=120 HEIGHT=20
ALT=""></TD>
</TR>

80 | P a g e
<TR>
<TD ROWSPAN=5 style="width: 19px">
<IMG SRC="images/Job-Portal-link_24.jpg" WIDTH=18 HEIGHT=527
ALT=""></TD>

<TD COLSPAN=5>&nbsp;</TD>
<TD COLSPAN=2>
&nbsp;</TD>

<TD COLSPAN=5>&nbsp;</TD>
<TD COLSPAN=2>
&nbsp;</TD>

<TD COLSPAN=3>&nbsp;</TD>
<TD>
&nbsp;</TD>

<TD COLSPAN=5>&nbsp;</TD>
<TD>
<IMG SRC="images/Job-Portal-link_32.jpg" WIDTH=11 HEIGHT=32
ALT=""></TD>
</TR>
<TR>
<TD COLSPAN=24>
<IMG SRC="images/Job-Portal-link_33.gif" WIDTH=659 HEIGHT=366
ALT=""></TD>
</TR>
<TR>
<TD COLSPAN=24>
&nbsp;</TD>
</TR>
<TR>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_35.jpg" WIDTH=9 HEIGHT=26
ALT=""></TD>

<TD><a href="JobSearch.aspx"><IMG SRC="images/Job-Portal-link_36.jpg" ALT="" WIDTH=52


HEIGHT=17 border="0"></a></TD>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_37.jpg" WIDTH=9 HEIGHT=26
ALT=""></TD>

<TD><a href="JobSearch.aspx"><IMG SRC="images/Job-Portal-link_38.jpg" ALT="" WIDTH=30


HEIGHT=17 border="0"></a></TD>

<TD COLSPAN=4><a href="JobSearch.aspx"><IMG SRC="images/Job-Portal-link_39.jpg" ALT=""


WIDTH=115 HEIGHT=17 border="0"></a></TD>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_40.jpg" WIDTH=11 HEIGHT=26
ALT=""></TD>

81 | P a g e
<TD COLSPAN=3><a href="JobSearch.aspx"><IMG SRC="images/Job-Portal-link_41.jpg"
ALT="" WIDTH=75 HEIGHT=17 border="0" style="height: 17px"></a></TD>
<TD ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_42.jpg" WIDTH=8 HEIGHT=26
ALT=""></TD>

<TD COLSPAN=2><a href="FeedBack.aspx"><IMG SRC="images/Job-Portal-link_43.gif" ALT=""


WIDTH=65 HEIGHT=17 border="0"></a></TD>
<TD COLSPAN=9 ROWSPAN=2>
<IMG SRC="images/Job-Portal-link_44.jpg" WIDTH=285 HEIGHT=26
ALT=""></TD>
</TR>
<TR>
<TD>
<IMG SRC="images/Job-Portal-link_45.jpg" WIDTH=52 HEIGHT=9
ALT=""></TD>
<TD COLSPAN=5>
<IMG SRC="images/Job-Portal-link_46.jpg" WIDTH=145 HEIGHT=9
ALT=""></TD>
<TD COLSPAN=3>
<IMG SRC="images/Job-Portal-link_47.jpg" WIDTH=75 HEIGHT=9
ALT=""></TD>
<TD COLSPAN=2>
<IMG SRC="images/Job-Portal-link_48.jpg" WIDTH=65 HEIGHT=9
ALT=""></TD>
</TR>
<TR>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=280 HEIGHT=1 ALT=""></TD>
<TD style="width: 19px">
<IMG SRC="images/spacer.gif" WIDTH=18 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=9 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=52 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=9 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=30 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=36 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=9 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=12 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=58 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=11 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=9 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=30 HEIGHT=1 ALT=""></TD>

82 | P a g e
<TD>
<IMG SRC="images/spacer.gif" WIDTH=36 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=8 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=14 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=51 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=12 HEIGHT=1 ALT=""></TD>
<TD class="style3">
<IMG SRC="images/spacer.gif" WIDTH=86 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=17 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=30 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=22 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=12 HEIGHT=1 ALT=""></TD>
<TD class="style2">
<IMG SRC="images/spacer.gif" WIDTH=86 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=9 HEIGHT=1 ALT=""></TD>
<TD>
<IMG SRC="images/spacer.gif" WIDTH=11 HEIGHT=1 ALT=""></TD>
</TR>
</TABLE>
</div>
</form>
</body>
</html>

--------------------------------------------------------------------------------------------------------------------------
LOGIN PAGE-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------

using System;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;

public partial class Login : System.Web.UI.Page


{

83 | P a g e
protected void Page_Load(object sender, EventArgs e)
{
txtUID.Focus();
if (!IsPostBack)
{
Response.Buffer = true;
Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d);
Response.Expires = -1500;
Response.CacheControl = "no-cache";
Session["UserId"] = null;
Session["Type"] = null;
}
}
string str = ConfigurationManager.ConnectionStrings["ConnectionString"].ToString();
string user;
string pass;
protected void btnSubmit_Click(object sender, EventArgs e)
{
if (txtUID.Text != "" && txtPwd.Text != "")
{
SqlConnection con = new SqlConnection(str);
SqlCommand cmd = new SqlCommand("select * from UserLogin where UserId='" +
txtUID.Text + "' and Pwd='" + txtPwd.Text + "'", con);
con.Open();
SqlDataReader dr = cmd.ExecuteReader();
while (dr.Read())
{
user = Convert.ToString(dr[1]);
pass = Convert.ToString(dr[2]);
}
if (txtUID.Text == user && txtPwd.Text == pass)
{
Session["UserId"] = txtUID.Text;
Session["Type"]= txtPwd.Text;
Response.Redirect("JSHome.aspx");
}
else
{
lblMsg.Text = "Incorrect Login Id or Password.Try Again.";
txtUID.Text = "";
txtPwd.Text = "";
}
}
else
{
lblMsg.Text = "Please fill username and password";
}
}
protected void btnCancel_Click(object sender, EventArgs e)
{
Response.Redirect("Index.aspx");
}
protected void btnFP_Click(object sender, EventArgs e)

84 | P a g e
{
Response.Redirect("ForgotPwd.aspx?UserType=" + "JS");
}
}

--------------------------------------------------------------------------------------------------------------------------
PERSONAL DETAILS-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;
public partial class PersonalDetail : System.Web.UI.Page
{
string UId;
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
UId = Session["UserId"].ToString();
string ck = "select * from JobSeeker where UserId='" + UId + "'";

DataSet ds = new DataSet();


ds = myclass.Filldataset(ck);
if (ds.Tables[0].Rows.Count > 0)
{
txtFstName.Text = ds.Tables[0].Rows[0]["FName"].ToString();
txtLName.Text = ds.Tables[0].Rows[0]["LName"].ToString();
txtFName.Text = ds.Tables[0].Rows[0]["FatherName"].ToString();
txtCAddress.Text = ds.Tables[0].Rows[0]["CAddress"].ToString();
txtPAddress.Text = ds.Tables[0].Rows[0]["PAddress"].ToString();
txtMobile.Text = ds.Tables[0].Rows[0]["MobileNo"].ToString();
txtPhone.Text = ds.Tables[0].Rows[0]["PhoneNo"].ToString();
ddldate.SelectedItem.Text = "";
ddlmonth.SelectedItem.Text = "";
ddlyear.SelectedItem.Text = "";
btnSubmit.Text = "Update";
btnProfessional.Enabled = true;
btnQualification.Enabled = true;
}
else
{
btnProfessional.Enabled = false;
btnQualification.Enabled = false;
btnCancel.Enabled = false;
btnResume.Enabled = false;

85 | P a g e
}
}
}
protected void btnSubmit_Click(object sender, EventArgs e)
{
lblMsg.Text = " ";
string DOB = ddldate.SelectedItem.Text +" "+ddlmonth.SelectedItem.Text +" "+
ddlyear.SelectedItem.Text;
UId = Session["UserId"].ToString();
if (btnSubmit.Text == "Submit")
{
try
{
string str = "insert into
JobSeeker(UserId,FName,LName,DOB,FatherName,CAddress,PAddress,PhoneNo,MobileNo)" +
" values('" + UId + "','" + txtFstName.Text + "','"
+ txtLName.Text +
"','" + DOB + "','" + txtFName.Text + "','" +
txtCAddress.Text +
"','" + txtPAddress.Text + "','" + txtPhone.Text +
"','" + txtMobile.Text + "')";
myclass.executecmd(str);
clear();
lblMsg.Text = "Your Personal Details has been submitted successfully.";
btnQualification.Enabled = true;
btnCancel.Enabled = true;
}
catch (Exception err)
{
Response.Write(err.Message);
}
}
else if(btnSubmit.Text=="Update")
{
string str = "update JobSeeker set FName='" + txtFstName.Text + "',LName='" +
txtLName.Text + "',DOB='"+DOB+"',FatherName='" + txtFName.Text + "',CAddress='" +
txtCAddress.Text + "',PAddress='" + txtPAddress.Text + "',PhoneNo='" + txtPhone.Text +
"',MobileNo='" + txtMobile.Text + "' where UserId='" + Session["UserId"].ToString() +
"'";
myclass.executecmd(str);
lblMsg.Text = "Your Personal Details has been Updated successfully.";
clear();
}
}
protected void clear()
{
txtFstName.Text = string.Empty;
txtLName.Text = string.Empty;
txtFName.Text = string.Empty;
txtCAddress.Text = string.Empty;
txtPAddress.Text = string.Empty;
txtMobile.Text = string.Empty;
txtPhone.Text = string.Empty;

86 | P a g e
ddldate.SelectedIndex = 0;
ddlmonth.SelectedIndex = 0;
ddlyear.SelectedIndex = 0;

}
protected void btnCancel_Click(object sender, EventArgs e)
{
Response.Redirect("UpdateAcademicDetails.aspx");
}
protected void btnQualification_Click(object sender, EventArgs e)
{
Response.Redirect("UpdateAcademicDetails.aspx");
}
protected void btnProfessional_Click(object sender, EventArgs e)
{
Response.Redirect("UpdatePreEmpDetail.aspx");
}
protected void Button1_Click(object sender, EventArgs e)
{
Response.Redirect("RSummary.aspx");
}
}

--------------------------------------------------------------------------------------------------------------------------
EMPLOYER DETAILS-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;
using System.Data.SqlClient;

public partial class EmployerDetails : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
string s = "select * from Category ";
DataSet ds1 = new DataSet();
ds1 = myclass.Filldataset(s);
if(ds1.Tables[0].Rows.Count>0)
{
ddlCategory.DataSource = ds1;
ddlCategory.DataTextField = "Name";
ddlCategory.DataValueField = "CATID";

87 | P a g e
ddlCategory.DataBind();
}
string UId = Session["UserId"].ToString();
string str = "select
e.UserId,e.EmpName,e.ContactPerson,e.CAddress,e.PhoneNo,e.MobileNo,e.Type,e.Period,e.Rate
,e.PaidAmount,c.Name from Employer e inner Join Category c on e.CATID = c.CATID where
UserId='"+UId+"'";
DataSet ds = new DataSet();
ds = myclass.Filldataset(str);
if (ds.Tables[0].Rows.Count > 0)
{
ddlCategory.SelectedItem.Text = ds.Tables[0].Rows[0]["Name"].ToString();
ddlType.SelectedValue = ds.Tables[0].Rows[0]["Type"].ToString();
if (ddlType.SelectedItem.Text == "Paid")
{
Panel1.Visible = true;
txtrate.Text = ds.Tables[0].Rows[0]["Rate"].ToString();
txtAmount.Text = ds.Tables[0].Rows[0]["PaidAmount"].ToString();
ddlPeriod.SelectedItem.Text = ds.Tables[0].Rows[0]["Period"].ToString();
}
txtName.Text = ds.Tables[0].Rows[0]["EmpName"].ToString();
txtCAddress.Text = ds.Tables[0].Rows[0]["CAddress"].ToString();
txtConPerson.Text = ds.Tables[0].Rows[0]["ContactPerson"].ToString();
txtMobile.Text = ds.Tables[0].Rows[0]["MobileNo"].ToString();
txtPhone.Text = ds.Tables[0].Rows[0]["PhoneNo"].ToString();
btnSubmit.Text = "Update";
}

}
protected void btnSubmit_Click(object sender, EventArgs e)
{
string UId = Session["UserId"].ToString();
if (btnSubmit.Text == "Submit")
{
try
{
if (ddlType.SelectedItem.Text == "Paid")
{
if (ddlPeriod.SelectedIndex != 0)
{
string str = "insert into
Employer(UserId,EmpName,ContactPerson,CAddress,PhoneNo,MobileNo,Type,Period,Rate,PaidAmou
nt,CATID)" +
" values('" + UId + "','" +
txtName.Text.ToString().Replace("'", "''") + "','" + txtConPerson.Text +
"','" + txtCAddress.Text + "','" +
txtPhone.Text + "','" + txtMobile.Text +
"','" + ddlType.SelectedItem.Text + "','" +
ddlPeriod.SelectedItem.Text + "','" + txtrate.Text + "','" + txtAmount.Text + "','" +
ddlCategory.SelectedItem.Value + "')";

88 | P a g e
myclass.executecmd(str);
clear();
lblerrmsg.Text = "";
lblMsg.Text = "Your Profile has been Submitted successfully.";
}
else
{
lblerrmsg.Text = "Please Select Period for Payment";
}

}
if (ddlType.SelectedItem.Text == "Free")
{
string str = "insert into
Employer(UserId,EmpName,ContactPerson,CAddress,PhoneNo,MobileNo,Type,CATID)" +
" values('" + UId + "','" + txtName.Text + "','"
+ txtConPerson.Text +
"','" + txtCAddress.Text + "','" + txtPhone.Text
+ "','" + txtMobile.Text +
"','" + ddlType.SelectedItem.Text + "','" +
ddlCategory.SelectedItem.Value + "')";

myclass.executecmd(str);
clear();
lblerrmsg.Text = "";
lblMsg.Text = "Your Profile has been Submitted successfully.";
}

}
catch (Exception err)
{
Response.Write(err.Message);
}
}
else
{
RequiredFieldValidator1.Enabled = false;
RequiredFieldValidator2.Enabled = false;
try
{
if (ddlType.SelectedItem.Text == "Paid")
{
//if (ddlPeriod.SelectedIndex != 0)
//{
string str = "update Employer set
EmpName='"+txtName.Text.ToString().Replace("'","''")
+"',ContactPerson='"+txtConPerson.Text+"',CAddress='"+txtCAddress.Text+"',PhoneNo='"+txtP
hone.Text+"',MobileNo='"+txtMobile.Text+"',Type='"+ddlType.SelectedItem.Text+"',Period='"
+ddlPeriod.SelectedItem.Text+"',Rate='"+txtrate.Text+"',PaidAmount='"+txtAmount.Text+"',C
ATID='"+ddlCategory.SelectedItem.Value+"' where UserId='"+UId+"'";
myclass.executecmd(str);
clear();
lblerrmsg.Text = "";

89 | P a g e
Response.Redirect("ViewEmpDetail.aspx");
//lblMsg.Text = "Your Profile has been Updated successfully.";
//}
//else
//{
//lblerrmsg.Text = "Please Select Period for Payment";
//}

}
if (ddlType.SelectedItem.Text == "Free")
{

string str = "update Employer set EmpName='" +


txtName.Text.ToString().Replace("'", "''") + "',ContactPerson='" + txtConPerson.Text +
"',CAddress='" + txtCAddress.Text + "',PhoneNo='" + txtPhone.Text + "',MobileNo='" +
txtMobile.Text + "',Type='" + ddlType.SelectedItem.Text + "' ,CATID='" +
ddlCategory.SelectedItem.Value + "'where UserId='"+UId+"'";
myclass.executecmd(str);
clear();

Response.Redirect("ViewEmpDetail.aspx");
//lblMsg.Text = "Your Profile has been Updated successfully.";
}

}
catch (Exception err)
{
Response.Write(err.Message);
}
}
}
protected void btnCancel_Click(object sender, EventArgs e)
{
Response.Redirect("Index.aspx");
}
protected void btnReset_Click(object sender, EventArgs e)
{

clear();
}

public void clear()


{
ddlCategory.SelectedIndex = 0;
ddlType.SelectedIndex = 0;
ddlPeriod.SelectedIndex = 0;
txtName.Text = string.Empty;
txtAmount.Text = string.Empty;
txtCAddress.Text = string.Empty;
txtConPerson.Text = string.Empty;
txtMobile.Text = string.Empty;
txtPhone.Text = string.Empty;
txtrate.Text = string.Empty;

90 | P a g e
}
protected void TextBox2_TextChanged(object sender, EventArgs e)
{

}
protected void ddlType_SelectedIndexChanged(object sender, EventArgs e)
{
if (ddlType.SelectedItem.Text == "Paid")
{
Panel1.Visible = true;
}
else if(ddlType.SelectedItem.Text=="Free")
{
Panel1.Visible = false;
}
}

protected void ddlPeriod_SelectedIndexChanged(object sender, EventArgs e)


{
string str = "select Rate From Rate where
Period='"+ddlPeriod.SelectedItem.Text+"'";
DataSet ds = new DataSet();
ds=myclass.Filldataset(str);
if (ds.Tables[0].Rows.Count > 0)
{
txtrate.Text = ds.Tables[0].Rows[0]["Rate"].ToString();
}

}
}

--------------------------------------------------------------------------------------------------------------------------
JOB SEARCH AND INTERVIEW SCHEDULING -CODE PAGE
--------------------------------------------------------------------------------------------------------------------------
using System;
using System.Data;

91 | P a g e
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;
using System.Net;
using System.Net.Mail;

public partial class JobSearch : System.Web.UI.Page


{
string strQuery,cat,keyskill,exp,title,loc,closingdate,timeslot,dropdown;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
if (Session["UserId"] == null)
{
gvJSearch.Columns[7].Visible = false;
}
// automatically show data in gridview
if (!IsPostBack)
{

strQuery = "select CATID,[Name] from Category";


ds = new DataSet();
ds = myclass.Filldataset(strQuery);
ddlCat.DataSource = ds;
ddlCat.DataTextField = "Name";
ddlCat.DataValueField = "CATID";
ddlCat.DataBind();
ddlCat.Items.Insert(0, "-- Select --");

ddlKSkill.Items.Insert(0, "-- Select --");

strQuery = "select LOCID,LocName from Location where IsActive='1'";


ds = new DataSet();
ds = myclass.Filldataset(strQuery);
ddlLoc.DataSource = ds;
ddlLoc.DataTextField = "LocName";
ddlLoc.DataValueField = "LOCID";

92 | P a g e
ddlLoc.DataBind();
ddlLoc.Items.Insert(0, "-- Select --");

strQuery = "select c.[name] as


Category,e.EmpName,p.UserId,p.PJID,p.JobTitle,p.KeySkill,p.ReqExp as Experience,"+
"l.LocName as Location,q.Qualification,p.Description,p.ClosingDate from
PostedJob p"+
" inner join Category c on p.CATID = C.CATID inner join Location l on "+
"p.LOCID = l.LOCID inner join Qualification q on p.QUAID=q.QUAID inner
Join Employer e on p.UserId=e.UserId ";
/*'strQuery1="Select Company"*/
ds = new DataSet();
ds = myclass.Filldataset(strQuery);
gvJSearch.DataSource = ds;
gvJSearch.DataBind();
}
}

// for select Category


protected void ddlCat_SelectedIndexChanged(object sender, EventArgs e)
{
if (ddlCat.SelectedIndex != 0)
{
strQuery = "select KSID,KeySkill from KeySkill where CATID='" +
ddlCat.SelectedValue.ToString() + "'";
ds = new DataSet();
ds = myclass.Filldataset(strQuery);
ddlKSkill.DataSource = ds;
ddlKSkill.DataTextField = "KeySkill";
ddlKSkill.DataValueField = "KSID";
ddlKSkill.DataBind();
}
else
{
ddlKSkill.Items.Clear();
ddlKSkill.Items.Insert(0, "-- Select --");
}
}

//for Search button


protected void SearchBtn_Click(object sender, EventArgs e)
{

93 | P a g e
strQuery = "select c.[name] as
Category,p.UserId,e.EmpName,p.JobTitle,p.PJID,p.KeySkill,p.ReqExp as Experience," +
"l.LocName as Location,q.Qualification,p.Description,p.ClosingDate from
PostedJob p" +
" inner join Category c on p.CATID = C.CATID inner join Location l on " +
"p.LOCID = l.LOCID inner join Qualification q on p.QUAID=q.QUAID inner
Join Employer e on p.UserId=e.UserId ";
if (ddlCat.SelectedIndex != 0)
{
cat = "where p.CATID = '" + ddlCat.SelectedValue.ToString() + "'";
}
else
{
cat = "where p.CATID is not null";
}
if (ddlKSkill.SelectedIndex > 0)
{
keyskill = " and p.KeySkill like '%" + ddlKSkill.SelectedItem.Text + "%'";
}
else
{
keyskill = " and p.KeySkill like '%%'";
}
if (ddlEYr.SelectedIndex > 0 && ddlEMon.SelectedIndex > 0)
{
exp = " and p.ReqExp like '%" + ddlEYr.SelectedItem.Text + "." +
ddlEMon.SelectedItem.Text + "%' or p.ReqExp <= convert(float,'" + ddlEYr.SelectedItem.Text +
"." + ddlEMon.SelectedItem.Text + "')";
}
else if (ddlEYr.SelectedIndex > 0 && ddlEMon.SelectedIndex <= 0)
{
exp = " and p.ReqExp like '%" + ddlEYr.SelectedItem.Text + "%' or p.ReqExp <=
convert(float,'" + ddlEYr.SelectedItem.Text + "')";
}
else if (ddlEYr.SelectedIndex <= 0 && ddlEMon.SelectedIndex > 0)
{
exp = " and p.ReqExp like '%0." + ddlEMon.SelectedItem.Text + "%' or p.ReqExp <=
convert(float,'0." + ddlEMon.SelectedItem.Text + "')";
}
else
{
exp = " and p.ReqExp is not null";
}

94 | P a g e
if (txtJTitle.Text != "")
{
title = " and p.JobTitle like '%" + txtJTitle.Text.Trim() + "%'";
}
else
{
title = " and p.JobTitle like '%%'";
}
if (ddlLoc.SelectedIndex != 0)
{
loc = " and p.LOCID='" + ddlLoc.SelectedValue.ToString() + "'";
}
else
{
loc = " and p.LOCID is not null";
}
strQuery = strQuery + cat + keyskill + exp + title + loc;
ds = new DataSet();
ds = myclass.Filldataset(strQuery);
gvJSearch.DataSource = ds;
gvJSearch.DataBind();
}
protected void CancelBtn_Click(object sender, EventArgs e)
{

//for Back
protected void btnBack_Click(object sender, EventArgs e)
{
if (Session["UserId"] != null)
{
Response.Redirect("JSHome.aspx");
}
else
{
Response.Redirect("Index.aspx");
}
}

//for apply to specific job from gridview


protected void gvJSearch_RowCommand(object sender, GridViewCommandEventArgs e)
{

95 | P a g e
try
{
string value = e.CommandArgument.ToString();
if (e.CommandName == "Apply")
{
if (Session["UserId"] != null)
{
string str = "select
r.RHeading,r.KeySkill,r.TExp,r.ASalary,j.PhoneNo,j.MobileNo,j.FName,j.LName from
UserLogin u left outer join UserResume r on u.UserId=r.UserId left Outer Join JobSeeker j on
u.UserId=j.UserId where u.UserId='" + Session["UserId"].ToString() + "'";
ds = new DataSet();
ds = myclass.Filldataset(str);
//string Uemail = ds.Tables[0].Rows[0]["EmailId"].ToString();
string RHeading = ds.Tables[0].Rows[0]["RHeading"].ToString();
string phone = ds.Tables[0].Rows[0]["PhoneNo"].ToString();
string mobile = ds.Tables[0].Rows[0]["MobileNo"].ToString();
string Key = ds.Tables[0].Rows[0]["KeySkill"].ToString();
string Exp = ds.Tables[0].Rows[0]["TExp"].ToString();
string CTC = ds.Tables[0].Rows[0]["ASalary"].ToString();
string JSName = ds.Tables[0].Rows[0]["FName"].ToString() + " " +
ds.Tables[0].Rows[0]["LName"].ToString();
string str1 = "select e.EmpName,p.JobTitle,p.UserId,p.PJID,p.ClosingDate from
PostedJob p left outer Join Employer e on p.UserId=e.UserId left outer join UserLogin u on
p.UserId=u.UserId where p.PJID='" + value + "'";
DataTable dt = new DataTable();
dt = myclass.filldatatable(str1);
string name = dt.Rows[0]["EmpName"].ToString();
//string email = dt.Rows[0]["EmailId"].ToString();
string position = dt.Rows[0]["JobTitle"].ToString();
string EmpId = dt.Rows[0]["UserId"].ToString();
string PJID = dt.Rows[0]["PJID"].ToString();
string closingdate = dt.Rows[0]["ClosingDate"].ToString();
/*string timeslot = gvJSearch.TemplateControl(ddlslot)*/
string msg = "<p>Hello Sir,</br></p>";
//msg = msg + "<p>This is refering to Job Id :" + " " + value + "<Br/>";
//msg = msg + "Please Consider this Resume for the same if it matches your
requirements.<br/><br/>";
//msg = msg + "Resume Heading: " + " " + RHeading + "<br/>" + "Name :" + " " +
JSName + "<br/>" + "Applied For:" + " " + position + "<br/>" + "KeySkills :" + " " + Key +
"<br/>" + "Total Experience :" + " " + Exp + "<br/>" + "Expected CTC :" + " " + CTC + "<br/>"
+ "Email Id :" + " " + Uemail + "<br/>" + "Mobile No. :" + " " + mobile + "<br/>" + "Another

96 | P a g e
Phone No.:" + " " + phone + " <br/><br/>" + "Thanking You<br/>" + "Regards<br/>" + " " +
name + "</p>";
//MailMessage mail = new MailMessage();
//NetworkCredential cred = new NetworkCredential("mamtashailey@gmail.com",
"HrithikRoshan");
//mail.To.Add(email);
//mail.Subject = RHeading;
//mail.From = new MailAddress(Uemail);
//mail.IsBodyHtml = true;
//mail.Body = msg;
//SmtpClient smtp = new SmtpClient("smtp.gmail.com");
//smtp.UseDefaultCredentials = false;
//smtp.EnableSsl = true;
//smtp.Credentials = cred;
//smtp.Port = 587;
//smtp.Send(mail);

for (int i = 0; i < gvJSearch.Rows.Count; i++)


{

DropDownList dropdown =
(DropDownList)gvJSearch.Rows[0].Cells[7].FindControl("ddlslot");
string query = "insert into
JobApplication1(UserId,EmpId,PJID,ClosingDate,TimeSlot,AplDate,IsActive) values('" +
Session["UserId"] + "','" + EmpId + "','" + PJID + "','" + closingdate + "','" +
dropdown.SelectedItem.Text + "','" + DateTime.Now.ToString("yyyy-MM-dd h:m:s") + "','1') ";
myclass.executecmd(query);
}
Label1.Text = "Your Application has been sent successfully to" + " " + name;
}
}
}
catch(Exception err)
{
Label1.Text=err.Message;
}
}

protected void f1_Load(object sender, EventArgs e)


{

}
protected void gvJSearch_SelectedIndexChanged(object sender, EventArgs e)

97 | P a g e
{

}
}

--------------------------------------------------------------------------------------------------------------------------
CHANGE PASSWORD PAGE-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;

public partial class ChangePwdEmployer : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
if (Session["Admin"] != null)
{
// DropDownList1.Visible = false;
}
}
protected void SubmitBtn_Click(object sender, EventArgs e)
{
if (txtPrePwd.Text != txtNewPwd.Text)
{
if (txtNewPwd.Text == txtConPwd.Text)
{
string str = "update UserLogin set Pwd ='" + txtNewPwd.Text + "' where Pwd='" +
txtPrePwd.Text + "' and Type='EM'";
myclass.executecmd(str);
lblErrMsg.Text = string.Empty;
lblMsg.Text = "Password Updated Successfully.";
clear();
}

98 | P a g e
else
{
lblErrMsg.Text = "Passwords not Matching.Please Type Correctly";
}
}
else
{
lblErrMsg.Text = "New Password and Existing Password are same.";
}
}
public void clear()
{
txtNewPwd.Text = string.Empty;
txtPrePwd.Text = string.Empty;
txtConPwd.Text = string.Empty;
}
}

--------------------------------------------------------------------------------------------------------------------------
FEEDBACK PAGE-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;

public partial class FeedBack : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void SubmitBtn_Click(object sender, EventArgs e)

99 | P a g e
{
string userid=Session["UserId"].ToString();
string str = "insert into FeedBack(UserId,FeedBack) values('" + userid + "','" +
txtfeedback.Text + "')";
myclass.executecmd(str);
lblmsg.Text = "Feedback sent successfully";
txtfeedback.Text = string.Empty;

}
protected void CancelBtn_Click(object sender, EventArgs e)
{

}
}

--------------------------------------------------------------------------------------------------------------------------
JOBSEEKER’S DETAILS-CODE PAGE
--------------------------------------------------------------------------------------------------------------------------

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using Classes;

public partial class ViewJSDetail : System.Web.UI.Page


{
string strQuery, str,userid;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
if (Session["Admin"] != null)
{

100 | P a g e
DetailsView1.Fields[7].Visible = false;
DetailsView2.Fields[6].Visible = false;
btnEdit.Visible = false;
btnEditProf.Visible = false;

}
if (!IsPostBack)
{

if (Request.QueryString["UserId"] != null)
{
userid = Request.QueryString["UserId"];
}
else
{
userid = Session["UserId"].ToString();
}
BindDetailsView1();

BindDetailsView2();

string str2 = "select q.Percentage,q.PassYear,ql.Qualification,s.Specialisation,c.[Name]


from UserQualification q Inner Join Qualification ql on q.QUAID=ql.QUAID inner Join
Specialisation s on q.SPID=s.SPID inner Join College c on q.COLID=c.COLID where
q.UserId='" + userid + "'";
DataSet dsq = new DataSet();
dsq = myclass.Filldataset(str2);
if (dsq.Tables[0].Rows.Count > 0)
{
GridView1.DataSource = dsq;
GridView1.DataBind();
}
else
{
btnEdit.Visible = false;
GridView1.DataSource = dsq;
GridView1.DataBind();
}

string str3 = "select e.UEmployer,c.[Name],r.[Role],e.Designation,e.ReleventExp from


UEmployerHist e inner Join Category c on e.CATID=c.CATID inner Join [Role] r on
e.RID=r.RID where e.UserId='" + userid + "'";

101 | P a g e
DataSet emds = new DataSet();
emds = myclass.Filldataset(str3);
if( emds.Tables[0].Rows.Count>0)
{
GridView2.DataSource = emds;
GridView2.DataBind();
}
else
{
btnEditProf.Visible = false;
GridView2.DataSource = emds;
GridView2.DataBind();
}
}
}
protected void BindDetailsView1()
{
if (Request.QueryString["UserId"] != null)
{

userid = Request.QueryString["UserId"];
}
else
{
userid = Session["UserId"].ToString();
}

if (Request.QueryString["UserId"] != null || Session["UserId"]!=null)


{

string str = "Select UserId,FName,LName,CAddress,PAddress,PhoneNo,MobileNo From


JobSeeker where UserId='" +userid + "'";
DataSet ds = new DataSet();
ds = myclass.Filldataset(str);
if (ds.Tables[0].Rows.Count > 0)
{
string name = ds.Tables[0].Rows[0]["FName"].ToString() + " " + ds.Tables[0].Rows[0]
["LName"].ToString();
Label1.Text = name;
}
DetailsView1.DataSource = ds;
DetailsView1.DataBind();
}

102 | P a g e
}
protected void BindDetailsView2()
{
if (Request.QueryString["UserId"] != null)
{
userid = Request.QueryString["UserId"];
}
else
{
userid = Session["UserId"].ToString();
}
string str1 = "select r.UserId,r.KeySkill,r.TExp,r.ASalary,r.RHeading,c.Name from
UserResume r inner Join Category c on r.CATID=c.CATID where r.UserId='" + userid + "'";
DataSet ds1 = new DataSet();
ds1 = myclass.Filldataset(str1);
DetailsView2.DataSource = ds1;
if (ds1.Tables[0].Rows.Count> 0)
{
DetailsView2.DataBind();
}

//ViewState["CatName"] = ds1.Tables[0].Rows[0]["Name"].ToString();
}
protected void DetailsView1_ModeChanging(object sender, DetailsViewModeEventArgs e)
{
if (DetailsView1.CurrentMode != DetailsViewMode.Edit)
{
e.Cancel = true;
}
BindDetailsView1();
}
protected void DetailsView1_ItemUpdating(object sender, DetailsViewUpdateEventArgs e)
{
string userid = DetailsView1.Rows[0].Cells[1].Text;
TextBox txtFName = (TextBox)DetailsView1.Rows[1].Cells[1].Controls[0];
TextBox txtLName = (TextBox)DetailsView1.Rows[2].Cells[1].Controls[0];
TextBox txtCAddr = (TextBox)DetailsView1.Rows[3].Cells[1].Controls[0];
TextBox txtPAddr = (TextBox)DetailsView1.Rows[4].Cells[1].Controls[0];
TextBox txtPhone = (TextBox)DetailsView1.Rows[5].Cells[1].Controls[0];
TextBox txtMobile = (TextBox)DetailsView1.Rows[6].Cells[1].Controls[0];
#region with Parameter
#endregion

103 | P a g e
strQuery = "UPDATE JobSeeker SET FName = '" + txtFName.Text + "', LName= '" +
txtLName.Text + "', CAddress='" + txtCAddr.Text + "', PAddress='" + txtPAddr.Text +
"',PhoneNo='" + txtPhone.Text + "',MobileNo='" + txtMobile.Text + "' WHERE (UserId = '" +
userid + "')";
myclass.executecmd(strQuery);
DetailsView1.ChangeMode(DetailsViewMode.ReadOnly);
BindDetailsView1();
}
protected void DetailsView1_PageIndexChanging(object sender, DetailsViewPageEventArgs
e)
{
DetailsView1.PageIndex = e.NewPageIndex;
BindDetailsView1();
}
protected void DetailsView1_ItemCommand(object sender, DetailsViewCommandEventArgs
e)
{
//if (e.CommandName.Equals("New"))
//{
// DetailsView1.ChangeMode(DetailsViewMode.Insert);
// BindDetailsView1();
//}
//else
if (e.CommandName.Equals("Cancel"))
{
DetailsView1.ChangeMode(DetailsViewMode.ReadOnly);
BindDetailsView1();
}
else if (e.CommandName.Equals("Edit"))
{
DetailsView1.ChangeMode(DetailsViewMode.Edit);
BindDetailsView1();
}
}
protected void DetailsView2_ItemCommand(object sender, DetailsViewCommandEventArgs
e)
{
if (e.CommandName.Equals("Cancel"))
{
DetailsView2.ChangeMode(DetailsViewMode.ReadOnly);
BindDetailsView1();
}
else if (e.CommandName.Equals("Edit"))

104 | P a g e
{
DetailsView2.ChangeMode(DetailsViewMode.Edit);
BindDetailsView1();
}
else if (e.CommandName == "Resume")
{
//string val = DetailsView2.DataKey["UserId"].ToString();
string value = e.CommandArgument.ToString();
str = "select Resume from UserResume where UserId='" + value + "'";
ds = new DataSet();
ds = myclass.Filldataset(str);
byte[] bytFile = (byte[])ds.Tables[0].Rows[0]["Resume"];
Response.Clear();
Response.Buffer = true;

Response.ContentType = "application/vnd.ms-word";
Response.AddHeader("content-disposition", "attachment;filename=Resume.doc");
Response.Charset = "";
Response.Cache.SetCacheability(HttpCacheability.Private);
Response.BinaryWrite(bytFile);
Response.End();
}
}
protected void DetailsView2_ItemUpdating(object sender, DetailsViewUpdateEventArgs e)
{
string userid = DetailsView2.DataKey["UserId"].ToString();
DropDownList ddlCat = (DropDownList)DetailsView2.FindControl("ddlCategroy");
ListBox lbKS = (ListBox)DetailsView2.FindControl("lbKeySkill");
string keys = "";
//for multiple key skill concatination into a single variable
for (int i = 0; i <lbKS.Items.Count; i++)
{
if (lbKS.Items[i].Selected == true)
{
if (keys == "")
{
keys = lbKS.Items[i].Text;
}
else
{
keys = keys + "," + lbKS.Items[i].Text;
}
}

105 | P a g e
}

DropDownList ddlEIY = (DropDownList)DetailsView2.FindControl("ddlTYr");


DropDownList ddlEIM = (DropDownList)DetailsView2.FindControl("ddlTMon");
DropDownList ddlASL = (DropDownList)DetailsView2.FindControl("ddlASL");
DropDownList ddlAST = (DropDownList)DetailsView2.FindControl("ddlAST");
TextBox txtRHead = (TextBox)DetailsView2.Rows[4].Cells[1].Controls[0];

strQuery = "UPDATE UserResume SET CATID= '" + ddlCat.SelectedValue.ToString() +


"', KeySkill='" + keys + "', TExp='" + ddlEIY.SelectedValue.ToString() + "." +
ddlEIM.SelectedValue.ToString() +
"',ASalary='" + ddlASL.SelectedValue.ToString() + "." +
ddlAST.SelectedValue.ToString() + "',RHeading='" + txtRHead.Text + "' WHERE (UserId = '" +
userid + "')";
myclass.executecmd(strQuery);
DetailsView2.ChangeMode(DetailsViewMode.ReadOnly);
BindDetailsView2();
}
protected void DetailsView2_ModeChanging(object sender, DetailsViewModeEventArgs e)
{
if (DetailsView2.CurrentMode != DetailsViewMode.Edit)
{
e.Cancel = true;
}
BindDetailsView2();
}
protected void DetailsView2_PageIndexChanging(object sender, DetailsViewPageEventArgs
e)
{
DetailsView2.PageIndex = e.NewPageIndex;
BindDetailsView2();
}
protected void DetailsView2_DataBinding(object sender, EventArgs e)
{

protected void DetailsView2_ItemCreated1(object sender, EventArgs e)


{
if (DetailsView2.CurrentMode == DetailsViewMode.Edit)
{
strQuery = "Select CATID,Name from Category";
DataSet ds = new DataSet();

106 | P a g e
ds = myclass.Filldataset(strQuery);
DropDownList ddl = new DropDownList();
ddl = (DropDownList)DetailsView2.FindControl("ddlCategroy");
ddl.DataSource = ds;
ddl.DataTextField = "Name";
ddl.DataValueField = "CATID";
//ddl.SelectedItem.Text = (string) ViewState["CatName"];
ddl.DataBind();

strQuery = "select KSID,KeySkill from Keyskill where CATID='" +


ddl.SelectedValue.ToString() + "'";
ds = new DataSet();
ds = myclass.Filldataset(strQuery);
ListBox lbKS = new ListBox();
lbKS = (ListBox)DetailsView2.FindControl("lbKeySkill");
lbKS.DataSource = ds;
lbKS.DataTextField = "KeySkill";
lbKS.DataValueField = "KSID";
lbKS.DataBind();
}
}
protected void DetailsView2_DataBound(object sender, EventArgs e)
{
if (DetailsView2.CurrentMode == DetailsViewMode.ReadOnly)
{
Label lbl =(Label) DetailsView2.Rows[0].Cells[1].Controls[0];
ViewState["CatName"] = lbl.Text;

Label lbl2 = (Label)DetailsView2.Rows[1].Cells[1].Controls[0];


string[] key = (lbl2.Text).Split(',');
ViewState["KeySkill"] = key;

Label lbl3 = (Label) DetailsView2.Rows[2].Cells[1].Controls[0];


string[] exp = (lbl3.Text).Split('.');
ViewState["ExpYr"] = exp[0];
ViewState["ExpMo"] = exp[1];
Label lbl4=(Label) DetailsView2.Rows[3].Cells[1].Controls[0];
string[] sal = (lbl4.Text).Split('.');
ViewState["ASL"] = sal[0];
ViewState["AST"] = sal[1];
}
if (DetailsView2.CurrentMode == DetailsViewMode.Edit)
{

107 | P a g e
DropDownList ddl = new DropDownList();
ddl = (DropDownList)DetailsView2.FindControl("ddlCategroy");
ddl.SelectedItem.Text = ViewState["CatName"].ToString();
DropDownList ddl2 = new DropDownList();
DropDownList ddl3 = new DropDownList();
ddl2 = (DropDownList)DetailsView2.FindControl("ddlTYr");
ddl3 = (DropDownList)DetailsView2.FindControl("ddlTMon");
ddl2.SelectedValue = ViewState["ExpYr"].ToString();
ddl3.SelectedValue = ViewState["ExpMo"].ToString();
ListBox keySkill = new ListBox();
keySkill = (ListBox)DetailsView2.FindControl("lbKeySkill");
string[] KSarr = (string[])ViewState["KeySkill"];
for (int i = 0; i < KSarr.Length; i++)
{
foreach (ListItem li in keySkill.Items)
{
if (li.Text == KSarr[i])
li.Selected = true;
}
}
DropDownList ddl4 = new DropDownList();
DropDownList ddl5 = new DropDownList();
ddl4 = (DropDownList)DetailsView2.FindControl("ddlASL");
ddl5 = (DropDownList)DetailsView2.FindControl("ddlAST");
ddl4.SelectedValue = ViewState["ASL"].ToString();
ddl5.SelectedValue = ViewState["AST"].ToString();
}
}
protected void btnEdit_Click(object sender, EventArgs e)
{
if (Request.QueryString["UserId"] != null)
{
userid = Request.QueryString["UserId"];
Response.Redirect("UpdateAcademicDetails.aspx?UserId=" + userid+"&"+"edit="+"1");
}
else
{
Response.Redirect("UpdateAcademicDetails.aspx?edit="+"1");
}
}
protected void btnEditProf_Click(object sender, EventArgs e)
{
if (Request.QueryString["UserId"] != null)

108 | P a g e
{
userid = Request.QueryString["UserId"];
Response.Redirect("UpdatePreEmpDetail.aspx?UserId=" + userid + "&" + "edit=" +
"1");
}
else
{
Response.Redirect("UpdateAcademicDetails.aspx?edit=" + "1");
}
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
Response.Redirect("JSHome.aspx");
}

CHAPTER 12
109 | P a g e
Output Screen

The following form are used


Home Page

Recruter ’s Login Page

110 | P a g e
111 | P a g e
Job Seeker’s Login Page

Jobseeker’s Home Page

112 | P a g e
Personal Details Page

113 | P a g e
114 | P a g e
Qualification Page

115 | P a g e
Professional Details Page

116 | P a g e
Resume Summary Page

117 | P a g e
Jobseeker’s Detail Page

118 | P a g e
Change Password Page

119 | P a g e
Job Search And Interview Scheduling Page

Employer’s Details Page

120 | P a g e
121 | P a g e
Employer’s Profile Page

Job Post Page

122 | P a g e
Posted Job Page

123 | P a g e
College List Page

124 | P a g e
Key Skill List Page

125 | P a g e
Add Location Page

126 | P a g e
ADD Qualification Page

127 | P a g e
128 | P a g e
User Feedback

CHAPTER 13
129 | P a g e
TESTING
TESTING STRATEGY
Testing is a process of executing a program with the intent of
finding an error. A good test case is the one that has a probability
of finding an as yet undiscovered error. If testing is conducted
successfully (according to the objective stated) it will uncover
errors in the software. As secondary benefit, testing
demonstrates that software function appears to be working
according to the specification that performance requirements
appear to have been met.

Testing is the set of activities that can be planned in


advance and conducted systematically. It is an integral part of
program development. It is in this stage, which we check that the
program, that has been coded, performs according to the user’s
requirements. The purpose of doing test is not to demonstrate
that there are no errors in the program but to detect any bugs
that may still exist.

In the testing stage, the main aim is to look for errors that
unknowingly have been occurred. It is common misconception

130 | P a g e
that the purpose of testing is to prove that a program is working
correctly. This is dangerous myth because it can lead insufficient
testing, and program with hidden fault. Because the actual result
and expected result may differ in the field of reality and it can be
hazardous for a program.

The importance of software testing and its implications with


respect to software quality cannot be over emphasized. Software
testing is a crucial element of software quality and represents the
ultimate review of specification design and coding.

The increasing visibility of software as a system element and


the attendant ‘costs’ associated with a software failure are
motivating forces for well planned, thorough testing. It is not
unusual for software development organization to expend 40% of
total project effort on testing. Testing is the process of exercising
software with the intent of finding errors. This fundamental
philosophy does not change for webapps.In fact, because web
based systems and applications reside on the network and
interoperate with many different operating systems, browser,
hardware platforms and backroom applications, the search for
errors represents a significant challenge for web engineers. The
webapp testing process begins by focusing on user-visible aspects

131 | P a g e
of the webapp and proceeds to tests that exercise technology and
infrastructure. Seven testing steps are performed:
content,interface,Navigation,component,configuration,Performanc
e,and security testing.

The testing process for webapp engineering begins with test that
exercise content and interface functionality that is immediately
visible to end users. As testing proceeds, aspects of the design
architecture and navigation are exercised. The user may or may
not be cognizant of these webapp elements.Finally, the focus
shifts to tests that exercise technological capabilities that are not
always apparent to end user-webapp infrastructure and
installation issues.

Following are the systematic strategy for software testing:-

 Specify product requirements in a quantifiable manner long


before testing commences.
 State testing objectives explicitly.
 Understand the users of the software and develop a profile
for each user category.
 Develop a testing plan that emphasizes “rapid cycle testing
“.

132 | P a g e
 Build “robust” software that is designed to test itself.
 Use effective formal technical reviews as a filter prior to test
itself.
 Develop a continuous improvement approach for the testing
process.

TESTING TECHNIQUE
Software Testing is the critical elements of the software quality
assurance and represents the ultimate review of the
specifications, design, and code generation. Once source code has
been generated, software must be tested to uncover (and
correct) as many as errors as possible before delivers to the
customers. The goal is to design a series a of test cases that have
a high intention of finding the errors .The technique provides
systematic guidelines for designing tests that :-

1) Exercise the internal logic of the software component.


2) Exercise the input and output domains of the program to
uncover errors in program function, behavior and
performance.

There are two types of testing technique s :


i) White box testing.

133 | P a g e
ii) Black box testing.

White box testing :


White box test focus on the program
control structure. Test cases are derived to ensure that all
statement in the program has been executed at least once
during testing and that all logical condition has been
exercised. Basic path testing, a white box testing, makes use
of program graph to derive the set of linearly independent
test that will ensure coverage .

Condition Testing:
Condition testing is tests case design method that exercise
the logical conditions contain in a program module. a simple
condition is a Boolean variable or a relational expression.

Branch Testing:
I have used Branch testing is probably the for compound
condition, the true and false (in project i.e. null values) for
each branch.

Data Flow Testing:


I have used data flow testing due to check the path of
program according to the locations of definitions and uses of
variables in the program.

Loop Testing:

134 | P a g e
In our project I have use only simple loop. And I have use m
pass through the loop where m<n.

BLACK BOX TESTING:


Black box testing focuses on the functional requirements of
the software. That is, black-box testing enable the software
engineer to derive set of input conditions that will fully
exercise all functional requirements for a program.

Graph-Based Testing Method:


I have used graph-based testing method for removing errors
associated with relationships. The first step in this testing is
to understand the objects that are modeled in software and
the relationship that connect these objects.

Equivalence Partitioning:

This testing is used for the following reason:


1. specific numeric values
2. range of values
3. set of related values
4. Boolean condition

For example:-
Check in phone number, code generation, password etc.

135 | P a g e
Boundary Value Analysis :
Boundary value analysis is a test case design technique that
complements equivalence partitioning. Rather than selecting
any element of equivalence class the selection of test cases
at the edges of the class. Rather than focusing solely on the
input condition,
The point of equivalence partitioning as;
1) An input condition specifies a range boundary by values
a and b, test cases should be design with values a and b
and just above and just below a and b.
2) An input condition specific a number of values, test
cases should be developed that exercise the minimum
and maximum number.

System Testing
During system testing the system is used experimentally to
ensure that the software does not fail i.e. it will run
according to its specifications and in the way users expect.
Special test data are input for the processing and the results
examine. A limited number of users try to use it in
unforeseen ways. It is preferable to discover any surprise
before the organization implements the system and depend
upon it.

136 | P a g e
In many organizations persons other than those who wrote
the original programs to ensure more complete and unbiased
testing and more reliable testing perform testing.
The norms that were followed during the phase were that
after the developer of the software has satisfied regarding
every aspect of the software under consideration he is
required to release the program source code. A setup name
release is used to copy the name file from the developers’
user area to a project area in the directory named with
developer user name. Here all the final testing used to be
done by persons other than the developer himself .if some
c h a n g e s w e r e d e s i r e d i n t h e p r o g r a m the developer were required
to use another setup. Retrieve, which copied back the latest version of the
program to developer areas.

As in this system data is entered at different levels I considered providing


various types of checks like range check, validity check, completeness check
etc. in different data entry screens according to the requirements.
Since the user are not familiar to the new system the data screens were
designed in such a way that were-.

 consistent
 easy to use
 has a fast response time

The following convention were used while designing the various


screen:

Unit Testing:
In unit testing I have testing a single program module in an isolated
environment. Testing of the processing procedures is the main focus.

137 | P a g e
Integration Testing:
Because of interfaces among the system modules, we use
integration testing. In other word’s it ensures that the data
moving between the modules is handled as intended.

System Testing:
System testing is the testing of the system against its initial
objective. It is done either in a simulated environment or in live
environment.

Test Review:
Test review is the process that ensures that testing is carried out
as planned. Test review decides whether or not the program is
ready to be shipper out for implementation.

Security Testing :
Security testing attempt to verify that protection mechanism built
into a system will, in fact, protect it form penetration
mechanisms.

138 | P a g e
TEST REPORTS
Test Case Result Actual Severity
Expected Result
Login
If all the fields are not filled and An alert An alert
the validation conditions are not message is message is
Minor
satisfied then, an alert message expected. displayed.
must be displayed.
JobSeeker’s Registration
If mandatory (*) the fields are not An alert An alert
filled and the validation conditions message is message is Minor
are not satisfied then, an alert expected. displayed.
message must be displayed.
Company Registration:
An alert An alert
If mandatory (*) the fields are not
message is message is
filled and the validation conditions Minor
expected. displayed.
are not satisfied then, an alert
message must be displayed.

Job Search An alert


message is
Jobseeker’s can check job online - Minor
expected
after selecting the Category, Key
Skill, experience, and Job Title.

139 | P a g e
Admin An alert An alert
message is message is
Admin can insert, update or delete Minor
expected displayed
any company or jobseeker’s
details also schedule the interview.

Rating Online It is total


community is user
This software is to be checked for Minor
completely friendly.
user friendly.
user friendly.

MAINTENANCE
An application has served the business needs of an organization for 10 to 15
years. During that time it has been concerned, adapted, and enhanced many

140 | P a g e
times. The application becomes unstable. It still works, but every time a
change is attempted. Much of the software we depend on today is on
average 10 to 15 years old. Even when these programs were created using
the best design in coding techniques known at the time and, they were
created when program size and storage space were principal concern. They
were then migrated to new a platform adjusted for changes in machine and
operating system technologies and enhance to meet new user needs all
without enough regard to overall architecture. The maintenance of existing
software can account for over 60% of all efforts expanded by a development
organization and the percentage continues to rise as more software is
produced. There are four different mechanism activities:

Corrective Maintenance
Even with the best quality assurance activities, it is likely that the
customer will uncover defects in the software. Corrective maintenance
changes the software defects.

Adaptive Maintenance
Over time, the original environment (e.g. CPU, operating system, business
rules, external product features) for which the software was developed is
likely to change. Adaptive maintenance results in modification to the software
to accommodate the changes to its external environments.

Perfective Maintenance

141 | P a g e
As software is used, the customer/user will recognize additional functions
that will provides benefits. Perfective maintenance extends the software
beyond its original functional requirements.

Preventive Maintenance or Reengineering


Computer software deteriorates due to change and because of this preventive
maintenance must be conducted to enables the software to serve the needs of
its end users.
In sense preventive maintenance makes changes to computer program so
that they can be more easily corrected, adapted and enhanced.

CHAPTER14
142 | P a g e
CHARTS
GANTT CHART

Gantt charts are a project control technique that can be used for
several purposes, including scheduling, budgeting, and resource
planning. A Gantt chart is a bar chart, with each bar representing an
activity. The bars are drawn against a time Line. The length of each
bar is proportional to the length of time planned for the activity.
A Gantt chart helps in scheduling the activities of a project, but it does
not help in identifying them. One can begin the activities identified
in the work breakdown structure. Gantt charts take different forms
depending on their intended use. They are best for resource
scheduling

The Diagram of Gantt Chart for this project is given below:-

143 | P a g e
GANTT CHART

144 | P a g e
PERT CHART
A PERT (Program Evaluation and Review Technique) chart is a network

of boxes (or circles) and arrows. There are different variations of PERT

charts. The boxes in PERT Chart can be decorated with starting and

ending dates for activities; the arrows help in computing the earliest

possible starting dates for the boxes at their heads. Some boxes can

be designated as milestone.

The Chart below shows that the path through the project that consists

of the “design”, “build code generator”, and “integration and testing”

activities is the critical path for the project. Any delay in any activity in

this path will cause a delay in the entire project.

As, it is abbreviated of Program Evaluation Review Technique


(PERT), is organized by the events and activities or tasks. This is
driven by information already developed in earlier project
planning activities.

 Estimation of efforts.
 A decomposition of product function

145 | P a g e
 Selection of the process model and task set.
 Decomposition of the task.

Pert provides quantative tools that allows the planner to :


1) Determine the critical path- the chain of task that determines
the duration of the project.
2) Established most likely time estimates for individual tasks by
applying statistical model and
3) Calculate boundary time that define a time window for the
particular task.
4) Pert is most likely to be used with most complex projects.

START DESIGN BUILD INTEGRATION


CODING TESTING
Update/Delete User Information
WEB

WRITE
MANUAL FINISH

PERT CHART

146 | P a g e
CHAPTER 15

COST ESTIMATION
OF THE
PROJECT
I am using the COCOMO model for estimating the cost of the
system.It is regarded as an semidetached system. Since this
project is somewhat small, COCOMO estimate might be
inaccurate. COCOMO is designed for use on system larger than 2
KDL.

This model estimates the total effort in term of person-month of technical


project staff. It does not include the cost of the secretarial staff that might
be needed.

The basic steps in this model are:

147 | P a g e
1) Ob tain an initial es tim ate o f the d evelo p m ent effo rt fro m th e
es ti m at e o f tho us ands o f d elive red lines o f so urc e c od e ( KDL ).
2) D et erm ine a s et o f m ultip lying fac to r fro m d iffe rent attrib u te
o f th e p ro jec t.
3) Ad ju s t the effo r t es tim at e b y m ultip lying th e initial es tim at e
wi th all the multip lying fac to r.

T h e i n i tial es tim ate is d et erm ined b y an eq uatio n o f the fo rm


u s ed i n the s tatic , s ing le- variab le m od es , using KDL as m easu r e
o f si ze. To d eterm in e the initial effo rt Ei in p ers o n- mo nths th e
eq u ati o n us ed is o f the ty p e
b
Ei = a*( K DL)
T h er e are 15 d iffer ent attrib ute, called co s t d river attrib u tes
th at d et erm ine th e multip lying fac to rs . Thes e fac to rs d ep end o n
p ro d uc t, c om p ute r, p ers o nal, and t ec hno lo g y.

Al l 15 fac to r are m ultip lied to g e ther to g et the effo rt


ad ju s tm ents fac to r( EAF). The final co s t es tim at e ,E, is ob tai n ed
b y m u l tip lying th e initial es tim at e b y the EAF.
E = EAF * Ei
C os t es tim atio n
T h e si ze es tim ates fo r thes e in lines o f co d e ar e.
68 03=6. 80 3 KDL
C ateg o ry o f p ro jec t is s em id etac hed s o co ns traint o f a & b a
fo l l o ws
A=3. 0 & b =1. 12
So , Ei= 3. 0( 6. 803) 1 . 1 2
= 3. 0( 8. 56 3)

148 | P a g e
= 25. 689

C ost d r iver Rat ing V alue s

Software reliability very high


1.40
Data base size high 1.08
Product complexity high 1.15
Computer turnaround time very high 1.15
Analyst capability high 0.86
Application experience nominal 1.00
Programmer capability high 0.86
Programming language exp. High 0.95
Morden prog. Practice high 0.95
Use of software tools low 1.10
Development schedule nominal 1.00
The effort adjustment factor(EAF) is
EAF =
1. 4*1. 0 8*1. 15 *1. 15*. 86 *1*. 86 *. 95*. 95* 1. 1*1

=1. 4 6
th e i n i ti al ef fo rt o f the p ro j ec t is

E = Ei*EAF

= 1. 46*2 0. 789
=30. 52 PM

CHAPTER 16

149 | P a g e
Future Scope of the
Project
FUTURE SCOPE
It is unreasonable to consider a computer based
information system complete or finished; the system
continues to evolve throughout its life cycle, even if it’s
successful. Due to the creative nature of the design, there
remain some lapses inaccurate communications between the
users and the developers. So, certain aspects of the system
must be modified as operational experience is gained with it.
As users work with the system, they develop ideas for change
and enhancements.

CONCLUSION
The JOB PORTALis looking forward to a more efficient and
streamlined processing system and better coordination
between Jobseeker’s and the Employer leading to desired
results in terms of quality, service, competitive ness.

CHAPTER 17

150 | P a g e
BIBLIOGRAPHY
 Jason Price, Mike gunderloy," Mastering visual C#.net "BPB Pub.
1999.

 Herbert Schildt," C#.net" TATA McGraw-Hill edition 2002.

 www.google.com

 www.codeproject.com

 Beginning ASP.NET 3.5 in C# 2008Second Edition Matthew


MacDonald.

 SQL Tutorial -tutorialspoint.com

 www.library.co.in

 www.stackoverflow.com

 www.wikipedia.org

CHAPTER 18

151 | P a g e
GLOSSARY
E.R.D. Entity-Relationship Diagram

D.F.D. Data Flow Diagram

DATA DICITIONARY : All definitions of elements in the system-


data flows,processes,and data stores-are described in detail in a data
dictionary.

COUPLING:Coupling is a measure of interconnection among modules in a


software structure.

COHESION:Cohesion is a natural extension of the information hiding


concept.

PRIMARY KEY: The column should be able to uniquely identified each


row. Such a column is candidate for a primary key.

FOREIGN KEY: The Foreign key is a set of attribute of one relvar R2,
whose values are required to match values of some candidate key of some
relay R1.

152 | P a g e
COMPOSITE KEY: The composite key is a combination of two or more
than two columns which are identified as primary key.

SCHEMA:The term Schema is used to mean & overall chart of all the data
item types and record –types stored in database.

ENTITY & ATTRIBUTE: All such item about which relevant information is
stored in the database are called Entities. The qualities of the entity which
we store as information are called Attributes.

SHARING DATA: A database allows the sharing of data under its control
by any numberof application program or users.

DATA INTEGRITY: Data integrity means that the data contained in the
databases both accurate & consistent.

DATA SECURITY: Data is a vital importance to an organization and may


be confidential. Such confidential data must not be accessed by
unauthorised persons. Different level of security could be implemented for
various types of data and operations .

153 | P a g e
FINISH

154 | P a g e

You might also like