ABSTRACT

ABSTRACT
Student Counselling Management System project is implemented in JAVA
platform. The main idea for developing this project is to provide a web portal for
Students to view all the College details. Users or Students should register in the
web site and provide his details to register for a college for seat allocation process
by online. After the seat allocation in a particular college he is going to get a
message that you have allocated a seat.
In old system the student counselling management process is done by
maintaining records manually and all students cant view all the details of all
colleges. But in the present Student counselling management system any student
can view any college information and can Opt or choose any college by online and
the student can send any request or complaint directly to the head of student
counselling management system. So student counselling management system by
online is more advantageous than old method of maintaining records by manually.

INDEX
1. INTRODUCTION
1.1 EXITING SYSTEM
1.2 PROPOSED SYSTEM
2. REQUIREMENT
3. ANALYSIS
3.1 SYSTEM ANALYSIS
3.2 PROBLEM DEFINITION
4. DATA BASE DESIGN
5. CODING
6. TESTING
7. SCREENS
8. CONCLUSION
9. BIBLIOGRAPHY
10. APPENDIX

INTRODUCTION

1. INTRODUCTION
The Online Counseling System is developed to enhance counseling. The software
will be great relief to the students. The Online Counseling System is developing to

enhance the counseling, which fully works as an online. This software will be great
relief to the student for Reporting, Registration and searching the information
about college and university. This software gives an overview of the entire institute
in a sort interval time and will be also great help to University to manage in the
whole counseling procedure by their paper work and reducing their time.

Existing System
Counseling Management System working manually or computerized in a
building. Therefore all types works are maintain in building. So maintain all the
counseling procedure very difficult. If we are reporting, then we need go to the
University and get a form for reporting and fill the form and submit in the queue
conditions. Then verify their form by the university and maintain the record in
computer or register. The system is mainly related to online counseling
management system. Which is developing an online web based application system,
it is necessary to make a thorough study of the existing system .There is no online
Counseling Management System .The all the information not maintains globally.
Therefore to maintain all the information of university is very difficult.

Proposed System
In proposed system at first reduce the problem, which is faced in Existing System.
So In the proposed system, Online Counseling System will provide the on line
facility for reporting / registration or access any type of information about the

college/university and globally maintain all the information by the university and
this project consist fallowing modules are
(1) Institute Record: Provide the fallowing types of facilities using different options: (2) Insert:This part allow any new institute, if we want to participate in counseling
then enter its details regarding the institute - Institute Code ,Name of the
institute, Name of the city, Category wise total number of seats i.e. General
Seats, OBC Seats, SC/ST seats.
(3) Search: It provides Searching for any institute details. - On the basis of its code. - On
the basis of its name.
(4) Delete: If any institute Withdraw from counseling then this part will help in deleting
that institute record.
(5) Display: It will help in displaying complete information about institute code name,
city, and total seats according to category.
(6) Student record: This module has two parts: - Search: - This will provide help in searching
record of any student who is allotted seats in an institute during counseling
procedure.
(7) Delete: This will allow to deleting record of any student after counseling. The
deletion can be on the basis of Roll no, Name.

MS-ACCESS
Microsoft access is a database program, which is
used to create collection of organized data items.
These items are called records. Each record has the
same formand consists of one or more pieces, each

of which stores a particular kind of data. Therecord

pieces are referred to as fields.Visual basic and
Microsoft access have a deep affinity for each other
asMicrosoft is the developer of both, this is not
necessarily surprising. The two programs share the
code to access database files.The access database is
a relational database by VB6.0 and Microsoft access.
Arelational database that structures the data by
breaking them into logical objects thathave
relationship between them. This reduces the amount
of redundant data andmakes comprehension easies.
They also provide mechanism to correctly maintain
therelationships between objects. This function is
called referential integrity.
So this provides the case to do programs and make
the project very user friendly. Also generating
reports using data report will helps us to create
report with various conditions using selection
formula method in data report

REQUIREMENTS

REQUIREMENTS

SOFTWARE SPECIFICATIONS

Operating System
Data Base
Server Software
JAVA

:
:
:
:

Windows
MSACCESS
TOMCAT 5.5
JSDK 1.4

HARDWARE SPECIFICATIONS
Processor
Hard Disk
RAM
Mouse
Keyboard

:
:
:
:
:

Pentium III 900 MHz

20 GB
128 MB
1 USB or 1 P/2S
1 USB or 1 P/2S

ANALYSIS

SYSTEM ANALYSIS
The existing system is the manual system. The manual system is error prone.
It is time consuming. It is very difficult for a student to know the correct
college and courses to by his / her cut-off mark. This system involves a lot of
manual entries with the applications to perform the desired task.
LIMITATIONS:

 Data maintenance adopted by the present system is not accurate.

Inaccurate result in case of duplicating, delay and inconsistency in reporting.
Generating consolidated reports is more difficult in manual system and it
may not be consistent.
The transactions are very time consuming.
There is no facility for the users to know whether the data is entered is valid
or not. This disadvantage is the major cause of errors in transaction.
There is inconsistency in maintaining datas.
No global view ability of datas.
It is not user friendly.

PROPOSED SYSTEM
The proposed system is designed to eliminate the drawbacks of the
existing system. It is designed by keeping in mind all the drawbacks of the
present system in order to provide a permanent solution to the problems. The
primary aim of the new system is to speedup transactions

The advantages of this system are:

User friendliness is the keyword for all the new software in the
market. The proposed system incorporates this concept into itself to
guide the user.

 At every stage of data entry necessary comments and validation

messages are provided to the user.
The proposed system is also expected to reduce the amount of paper
work involved. The hard copies of only necessary documents need to
be taken the rest can be avoided.
Competitive environment is developed with the publications of other
members of same level
Good communication is being held via mail options.

DATA BASE
DESIGN

Introduction to data base Design

Basic Concepts
A database is a collection of logically related
records
A relational database stores its data in 2dimensional tables
A table is a two-dimensional structure made up
of rows (tuples, records) and columns (attributes,
fields)
Example: a table of students engaged in sports
activities, where a student is allowed to participate in
at most one activity.

 Each row is unique and stores data about one entity

