CHAPTER 1

INTRODUCTION

KPO is one of the fast growing services company involved in IT services,

BPO and KPO It is being claimed that KPO is one step extension of Business
Processing Outsourcing (BPO) because BPO Industry is shaping into Knowledge
Process Outsourcing because of its favorable advantageous and future scope.
Knowledge process can be defined as high added value processes chain where the
achievement of objectives is highly dependent on the skills, domain knowledge and
experience of the people carrying out the activity. And when this activity gets
outsourced a new business activity emerges, which is generally known as Knowledge
Process Outsourcing.
As a service provider KPO always strive to service the customer and makes
sure that its services fulfill customer's requirements and bring cost cutting and
efficiency in business productivity

1.1 Objection of the project:

In Order to be able to define our system architecture, we must first
dearly state what our objective that will deriver system behavior at the same
one of our objective is to create an experience, which is not only unique to the
(user) client, but also makes him feel that he has loyal attachment to the
system and approaches us whenever he/she needs.
To achieve better results and success by implement computerized
process instead of manual process

1.2 Modules and Their Description

Administrative Modules

 Client Modules

 Careers

1
Administrator (server) module:

1. Login
2. Client details
3. Communication(client & server)
4. Career detail

Login:
Here, the Admin Entered by giving login id and password for verifying the
client details

Client Details:
The Client details such as name, mail id, company name, phone no and
address etc. These are all displayed in this module.

Communication:
Here Server and Client can communicate each other about Knowledge resource.

Career Details:
Here KPO can view the career details for newly applied graduates.

Client Modules:
1. Registration
2. Login
3. Communication (server and client)
4. Feedback

Registration:
The User details such as name, password, Address, City, EmailId, and
Contact Number are entered here.

Login:
Here, the username and password is entered to login to the application.

2
Communication:
Here Server and Client can communicate each other about Knowledge
resource.

Feedback:
Here client can enter the comments about the kpo process

Career Details:
It provides career opportunities for Technical and Master degree
graduates.

Application Form:
It provides application form for applying jobs in KPO organization.

3
 CHAPTER -2

SOFTWARE PROJECT PLAN

This chapter discusses about that time schedule for the project and it contains
the various phases of the project.

The Various Phases of the Project:

S.NO TASK DURATION

1 10 Day’s
Requirement Specification

2 10 Day’s
Requirement document specification

3 Design analysis 20 Day’s

4 15 Day’s
Design Documentation
20 Day’s
5 Design Review

15 Day’s
6 Coding

Total 90 Day’s

4
 CHAPTER-3

CUSTOMER REQUIREMENT DETERMINATION

3.1 Existing System

BPO may include both IT management and business operations, the
approach is primarily about turning over functions such as data entry, payroll,
accounting, billing or even real estate management to a third party. Though these
business processes may depend on IT, they are separate functions from core IT
operations, such as data center activities or network management. It won’t be have
professional Knowledge people for delivering the different domain Knowledge
sources like Research & Development, medical, IT, Technical and web sources.

3.2 Proposed System

KPO, calls for the application of specialized domain pertinent
knowledge of a high level. The KPO typically involves a component of Business
Processing Outsourcing (BPO), Research Process Outsourcing (RPO) and Analysis
Proves Outsourcing (APO). KPO business entities provide typical domain-based
processes, advanced analytical skills and business expertise, rather than just process
expertise. KPO Industry is handling more amount of high skilled work other than the
BPO Industry. While KPO derives its strength from the depth of knowledge,
experience and judgment factor.
In fact, it is the evolution and maturity of the Indian BPO sector that
has given rise to yet another wave in the global outsourcing scenario. The success
achieved by many overseas companies in outsourcing business process operations to
India has encouraged many of the said companies to start outsourcing their high-end
knowledge work as well. Cost savings, operational efficiencies, availability of and
access to a highly skilled and talented workforce and improved quality are all
underlying expectations in outsourcing high-end process

5
 CHAPTER 4

SOFTWARE REQUIREMENTS SPECIFICATION

Software Requirements Specification (SRS) is the starting point of the

software development activity. Little importance was given to this phases in the early
days of software development. The emphasis was first on coding and then shifted to
design.
As systems grew more complex, it become evident that the goal of the
entire system cannot be easily comprehended. Hence need for the requirements
analysis phase arose. Now, for large software systems, requirements analysis is
perhaps the most difficult activity and also the most error prone.
Some of the difficulty is due to the scope of this phase. The software
project is imitated by the client needs. In the beginning these needs are in the minds of
various people in the client organization. The requirement analyst has to identify the
requirements by tacking to these people and understanding there needs. In situations
where the software is to automated a currently manuals process, most of the needs can
be understood by observing the current practice.
The SRS is a means of translating the ideas in the minds of the clients
(the output) into formal document (the output of the requirements phase). Thus the
output of the phase is a set of formally specified requirements, which hopefully are
complete and consistent, while the input has none of these properties.

6
4.1 Functional Requirements

Login

Admin
Registration
(Kpo)

KPO
Client Communication
Organization

Admin details
Graduates

Careers

Feedback

