You are on page 1of 75

Department of Computer Science

TABLE OF CONTENTS
Topic
Page Number

Introduction
Page No. 4

Objective of Project

Page No. 5

Benefits to prospective clients from the project

Page No. 7

Functional Details of Different Modules

Page No. 9

Database Schema and design

Page No. 13

DFD and ER-DIGRAM

Page No.28

Hardware and Software Requirement specifications

Page No. 34

Requirement Analysis

Page No. 36

Feasibility Study

Page No. 38

Coding

Testing
1

Page No. 44

Page No. 60

Department of Computer Science

Security Features

Page No. 73

Future Scope and Enhancements

Page No. 74

References
Page No. 75

Department of Computer Science

INTRODUCTION

Department of Computer Science

INTRODUCTION
Ebani.in serves companies in North America, Europe, and Asia. Were based
in metropolitan Atlanta, Georgia, with additional offices in New Jersey, Virginia,
and the Carolinas; as well as in Middlesex, England. Our wholly owned, fully
equipped development centers are in Delhi and Meerut, India. Among our
numerous awards and rankings on top business lists, we are honored to have been
named National Supplier of the Year by the National Minority Supplier
Development Council.

Since last several years fundamental changes taking place in education system. A
rapid development and versatile use of the Web requires appropriate and skilled
learning process. Here, an approach to test technical skills and the learning process
is illustrated by the scalable and efficient platform, highly optimized for the users
in various software/networking technologies.

Department of Computer Science

PROJECT OBJECTIVES

E-Learning is a comprehensive web-based Exam Management Software. It is


designed for better interaction between students, teachers & Admin management.
This management software very gracefully handles all the requirements for easy
Online Learning.

The software being web based can be accessed from anywhere in the world, which
enables the students, teachers, and any registered user to test his/her skills any time
on various technologies & subjects.

Since last several years fundamental changes taking place in education system. A
rapid development and versatile use of the Web requires appropriate and skilled
learning process. Here, an approach to test technical skills and the learning process
is illustrated by the scalable and efficient platform, highly optimized for the users
in various software/networking technologies.

Department of Computer Science

The professionals or students are very busy now days, this E-Learning
system helps them to test their skills at anytime from anywhere. They can check
their performance from a remote location. They can also register for various
technologies/subjects through online registration.

Department of Computer Science

Proposed System

Department of Computer Science

BENEFITS TO PROSPECTIVE CLIENTS FROM THE PROJECT

This project will be designed for both professionals and students or any
interested user can register with this system to test their skills and parallel learning
process on various fields and technologies.
The software being web based can be accessed from anywhere in the world,
which enables the Students, Professionals and any registered user to test his/her
skills anytime and anywhere.

Department of Computer Science

Modules & Description

Department of Computer Science

FUNCTIONAL DETAILS OF DIFFERENT MODULES

Admin: Admin related tasks are provided in sub menus are as follows:

Admin Account setting : You can manage / edit existing admin user account

details.
Student Account setting : You can manage / edit existing student user

account details.
Assign Subject : Admin can assign subjects/classes to the faculties.
Add New Class : Admin can add new class to the system, so that

students/users can get more options on various technologies.


Account Blocking : Admin can block any user on this system to login if

found doing some suspicious activities.


Profile Editing : Admin can edit any user profile information and Individual

user can edit his/her profile Information.


User Registration : Admin can register any user Class Modrerator / general

user(student).
Logout : Admin/User can redirect to login page.

Account Setting:

10

Department of Computer Science

Profile Editing : Any user can edit his/her profile information.


Password Change: Any user can edit his/her Password.

After successful login Admin/Moderators will be redirected to their Home page


there they will find the listing of their assigned classes/subjects.
After selecting the class following option will be visible:
Create Test: Admin/moderators can create a test for assigned
classes/subjects.
Uploading Study material: Admin/moderators can upload subject related
notes for student so that user can easily find study material on various
subject.
Assign test: After creating test Admin/moderators can assign these test to
user.

User: User related tasks are provided in sub menus are as follows:

Choose Subject : User can choose subjects/classes.


Profile Editing :User can edit his/her profile information .
User Registration :New user can register from login page.

Take Assessment: User can attempt their corresponding activated

assessments.

Gradebook : User can view their assessment grades/marks by clicking on

this link.
Downloading Study material: Admin/student can download subject related
notes from website so that user can easily study the material provided on

11

various subject.
Logout : User can redirect to login page.

Department of Computer Science

Some Common Features are provided to both type of the user :


Forum: A forum is provided to facilitate the users to communicate on
various topics.
Testimonials: A testimonial is published on each page of website ,which
shows the latest news/notice updated by the user/faculity.
Course Catalog: The course catalog provides the knowledge about the
course running on the website.

DATABASE SCHEMA
12

& DESIGN

Department of Computer Science

DATABASE SCHEMAS

Table Name: Admin_credentials


Primary Key: Email_id
13

Department of Computer Science

Data Name

Data type

width

Constraint

Password

Varchar

20

Not null

Email_id

Varchar

30

Not null

Status

Varchar

Not null

width

Constraint

Table Name: Admin_detail


Primary Key: Email_id
Data Name

Data type

Sno

int

F_name

varchar

20

Not null

L_name

Varchar

20

Not null

Address

Varchar

100

Not null

Contact_no

Varchar

50

Not null

Email_id

Varchar

25

Not null

Age

Varchar

Not null

High_qul

Varchar

50

Not null

Gender

Varchar

10

Not null

Dob

Varchar

20

Not null

Hobby

Varchar

20

Not null

Interest

Varchar

50

Not Null

14

Not null

Department of Computer Science

Table Name: Student_credentials


Primary Key: Email_id
Data Name

Data type

width

Constraint

Password

Varchar

20

Not null

Email_id

Varchar

30

Not null

Status

Varchar

Not null

width

Constraint

Table Name: Student_detail