Row order is unimportant
Each column has a unique attribute name
Each column (attribute) description (metadata) is
stored in the database
Access metadata is stored and manipulated via the
Table Design View grid
Column order is unimportant
All entries in a column have the same data type
Access examples: Text (50), Number (Integer),
Date/Time
Each cell contains atomic data: no lists or subtables.
Table Characteristics
Each row is unique and stores data about one entity
Row order is unimportant
Each column has a unique attribute name

 Each column (attribute) description (metadata) is

stored in the database
Access metadata is stored and manipulated via the
Table Design View grid
Column order is unimportant
All entries in a column have the same data type
Access examples: Text (50), Number (Integer),
Date/Time
Each cell contains atomic data: no lists or subtables.
Primary Keys
A primary key is an attribute or a collection of
attributes whose value(s) uniquely identify each row
in a relation
A primary key should be minimal: it should not
contain unnecessary attributes

We
assume
that a student is allowed to participate in at most one
activity.
The only possible primary key in the above table is
StudentID.

 Sometimes there is more than one possible choice;

each possible choice is called a candidate key
What if we allow the students to participate in
more than one activity?

now the only possible primary key is the combined

value of (StudentID, Activity),
such a multi-attribute primary key is called a
composite key or concatenated key.
Composite Keys
A table can only have one primary key
But sometimes the primary key can be made up of
several fields
Concatenation means putting two things next to
one another: the concatenation of burger and foo
is burgerfoo.
consider the following table of cars.

 License Plate is not a possible primary key,

because two different cars can have the same license
plate number if theyre from different states
but if we concatenate LicensePlate and State, the
resulting value of (LicensePlate, State) must be
unique:
Example: LVR120NJ and LVR120CT
Therefore, (LicensePlate, State) is a possible
primary key (a candidate key)
Sometimes we may invent a new attribute to serve
as a
Primary key (sometimes called a synthetic key)
If no suitable primary key is available
Or, to avoid composite keys
In Access, Auto number fields can serve this
Purpose
Foreign Keys
a foreign key is an attribute or a collection of
attributes whose value are intended to match the

primary key of some related record (usually in a

different table)
Example: the STATE and CITY table below

 Primary key in STATE relation: StateAbbrev

Primary key in CITY relation: (StateAbbrev,
CityName)
Foreign key in CITY relation: StateAbbrev

Outline Notation
STATE (StateAbbrev, StateName, UnionOrder,
StateBird, StatePopulation)
CITY(StateAbbrev, CityName, CityPopulation)
StateAbbrev foreign key to STATE
Underline all parts of each primary key
Note foreign keys with attribute foreign key to
TABLE
Functional Dependency
Attribute B is functionally dependent on attribute A
if given a value of attribute A, there is only one
possible corresponding value of attribute B
That is, any two rows with the same value of A
must have the same value for B
Attribute A is the determinant of attribute B if
attribute B is functionally dependent on attribute A
In the STATE relation above, StateAbbrev is a
determinant of all other attributes
In the STATE relation, the attribute StateName is
also a determinant of all other attributes
So, StateAbbrev and StateName are both candidate
keys for STATE
In the CITY relation above, the attributes

(StateAbbrev, CityName) together are a determinant

of the attribute CityPopulation
In the CITY relation, the attribute CityName is not
a determinant of the attribute CityPopulation
because multiple cities in the table may have the
same name.
A dependency diagram or bubble diagram is a
pictorial representation of functional dependencies
An attribute is represented by an oval
You draw an arrow from A to B when attribute A
is a determinant of attribute B.
Good Database Design Principles
1. No redundancy
A field is stored in only one table, unless it happens
to be a foreign key
Replication of foreign keys is permissible, because
they allow two tables to be joined together
2. No bad dependencies
In the dependency diagram of any relation in the
database, the determinant should be the whole
primary key, or a candidate key. Violations of this
rule include:
Partial dependencies.
Transitive dependencies.

Normalization is the process of eliminating bad

Dependencies by splitting up tables and linking them
with foreign keys
normal forms are categories that classify how
Completely a table has been normalized
There are six recognized normal forms (NF):

Main Phases of Database Design

In the picture below there are the main phases of
database design. Database design is connected with
application design.

The requirements and the collection analysis phase

produce both data requirements and functional
requirements. The data requirements are used as a
source of database design. The data requirements
should be specified in as detailed and complete form
as possible.
In parallel with specifying the data requirements, it
is useful to specify the known functional
requirements of the application. These consist of
user-defined operations that will be applied to the
database (retrievals and updates). The functional
requirements are used as a source of application
software design. Of course some functions may
produce also needs for database design.
Note that some phases are database management

system independent and some are dependent. The

idea is to design first the database without thinking
about the actual database system - just to concentrate
on the data.

Conceptual Design
Once all the requirements have been collected and
analyzed, the next step is to create a conceptual
schema for the database, using a high level
conceptual data model. This phase is called
conceptual design.
The result of this phase is an Entity-Relationship
(ER) diagram or UML class diagram. It is a highlevel data model of the specific application area. It
describes how different entities (objects, items) are
related to each other. It also describes what attributes
(features) each entity has. It includes the definitions
of all the concepts (entities, attributes) of the
application area.
During or after the conceptual shema design, the
basic data model operations can be used to specify
the high-level user operations identified during the
functional analysis. This also serves to confirm that
the conceptual schema meets all the indentified
functional requirements.

There are several notations to draw the ER diagram.

Logical Design
The result of the logical design phase (or data model
mapping phase) is a set of relation schemas. The ER
diagram or class diagram is the basis for these
relation schemas.
To create the relation schemas is quite a mechanical
operation. There are rules how the ER model or class
diagram is transferred to relation schemas.
The relation schemas are the basis for table
definitions. In this phase (if not done in previous
phase) the primary keys and foreign keys are
defined.
Normalization
Normalization is the last part of the logical design.
The goal of normalization is to eliminate redundancy
and potential update anomalies.