7
4.2 Performance Requirements
The project must the end user requirements. Accuracy and fast must be
imposed in the Project.
The project is development as easy as possible for the sake of end user. The
project has to be developed with view of satisfying the future requirements and future
enhancement.
The tool has been finally implemented satisfying the needs specified by the
company. As per the performance is concerned this system said is performing
This processing as well as tine taken to generate well reports where also even
when large amount of data was used. The system is designed in such a way that even
when large amount of data used for processing there would less performance
degradation.

4.3 Interface requirements

4.3.1 Hardware Interface

The stranded input device like keyboard and mouse are to get input. The
output will be generated and display in the monitor. The reports can also be exported
to a SQL-server document are text file. The stranded printer in used to take outputs.

4.3.2 Software Interface

The design part and interface id done the front end ASP.Net and SQL server
as a backend of the project.

4.4 Operational requirements

The database or databases that are being failed over to the stand by server
cannot be used for anything else. but databases on the standby server not being used
for failover can still be used normally.
When it comes time for actual failover, you much one of two things to make your
application work either rename the standby server the same name as the failed
8
production server(and the IP address),or re-point your user’s applications to new
standby server in some cases, neither of this option is practical

4.5 Resource Requirement

4.5.1 Hardware Requirement

The hardware used for the development of the project is:

PROCESSOR : PENTIUM III 766 MHz

RAM : 128 MD SD RAM
MONITOR : 15” COLOR
HARD DISK : 20 GB
FLOPPY DRIVE : 1.44 MB
CDDRIVE : LG 52X
KEYBOARD : STANDARD 102 KEYS
MOUSE : 3 BUTTONS

4.5.2 Software Requirement

The software used for the development of the project is:

OPERATING SYSTEM : Windows 2000 Professional

ENVIRONMENT : Visual Studio .NET 2008
.NET FRAMEWORK : Version 2.0
LANGUAGE Visual C#.NET
WEB TECHNOLOGY : Active Server Pages.NET
WEB SERVER : Internet Information Server 5.0
BACK END : Sqlserver2005
REPORTS : WebFormDataGridcontrol

9
4.6 Security Requirements
Web application are available via network access, it is a difficult. If not
possible, to limit the population of the end-user who may access the applications? In
order to product sensitive connect and provide secure mode be implemented
throughout the infrastructure that the supports web application and within the
application itself.
Web Application have become heavy integrated with critical corporate and
database.
E-commerce application extracts and then store sensitive customer
information.
4.7 Design Requirements
To create project, add base masters and masters to the project, assign
behaviors to the master, create and assign behavior sets, and then apply, test and
validate those behaviors. It also shows how to create and build a stencil to hold the
shapes.
4.8 Quality and Reliability Requirements
A software component that is developed for reuse would be correct and would
contain no defects. In reality, formal verification is not carried out routinely, and
defects can add to occur. However with each reuse, defects are found eliminated, and
a components qualify improve as a result. Over time the components virtually defect
free.
Software reliability is defined in statical term as” the probability of faultier-
free operation of a computer program in a specified environment for specified tine”.
The software quality and reliability, failure is nonconformance to software
requirements. Failure can be only anything or catastrophic. one failure can be
corrected within seconds while another requirements week even mouths to correct.
Complicating the issue even further, the correction of the one failure may in fact
result in the introduction of the errors that ultimately result in other failure

Web Correct link processing

Application Reliability Error recovery
Quality Input validation and recovery
10
 CHAPTER 5

SYSTEM ANALYSIS

Data Flow Diagram

Level-1:

Login User
Details
Admin Admin Details
Admin
Communication

Level-2

Login

Registration
Client Client
Process
Communicati
on
Feedback

11
 Pre
Level-3:
mium

Admi Login
n
Admin
Login

Admin
Reg, careers,
Details
feedback

Communic
Server & Client
ation
comm.

Level-4:

Graduates Application for Jobs

KPO

12
USE CASE DIAGRAM

Identifying Exciting User

Create New Account

Contact Details

Online Application

CLIENT
SERVER
View Client Details

View Carrier Details

View Feedback

13
Software Life Cycle

Title Authorization
Submission Certificate

Students
DB

Learning
Training
Process

Problem Analysis:
KPO

Authorization
Signatory
Front-end Asp.net
Back-end: SQL
Server
Code behind:
C#.net
Networking
Design:
Internet Explorer
6.0

Coding Validation Testin Docume Reports

g n

Certificate

Programmer
Complete
Training Certificate
Certificate
14
 CHAPTER-6

SYSTEM DESIGN

Design is multi-step process that focuses on data structure software

architecture, procedural details, (algorithms etc.) and interface between modules. The
design process also translates the requirements into the presentation of software that
can be accessed for quality before coding begins.
Computer software design changes continuously as new methods; better
analysis and broader understanding evolved. Software Design is at relatively early
stage in its revolution.
Therefore, Software Design methodology lacks the depth, flexibility and
quantitative nature that are normally associated with more classical engineering
disciplines. However techniques for software designs do exist, criteria for design
qualities are available and design notation can be applied.

6.1 INPUT DESIGN

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

based format. Input design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system.
In the project, the input design is made in various web forms with
various methods.
1. Login
2. Communication
3. Career Details
4. Feedback

Login:
Here, the Admin and Entered by giving login id and password.