Primary Key: Email_id
Data Name

Data type

Sno

int

F_name

varchar

20

Not null

L_name

Varchar

20

Not null

Address

Varchar

100

Not null

Contact_no

Varchar

50

Not null

Email_id

Varchar

25

Not null

Age

Varchar

Not null

High_qul

Varchar

50

Not null

15

Not null

Department of Computer Science

Gender

Varchar

10

Not null

Dob

Varchar

20

Not null

Percentage

Varchar

Not Null

College

Varchar

50

Not null

Hobby

Varchar

20

Not null

width

Constraint

Table Name: admin_subject_mapping


Primary Key: Sno
Data Name

Data type

Sno

int

Email_id

Varchar

30

Not null

Subject

Varchar

10

Not null

Subject_fee

Varchar

Not null

Duration

Varchar

10

Not null

width

Constraint

Not null

Table Name: student_subject_mapping


Primary Key: Sno
Data Name
16

Data type

Department of Computer Science

Sno

int

Not null

U_id

Varchar

50

Not null

Subject

Varchar

20

Not null

width

Constraint

Table Name: forum_question


Primary Key: Sno
Data Name

Data type

Sno

int

Question

Varchar

100

Not null

Date2

Varchar

17

Not null

width

Constraint

Not null

Table Name: questionreply


Primary Key: Sno
Data Name

Data type

Sno

int

Not null

ques_id

Int

Not null

Reply

Varchar

250

Not null

Date2

Varchar

17

Not null

Uname

Varchar

30

Not null

17

Department of Computer Science

Table Name: student_grade


Primary Key: Sno
Data Name

Data type

width

Constraint

Sno

Int

Email_id

Varchar

30

Not null

Test_name

Varchar

20

Not null

Test_id

Varchar

Not null

Marks_obtained

Varchar

Not null

Max_marks

Varchar