Redundancy means that the same data is saved more

than once in a database. Update anomaly is a
consequence of redundancy. If a piece of data is
saved in more than one place, the same data must be
updated in more than one place.
Normalization is a technique by which one can
modify the relation schema to reduce the
redundancy. Each normalization phase adds more
relations (tables) into the database.
Physical Design
The goal of the last phase of database design,
physical design, is to implement the database. At this
phase one must know which database management
system (DBMS) is used. For example, different
DBMS's have different names for data types and
have different data types.
The SQL clauses to create the database are written.
The indexes, the integrity constraints (rules) and the

users' access rights are defined.

Finally the data to test the database is added in.
In parallel with these activities, application programs
are designed. The implementation of the programs
can start when the database is created and data has
been added in. Source: Elmasri, Navathe. 2004.
Fundamentals of Database Systems. AddisonWesley. Chapter 3. Data Modelling Using the EntityRelationship Model.
Conceptual Database Design - Entity
Relationship(ER) Modeling
Database Design Techniques
1.

ER Modeling (Top down Approach)

2.

Normalization (Bottom Up approach)

Let's see ER Modeling in detail.

What is ER Modeling?
A graphical technique for understanding and
organizing the data independent of the actual
database implementation
We need to be familiar with the following terms to
go further.
Entity
Anything that has an independent existence and
about which we collect data. It is also known as
entity type.
In ER modeling, notation for entity is given below.

Entity instance
Entity instance is a particular member of the entity
type.
Example for entity instance: A particular employee

Regular Entity
An entity which has its own key attribute is a regular
entity.
Example for regular entity: Employee.
Weak entity
An entity which depends on other entity for its
existence and doesn't have any key attribute of its
own is a weak entity.
Example for a weak entity: In a parent/child
relationship, a parent is considered as a strong entity
and the child is a weak entity.
In ER modeling, notation for weak entity is given
below.

Attributes
Properties/characteristics which describe entities are
called attributes.

In ER modeling, notation for attribute is given

below.

Domain of Attributes
The set of possible values that an attribute can take
is called the domain of the attribute. For example,
the attribute day may take any value from the set
{Monday, Tuesday ... Friday}. Hence this set can be
termed as the domain of the attribute day.
Key attribute
The attribute (or combination of attributes) which is
unique for every entity instance is called key
attribute.
E.g the employee_id of an employee,
pan_card_number of a person etc. If the key attribute
consists of two or more attributes in combination, it
is called a composite key.
In ER modeling, notation for key attribute is given
below.

Simple attribute
If an attribute cannot be divided into simpler
components, it is a simple attribute.
Example for simple attribute: employee_id of an
employee.
Composite attribute
If an attribute can be split into components, it is
called a composite attribute.
Example for composite attribute : Name of the
employee which can be split into First_name,
Middle_name, and Last_name.
Single valued Attributes
If an attribute can take only a single value for each
entity instance, it is a single valued attribute.
example for single valued attribute : age of a student.
It can take only one value for a particular student.

Multi-valued Attributes
If an attribute can take more than one value for each
entity instance, it is a multi-valued attribute. Multivalued
example for multi valued attribute : telephone
number of an employee, a particular employee may
have multiple telephone numbers.
In ER modeling, notation for multi-valued attribute
is given below.

Stored Attribute
An attribute which need to be stored permanently is
a stored attribute
Example for stored attribute: name of a student
Derived Attribute
An attribute which can be calculated or derived
based on other attributes is a derived attribute.

Example for derived attribute: age of employee

which can be calculated from date of birth and
current date.
In ER modeling, notation for derived attribute is
given below.

Relationships
Associations between entities are called
relationships
Example: An employee works for an organization.
Here "works for" is a relation between the entities
employee and organization.
In ER modeling, notation for relationship is given
below.

However in ER Modeling, to connect a weak Entity

with others, you should use a weak relationship
notation as given below

Degree of a Relationship
Degree of a relationship is the number of entity
types involved. The n-ary relationship is the general
form for degree n. Special cases are unary, binary,
and ternary, where the degree is 1, 2, and 3,
respectively.
Example for unary relationship: An employee is a
manager of another employee
Example for binary relationship: An employee
works-for department.
Example for ternary relationship: customer purchase
item from a shop keeper

Cardinality of a Relationship
Relationship cardinalities specify how many of each
entity type is allowed. Relationships can have four
possible connectivitys as given below.

One to one (1:1) relationship

One to many (1:N) relationship

Many to one (M:1) relationship

Many to many (M:N) relationship

The minimum and maximum values of this
connectivity is called the cardinality of the
relationship
Example for Cardinality One-to-One (1:1)
Employee is assigned with a parking space.

One employee is assigned with only one parking

space and one parking space is assigned to only one
employee. Hence it is a 1:1 relationship and
cardinality is One-To-One (1:1)
In ER modeling, this can be mentioned using
notations as given below

Example for Cardinality One-to-Many (1:N)

Organization has employees

One organization can have many employees, but one

employee works in only one organization. Hence it
is a 1: N relationship and cardinality is One-ToMany (1: N)
In ER modeling, this can be mentioned using
notations as given below

Example for Cardinality Many-to-One (M: 1)

It is the reverse of the One to Many relationships.
employee works in organization

One employee works in only one organization But

one organization can have many employees. Hence

it is an M: 1 relationship and cardinality is Many-toOne (M: 1)

In ER modeling, this can be mentioned using
notations as given below.

Cardinality Many-to-Many (M:N)

Students enrolls for courses

One student can enroll for many courses and one

course can be enrolled by many students. Hence it is
a M: N relationship and cardinality is Many-toMany (M: N)
In ER modeling, this can be mentioned using
notations as given below

Relationship Participation
1. Total
In total participation, every entity instance will be
connected through the relationship to another
instance of the other participating entity types
2. Partial
Example for relationship participation
Consider the relationship - Employee is head of the
department.
Here all employees will not be the head of the
department. Only one employee will be the head of

the department. In other words, only few instances