15
Communication:
Here Server and Client can communicate each other about Knowledge resource.

Career Details:
Here KPO can view the career details for newly applied graduates.

Feedback:
Here client can enter comments and suggestions about the kpo org
.

ADMINISTRATOR MODULE FORMS:

1. Login
2. Client details
3. Communication (client & server)
4. Career details

Login:
Here, the Admin Entered by giving login id and password for verifying the
client details.

Client Details:
The Client details such as name, mail id, company name, phone no and
address etc. These are all displayed in this module.

Communication:
Here Server and Client can communicate each other about Knowledge resource.

Career Details:
Here KPO can view the career details for newly applied graduates.

16
CLIENT MODULES:
1. Registration
2. Login
3. Communication (server and client)
4. Feedback

Registration:
The User details such as name, password, Address, City, EmailId, and
Contact Number are entered here.

Login:
Here, the username and password is entered to login to the application.

Communication:
Here Server and Client can communicate each other about Knowledge
resource.

Feedback:
Here client can enter the comments about the kpo process

CAREER DETAILS:
It provides career opportunities for Technical and Master degree graduates.
1. Application Form

Application Form:
It provides application form for applying jobs in KPO organization.

6.2 OUTPUT DESIGN

Output design generally refers to the results and information that are
generated by the system for many end-users; output is the main reason for developing
the system and the basis on which they evaluate the usefulness of the application. In
any system, the output design determines the input to be given to the application.

17
6.3 INTERFACE DESIGN
he ODBC (Open Database Connectivity) interface is a pure .NET to execute
SQl statement. The ODBC provides a set classes and interfaces that can be used by
developers to write database applications. Basic ODBC interactions in its simplest
form, can be broken down into four steps:

1. Open a connection to the database.

2. Execute a SQL statement
3. Process the result
4. Close the connection to the database

6.4 TABLE AND DATABASE DESIGN:

6.4.1 Normalization:

Normalization is the process of strutting relational database schema such that

most ambiguity is removed. The stage of normalization are referred to as forms and
progress from the least restrictive(first normal form)through the most restrictive(Fifth
normal form), generally , most database designers do not attempt to implement
anything higher then normal form of Boyce code Normal Form.

6.4.1.1FIRST NORMAL FORM:

A relation is said to be in First normal form (INF) if and each attributed

of the relation is atomic. More simply, to be INF, each column must contain only a
single value and each now contain in the same column.

6.4.1.2 SECOND NORMAL FORM:

In the Second normal Form, a relation must first fulfill the

requirement to be in first Normal Form. Additional, each donkey attribute in the
relation must be functionality dependent upon the primary key.

18
6.4.1.3 THIRD NORMAL FORM:

A table is said to be in third normal form and every non key attribute is
functionality dependent only on the primary key. This normalization process is
applied to this system and the normalized tables are given in the above section.

TABLE DESIGN

Registration:

Application:

Feedback:

Communication (Chat):

19
Database Design

The database design is a must for any application developed

especially more for the data store projects. Since the chatting method involves storing
the message in the table and produced to the sender and receiver, proper handling of
the table is a must.
In the project, admin table is designed to be unique in accepting the username
and the length of the username and password should be greater than zero.

6.5 FRONT END DESIGN

FEATURES OF VISUAL BASIC .NET

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.

OBJECTIVES OF .NET FRAMEWORK:

1. To provide a consistent object-oriented programming environment whether
object codes is stored and executed locally on Internet-distributed, or executed
remotely.
2. To provide a code-execution environment to minimizes software
deployment and guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and
Web-based applications. To make communication on distributed environment to
ensure that code be accessed by the .NET Framework can integrate with any other
code.

COMPONENTS OF. NET FRAMEWORK

1. THE COMMON LANGUAGE RUNTIME (CLR):
The common language runtime is the foundation of the .NET Framework. It
manages code at execution time, providing important services such as memory
management, thread management, and remoting and also ensures more security and
20
robustness. The concept of code management is a fundamental principle of the
runtime. Code that targets the runtime is known as managed code, while code that
does not target the runtime is known as unmanaged code.
THE .NET FRAME WORK CLASS LIBRARY:
It is a comprehensive, object-oriented collection of reusable types used
to develop applications ranging from traditional command-line or graphical user
interface (GUI) applications to applications based on the latest innovations provided
by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that
load the common language runtime into their processes and initiate the execution of
managed code, thereby creating a software environment that can exploit both
managed and unmanaged features. The .NET Framework not only provides several
runtime hosts, but also supports the development of third-party runtime hosts.
Internet Explorer is an example of an unmanaged application that hosts
the runtime (in the form of a MIME type extension). Using Internet Explorer to host
the runtime to enables embeds managed components or Windows Forms controls in
HTML documents.

FEATURES OF THE COMMON LANGUAGE RUNTIME:

The common language runtime manages memory; thread
execution, code execution, code safety verification, compilation, and other system
services these are all run on CLR.
Security.
Robustness.
Productivity.
Performance.
SECURITY
The runtime enforces code access security. The security features
of the runtime thus enable legitimate Internet-deployed software to be exceptionally
feature rich. With regards to security, managed components are awarded varying
degrees of trust, depending on a number of factors that include their origin to perform
file-access operations, registry-access operations, or other sensitive functions.