Not null`

Date1

Varchar

20

Not null

width

Constraint

Not null

Table Name: sub_detail


Primary Key: Subject
Data Name

Data type

Sno

int

Subject

Varchar

10

Not null

Subject_fee

Varchar

10

Not null

18

Not null

Department of Computer Science

Duration

Varchar

10

Not null

width

Constraint

Table Name: test_detail


Primary Key:Sno
Data Name

Data type

Sno

int

test_name

varchar

20

Not null

Subject

Varchar

20

Not null

Test_id

Varchar

20

Not null

Instructor_name

Varchar

50

Not null

Question

Varchar

300

Not null

Option1

Varchar

100

Not null

Option2

Varchar

100

Not null

Option3

Varchar

100

Not null

Option4

Varchar

100

Not null

Correct_ans

Varchar

100

Not null

Posted_by

Varchar

30

Not null

Table Name: test_name_detail


19

Not null

Department of Computer Science

Primary Key: Sno


Data Name

Data type

width

Constraint

Sno

int

Instructor_name

Varchar

20

Not null

Instructor_id

Varchar

30

Not null

Test_name

Varchar

20

Not null

Subject

Varchar

20

Not null

Creationtime

Datetime

Not null

Not null

Table Name: testimonial


Primary Key:Sno
Data Name

Data type

Sno

int

Not null

Date_add

Datetime

Not null

Comment

Varchar

100

Not null

Username

Varchar

30

Not null

20

width

Constraint

Department of Computer Science

Table Name: user_test_record


Primary Key: Sno

Data Name

Data type

Sno

int

Email_id

Varchar

25

Not null

Test_id

Varchar

20

Not null

Test_name

Varchar

20

Not null

Question_id

Varchar

Not null

Question

Varchar

300

Not null

Option1

Varchar

100

Not null

Option2

Varchar

100

Not null

Option3

Varchar

100

Not null

Option4

Varchar

100

Not null

Correct_ans

Varchar

100

Not null

Answer

Varchar

100

Not null

Q_Serial_No_in_test Smallint

21

width

Constraint
Not null

Not null

Department of Computer Science

DATABASE SNAPSHOT

22

Department of Computer Science

DATABASE SNAPSHOT

23

Department of Computer Science

24

Department of Computer Science

25

Department of Computer Science

Data flow diagrams

26

Department of Computer Science

DATAFLOW DIAGRAM

Fig. Context Level DFD

27

Department of Computer Science

28

Department of Computer Science

Fig. 1 Level DFD

29

Department of Computer Science

Fig.

30

2 Level DFD

Department of Computer Science

Entity Relationship
diagrams

31

Department of Computer Science

E-R Diagram

32

Department of Computer Science

TECHNICAL
REQUIREMENT
SPECIFICATION

TECHICAL REQUIREMENT SPECIFICATION

33

Department of Computer Science

1. Hardware Specification:
a. Pentium-IV based PC
b. 512 MB RAM
c. 40 GB Hard Disk Space
d. 108 keys Keyboard
2. Software Specification:
a. Windows Server [2003 or 2008]
b. SQL Server 2005
c. Microsoft .net framework 3.5
d. Visual Web Developer [also called ASP.NET]
e. Visual C# [C# Language pronounced as C Sharp]
f. SQL Client Namespace for SQL Server Database Interconnection

34

Department of Computer Science

ANALYSIS

ANALYSIS

35

Department of Computer Science

Requirement Analysis
At the heart of system analysis is a detailed understanding of all important
facets of business area under investigation. (For this reason, the process of
acquiring this is often termed the detailed investigation) Analyst, working closely
with the employees and managers, must study the business process to answer
these key questions:

What is being done?


How is it being done?
How frequent does it occur?
How great is the volume of transaction or decisions?
How well is the task being performed?
Does a problem exist?
If a problem exists, how serious is it?
If a problem exists, what is the underlying cause?

Requirement analysis relies on fact-finding techniques. These include:

Interview
Questionnaires
Record inspection
On-site observation

Feasibility Study
36

Department of Computer Science

A feasibility study is conducted to select the best system that meets


performance requirement. This entails an identification description, an evaluation of
candidate system and the selection of best system for he job. The system required
performance is defined by a statement of constraints, the identification of specific
system objective and a description of outputs.

The key consideration in feasibility analysis is:

1. Economic Feasibility:

2. Technical Feasibility:

3. Operational Feasibility:

Economical feasibility

37

Department of Computer Science


It looks at the financial aspects of the project. It determines whether
the management has enough resources and budget to invest in the proposed
system and the estimated time for the recovery of cost incurred. It also determines
whether it is worth while to invest the money in the proposed project. Economic
feasibility is determines by the means of cost benefit analysis. The proposed system
is economically feasible because the cost involved in purchasing the hardware and
the software are within approachable. The personal cost like salaries of employees
hired are also nominal, because working in this system need not required a highly
qualified professional. The operating-environment costs are marginal. The less time
involved also helped in its economical feasibility. It was observed that the
organization has already using computers for other purpose, so that there is no
additional cost to be incurred for adding this system to its computers.
The backend required for storing other details is also the same database that
is Sql. The computers in the organization are highly sophisticated and dont needs
extra components to load the software. Hence the organization can implement the
new system without any additional expenditure. Hence, it is economically feasible.

Software Cost :

Visual Studio

Microsoft SQL Server:

38

20,000/-

15,000/-

Department of Computer Science

Manpower Cost

Team cost

25,000/-

System Cost

40,000/-

Total Cost

1, 00,000/-

Technical Feasibility

It is a measure of the practically of a specific technical solution and the


availability of technical resources and expertise

The proposed system uses Asp.net as front-end and SQL server 2005 as
back-end tool.

39

Department of Computer Science

SQL Server 2005 is a popular tool used to design and develop database
objects such as table views, indexes.

The above tools are readily available, easy to work with and widely used
for developing commercial application.

Hardware used in this project are- p4 processor 2.4GHz, 128 MB


RAM, 40 GB hard disk, floppy drive. These hardware were already available on the
existing computer system. The software like MS-Access 2003, Web logic Server,
Thin Driver, JDK, JSDK, J2EE and operating system WINDOWS-XP used were
already installed

On the existing computer system. So no additional hardware

and software were required to purchase and it is technically feasible. The technical
feasibility is in employing computers to the organization. The organization is
equipped with enough computers so that it is easier for updating. Hence the
organization has not technical difficulty in adding this system.

Tools Used :

1) Visual Studio 2008


2) Microsoft SQL Server 2005
3) Adobe Dreamweaver CS5

Operational Feasibility
40

Department of Computer Science

The system will be used if it is developed well then be resistance for users
that undetermined

No major training and new skills are required as it is based on


DBMS model.

It will help in the time saving and fast processing and dispersal
of user request and applications.

New product will provide all the benefits of present system with
better performance.

Improved information, better management and collection of the


reports.

User support.

User involvement in the building of present system is sought to


keep in mind the user specific requirement and needs.

User will have control over there own information. Important


information such as pay-slip can be generated at the click of a
button.

41

Department of Computer Science

Faster and systematic processing of user application approval,


allocation of IDs, payments, etc. used had greater chances of
error due to wrong information entered by mistake.

Behavioral Feasibility

People are inherent to change. In this type of feasibility check, we come to


know if the newly developed system will be taken and accepted by the working
force i.e. the people who will use it.

42

Department of Computer Science

Coding

CODING

43

Department of Computer Science

GUI INTERFACE CODING

Our project is web based project. We have used HTML to provide the GUI
Interface.
For creating forms we use form tag of html
Addnewsub.aspx
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<style>
.invisible
{
display:none;
}
.style12
{
color: #FFFFCC;
}
.style28
{
color: #800000;
width: 420px;
font-weight: bold;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<table style="height: 272px; width: 489px; " >
<tr><td class="style28">SUBJECT NAME</td><td>
<asp:TextBox ID="txt_sub" runat="server"></asp:TextBox>
</td><td class="style1">
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ErrorMessage="*" ControlToValidate="txt_sub"
ValidationGroup="a"></asp:RequiredFieldValidator>
</td></tr>
<tr><td class="style28">SUBJECT FEES</td><td>
<asp:TextBox ID="txt_subfee" runat="server"></asp:TextBox>
</td><td class="style1">
<asp:RequiredFieldValidator ID="RequiredFieldValidator2"
runat="server"
ErrorMessage="*" ControlToValidate="txt_subfee"
ValidationGroup="a"></asp:RequiredFieldValidator>
</td></tr>
<tr><td class="style28">DURATION</td><td>

44

Department of Computer Science


<asp:TextBox ID="txt_duration" runat="server"></asp:TextBox>
</td><td class="style1">
<asp:RequiredFieldValidator ID="RequiredFieldValidator3"
runat="server"
ErrorMessage="*" ControlToValidate="txt_duration"
ValidationGroup="a"></asp:RequiredFieldValidator>
</td></tr>
<tr><td align="center">
<asp:LinkButton ID="lbtn_Submit" runat="server" Font-Underline="False"
onclick="lbtn_Submit_Click" style="color: #000066; font-weight:
700">ADD</asp:LinkButton>
</td><td align="center">
<asp:LinkButton ID="lbtn_rest" runat="server" Font-Underline="False"
onclick="lbtn_rest_Click" style="color: #000066; font-weight:
700">RESET</asp:LinkButton></td><td class="style1">
<asp:Label ID="lbl_msg" runat="server" Text=""></asp:Label>
</td></tr>
</table>
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
Width="427px" onrowupdating="GridView1_RowUpdating"
onrowediting="GridView1_RowEditing"
onrowcancelingedit="GridView1_RowCancelingEdit"
onselectedindexchanged="GridView1_SelectedIndexChanged">
<Columns>
<asp:BoundField DataField="sno" HeaderText="sno" SortExpression="sno"
ReadOnly="true" >
<ControlStyle CssClass="invisible" />
<HeaderStyle CssClass="invisible" Width="50px" />
<ItemStyle CssClass="invisible" />
</asp:BoundField>
<asp:TemplateField>
<HeaderTemplate>
S.No
</HeaderTemplate>
<ItemTemplate>
<%# Container.DataItemIndex + 1 %>
</ItemTemplate>
<HeaderStyle BackColor="#264258" ForeColor="White" Height="24px"
Width="50px" />
</asp:TemplateField>
<asp:BoundField DataField="Subject"
HeaderText="Subject" SortExpression="Subject" ReadOnly="true" >
<ControlStyle CssClass="invisible" />
<HeaderStyle CssClass="invisible" Width="50px" />
<ItemStyle CssClass="invisible" />
</asp:BoundField>
<asp:TemplateField HeaderText="Subject">
<EditItemTemplate>

45

Department of Computer Science


<div> <asp:TextBox ID="txt_name"
runat="server" Text='<%# Bind("subject") %>' TextMode="SingleLine"
Width="200px" ValidationGroup="GridArm"></asp:TextBox> </div>
<div>
<asp:RequiredFieldValidator
ID="RequiredFieldValidator6" ControlToValidate="txt_name" runat="server"
ValidationGroup="GridArm"
ErrorMessage="Subject..?"></asp:RequiredFieldValidator></div>
</EditItemTemplate>
<ItemTemplate >
<asp:Label ID="lblNewname"
runat="server" Text='<%# Bind("subject") %>'></asp:Label>
</ItemTemplate>
<HeaderStyle BackColor="#264258"
ForeColor="White" Width="100px" HorizontalAlign="Left" />
</asp:TemplateField>
<asp:TemplateField HeaderText="Subject Fees">
<EditItemTemplate>
<div> <asp:TextBox ID="txt_fee"
runat="server" Text='<%# Bind("subject_fee") %>' TextMode="SingleLine"
Width="200px" ValidationGroup="GridArm"></asp:TextBox> </div>
<div>
<asp:RequiredFieldValidator
ID="RequiredFieldValidator7" ControlToValidate="txt_fee" runat="server"
ValidationGroup="GridArm"
ErrorMessage="Fees..?"></asp:RequiredFieldValidator></div>
</EditItemTemplate>
<ItemTemplate >
<asp:Label ID="lblNewfee"
runat="server" Text='<%# Bind("subject_fee") %>'></asp:Label>
</ItemTemplate>
<HeaderStyle BackColor="#264258"
ForeColor="White" Width="100px" HorizontalAlign="Left" />
</asp:TemplateField>
<asp:TemplateField HeaderText="Duration">
<EditItemTemplate>
<div> <asp:TextBox ID="txt_dura"
runat="server" Text='<%# Bind("duration") %>' TextMode="SingleLine"
Width="200px" ValidationGroup="GridArm"></asp:TextBox> </div>
<div>
<asp:RequiredFieldValidator ID="RequiredFieldValidator8"
ControlToValidate="txt_dura" runat="server"
ValidationGroup="GridArm"
ErrorMessage="Duration...?"></asp:RequiredFieldValidator></div>
</EditItemTemplate>
<ItemTemplate >
<asp:Label ID="lblNewdura"
runat="server" Text='<%# Bind("duration") %>'></asp:Label>
</ItemTemplate>
<HeaderStyle BackColor="#264258"
ForeColor="White" Width="100px" HorizontalAlign="Left" />

46

Department of Computer Science

</asp:TemplateField>

<asp:CommandField ShowEditButton="True" />


<asp:CommandField ShowSelectButton="True" SelectText="Delete" />
</Columns>
</asp:GridView>
</asp:Content>

Login.aspx
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled Page</title>
<style type="text/css">
.style1
{
width: 143px;
}
.style2
{
font-family: "Comic Sans MS";
color: #FFFF00;
}
.style4
{
width: 143px;
font-family: "Comic Sans MS";
color: #FFFF00;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<center>
<div style="height: 388px; margin-top: 2px">
<fieldset style="border-style: outset; border-color: #0000FF; width:325px;
height: 208px; background-repeat: repeat; background-image:
url('./image/FN02.JPG');">
<table style="height: 166px; width: 309px">
<tr><td align="center" style="font-size: larger; " colspan="3"
class="style2">LOGIN</td>
</tr>
<tr><td class="style1" style="font-size: larger; color: #660066">
<asp:RadioButton ID="rbtn_st" runat="server" AutoPostBack="True"
Checked="True"
GroupName="login" oncheckedchanged="rbtn_st_CheckedChanged"
style="font-family: 'Comic Sans MS';" Text="STUDENT"
ForeColor="#FFFF66" />
</td><td>
<asp:RadioButton ID="rbtn_ad" runat="server" AutoPostBack="True"

47

Department of Computer Science


GroupName="login" oncheckedchanged="rbtn_ad_CheckedChanged"
style="color: #FFFF00; font-family: 'Comic Sans MS';"
Text="ADMIN"

ForeColor="Yellow" />
</td><td>
&nbsp;</td></tr>
<tr><td class="style4" style="font-size: larger; ">USER NAME</td><td>
<asp:TextBox ID="txt_un" runat="server" Height="27px" Width="155px"
BorderColor="#CC0099"
OnTextChanged="txt_un_TextChanged"
AutoPostBack="True"></asp:TextBox></td><td>
</td></tr>
<tr><td class="style4" style="font-size: larger">PASSWORD</td><td>
<asp:TextBox ID="txt_pwd" runat="server" Height="27px" Width="155px"
BorderColor="#CC0099" BorderStyle="Inset" TextMode="Password"
></asp:TextBox></td><td>
&nbsp;</td></tr>
<tr><td class="style1">
<asp:LinkButton ID="btn_nu" runat="server" onclick="btn_nu_Click"
style="font-family: 'Comic Sans MS'">New User</asp:LinkButton>
</td><td>
<asp:LinkButton ID="btn_sin" runat="server" onclick="btn_sin_Click"
ValidationGroup="a" style="font-family: 'Comic Sans MS'">Sign
in</asp:LinkButton>
</td><td>
&nbsp;</td></tr>
<tr><td class="style1" align="left">
<asp:LinkButton ID="lbtn_fgp" runat="server"
onclick="lbtn_fgp_Click">Forget passward</asp:LinkButton>
</td><td>
<asp:CheckBox ID="chk_rem" runat="server" ForeColor="#000EF7"
Text="Remember Me" />
</td><td>
&nbsp;</td></tr>
<tr><td class="style1" align="left">
<asp:Label ID="lba_msg" runat="server"
style="font-style: italic; font-size: medium; color: #0000FF"
Text=""></asp:Label>
</td><td>
&nbsp;</td><td>
&nbsp;</td></tr>
</table>
</fieldset>
</div>
</center>
</form>
</body>
</html>

Profileditadmin.aspx
48

Department of Computer Science


asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<style type="text/css">
.style1
{
}

width: 147px;
text-align: left;

.style5
{

font-size: large;
font-weight: bold;
color: #000066;
text-decoration: underline;
.style8
{
text-align: left;
height: 23px;
}
.style12
{
text-align: left;
height: 53px;
width: 134px;
}
.style13
{
height: 53px;
}
.style14
{
height: 53px;
}
.style15
{
color: #FFFF00;
font-weight: bold;
text-align: right;
padding-right: 15px;
height: 47px;

}
.style16
{

text-align: left;
height: 47px;
width: 147px;
}
.style17
{

49

Department of Computer Science

height: 47px;
width: 19px;

}
.style19
{

height: 47px;
}
.style21
{
text-align: left;
height: 36px;
width: 147px;

}
.style22
{

height: 36px;
width: 19px;

}
.style24
{
height: 36px;
}
.style25
{
height: 36px;
}
.style27
{
text-align: left;
height: 42px;
color: #87A824;
width: 147px;

}
.style28
{

height: 42px;
width: 19px;

}
.style30
{
height: 42px;
}
.style31
{
height: 42px;
}
.style33
{

50

Department of Computer Science

text-align: left;
height: 54px;
width: 147px;
}
.style34
{
height: 54px;
width: 19px;
}
.style35
{
height: 54px;
}
.style36
{
height: 54px;
}
.style37
{
color: #FFFF00;
font-weight: bold;
text-align: right;
padding-right: 15px;
height: 55px;

}
.style38
{

text-align: left;
height: 55px;
width: 147px;
}
.style39
{
height: 55px;
width: 19px;
}

.style40

{
color: #FFFF00;
font-weight: bold;
text-align: right;
}
{

height: 42px;
.style42
color: #FFFF00;
font-weight: bold;
text-align: right;

51

Department of Computer Science


}
.style43
{
color: #FFFF00;
font-weight: bold;
text-align: right;
}
{

height: 46px;
.style44

width: 19px;
}
.style45
{
text-align: left;
height: 23px;
width: 134px;
}
.style46
{
text-align: left;
height: 36px;
width: 134px;
}
.style47
{
}
{

width: 248px;
.style48

color: #B5773F;
}
.style49
{
color: #800000;
}
.style53
{
width: 248px;
height: 46px;
}
.style54
{
text-align: left;
height: 46px;
width: 134px;
}
.style56
{
height: 46px;
width: 30%;
}
.style58
{

52

Department of Computer Science


height: 46px;
}
.style59
{
text-align: left;
height: 46px;
width: 147px;
}
.style60
{
height: 46px;
width: 19px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<iframe width="174px" height="189px" name="gToday:normal:agenda.js"
id="gToday:normal:agenda.js" src="dtpicker/ipopeng.htm" scrolling="no"
frameborder="0" style="visibility:visible; z-index:999; position:absolute;
top:-500px; left:-500px;"></iframe>
<div style="margin-top: 69px; text-align:center; height: 459px; width:
696px; margin-right: 0px;" ><span class="style5">Edit Profile</span><center>

<table style="border-style: inset; border-color: #9900CC; height: 425px;


width: auto; ">
<tr>
<td class="style40"><span class="style49">First
Name</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:
</td>
<td class="style27">
<asp:Label ID="lb_fname" runat="server" Text=""
ForeColor="Yellow" style="color: #800000; font-weight:
700"></asp:Label>
</td><td class="style28">
<asp:LinkButton ID="lbtn_fn" runat="server" onclick="lbtn_fn_Click"
ForeColor="Yellow" style="color:
#800000">Edit</asp:LinkButton></td>
<td align="left" class="style47">
<asp:Label ID="lb_nfn" runat="server" Text="New First Name"
Visible="False"
ForeColor="Yellow" style="font-weight: 700; color:
#800000;"></asp:Label></td>
<td class="style46">
<asp:TextBox ID="txt_fn" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td class="style30" style="width:auto;" >
<asp:LinkButton ID="lbtn_ok" runat="server"
onclick="lbtn_ok_Click"
Visible="False" ForeColor="Yellow" style="color:
#800000">Ok</asp:LinkButton></td>
<td class="style31" style="width:auto;" >

53

Department of Computer Science


<asp:LinkButton ID="lbtn_fc" runat="server"
onclick="lbtn_fc_Click"
ForeColor="Yellow" Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>
<td class="style43"><span class="style49">Last
Name&nbsp;&nbsp;&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:
</td>
<td class="style59">
<asp:Label ID="lb_lname" runat="server" style="color: #800000"
ForeColor="Yellow"></asp:Label>
</td><td class="style60">
<asp:LinkButton ID="lbtn_ln" runat="server" onclick="lbtn_ln_Click"
ForeColor="Yellow" style="color: #800000"
>Edit</asp:LinkButton>
</td>
<td align="left" class="style53">
<asp:Label ID="lb_nln" runat="server" Text="New Last Name"
Visible="False"
ForeColor="Yellow" style="font-weight: 700; color:
#800000;"></asp:Label></td>
<td class="style54">
<asp:TextBox ID="txt_ln" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td class="style58">
<asp:LinkButton ID="lbtn_okl" runat="server"
Visible="False" onclick="lbtn_okl_Click"
ForeColor="Yellow"
style="color: #800000">Ok</asp:LinkButton></td>
<td class="style56">
<asp:LinkButton ID="lbtn_fc0" runat="server"
onclick="lbtn_fc0_Click"
ForeColor="Yellow" Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>
<td class="style42"><span
class="style49">Address&nbsp;&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
</td>
<td class="style16">
<asp:Label ID="lb_add" runat="server" style="color: #800000"
ForeColor="Yellow"></asp:Label>
</td><td class="style17">
<asp:LinkButton ID="lbtn_add" runat="server" onclick="lbtn_add_Click"
ForeColor="Yellow" style="color: #800000"
>Edit</asp:LinkButton></td>
<td align="left" class="style47">
<asp:Label ID="lb_nadd" runat="server" Text="New Address"
Visible="False"
ForeColor="Yellow" style="font-weight: 700; color:
#800000;"></asp:Label></td>

54

Department of Computer Science


<td class="style46">
<asp:TextBox ID="txt_add" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td >
<asp:LinkButton ID="lbtn_okadd" runat="server"
Visible="False" onclick="lbtn_okadd_Click"
ForeColor="Yellow"
style="color: #800000">Ok</asp:LinkButton></td>
<td class="style19">
<asp:LinkButton ID="lbtn_fc1" runat="server"
onclick="lbtn_fc1_Click"
ForeColor="Yellow" Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>
<td class="style42"><span class="style49">Contact
No&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</td>
<td class="style1">
<asp:Label ID="lb_cn" runat="server" ForeColor="Yellow" style="color:
#800000"></asp:Label>
</td><td class="style44">
<asp:LinkButton ID="lbtn_cn" runat="server" onclick="lbtn_cn_Click"
ForeColor="Yellow" style="color: #800000">Edit</asp:LinkButton></td>
<td align="left" class="style47">

<asp:Label ID="lb_ncn" runat="server" Text="New Contact No."


Visible="False"
ForeColor="Yellow" style="font-weight: 700; color:
#800000;"></asp:Label></td>
<td class="style45">
<asp:TextBox ID="txt_cn" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td>
<asp:LinkButton ID="lbtn_okcn" runat="server"
Visible="False" onclick="lbtn_okcn_Click"
ForeColor="Yellow"
style="color: #800000">Ok</asp:LinkButton></td>
<td class="style6">
<asp:LinkButton ID="lbtn_fc2" runat="server"
onclick="lbtn_fc2_Click"
ForeColor="Yellow"
Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>
<td class="style42"><span
class="style49">Age&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</td>
<td class="style1">
<asp:Label ID="lbl_age" runat="server" Text="" ForeColor="Yellow"
style="color: #800000"></asp:Label>
</td><td class="style44">

55

Department of Computer Science


<asp:LinkButton ID="lbtn_age_edit" runat="server"
ForeColor="Yellow" onclick="lbtn_age_edit_Click"
style="color: #800000"
>Edit</asp:LinkButton>
</td>
<td align="left" style="font-weight: 700" class="style47">
<asp:Label ID="lb_nageo" runat="server" Text="New Age"
Visible="False"
ForeColor="Yellow" style="color: #800000"></asp:Label></td>
<td class="style45">
<asp:TextBox ID="txt_age0" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td>
<asp:LinkButton ID="lbtn_okage" runat="server"
ForeColor="Yellow" Visible="False"
onclick="lbtn_okage_Click"
style="color: #800000">Ok</asp:LinkButton></td>
<td class="style6">
<asp:LinkButton ID="lbtn_cage" runat="server"
onclick="lbtn_cage_Click"
ForeColor="Yellow"
Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>

<td class="style42"><span
class="style49">Gender</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</td>
<td class="style1">
<asp:Label ID="lbl_gen" runat="server"
ForeColor="Yellow"
style="color: #800000"></asp:Label>
</td><td class="style44" >
<asp:LinkButton ID="lbtn_gen"
runat="server" ForeColor="Yellow"
onclick="lbtn_gen_Click" style="color:
#800000">Edit</asp:LinkButton>
</td>
<td align="left" class="style47">
<asp:Label ID="lbl_geno" runat="server" ForeColor="Yellow"
Text="Gender"
style="font-weight: 700; color: #800000;"
Visible="False"></asp:Label>
</td>
<td class="style12">
<asp:TextBox ID="txt_geno" runat="server"
BorderColor="#990099" Visible="False"></asp:TextBox>
</td>
<td class="style13">
<asp:LinkButton ID="lbtn_okgen" runat="server"
ForeColor="Yellow"
Visible="False" onclick="lbtn_okgen_Click"
style="color: #800000">Ok</asp:LinkButton>

56

Department of Computer Science


</td>
<td class="style14">
<asp:LinkButton ID="lbtn_cngen" runat="server"
ForeColor="Yellow"
Visible="False" onclick="lbtn_cngen_Click1"
style="color: #800000">Cancel</asp:LinkButton>
</td></tr>
<tr>
<td class="style42"><span class="style49">Date of
Birth</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</td>
<td class="style1">
<asp:TextBox ID="txt_dob" runat="server"
BorderStyle="Outset" ForeColor="Yellow"
Width="117px" BorderColor="#000066"></asp:TextBox>
<a hidefocus="" href="javascript:void(0)"
onclick="if(self.gfPop)
gfPop.fPopCalendar(document.getElementById('ctl00_ContentPlaceHolder1_txt_dob'
));return false;">
<img align="absMiddle" border="0" class="style3"
src="dtPicker/calbtn.gif"
style="height: 16px; width: 26px; margin-bottom: 0px;" /></a></td>
<td class="style44" >

runat="server" ForeColor="Yellow"

<asp:LinkButton ID="lbtn_dobup"

onclick="lbtn_dobup_Click"
style="color: #800000">Update</asp:LinkButton>
</td>
<td align="left" class="style47">
&nbsp;</td>
<td width="auto">
</td>
<td class="style13">
&nbsp;</td>
<td class="style14">
&nbsp;</td></tr>
<tr>
<td class="style42"><span
class="style49">Qualification&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp; :
</td>
<td class="style33">
<asp:Label ID="lb_hq" runat="server" Text="" ForeColor="Yellow"
style="color: #800000"></asp:Label>
</td><td class="style34">
<asp:LinkButton ID="lbtn_hq" runat="server" onclick="lbtn_hq_Click"
ForeColor="Yellow" style="color: #800000">Edit</asp:LinkButton></td>
<td align="left" class="style47" >
<asp:Label ID="lb_nhq" runat="server" Text="New Qualification"
Visible="False" ForeColor="Yellow"
style="font-weight: 700; color: #800000;"></asp:Label></td>

57

Department of Computer Science


<td class="style46" >
<asp:TextBox ID="txt_hq" runat="server" Visible="False"
BorderColor="#990099"
BorderStyle="Inset"></asp:TextBox></td>
<td class="style35">
<asp:LinkButton ID="lbtn_okhq" runat="server"
onclick="lbtn_okhq_Click"
ForeColor="Yellow" Visible="False" style="color:
#800000">Ok</asp:LinkButton></td>
<td class="style36">
<asp:LinkButton ID="lbtn_fc3" runat="server"
onclick="lbtn_fc3_Click"
ForeColor="Yellow" Visible="False" style="color:
#800000">Cancel</asp:LinkButton></td></tr>
<tr>
<td class="style37"><span
class="style49">Hobbies&nbsp;&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
</td>
<td class="style38">
<asp:DropDownList ID="ddl_hob" runat="server" style="color: #990099"
ForeColor="Yellow">
<asp:ListItem>select</asp:ListItem>
<asp:ListItem>chatting</asp:ListItem>
<asp:ListItem>Listening music</asp:ListItem>

</td>

<asp:ListItem>Reading books</asp:ListItem>
<asp:ListItem>playing cricket</asp:ListItem>
<asp:ListItem>Hacking</asp:ListItem>
<asp:ListItem>watching t.v.</asp:ListItem>
</asp:DropDownList>

<td class="style39">
<asp:LinkButton ID="lbtn_hob" runat="server"
ForeColor="Yellow" onclick="lbtn_hob_Click"
style="color: #800000">Ok</asp:LinkButton></td></tr>
</table>
</asp:Content>

58

</center></div>

Department of Computer Science

Testing

TESTING
59

Department of Computer Science

SYSTEM TESTING

Here the System testing involved is the most widely used testing process consisting
of five stages as shown in the figure. In general, the sequence of testing activities
is component testing, integration testing, and then user testing.

However, as

defects are discovered at any one stage, they require program modifications to
correct them and this may require other stages in the testing process to be
repeated.

60

Department of Computer Science

Unit
testing
Module
testing
Subsystem
testing
System
testing
Acceptanc
e testing

(Component testing)

61

(Integration testing)

(User testing)

Department of Computer Science


Testing is the process of detecting errors. Testing performs a very critical role
for quality assurance and for ensuring the reliability of the software. The results of
testing are used later on during maintenance also.

Testing is vital to the success of the system. System testing makes a logical
assumption that if the parts of the system are correct, the goal will be successfully
achieved. In adequate testing or non-testing leads to errors that may not appear
until months or even years later (Remember the New York three day power failures
due to a misplaced Break statement).

This creates two problems:


1.

The time lag between the cause and the appearance of the problem.

2.

The time interval effect of the system errors on files and the records on the
system.

A small error can conceivably explode into a much larger problem. Effective testing
early in the process translates directly into long term cost savings from a reduced
number of errors.

Another reason for system testing is its utility as a user oriented vehicle before
implementation. The best program is worthless if it does not meet the user
requirements. Unfortunately, the users demands are often compromised by efforts
to facilitate program or design efficiency in terms of processing time or design
efficiency.

62

Department of Computer Science


Thus in this phase we went to test the code we wrote. We needed to know if the
code compiled with the design or not? Whether the code gave the desired outputs
on given inputs? Whether it was ready to be installed on the users computer or
some more modifications were needed?

Through the web applications are characteristically different from there software
counterparts but the basic approach for testing these web applications is quite
similar. These basic steps of testing have been picked from software engineering
practices. The following are the steps, we undertook:

1. The content of the Intranet site is reviewed to uncover Content


Errors. Content Errors covers the typographical errors, grammatical errors,
errors in content consistency, graphical representation and cross referencing
errors

2. The design model of the web application is reviewed to uncover the


navigation errors. Use cases, derived as a part of the analysis activity allows
a web designer to exercise each usage scenario against the architectural and
navigational design. In essence these non-executable tests help to uncover
the errors in navigation.

3. When web applications are considered the concept of unit changes. Each web
page encapsulates content navigation links, content and processing elements
(Forms, Scripts, and JSPs as in our case). It is not always possible to test

63

Department of Computer Science


4. each of these individually. Thus is the base of the web applications the unit to
be considered is the web page. Unlike the testing of the algorithmic details of
a module the data that flows across the module interface, page level testing
for web applications is driven by content, processing and links encapsulating
the web page.

5.

The Assembled web application is tested for overall functionality and content
delivery. The various user cases are used that test the system for errors and
mistakes.

6. The Web application is tested for a variety of environmental settings and is


tested for various configurations and upon various platforms.
The modules are integrated and integration test are conducted.

7. Thread based testing is done to monitor the regression tests so that the site
does not become very slow is a lot of users are simultaneously logged on.

8. A controlled and monitored population of end users tests Intranet application,


this all comprises of the User Acceptance Testing.

Because web applications evolve continuously, the testing process is an


ongoing activity, conducted by web support staff in our case the Organizations
IS people who will finally update and manage the application .

64

Department of Computer Science


PSYCHOLOGY OF TESTING

The aim of testing is often to demonstrate that a program works by showing


that it has no errors. The basic purpose of testing phase is to detect the errors that
may be present in the program. Hence one should not start testing with the intent
of showing that a program works, but the intent should be to show that a program
doesnt work. Testing is the process of executing a program with the intent of
finding errors.

TESTING OBJECTIVES:

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


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

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


error.

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

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

The tests are inadequate to detect possibly present errors.

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

LEVELS OF TESTING

In order to uncover the errors present in different phases, we have the concept of
levels of testing. The basic levels of testing are

65

Department of Computer Science

Client Needs
Acceptance Testing

Requirements
System Testing

Design
Integration Testing

Code

Unit

Testing

Unit testing

Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications, testing is done to
uncover errors within the boundary of the module. All modules must be successful
in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, HR Department, Interviewer Section, etc. Each module has
been tested by giving different sets of inputs. When developing the module as well
as finishing the development, the module works without any error. The inputs are
validated when accepting them from the user.
66

Department of Computer Science

Integration Testing

After unit testing, we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing interfaces
between modules. This testing activity can be considered as testing the design and
hence the emphasis on testing module interactions.

In this project the main system is formed by integrating all the modules.
When integrating all the modules I have checked whether the integration effects
working of any of the services by giving different combinations of inputs with which
the two services run perfectly before Integration.

SYSTEM TESTING

Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal is to see if software meets its
requirements.
Here entire HRRP has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.

ACCEPTANCE TESTING
67

Department of Computer Science

Acceptance Testing is performed with realistic data of the client to


demonstrate that the software is working satisfactorily. Testing here is focused on
external behavior of the system; the internal logic of program is not emphasized.

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


equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations
and also a complete verification to determine whether the objectives are met and
the user requirements are satisfied.

WHITE BOX TESTING

This is a unit testing method, where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in
the code is executed at least once. The white box testing is also called Glass Box
Testing.

I have generated a list of test cases, sample data, which is used to check all
possible combinations of execution paths through the code at every module level.

White-box test focuses on the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to ensure that
all statement in the program control structure. Test cases are derived to ensure that all
68

Department of Computer Science


statement in the program has been executed at least once during testing and that all logical
conditions have been exercised. Basis path testing, a white box technique, makes use of
program graphs (or graph matrices) to derive the set of linearly independent test that will ensure
coverage. Condition and data flow testing further exercising degrees of complexity.

BLACK BOX TESTING

This testing method considers a module as a single unit and checks the unit
at interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.
Black-box test are designed to uncover errors functional requirement without
regard to the internal workings of a program. Black-box testing techniques focus on
the information domain of the software, deriving test cases by partitioning the input
and output domain of a program in manner that provides through test coverage.
The black-box test is used to demonstrate that software functions are operational,
that input is properly produced, and that the integrity of external information are
maintained. A black-box test examines some fundamental aspect of a system with
little or no regard for the integral logical structure of the software.

TEST INFORMATION FLOW


69

Department of Computer Science


A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vortex of the spiral and, concentrates on each unit, component
of the software as implemented in source code. Testing progresses moving outward
along the spiral to integration testing, where the focus is on designed the
construction of the software architecture. Taking another turn outward on spiral,
Considering the process from a procedural point of view, testing within the
context of software engineering is actually a series of four steps that are
implemented sequentially. The steps are shown in Figure. Initially, tests focus on
each component individually, ensuring that it functions properly as unit. Hence, the
name unit testing. Unit testing makes heavy use of white-box testing techniques,
exercising specific paths in modules control structure to ensure complete coverage
and maximum error detection.

System Testing
Validation Testing
Integration Testing

Validation testing

System Security

70

Department of Computer Science

6.3 INFORMATION FLOW OF DATA FOR TESTING

Evaluati
on

Software
Configuration
Test Results

Error

Testing

Expected
Results

Error
Rate
Data
Debug

Reliabili
ty Model
Test Configuration

Predicated Reliability
Correction

71

Department of Computer Science

SECURITY FEATURES

A. Only authenticated user can login.


B. Password will be saved in encrypted form.
C. Integrated security will be provided so that unauthorized user can
not access the data layer and source code.
D. We are using the secure session for every user.
E. Client certificate authentication.

FUTURE SCOPE

72

Department of Computer Science

E-learning permits the delivery of knowledge and test their skills on various
technologies to learner at an accelerated pace, opening up new vistas of knowledge
transfer.
Early adopters are companies that have tried to supplement face-to-face meetings,
demonstrations, training classes and lectures with this technology. The adoption
of E-learning in all spherescorporate, schools, universities, etcis low at
present. The Indian market is not substantial when compared to the international
market which is worth about $6 billion to $7 billion, says Harish Joshy, Vicepresident of LionBridge Technologies, an e-learning player.
E-learning in India has been most successful in the corporate segment where it is
seen as a means of achieving business goals and motivating employees.

73

Department of Computer Science

REFERENCES

REFERENCES

74

All about Microsoft controls in C#

Department of Computer Science

http://www.msdn.microsoft.com/

Wikipedia for various diagrams & testing methods


http://www.wikipedia.org/

Cool text for Images and Buttons


http://cooltext.com/

K-State Research Exchange for samples in report


writing
http://krex.k-state.edu/dspace/handle/2097/959

Smart Draw for drawing all the Diagrams used in this


report.
http://www.smartdraw.com/

Sample Ecommerce Application


http://www.NewEgg.com

Ajax Toolkit controls


http://asp.net/ajax

75

You might also like