of employee entity participate in the above
relationship. So employee entitys participation is
partial in the said relationship.
However each department will be headed by some
employee. So department entitys participation is
total in the said relationship.
Advantages and Disadvantages of ER Modeling
( Merits and Demerits of ER Modeling )
Advantages
1.

ER Modeling is simple and easily

understandable. It is represented in business users
language and it can be understood by non-technical
specialist.

2.

Intuitive and helps in Physical Database

creation.

3.

Can be generalized and specialized based on

needs.

4.

Can help in database design.

5.

Gives a higher level description of the system.

Disadvantages
1.

Physical design derived from E-R Model may

have some amount of ambiguities or inconsistency.

2.

Sometime diagrams may lead to

misinterpretations
DATA BASE TABLES
Table: Registration (Student Login)
s.no.

Column Name

Date-Type

Description

Un

text

Students user name.

Pwd

Text

Students email.

Aun

Text

AlternativeStudents password.

phoneno

Text

Students phone number.

Crn

Text

Students ceep rank number.

email

text

Students email.

Date-Type
Text
Text
Text
Text
Text
Text
Text
Text

Description
College identification number
College name
College Address
College phone number
Inforamtion technology saets
Ece seats
Mech seats
Eee seats

Table: collegeslist
s.no.
1
2
3
4
5
6
7
8

Column Name
Collegeid
Collegename
CollegeAddress
Collegephone
Itseats
eceseats
Mechseats
eeeseats

Table: alloted
s.no.
1
2
3
4
5

Column Name

Username
Collegeid
Branch
Ceepno
email

Date-Type
Text
Text
Text
Text
Text

Description

Date-Type
Text
Text
Text
Text

Description

Students user name

College identification number
Branch of college
Student Rank
Student email

Table: other
s.no.
1
2
3
4

Column Name

Name
Email
Phoneno
Rs

Students name
Students email
Students phone number
Request or resonse of student

CODING

Coding
REGISTRATION.JSP
<html>
<title>STUDENT COUNSELLING MANAGEMENT SYSTEM</title>
<style type="text/css">
div.color {
border-width:1px;
border-style:solid;
}