21
ROBUSTNESS:
The runtime also enforces code robustness by implementing a strict
type- and code-verification infrastructure called the common type system(CTS). The
CTS ensures that all managed code is self-describing. The managed environment of
the runtime eliminates many common software issues.
PRODUCTIVITY:
The runtime also accelerates developer productivity. For example,
programmers can write applications in their development language of choice, yet take
full advantage of the runtime, the class library, and components written in other
languages by other developers.
PERFORMANCE:
The runtime is designed to enhance performance. Although the
common language runtime provides many standard runtime services, managed code is
never interpreted. A feature called just-in-time (JIT) compiling enables all managed
code to run in the native machine language of the system on which it is executing.
Finally, the runtime can be hosted by high-performance, server-side applications, such
as Microsoft® SQL Server™ and Internet Information Services (IIS).
ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a
unified Web development platform that provides the services necessary for developers
to build enterprise-class Web applications. While ASP.NET is largely syntax
compatible, it also provides a new programming model and infrastructure for more
secure, scalable, and stable applications.
ASP.NET is a compiled, NET-based environment, we can author
applications in any .NET compatible language, including Visual Basic .NET, C#, and
JScript .NET. Additionally, the entire .NET Framework is available to any ASP.NET
application. Developers can easily access the benefits of these technologies, which
include the managed common language runtime environment (CLR), type safety,
inheritance, and so on.
ASP.NET has been designed to work seamlessly with WYSIWYG
HTML editors and other programming tools, including Microsoft Visual Studio .NET.
Not only does this make Web development easier, but it also provides all the benefits
that these tools have to offer, including a GUI that developers can use to drop server
controls onto a Web page and fully integrated debugging support.
22
 Developers can choose from the following two features when creating an
ASP.NET application. Web Forms and Web services, or combine these in any way
they see fit. Each is supported by the same infrastructure that allows you to use
authentication schemes; cache frequently used data, or customizes your application's
configuration, to name only a few possibilities.
Web Forms allows us to build powerful forms-based Web pages. When
building these pages, we can use ASP.NET server controls to create common UI
elements, and program them for common tasks. These controls allow we to rapidly
build a Web Form out of reusable built-in or custom components, simplifying the
code of a page.
An XML Web service provides the means to access server functionality
remotely. Using Web services, businesses can expose programmatic interfaces to their
data or business logic, which in turn can be obtained and manipulated by client and
server applications. XML Web services enable the exchange of data in client-server or
server-server scenarios, using standards like HTTP and XML messaging to move data
across firewalls. XML Web services are not tied to a particular component technology
or object-calling convention. As a result, programs written in any language, using any
component model, and running on any operating system can access XML Web
services.
Each of these models can take full advantage of all ASP.NET features, as
well as the power of the .NET Framework and .NET Framework common language
runtime.
Accessing databases from ASP.NET applications is an often-used
technique for displaying data to Web site visitors. ASP.NET makes it easier than ever
to access databases for this purpose. It also allows us to manage the database from
your code.
ASP.NET provides a simple model that enables Web developers to write
logic that runs at the application level. Developers can write this code in the
global.aspx text file or in a compiled class deployed as an assembly. This logic can
include application-level events, but developers can easily extend this model to suit
the needs of their Web application.
ASP.NET provides easy-to-use application and session-state facilities that
are familiar to ASP developers and are readily compatible with all other .NET
Framework APIs.
23
 ASP.NET offers the IHttpHandler and IHttpModule interfaces.
Implementing the IHttpHandler interface gives you a means of interacting with the
low-level request and response services of the IIS Web server and provides
functionality much like ISAPI extensions, but with a simpler programming model.
Implementing the IHttpModule interface allows you to include custom events that
participate in every request made to your application.
ASP.NET takes advantage of performance enhancements found in
the .NET Framework and common language runtime. Additionally, it has been
designed to offer significant performance improvements over ASP and other Web
development platforms. All ASP.NET code is compiled, rather than interpreted,
which allows early binding, strong typing, and just-in-time (JIT) compilation to native
code, to name only a few of its benefits. ASP.NET is also easily factorable, meaning
that developers can remove modules (a session module, for instance) that are not
relevant to the application they are developing.
ASP.NET provides extensive caching services (both built-in services
and caching APIs). ASP.NET also ships with performance counters that developers
and system administrators can monitor to test new applications and gather metrics on
existing applications.
Writing custom debug statements to your Web page can help
immensely in troubleshooting your application's code. However, it can cause
embarrassment if it is not removed. The problem is that removing the debug
statements from your pages when your application is ready to be ported to a
production server can require significant effort.
ASP.NET offers the Trace Context class, which allows us to write
custom debug statements to our pages as we develop them. They appear only when
you have enabled tracing for a page or entire application. Enabling tracing also
appends details about a request to the page, or, if you so specify, to a custom trace
viewer that is stored in the root directory of your application.
The .NET Framework and ASP.NET provide default authorization
and authentication schemes for Web applications. we can easily remove, add to, or
replace these schemes, depending upon the needs of our application .

24
DATA ACCESS WITH ADO.NET
As you develop applications using ADO.NET, you will have different
requirements for working with data. You might never need to directly edit an XML
file containing data - but it is very useful to understand the data architecture in
ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:
Interoperability
Maintainability
Programmability
Performance Scalability

INTEROPERABILITY:
ADO.NET applications can take advantage of the flexibility and broad
acceptance of XML. Because XML is the format for transmitting datasets across the
network, any component that can read the XML format can process data. The
receiving component need not be an ADO.NET component.
The transmitting component can simply transmit the dataset to its
destination without regard to how the receiving component is implemented. The
destination component might be a Visual Studio application or any other application
implemented with any tool whatsoever.
The only requirement is that the receiving component be able to read
XML. SO, XML was designed with exactly this kind of interoperability in mind.

MAINTAINABILITY:
In the life of a deployed system, modest changes are possible, but
substantial, Architectural changes are rarely attempted because they are so difficult.
As the performance load on a deployed application server grows, system resources
can become scarce and response time or throughput can suffer. Faced with this
problem, software architects can choose to divide the server's business-logic
processing and user-interface processing onto separate tiers on separate machines.
In effect, the application server tier is replaced with two tiers, alleviating the
shortage of system resources. If the original application is implemented in ADO.NET
using datasets, this transformation is made easier.

25
 ADO.NET data components in Visual Studio encapsulate data access
functionality in various ways that help you program more quickly and with fewer
mistakes.
PERFORMANCE:
ADO.NET datasets offer performance advantages over ADO
disconnected record sets. In ADO.NET data-type conversion is not necessary.

SCALABILITY:
ADO.NET accommodates scalability by encouraging programmers to
conserve limited resources. Any ADO.NET application employs disconnected access
to data; it does not retain database locks or active database connections for long
durations.
VISUAL STUDIO .NET
Visual Studio .NET is a complete set of development tools for
building ASP Web applications, XML Web services, desktop applications, and
mobile applications In addition to building high-performing desktop applications, you
can use Visual Studio's powerful component-based development tools and other
technologies to simplify team-based design, development, and deployment of
Enterprise solutions.
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use
the same integrated development environment (IDE), which allows them to share
tools and facilitates in the creation of mixed-language solutions. In addition, these
languages leverage the functionality of the .NET Framework and simplify the
development of ASP Web applications and XML Web services.
Visual Studio supports the .NET Framework, which provides a
common language runtime and unified programming classes; ASP.NET uses these
components to create ASP Web applications and XML Web services. Also it includes
MSDN Library, which contains all the documentation for these development tools.

XML WEB SERVICES:

XML Web services are applications that can receive the requested data
using XML over HTTP. XML Web services are not tied to a particular component
technology or object-calling convention but it can be accessed by any language,
component model, or operating system. In Visual Studio .NET, you can quickly create
26
and include XML Web services using Visual Basic, Visual C#, JScript, Managed
Extensions for C++, or ATL Server.
XML SUPPORT:
Extensible Markup Language (XML) provides a method for describing
structured data. XML is a subset of SGML that is optimized for delivery over the
Web. The World Wide Web Consortium (W3C) defines XML standards so that
structured data will be uniform and independent of applications. Visual Studio .NET
fully supports XML, providing the XML Designer to make it easier to edit XML and
create XML schemas.

VISUAL BASIC .NET

Visual Basic.NET, the latest version of visual basic, includes many new
features. The Visual Basic supports interfaces but not implementation inheritance.
Visual basic.net supports implementation inheritance, interfaces and
overloading. In addition, Visual Basic .NET supports multithreading concept.

COMMON LANGUAGE SPECIFICATION (CLS):

Visual Basic.NET is also compliant with CLS (Common Language
Specification) and supports structured exception handling. CLS is set of rules and
constructs that are supported by the CLR (Common Language Runtime). CLR is the
runtime environment provided by the .NET Framework; it manages the execution of
the code and also makes the development process easier by providing services.
Visual Basic.NET is a CLS-compliant language. Any objects, classes, or
components that created in Visual Basic.NET can be used in any other CLS-
compliant language. In addition, we can use objects, classes, and components created
in other CLS-compliant languages in Visual Basic.NET .The use of CLS ensures
complete interoperability among applications, regardless of the languages used to
create the application.

27
IMPLEMENTATION INHERITANCE:

Visual Basic.NET supports implementation inheritance. This means that,

while creating applications in Visual Basic.NET, we can drive from another class,
which is know as the base class that derived class inherits all the methods and
properties of the base class. In the derived class, we can either use the existing code of
the base class or override the existing code. Therefore, with help of the
implementation inheritance, code can be reused.

CONSTRUCTORS AND DESTRUCTORS:

Constructors are used to initialize objects, whereas destructors are used to

destroy them. In other words, destructors are used to release the resources allocated to
the object. In Visual Basic.NET the sub finalize procedure is available. The sub
finalize procedure is used to complete the tasks that must be performed when an
object is destroyed. The sub finalize procedure is called automatically when an object
is destroyed. In addition, the sub finalize procedure can be called only from the class
it belongs to or from derived classes.

GARBAGE COLLECTION:

Garbage Collection is another new feature in Visual Basic.NET. The .NET