a{color:#0000A0;text-decoration:none;}
</style>
<script language="JavaScript">
function big(lyr) {
document.all[lyr].style.height = '100px';
}
function small(lyr) {
document.all[lyr].style.height = '32px';
}
function start() {
document.all.Layer0.style.height = '32px';
document.all.Layer1.style.height = '32px';
document.all.Layer2.style.height = '42px';
document.all.Layer3.style.height = '42px';

document.all.Layer4.style.height = '32px';
}
</script>
<script type="text/javascript" language="javascript>
function checkform()
{
var s1=document.regist.name.value;
var s2=s1.length;
var s3=document.regist.Password.value;
var s4=s3.length;
var s5=document.regist.cPassword.value;
var s6=s5.length;
var s7=document.regist.phoneno.value;
alert("entered user name number of characters"+s2);

alert("entered password number of characters"+s4);

alert("entered phone number of characters"+s7);
if (s2<6)
{
alert("Enter minimium of 6 characters for correct User Name");
return false;
}
else if (s4<6)
{
alert("Enter minimium of 6 characters for correct Password");
return false;
}
else if (s3!=s5)
{

alert("Entered Password and confirm password don't match");

return false;
}
else if (s7.length<9)
{
alert("Enter minimium of 6 characters for phone");
return false;
}
// If the script gets this far through all of your fields
// without problems, it's ok and you can submit the form
return true;
}
</script>
<style type="text/css">

div.color {
border-width:1px;
border-style:solid;
}
a{color:#0000A0;text-decoration:none;}
</style>
<script language="JavaScript">
function big(lyr)
{
document.all[lyr].style.height='100px';
}
function small(lyr)
{
document.all[lyr].style.height='32px';

}
function start()
{
document.all.Layer0.style.height='32px';
document.all.Layer1.style.height='32px';
document.all.Layer2.style.height='42px';
document.all.Layer3.style.height='42px';
document.all.Layer4.style.height='32px';
}
</script>
</HEAD>
<BODY onLoad="start()">
<div id="photolayer" style="z-index: 1; left:-200px; top:-100px; width:
1500px;

height:

109px;

background-color:#7FE817;

color:#2B65EC; visibility: visible">

layer-background-

<center

style="position:relative;color:#C35817;font-size:40;left:-

100;">STUDENT COUNSELLING MANAGEMENT SYSTEM</center>

</div>`
<div

id="Layer0"

class="color"

style="position:absolute;width:175px;height:32px;z-index:1;
left:239px; top:75px;overflow:hidden;" >
<div class="color" style=" font-size:23px;"><font face="Verdana, Arial,
Helvetica, sans-serif">
<a href="index.jsp"><center>Home</center></a><br><br>
</div>
</div>
<div

id="Layer1"

class="color"

style="position:absolute;width:175px;height:32px;z-index:1;
left:413px; top:75px;overflow: hidden" onMouseOut="small('Layer1')">
<div

align="center"

class="color"

style="

face="Verdana, Arial, Helvetica, sans-serif">

<a href="register.jsp">Register</a><br><br>

font-size:23px;"><font

</div>
</div>
<div

id="layer2"

class="color"

style="position:absolute;width:175px;height:32px;z-index:1;
left:590px; top:75px;overflow: hidden" ; onMouseOut="small('layer2')">
<div

align="center"

class="color"

style="

font-size:23px;"><font

face="Verdana, Arial, Helvetica, sans-serif">

<a href="login.jsp">Login</a><br />
<br>
</div>
</div>
<div

id="Layer3"

class="color"

style="position:absolute;width:175px;height:32px;z-index:1;
left:766px; top:75px;overflow: hidden" >
<div class="color"

style=" font-size:23px;"><font face="Verdana, Arial,

Helvetica, sans-serif">

<a href="other.jsp"><center>Other</center></a><br>
</div>
</div>

<div

id="Layer4"

class="color"

style="position:absolute;width:175px;height:32px;z-index:1;
left: 941px; top:75px;overflow: hidden"; >
<div class="color"

style=" font-size:23px;"><font face="Verdana, Arial,

Helvetica, sans-serif">
<a href="Contact.jsp"><center>Contact Us</center></a><br>
</div>
</div>
<table align="center" >
<tr>
<td align="left">

<table width="100%" height="550"

align="center" cellpadding="3"

cellspacing="2" >
<tr>
<td

align="left"

valign="top"

><div

align="center">Register

</div></td>
</tr>
<tr>
<td align="left" valign="top">
<form action="abcd.jsp" method="get" >
<table width="100%" border="0" cellspacing="1" cellpadding="3">
<tr>
<td>User Name </td>
<td>:</td>
<td><input name="un" type="text"/></td>
</tr>

Profile

<tr><td>&nbsp</td></tr>
<tr>
<td>Password</td>
<td>:</td>
<td><input name="up" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>
<tr>
<td>Confirm password </td>
<td>:</td>
<td><input name="cup" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>

<tr>
<td>Actual user name<font color="red">^*</font></td>
<td>:</td>
<td><input name="aun" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>
<tr>
<td>Phone Number<font color="red">^*</font></td>
<td>:</td>
<td><input name="phoneno" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>
<tr>
<td>Ceep Rank Number<font color="red">^*</font></td>

<td>:</td>
<td><input name="crn" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>
<tr>
<td>Email<font color="red">^*</font></td>
<td>:</td>
<td><input name="email" type="text"/></td>
</tr>
<tr><td>&nbsp</td></tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>

<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td><input type="submit" name="Submit" value="Submit"/></td>
</tr>
</table>
</form>
</td>
</tr>
<tr>
<td>&nbsp;</td>
</tr>
</table>
</td>

</tr>
</table>
<br><br><br><br>

<div style="color:white; background-color:#7FE817; text-align: center;fontsize: x-large; width: 1495px; position: absolute; top:640px;left:0px;">
Copyright

Information@STUDENT

COUNSELLING

MANAGEMENT

SYSTEM</div>
</div>
</body>
</html>

LOGIN.JSP
<html>
<title>STUDENT COUNSELLING MANAGEMENT SYSTEM</title>
<style type="text/css">
div.color {
border-width:1px;

border-style:solid;
}
a{color:#0000A0;text-decoration:none;}
</style>
<script language="JavaScript">
function big(lyr) {
document.all[lyr].style.height = '100px';
}
function small(lyr) {
document.all[lyr].style.height = '32px';
}
function start() {
document.all.Layer0.style.height = '32px';
document.all.Layer1.style.height = '32px';
document.all.Layer2.style.height = '42px';
document.all.Layer3.style.height = '42px';
document.all.Layer4.style.height = '32px';
}
</script>
</HEAD>
<BODY onLoad="start()">
<div id="photolayer"
style="z-index: 1; left:-200px; top:-100px; width: 1500px;
height:
109px;
background-color:#7FE817;
layer-backgroundcolor:#2B65EC; visibility: visible">
<center
style="position:relative;color:#C35817;font-size:40;left:100;">STUDENT COUNSELLING MANAGEMENT SYSTEM</center>
</div>`
<div
id="Layer0"
class="color"
style="position:absolute;width:175px;height:32px;z-index:1;
left:239px; top:75px;overflow:hidden;" >
<div class="color" style=" font-size:23px;"><font face="Verdana, Arial,
Helvetica, sans-serif">

<a href="index.jsp"><center>Home</center></a><br><br>
</div>
</div>
<div
id="Layer1"
class="color"
style="position:absolute;width:175px;height:32px;z-index:1;
left:413px; top:75px;overflow: hidden" onMouseOut="small('Layer1')">
<div align="center" class="color"
style=" font-size:23px;"><font
face="Verdana, Arial, Helvetica, sans-serif">
<a href="register.jsp">Register</a><br><br>
</div>
</div>
<div
id="layer2"
class="color"
style="position:absolute;width:175px;height:32px;z-index:1;
left:590px; top:75px;overflow: hidden" ; onMouseOut="small('layer2')">
<div align="center" class="color"
style=" font-size:23px;"><font
face="Verdana, Arial, Helvetica, sans-serif">
<a href="login.jsp">Login</a><br />
<br>
</div>
</div>
<div
id="Layer3"
class="color"
style="position:absolute;width:175px;height:32px;z-index:1;
left:766px; top:75px;overflow: hidden" >
<div class="color" style=" font-size:23px;"><font face="Verdana, Arial,
Helvetica, sans-serif">
<a href="other.jsp"><center>Other</center></a><br>
</div>
</div>
<div
id="Layer4"
class="color"
style="position:absolute;width:175px;height:32px;z-index:1;
left: 941px; top:75px;overflow: hidden"; >
<div class="color" style=" font-size:23px;"><font face="Verdana, Arial,
Helvetica, sans-serif">
<a href="Contact.jsp"><center>Contact Us</center></a><br>
</div>
</div>
<br><br>
<form action="check.jsp" method="get">

<table
ALIGN="CENTER"
cellpadding="3"
class="tableheader" >
<tr>
<td colspan="2" align="left"><div>User Login<div></td>
</tr>
<tr>
<td align="center"><div>User Name<div></td>
<td><input name="un" type="text" id="uname" /></td>
</tr>

cellspacing="0"

<tr>
<td align="center"><div>Password<div></td>
<td><input name="up" type="password" id="upass" /></td>
</tr>
<tr>
<td colspan="2" align="center">&nbsp;</td>
</tr>
<tr>
<td colspan="1" align="right"><input type="submit" name="Submit"
value="Login" /></td>
<td align="left"><input type="reset" value="Reset" /></td>
</tr>
</table>
</form>
</tr>
</table>
<div style="color:white; background-color:#7FE817; text-align: center;fontsize: x-large; width: 1495px; position: absolute; top:623px;left:0px;">
Copyright Information@STUDENT COUNSELLING MANAGEMENT
SYSTEM</div>
</div>
</body>
</html>

TESTING

Testing
1. TESTING
INTRODUCTION TO TESTING:
Testing is the process of analyzing a system or system component for finding
differences between the expected behavior specified by system models and the observed
behavior of the system.
It is the process of detecting errors. Testing performs a very critical role for quality assurance
and for ensuring the reliability of software. The results of testing are used later on during
maintenance also.

TESTING STRATEGIES
Software Testing
It is the process of evaluation a software item to
detect differences between given input and expected
output. Also to assess the feature of a software item.
Testing assesses the quality of the product. Software
testing is a process that should be done during the
development process. In other words software
testing is a verification and validation process.

Verification
Verification is the process to make sure the product
satisfies the conditions imposed at the start of the
development phase. In other words, to make sure the
product behaves the way we want it to.
Validation
Validation is the process to make sure the product
satisfies the specified requirements at the end of the
development phase. In other words, to make sure the
product is built as per customer requirements.
Basics of software testing
Black box testing and white box testing.
Black box Testing
Black box testing is a testing technique that ignores
the internal mechanism of the system and focuses on
the output generated against any input and execution
of the system. It is also called functional testing.

Internal system design is not considered in this type

of testing. Tests are based on requirements and
functionality.

White box Testing

White box testing is a testing technique that takes
into account the internal mechanism of a system. It
is also called structural testing and glass box testing.
This testing is based on knowledge of the internal
logic of an applications code. Also known as Glass
box Testing. Internal software and code working
should be known for this type of testing. Tests are
based on coverage of code statements, branches,
paths, conditions.
Black box testing is often used for validation and
white box testing is often used for verification.
Types of testing
1. Unit Testing.
2. Integration Testing.

3.Functional Testing.
4. System Testing.
5. Stress Testing.
6. Performance Testing.
7. Usability Testing.
8. Acceptance Testing.
9. Regression Testing.
10. Beta Testing.
11. Unit Testing.
12. Sanity testing.
13. Incremental integration testing.
14. End-to-end testing.
15. Load testing.
16. Security testing.

17. Exploratory Testing.

18. Realization tests.
19. Mutation Testing.
20. Build Acceptance Tests.
21. Smoke Tests.
22. Bug Regression Testing.
23. Database Testing.
24. Functional Testing (or) Business functional
testing.
25. Volume Testing.
26. Installation testing.
27. Configuration Testing.
28. Documentation Testing.

29. Recovery/Error Testing.

30. Alpha Testing.
31. Parallel/Audit Testing
Unit testing
1. Unit testing is the testing of an individual unit or
group of related units. It falls under the class of
white box testing. It is often done by the
programmer to test that the unit he/she has
implemented is producing expected output against
given input.
2. Testing of individual software components or
modules. Typically done by the programmer and not
by testers, as it requires detailed knowledge of the
internal program design and code. may require
developing test driver modules or test harnesses.
Integration Testing
1. Integration testing is testing in which a group of
components are combined to produce output. Also,
the interaction between software and hardware is

tested in integration testing if software and hardware

components have any relation. It may fall under both
white box testing and black box testing.
2. Testing of integrated modules to verify combined
functionality after integration. Modules are typically
code modules, individual applications, client and
server applications on a network, etc. This type of
testing is especially relevant to client/server and
distributed systems.
Functional Testing
1. Functional testing is the testing to ensure that the
specified functionality required in the system
requirements works. It falls under the class of black
box testing.
2. This type of testing ignores the internal parts and
focus on the output is as per requirement or not.
Black-box type testing geared to functional
requirements of an application.
System Testing
1. System testing is the testing to ensure that by
putting the software in different environments (e.g.,

Operating Systems) it still works. System testing is

done with full system implementation and
environment. It falls under the class of black box
testing.
2. Entire system is tested as per the requirements.
Black-box type testing that is based on overall
requirements specifications, covers all combined
parts of a system.
Stress Testing
1. Stress testing is the testing to evaluate how system
behaves under unfavorable conditions. Testing is
conducted at beyond limits of the specifications. It
falls under the class of black box testing.
2. System is stressed beyond its specifications to
check how and when it fails. Performed under heavy
load like putting large number beyond storage
capacity, complex database queries, continuous input
to system or database load.
Performance Testing
1. Performance testing is the testing to assess the
speed and effectiveness of the system and to make

sure it is generating results within a specified time as

in performance requirements. It falls under the class
of black box testing.
2. Term often used interchangeably with stress and
load testing. To check whether system meets
performance requirements. Used different
performance and load tools to do this.
3. Performance testing is designed to test run time
performance of software within the context of an
integrated system. It is not until all systems elements
are fully integrated and certified as free of defects
the true performance of a system can be ascertained
4. Performance tests are often coupled with stress
testing and often require both hardware and software
infrastructure. That is, it is necessary to measure
resource utilization in an exacting fashion. External
instrumentation can monitor intervals, log events. By
instrument the system, the tester can uncover
situations that lead to degradations and possible
system failure
Usability Testing

Usability testing is performed to the perspective of

the client, to evaluate how the GUI is user-friendly?
How easily can the client learn? After learning how
to use, how proficiently can the client perform? How
pleasing is it to use its design? This falls under the
class of black box testing.
Acceptance Testing
1. Acceptance testing is often done by the customer
to ensure that the delivered product meets the
requirements and works as the customer expected. It
falls under the class of black box testing.
2. Normally this type of testing is done to verify if
system meets the customer specified requirements.
User or customers do this testing to determine
whether to accept application.
Regression Testing
1. Regression testing is the testing after modification
of a system, component, or a group of related units
to ensure that the modification is working correctly
and is not damaging or imposing other modules to
produce unexpected results. It falls under the class of
black box testing.

2. Testing the application as a whole for the

modification in any module or functionality.
Difficult to cover all the system in regression testing
so typically automation tools are used for these
testing types.
Beta Testing
Beta testing is the testing which is done by end
users, a team outside development, or publicly
releasing full pre-version of the product which is
known as beta version. The aim of beta testing is to
cover unexpected errors. It falls under the class of
black box testing.
Sanity testing
Testing to determine if a new software version is
performing well enough to accept it for a major
testing effort. If application is crashing for initial use
then system is not stable enough for further testing
and build or application is assigned to fix.
Typically an initial testing effort to determine if a
new software version is performing well enough to
accept it for a major testing effort, For example, if

the new software is crashing systems every 5

minutes, bogging down systems to a crawl, or
destroying databases, the software may not be in a
sane enough condition to warrant further testing in
its current state
Incremental integration testing
Bottom up approach for testing i.e continuous
testing of an application as new functionality is
added; Application functionality and modules should
be independent enough to test separately. done by
programmers or by testers.
End-to-end testing
Similar to system testing, involves testing of a
complete application environment in a situation that
mimics real-world use, such as interacting with a
database, using network communications, or
interacting with other hardware, applications, or
systems if appropriate.
Load testing

Its a performance testing to check system behavior

under load. Testing an application under heavy
loads, such as testing of a web site under a range of
loads to determine at what point the systems
response time degrades or fails.
Security testing
If your site requires firewalls, encryption, user
authentication, financial transactions, or access to
databases with sensitive data, you may need to test
these and also test your sites overall protection
against unauthorized internal or external access

Exploratory Testing
Often taken to mean a creative, internal software
test that is not based on formal test plans or test
cases; testers may be learning the software as they
test it
Realization tests

With the increased focus on the value of Business

returns obtained from investments in information
technology, this type of test or analysis is becoming
more critical. The benefits realization test is a test or
analysis conducted after an application is moved into
production in order to determine whether the
application is likely to deliver the original projected
benefits. The analysis is usually conducted by the
business user or client group who requested the
project and results are reported back to executive
management
Mutation Testing
Mutation testing is a method for determining if a set
of test data or test cases is useful, by deliberately
introducing various code changes (bugs) and
retesting with the original test data/cases to
determine if the bugs are detected. Proper
implementation requires large computational
resources
Sanity testing: Typically an initial testing effort to
determine if a new software version is performing

well enough to accept it for a major testing effort.

For example, if the new software is crashing systems
every 5 minutes, bogging down systems to a crawl,
or destroying databases, the software may not be in a
sane enough condition to warrant further testing in
its current state
Build Acceptance Tests
Build Acceptance Tests should take less than 2-3
hours to complete (15 minutes is typical). These test
cases simply ensure that the application can be built
and installed successfully. Other related test cases
ensure that Testing received the proper Development
Release Document plus other build related
information (drop point, etc.). The objective is to
determine if further testing is possible. If any Level
1 test case fails, the build is returned to developers
un-tested
Smoke Tests
Smoke Tests should be automated and take less than
2-3 hours (20 minutes is typical). These tests cases

verify the major functionality a high level. The

objective is to determine if further testing is
possible. These test cases should emphasize breadth
more than depth. All components should be touched,
and every major feature should be tested briefly by
the Smoke Test. If any Level 2 test case fails, the
build is returned to developers un-tested
Bug Regression Testing
Every bug that was Open during the previous
build, but marked as Fixed, Needs Re-Testing for
the current build under test, will need to be
regressed, or re-tested. Once the smoke test is
completed, all resolved bugs need to be regressed. It
should take between 5 minutes to 1 hour to regress
most bugs
Database Testing
Database testing done manually in real time, it
check the data flow between front end back ends.
Observing that operations, which are operated on
front-end is effected on back-end or not.

The approach is as follows:

While adding a record there front-end check backend that addition of record is effected or not. So
same for delete, update, Some other database testing
checking for mandatory fields, checking for
constraints and rules applied on the table , some time
check the procedure using SQL Query analyzer
Functional Testing (or) Business functional
testing
All the functions in the applications should be tested
against the requirements document to ensure that the
product conforms with what was specified.(They
meet functional requirements)Verifies the crucial
business functions are working in the application.
Business functions are generally defined in the
requirements Document. Each business function has
certain rules, which cant be broken. Whether they
applied to the user interface behavior or data behind
the applications. Both levels need to be verified.
Business functions may span several windows (or)
several menu options, so simply testing that all

windows and menus can be used is not enough to

verify the business functions. You must verify the
business functions as discrete units of your testing
* Study SRS
* Identify Unit Functions
* For each unit function
* Take each input function
* Identify Equivalence class
* Form Test cases
* Form Test cases for boundary values
* From Test cases for Error Guessing
* Form Unit function v/s Test cases, Cross
Reference Matrix
User Interface Testing (or) structural testing

It verifies whether all the objects of user interface

design specifications are met. It examines the
spelling of button test, window title test and label
test. Checks for the consistency or duplication of
accelerator key letters and examines the positions
and alignments of window objects
Volume Testing
Testing the applications with voluminous amount of
data and see whether the application produces the
anticipated results (Boundary value analysis)
Stress Testing
Testing the applications response when there is a
scarcity for system resources
Load Testing
It verifies the performance of the server under stress
of many clients requesting data at the same time
Installation testing

The tester should install the systems to determine

whether installation process is viable or not based on
the installation guide
Configuration Testing
The system should be tested to determine it works
correctly with appropriate software and hardware
configurations
Compatibility Testing
The system should be tested to determine whether it
is compatible with other systems (applications) that
it needs to interface with
Documentation Testing
It is performed to verify the accuracy and
completeness of user documentation
1. This testing is done to verify whether the
documented functionality matches the software
functionality

2. The documentation is easy to follow,

comprehensive and well edited
If the application under test has context sensitive
help, it must be verified as part of documentation
testing
Recovery/Error Testing
Testing how well a system recovers from crashes,
hardware failures, or other catastrophic problems
Comparison Testing
Testing that compares software weaknesses and
strengths to competing products
Acceptance Testing
Acceptance testing, which black box is testing, will
give the client the opportunity to verify the system
functionality and usability prior to the system being
moved to production. The acceptance test will be the
responsibility of the client; however, it will be

conducted with full support from the project team.

The Test Team will work with the client to develop
the acceptance criteria
Alpha Testing
Testing of an application when development is
nearing completion, Minor design changes may still
be made as a result of such testing. Alpha Testing is
typically performed by end-users or others, not by
programmers or testers
Beta Testing
Testing when development and testing are
essentially completed and final bugs, problems need
to be found before the final release. Beta Testing is
typically done by end-users or others, not by
programmers or testers
Regression Testing
The objective of regression testing is to ensure
software remains intact. A baseline set of data and

scripts will be maintained and executed to verify

changes introduced during the release have not
undone any previous code. Expected results from
the baseline are compared to results of the software
being regression tested. All discrepancies will be
highlighted and accounted for, before testing
proceeds to the next level
Incremental Integration Testing
Continuous testing of an application as new
functionality is recommended. This may require
various aspects of an applications functionality be
independent enough to work separately before all
parts of the program are completed, or that test
drivers are developed as needed. This type of testing
may be performed by programmers or by testers
Usability Testing
Testing for user-friendliness clearly this is
subjective and will depend on the targeted end-user
or customer. User interviews, surveys, video
recording of user sessions, and other techniques can

be used. Programmers and testers are usually not

appropriate as usability testers
Integration Testing
Upon completion of unit testing, integration testing,
which is black box testing, will begin. The purpose
is to ensure distinct components of the application
still work in accordance to customer requirements.
Test sets will be developed with the express purpose
of exercising the interfaces between the components.
This activity is to be carried out by the Test Team.
Integration test will be termed complete when actual
results and expected results are either in line or
differences are explainable/acceptable based on
client input
System Testing
Upon completion of integration testing, the Test
Team will begin system testing. During system
testing, which is a black box test, the complete
system is configured in a controlled environment to
validate its accuracy and completeness in performing

the functions as designed. The system test will

simulate production in that it will occur in the
production-like test environment and test all of the
functions of the system that will be required in
production. The Test Team will complete the system
test. Prior to the system test, the unit and integration
test results will be reviewed by SQA to ensure all
problems have been resolved. It is important for
higher level testing efforts to understand unresolved
problems from the lower testing levels. System
testing is deemed complete when actual results and
expected results are either in line or differences are
explainable/acceptable based on client input
Parallel/Audit Testing
Testing where the user reconciles the output of the
new system to the output of the current system to
verify the new
Other way of classification of testing
WHITE BOX TESTING

This testing is also called as Structural Testing because it uses the internal structure of the
program to derive the test data. The software has been thoroughly tested using the White Box
Testing Strategy and it is confirmed that it is working according to the standards and the
requirement specifications.
BLACK BOX TESTING:
This testing is also called as Functional Testing because it is based on the definition of what
programming is intended to do, i.e., on the programs specified rather than of the internal
structure of the program. The software has been tested using the Black Box Testing Strategy
and confirmed that it is working according to the standards and the requirements specified.
UNIT TESTING:
Unit testing focuses on testing individual modules within a program.
There are two types of unit testing
Static analysis tests
Dynamic analysis tests

STATIC ANALYSIS TEST:

These evaluate the quality of a module through a direct examination of a source code
without executing on the machine.
DYNAMIC ANALYSIS TEST:
Dynamic tests require the module to be executed on a machine.
There are two types of dynamic analysis tests.
Black-box test
In black-box testing internal logic of a module is not examined. Test cases are
designed based on the requirements specification of the module and are executed to find
the deviations from requirements.
White-box test

White-box testing reveals the internal workings of a module. Test cases are
designed after the examination of internal logic of a module and traverse the different
execution paths built into the system.
UNIT TESTING:
It detects faults by focusing on small groups of components. Two or more components
are integrated and tested, and once tests do not reveal any new faults, additional
components are added to the group
There are three types of integration testing.
1. BIG-BANG TESTING
All components are tested individually and tested together as a single system.
2. TOP-DOWN TESTING
This strategy unit tests the components of the top layer first and then
integrates the components of the next layer down. When all the components
of the new layer have been tested together, the next layer is selected. Again
the tests incrementally add one component after the other to the test.

BOTTOM-UP TESTING
This strategy unit tests the components of the bottom layer first and then
integrates the components of the next layer up. When all the components of the
new layer have been tested together, the next up-layer is selected. This is repeated
until all components from all layers are combined together.
SYSTEMTESTING:
It tests all the components together, seen as a single system to identify errors from
the problem statement, requirement analysis and system design respectively.
System testing is of three types.
1. FUNCTIONAL TESTING
Tests the requirements specified as in requirement analysis document and user
manual in applicable cases and are done by the developer.
2. PERFORMANCE TESTING

Tests the nonfunctional requirements specified as in requirement analysis

document and are done by the developer.
3. ACCEPTENCE TESTING
Usability, functional and performance tests that are performed by client in the
development environment against acceptance criteria i.e. from project agreement.

INSTALLATION TESTING
Usability, functional and performance tests that are performed by client in the
target environment.
A test case is a set of input data and expected results that exercises the component
with the purpose of causing failures and detecting faults. Test cases are classified into
black box test and white box test.

Test case Execution & Analysis

The test cases that are used in the project are:
Test Case

Action

Context

Result

Existing ID

When User ID and

Password are
mismatched

Login Failure

LOGIN PAGE
Test case ID

Description

Input Value

Enter User ID

spcestudent

Expected
Values
Accept
Values

Actual
Values
Dot not show

Result
Pass

SCREEN SHORTS

SCREEN SHORTS

CONCLUSION

CONCLUSION

This project incorporates all requirements of a Server. This system has been
developed as versatile and user- friendly as possible, keeping in mind the advanced
features in this technology. This project is friendly to user and system interfaces. In
this project it java front end & MSACCESS as a back end. With help of ms access
ever Worry data loss and so. It is very secure and safety. Without an authorized
person this project cant be run or update. The STUDENT COUNSELING
MANAGEMENT SYSTEM project which help student for their higher Studies and
to select an good college and also a good course.

BIBLIOGRAPHY

REFERENCES:

1. http://www.tutorialspoint.com/jsp/
2. www.roseindia.net