Framework monitors allocated resources, such as objects and variables. In addition,
the .NET Framework automatically releases memory for reuse by destroying objects
that are no longer in use. In Visual Basic.NET, the garbage collector checks for the
objects that are not currently in use by applications. When the garbage collector
comes across an object that is marked for garbage collection, it releases the memory
occupied by the object.

28
OVERLOADING:

Overloading is another feature in Visual Basic.NET. Overloading

enables us to define multiple procedures with the same name, where each procedure
has a different set of arguments. Besides using overloading for procedures, we can use
it for constructors and properties in a class.

MULTITHREADING:

Visual Basic.NET also supports multithreading. An application that

supports multithreading can handle multiple tasks simultaneously, we can use
multithreading to decrease the time taken by an application to respond to user
interaction. To decrease the time taken by an application to respond to user
interaction, we must ensure that a separate thread in the application handles user
interaction.

STRUCTURED EXCEPTION HANDLING:

Visual Basic.NET supports structured handling, which enables us to

detect and remove errors at runtime. In Visual Basic.NET, we need to use Try…
Catch…Finally statements to create exception handlers. Using Try…Catch…Finally
statements, we can create robust and effective exception handlers to improve the
performance of our application.

6.6 BACK END DESIGN

6.6.1 FEATURES OF SQL-SERVER

The OLAP Services feature available in SQL Server version 7.0 is now
called SQL Server 2000 Analysis Services. The term OLAP Services has been
replaced with the term Analysis Services. Analysis Services also includes a new data
mining component. The Repository component available in SQL Server version 7.0 is
now called Microsoft SQL Server 2000 Meta Data Services. References to the
component now use the term Meta Data Services. The term repository is used only in
reference to the repository engine within Meta Data Services
29
 SQL-SERVER database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO

TABLE
A database is a collection of data about a specific topic.
VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet Vie
Design View
To build or modify the structure of a table we work in the table design view.
We can specify what kind of data will be hold.
Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view
mode.

QUERY:
A query is a question that has to be asked the data. Access
gathers data that answers the question from one or more table. The data that make up
the answer is either dynaset (if you edit it) or a snapshot(it cannot be edited).Each
time we run query, we get latest information in the dynaset.Access either displays the
dynaset or snapshot for us to view or perform an action on it ,such as deleting or
updating.

30
FORMS:
A form is used to view and edit information in the database
record by record .A form displays only the information we want to see in the way we
want to see it. Forms use the familiar controls such as textboxes and checkboxes. This
makes viewing and entering data easy.
Views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View
Design View
To build or modify the structure of a form, we work in forms design
view. We can add control to the form that are bound to fields in a table or query,
includes textboxes, option buttons, graphs and pictures.
Form View
The form view which display the whole design of the form.
REPORT:
A report is used to views and print information from the database. The
report can ground records into many levels and compute totals and average by
checking values from many records at once. Also the report is attractive and
distinctive because we have control over the size and appearance of it.
MACRO:
A macro is a set of actions. Each action in macros does something.
Such as opening a form or printing a report .We write macros to automate the
common tasks the work easy and save the time.

MODULE:
Modules are units of code written in access basic language. We can
write and use module to automate and customize the database in very sophisticated
ways.

31
6.7. Algorithm:

Step1: Enter User name and Password the Client

Step2: Username and password is incorrect then click New Registration
Step3: The Registration finished then views the KPO details
Step4: The requirement is full field then clicks contact and send email
Step5: Enter the feedback and submit the server
Step6: Login Username and password for Admin
Step7: View the Client details and career details and feedback
Step8: Finally logout successfully

32
 CHAPTER-7

CODINGS

Login Form
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 System.Data.SqlClient;

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

{
string conn = "Data Source=APTTECH3;Initial
Catalog=kpo;Integrated Security=True";
protected void Page_Load(object sender, EventArgs e)
{
lblcheck.Visible = false;
}

protected void Btngo_Click(object sender, EventArgs

e)
{
if (Textuname.Text == "admin" && Textpwd.Text ==
"admin")
{
Response.Redirect("Admin.aspx");
}
else
if(ddlusertype.SelectedItem.ToString()=="Client")
{
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "select username,pwd from
comregistration where username='" + Textuname.Text +
"'and pwd='" + Textpwd.Text + "'";
SqlCommand cmd = new SqlCommand(sql, con);
SqlDataReader dr = cmd.ExecuteReader();
if (dr.Read())
{
Response.Redirect("communication.aspx");

33
 }
else
{
lblcheck.Visible = false;
}
}
}
}

Admin

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 System.Data.SqlClient;

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

{
string conn = "Data Source=APTTECH3;Initial
Catalog=kpo;Integrated Security=True";
protected void Page_Load(object sender, EventArgs e)
{

}
protected void compdetails_Click(object sender,
EventArgs e)
{
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "select*from comregistration";
SqlDataAdapter da = new SqlDataAdapter(sql, con);
DataSet ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
con.Close();
}
protected void careerdetails_Click(object sender,
EventArgs e)
{

34
 SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "select*from application";
SqlDataAdapter da = new SqlDataAdapter(sql, con);
DataSet ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
con.Close();
}
protected void Feedback_Click(object sender,
EventArgs e)
{
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "select*from feedback";
SqlDataAdapter da = new SqlDataAdapter(sql, con);
DataSet ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
con.Close();

}
}
Application Form

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 System.Data.SqlClient;

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

{
string conn = "Data Source=APTTECH3;Initial
Catalog=kpo;Integrated Security=True";
protected void Page_Load(object sender, EventArgs e)
{
lbljob.Visible = false;
}
protected void BtnSubmit_Click(object sender,
EventArgs e)

35
 {
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "insert into application values('" +
Textname.Text + "','" + Textadd.Text + "','" +
Textmobile.Text + "','" + Textemail.Text + "','" +
ddlqualif.SelectedItem.ToString() + "','" +
ddlpassedout.SelectedItem.ToString() + "','" +
Textskills.Text + "','"
+ddlinterest.SelectedItem.ToString() + "')";
SqlCommand cmd = new SqlCommand(sql,con);
cmd.ExecuteNonQuery();
con.Close();
lbljob.Visible = true;
}

//protected void Button1_Click(object sender,

EventArgs e)
//{
// Textname.Text = "";
// Textadd.Text = "";
// Textmobile.Text = "";
// Textemail.Text = "";
// ddlqualif.SelectedItem.ToString() = "";
// ddlpassedout.SelectedItem.ToString() = "";
// Textskills.Text = "";
// ddlinterest.SelectedItem.ToString() = "";
//}
}

Communication

sing 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 System.Data.SqlClient;

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

{
SqlConnection con = new SqlConnection("Data
Source=APTTECH3;Initial Catalog=kpo;Integrated
Security=True");

36
 protected void Page_Load(object sender, EventArgs e)
{
string sql = "select * from chat";
SqlCommand cmd1 = new SqlCommand(sql, con);
SqlDataReader dr = cmd1.ExecuteReader();
while (dr.Read())
{
ListBox1.Items.Add(dr[1].ToString());
}
con.Close();
}

public void Button1_Click(object sender, EventArgs e)

{

con.Open();
SqlCommand cmd = new SqlCommand("insert into
chat(kpomessage) values ('" + Textkpo.Text + "')",con);
cmd.ExecuteNonQuery();

}
protected void Btnclear_Click(object sender,
EventArgs e)
{
Textkpo.Text = "";
}
}

Feedback

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 System.Data.SqlClient;

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

{

37
 string conn = "Data Source=APTTECH3;Initial
Catalog=kpo;Integrated Security=True";
protected void Page_Load(object sender, EventArgs e)
{
lblerror.Visible = false;
Imagtanku.Visible = false;
Textsmail.Text = "[email protected]";
}
protected void Button2_Click(object sender, EventArgs
e)
{
if (Textsmail.Text != "" && Textname.Text != ""
&& Textcmail.Text != "" && Textcomment.Text != "")
{
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "insert into feedback values('"
+ Textsmail.Text + "','" + Textname.Text + "','" +
Textcmail.Text + "','" + Textcomment.Text + "')";
SqlCommand cmd = new SqlCommand(sql, con);
cmd.ExecuteNonQuery();
con.Close();
Imagtanku.Visible = true;
}
else
{
lblerror.Visible = true;
}
}
protected void Button1_Click(object sender, EventArgs
e)
{
Textname.Text = "";
Textcmail.Text = "";
Textcomment.Text = "";

}
}
Registration:

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

38
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;

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

{
string conn = "Data Source=APTTECH3;Initial
Catalog=kpo;Integrated Security=True";
protected void Page_Load(object sender, EventArgs e)
{
lblreg.Visible = false;
}
protected void Btnsubmit_Click(object sender,
EventArgs e)
{
SqlConnection con = new SqlConnection(conn);
con.Open();
string sql = "insert into comregistration
values('" + Textname.Text + "','" + Textpwd.Text + "','"
+ Textcomp.Text + "','" + Textadd.Text + "','" +
ddlcity.SelectedItem.ToString() + "','" + Textmobile.Text
+ "','" + Textemail.Text + "')";
SqlCommand cmd = new SqlCommand(sql, con);
cmd.ExecuteNonQuery();
con.Close();
lblreg.Visible = true;
}
protected void btnclear_Click(object sender,
EventArgs e)
{
Textname.Text = "";
Textpwd.Text = "";
Textcomp.Text = "";
Textadd.Text = "";
Textmobile.Text = "";
Textemail.Text = "";
}
}

39
 CHAPTER-8

SYSTEM TESTING

System testing involves user training system testing and successful

running of the developed proposed system. The user tests the developed system and
changes are made according to their needs. The testing phase involves the testing of
developed system using various kinds of data.
An elaborate testing of data is prepared and the system is tested using the test
data. While testing, errors are noted and the corrections are made. The corrections are
also noted for the future use. The users are trained to operate the developed system.
TESTING:
System testing is the stage of implementation that is aimed at ensuring that the
system works accurately and efficiently before live operation commences. Testing is
vital to the success of the system. System testing makes logical assumption that if all
the parts of the system are correct, then the goal will be successfully achieved. A
series of testing are done for the proposed system before the system is ready for the
user acceptance testing.
The following are the types of Testing:
1. Unit Testing
2. Integration Testing
3. Validation Testing
4. Verification testing
5. User acceptance testing
8.1 Unit Testing
Unit testing focuses verification efforts on the smallest unit of the software
design, the module. This is also known as “module testing”. The modules are tested
separately. This testing was carried out during programming stage itself. In this
testing each module is found to be working satisfactorily as regards to the expected
output rom the module.

40
8.2 Integration Testing
Data can be lost across an interface: one module can have adverse efforts on
another. Integration testing is the systematic testing for construction of program
structure, while at the same time conducting tests to uncover errors associated within
the interface. Here correction is difficult because the isolation of cause is complicated
by the cast expense of the entire program. Thus in the integration testing step, all the
errors uncovered are corrected for the next testing steps.
8.3 Validation Testing
At the conclusion of integration testing, software is completely assembled as a
package, interfacing errors have been uncovered and corrected and a final series of
software tests begins validation test has been conducted one of the two possible
conditions exists. One is the function or performance characteristics confirm to
specification and are accepted and the other is deviation from specification is
uncovered and a deficiency list is created.
8.4 Verification Testing
Verification is a fundamental concept in software design. This is the bridge
between customer requirements and an implementation that satisfies those
requirements.
This is verifiable if it can be demonstrated that the testing will result in an
implementation that satisfies the customer requirements.
Inadequate testing or non-testing leads to errors that may appear few months
later. This will create two problems
 Time delay between the cause and appearance of the problem.
 The effect of the system errors on files and records within the system
8.5 User Acceptance Testing

User acceptance testing of a system is the key factor of the success of any
system. The system under study is tested for the user acceptance by constantly
keeping in touch with the prospective system users at any time of developing and
making changes whenever required.

41
 CHAPTER 9

PROBLEMS FACD

When there is a clear goal in sight but no clear set of directions or means to
attain
that goal, then it is called a problem. Problems can be broken down into four
aspects; goal, givens, means of transforming conditions, and obstacles.
Goal – the goal is the desired end state which the problem solving is being
directed toward.
The hope is to reach that end state and be able to assess whether or not you
achieved what you wanted.
Givens- these are the objects, conditions, and constraints that accompany a
problem, and can be either explicit or implicit.
Means of transforming conditions- there should be a way of changing the
initial state of the problem. this is most usually a person’s knowledge or skill level.
For instance ,a computer programmer presented with a problem would utilize his or
her knowledge of programming language to transform the state of the problem.
Obstacles- the problem should present a challenge. If there are no challenges
involved and the situation can be easily solved then it is not so a problem so much as
a routines task.
Every problem has a problem faced, which is the whole range of
possible states and operators. only some of these states and operators will bring the
person closer to the goal state. The problem starts at the initial state and operators
are applied to change the state, creating a series of intermediate states that should
hopefully lead to the final goal state

42
 CHAPTER 10

FUTURE PLANS

Every application has its own merits and demerits. The project has
covered almost all the requirements. Further requirements and improvements can
easily be done since the coding is mainly structured or modular in nature. Changing
the existing modules or adding new modules can append improvements. Further
enhancements can be made to the application, so that the web site functions very
attractive and useful manner than the present one.

43
 CONCLUSION

It is concluded that the application works well and satisfy the users.
The application is tested very well and errors are properly debugged. The site is
simultaneously accessed from more than one system. Simultaneous login from more
than one place is tested.
The site works according to the restrictions provided in their respective
browsers. Further enhancements can be made to the application, so that the web site
functions very attractive and useful manner than the present one. The speed of the
transactions become more enough now.

44
APPENDIX

Home Page

45
 Login

46
REGEISTARION

47
APPLICATION

48
ABOUT US

49
CONTACT DETAILS

50
CAREERS

51
CAREERS DETAILS

52
CLIENT DETAILS

53
FEEDBACK

54
FEEDBACK DETAILS

55
 REFERENCES

1. STEVE HARRIS AND ROBMACDONALD,

“WEB DEVELOPMENT WITH C#.NET”

-APRES

2. MATTHEW MACDONALD,
“MICROSOFT VISUAL BASIC.NET PROGRAMMER’S
COOKBOOK”
-TATA McGraw HILL EDITION

3. CHRIS GOODE, JOHN KAUFFMAN

“BEGINNING ASP.NET 1.0 WITH VISUAL C # .NET”
-WROX PROGRAMMER TO PROGRAMMER

4. Douglas O.Reilly,
“DESIGNING MICROSOFT ASP.NET APPLICATIONS”
-TATA McGraw HILL EDITION

56
 BIBLIOGRAPHY

► www.codeproject.com/KB/custom-controls/asppopup.aspx

► http://www.developerfusion.com/code/4673/programatically-load-user-controls/

► http://www.developerfusion.com/code/4596/how-to-access-a-mysql-database-

with-net/

► http://www.developerfusion.com/code/3826/adding-controls-to-placeholders-

dynamically/

► http://aspalliance.com/

1125_Dynamically_Templated_GridView_with_Edit_Delete_and_Insert_Options

► http://www.15seconds.com/issue/041020.htm

► http://www.a1vbcode.com/app-3619.asp

► http://www.aspcode.net/ASPNET-301-redirect.aspx

► http://www.aspcode.net/Master-pages-in-ASP-free-template-engine.aspx

57