A.

PROJECT REPORT ON

ONLINE COUNSELING SYSTEM

 TABLE OF CONTENTS

1. INTRODUCTION.....................................................................................................

1.1 PROFILE OF THE COMPANY..................................................................................

2. ABOUT PROJECT....................................................................................................

3. EVALUATION OF EXISTING SYSTEM..............................................................

3.1 OVERVIEW OF THE EXISTING SYSTEM................................................................

3.2 LIMITATIONS OF THE EXISTING SYSTEM..............................................................

4. PROPOSED SYSTEM..............................................................................................

4.1 INTRODUCTION...................................................................................................
4.2 FEATURES OF THE PROPOSED SYSTEM.................................................................

5. OBJECTIVE OF THE PROJECT...........................................................................

6. SCOPE OF THE PROJECT....................................................................................

7. SYSTEM ANALYSIS................................................................................................

7.1 INTRODUCTION.....................................................................................................
7.2 REQUIREMENT ANALYSIS.....................................................................................
7.3 S/w & H/w REQUIREMENT SPECIFICATION...........................................................
7.4 FEASIBILITY STUDY..............................................................................................
7.5 SOFTWARE ENGINEERING PARADIGM...................................................................

8. SYSTEM DESIGN.....................................................................................................

8.1 INTRODUCTION.....................................................................................................
8.2 MODULE DESCRIPTION........................................................................................

8.3 DATA FLOW DIAGRAM..........................................................................................

8.4 E-R DIAGRAM.......................................................................................................
8.5 DATABASE DESIGN...............................................................................................
8.6 INPUT-OUTPUT DESIGN.........................................................................................
8.7 INPUT-OUTPUT FORMS..........................................................................................
9. CODE DESIGN..........................................................................................................

10. TESTING....................................................................................................................

10.1 SYSTEM TESTING..................................................................................................

10.2 UNIT TESTING.......................................................................................................
10.3 MODULE TESTING.................................................................................................
10.4 INTEGRATION TESTING.........................................................................................
10.5 ACCEPTANCE TESTING..........................................................................................

11. IMPLEMENTATION & MAINTENANCE...........................................................

11.1 IMPLEMENTATION.................................................................................................
11.2 MAINTENANCE.....................................................................................................
11.3 COST ESTIMATION................................................................................................

12. CONCLUSIONS........................................................................................................

13. BIBLIOGRAPHY......................................................................................................
 1. INTRODUCTION

1.1 Profile of the Company: -

Gnix Info soft Ltd.
GNIX is an outsourcing center, which is developing and
distributing its own software solutions. Our outsourcing center handles not only
software development projects of various sizes and types but also entire business
processes.
Gnix is a highly experienced team of software developers
specializing in emerging internet and web technologies. We build professional,
innovative and creative solutions for the web, based on open source components, open
standards and frameworks. We work closely with our clients to provide a clear vision
and understanding of how emerging technologies can be used to gain a distinct
advantage over their competitors.
Gnix offers a range of professional IT consulting services to global
companies. Designed to update and enhance internal and external business systems,
these services include IT project management, strategy development, upgrades,
systems advice and more.
No high quality product can be used efficiently today without
embedding it in a rich framework of services. Although our products render a high
degree of user-friendliness, other problems remain to be solved that our located down-
or upstream of the software use.
Gnix consultants are experts in IT services. Their experience in IT
and in depth knowledge of business essentials can save you considerable time and
money. This combination of development and consulting is the continuing
improvement process of our products. And this company fallows the fallowing types
of activities-
Gnix Profile: -

We Understand you perfectly we know that you are young; you wish to
gain experience and to make a smooth transition between the bohemian college life
and the real world. Or that you possess valuable knowledge/experiences in various
fields that are unrelated to programming, such as: marketing, philology or consumer
psychology. This is why we are supporting your growth with trainings and other
methods.

Our Expectations: -

We are seeking creative, talented, flexible, perseverant persons who

stand out for their good technical and communication skills and are interesting in
constantly challenging their current limits. We will grow together by sharing our
knowledge, experiences, dream and visions.

Service overview: -

Gnix is a highly experienced team of software developers specializing

in emerging internet and web technologies. We build professional, innovative and
creative solutions for the web, based on open source components, open standards and
frameworks. And our core values-

- Quality
- Reliability
- Responsibility
- Honesty
- Flexibility
- Elegance
 2. ABOUT PROJECT

Project Title: - Online Counseling System

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 there paper work and reducing their time.
This project consist fallowing modules.

(1) Institute record - Covering Details regarding Institute

(2) Student record - Covering Details regarding Students
(3) Counseling - Helps in Category wise counseling.

3. EVALUATION OF EXISTING SYSTEM

 3.1 Existing System: -
Present system or Existing system of “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
there 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

3.2. Limitations of the Existing System: -

The maintenance of various records and procedure of reporting are being done
manually by the counseling department. This leads to many drawbacks some of which
are:
 It is a time consuming process.
 Proper arrangements should be made before and after the examination -which
is both money spending and time consuming.
 As the number of student’s increases counseling process becomes more and
more difficult.
 Not globally maintain the information
 Evaluating of answer sheets also consumes heavy amount of time.
 Difficult to management the all types of information of college or university
 Further more, manual evaluation is prone to errors.

4. PROPOSED SYSTEM

4.1 Introduction: -
 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: -

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.

Search: - It provides Searching for any institute details.

- On the basis of its code.
- On the basis of its name.

Delete: - If any institute Withdraw from counseling then this part will help in deleting
that institute record.

Display: - It will help in displaying complete information about institute code name,
city, and total seats according to category.

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

Delete: - This will allow to deleting record of any student after counseling. The
deletion can be on the basis of Roll no, Name.

(3) Counseling: -

This is the third and important module .It is divided into category wise
counseling. So there are three modes of counseling.

(a) General counseling:-

 Candidates in General Category enter in this counseling then he is
allotted to see the status of vacant and occupied general eats in every institute
the process “STATUS” if the satisfied he is allotted seats .In this procedure candidate
fill the complete form which includes details–
Name, Roll No, Rank, Sex, Category, etc.
But any Student want to withdraw after allotted the seats then can be withdraw with
the help in deleting the student record.

b) OBC counseling:-

Candidates in OBC Category enter in this counseling then he is

allotted to see the status of vacant and occupied general eats in every institute the
process “STATUS” if the satisfied he is allotted seats . In this procedure candidate
fill the complete form which includes details-
Name, Roll No, Rank, Sex, Category, etc.
But any Student want to withdraw after allotted the seats then can be withdraw with
the help in deleting the student record .
(c) C/ST Counseling:-

Candidates in SC/ST Category enter in this counseling then he is

allotted to see the status of vacant and occupied general seats in every institute
the process “STATUS” if the satisfied he is allotted seats .In this procedure candidate
fill the complete form which includes details – .
Name, Roll no, Rank, Sex, Category, etc.
But any Student want to withdraw after allotted the seats then can be withdraw with
the help in deleting the student record.

4.2 Features Of The Proposed System: -

The proposed system will aim to automate all the activities and eliminate all the
drawbacks that the existing system of manual operation faces. The important features
of functionality of the proposed system are listed below-
  The proposed system will save significant amount of time and effort
invested by the university every year.
 The System fully works as an online.

 Centralized maintain all information.

 It helps the university to dynamically add records to the database.
 Easy to Searching the information about college or university.

 Easy to managing whole counseling procedure

5. OBJECTIVE OF THE PROJECT

Online counseling System is fully work as online using the internet, which is
provides facility online such as- Student Counseling , Managing the student record,
Managing the Institute record and Searching the any other information about
Counseling procedure/Institutes, this types of information easy to search through the
website .

6. SCOPE OF THE PROJECT

 Types of information Online, and Efficient and systematic maintenance of
the huge Database, speeding up queries and faster processing are also be factor for
going for this project.

This system is applicable for any other university /Institute, which is work as
an online .The package will require data to be entered in user-friendly forms.

This system provide the scope of online working using the internet such as -
Student reporting ,counseling ,Institute registration for counseling , searching the
information of counseling procedure and total Seats of college etc.
There are fallowing modules and forms are used-

(1) Institute Record.

(2) Student Record.

(3) Counseling.

(4) Category’s selection form.

(5) Reporting, Withdraw.

7. SYSTEM ANALYSIS

7.1 Introduction: -
System Analysis is a detailed study of the various operations performed by
a system and their relationship within and outside the system .It is a systematic
technique that defines goals and objectives the goal of the development is to deliver
the system in the line with the user’s requirements, and analysis is this process.

System study has been conducted with the following objectives in mind: -

 Identify the client’s need.

 Evaluate the system concept for feasibility.
 Perform economical and technical analysis.
 Allocate functional to hardware, software, people, database and other system elements
 Establish cost and schedule constraints.
 Both hardware and software expertise is required to successfully attain the
objectives.

7.2 Requirement Analysis: -

Information gathering is usually the first phase of the software
development project. The purpose of this phase is to identify and document the exact
requirements for the system. The user’s request identifies the need for a new
information system and on investigation re-defined the new problem to be based on
MIS, which supports management. The objective is to determine whether the request
is valid and feasible before a recommendation is made to build a new or existing
manual system continues.

The major steps are –

 Defining the user requirements.

 Studying the present system to verify the problem.
 Defining the performance expected by the candidate to use requirements.

7.3 S/W and H/W Requirement Specification: -

Hardware Requirements: -

 Pentium IV 1.8 GHz and Above

 128 MB DDRAM or More
 40 GB HDD
 Printer
 Power Backup
 Internet Connection

Software Requirements: -

 Windows XP/Wins 2000 Professional

 J2EE ( jsp, servlet )
 Weblogic81
 Oracle 8i
 Java Script
 HTML
 IDE -My Eclipse 3.1.1
Introduction To Java: -
Java is a high level, third-generation programming language, like C,
FORTRAN, Perl and many others. It is a platform for distributed computing – a
development and run-time environment that contains built-in support for the World
Wide Web.

History Of Java: -
Java development began at Sun Microsystems in 1991, the same year
the World Wide Web was conceived. Java’s creator, James Gosling did not design
java for the Internet. His Objective was to create a common development environment
for consumer electronic devices which was easily portable from one device to
another. This effort evolved into a language, code named Oak and later renamed Java
that retains much of the syntax and power of c++, but is simpler and more platforms
independent.

Java Features: -
Some of the important features of Java are as follows: -
 Simplicity
 Object oriented
 Platform Independence
 Security
 Robust
 High Performance
 Multi Threading
 Dynamic linking.
 Garbage Collection.
One of the most important features of Java is Platform Independence which makes it
famous and suitable language for World Wide Web.

Why Java Is Platform Independent?

 Java is Platform Independent because of Java Virtual Machine (JVM).

Java Virtual Machine (JVM):-

The client application or operating system must have a java byte-code
interpreter to execute byte-code instructions. The interpreter is a part of a lager
program called the JVM. The JVM interprets the byte code into native code and is
available on platforms that support java.

When the user runs a Java program, it is unto the JVM to load,
possibly verify, and then execute it. The JVM can perform this function from within a
browser or any other container program or directly on top of the operating system.

When a browser invokes the JVM to run a Java program, the JVM
does a number of things: -

1. It validates the requested byte-codes, verifying that they pass various formatting and
security checks.

It allocates memory for the in coming java class files and guarantees that the security
of JVM is not violated. This is known as the class loader.

2. It interprets the byte code instructions found in the class files to execute the program.
Servlets / JSP are middleware technologies which are used in web
based projects because they use:-
1. HTTP Protocol to handle Request and Response.
2. They are invoked through Browser.
3. They give out put in HTML format.
4. They need Browser Support.

We have designed web based forms using Servlets and JSP in which we
have defined business logic.

About HTML: -
 Hypertext Markup Language (HTML) is a language for describing
how pages of text, graphics, and other information are organized. Hypertext means
text stored in electronic form with cross-reference links between pages. An HTML
page contains HTML tags, which are embedded commands that supply information
about the page’s structure, appearance, and contents. Web browsers use this
information to determine how to display the page.

About ORACLE 8i: -

Oracle 8i contains all the features of previous version. It also supports

some new features & enhancement to some existing features. Oracle servers provide
effective solution for the major features.

 Large Database & Space Management Control: -

Oracle supports the largest database potential hundreds of Giga Bytes

in size. To make efficient use of expensive devices, it allows full control of space
usage.

 Many Concurrent Database Performances: -

It supports large no of concurrent users executing a variety of database

Applications operation on the same data. It minimizes data connection & guarantees
data concurrency.

 High Transaction Processing Performance: -

Oracle maintains the processing features with a high degree of overall

system performance. Database user doesn’t suffer from slow processing performance.

 High Availability: -
 At some sets Oracle works 24 Hours per day with no downtime or
limit database throughput. Normal system operation such as database backup &
partial completion system failure don’t interrupt database use.

 Controlled Availability: -

Oracle can selectively control the availability of data at the database

level & sub Database level. Eg- an administrator can disallow use of a specific
application .Data can be reloaded without affecting other application.

 Manageable Security: -

To protect against unauthorized database aspects & users .Oracle

provides failsafe security features to limit & monitor the data area. The system makes
it easy to manage even the most completed designs for data assets.

 Database Enforced Integrity: -

Oracle enforces data integrity “Business rules” that dictates the

standards for applicable data. As result the cost of coding & managing checks in
many database applications are eliminated.

 Distributed Database System: -

Distributed systems have same degree of user transparency & data

consistency as non-distributed systems. Yet receives the advantages of local database
management.

 Portability: -
 Oracle software is compatible to work under different operating system
& same on all system. Application developed on Oracle can be used on virtually any
system with little or no more modification.

 Compatibility: -

Oracle software is compatible with industry standards, including most

industry standards operating systems. Application developed on Oracle can be used
on virtually any system with little or no modification.

 Connectivity: -

Oracle software allows different types of computers & operating

system to share information networks.

7.4 FEASIBILITY STUDY: -

Feasibility study is the process of determination of whether or not a

project is worth doing. Feasibility studies are undertaken within tight time constraints
and normally culminate in a written and oral feasibility report. I have taken two weeks
in feasibility study with my co-developer. The contents and recommendations of this
feasibility study helped us as a sound basis for deciding how to precede the project. It
helped in taking decisions such as which software to use, hardware combinations, etc.

The following is the process diagram for feasibility analysis. In the

diagram, the feasibility analysis starts with the user set of requirements. With this, the
existing system is also observed. The next step is to check for the deficiencies in the
existing system. By evaluating the above points a fresh idea is conceived to define
and quantify the required goals. The user consent is very important for the new plan.
Along with, for implementing the new system, the ability of the organization is also
checked. Besides that, a set of alternatives and their feasibility is also considered in
case of any failure in the proposed system. Thus, feasibility study is an important part
in software development.

WORKING CURRENT SYSTEM USERS CONSESUS

DEFICIENCES IN
USER CURRENT SYSTEM
STATED
REQUIREMENTS ANALYZE TO FIND DEFINE AND
DEFICIENCES QUANTIFY GOALS

REVISION BASED ON FEASIBILITY

CONSTRAINTS ON RESOURCES

EVALUATE FIND BROAD

FEASIBILITY OF ALTERNATIVE
ALTERNATES SOLUTION
PROPOSED FEASIBILITY
ALTERNATIVES
ALTERNATIVES

(Figure – 1) PROCESS DIAGRAM FOR FEASIBILITY ANALYSIS

In the SDLC (Systems Development Life Cycle) of our project we

maintained a number of feasibility checkpoints between the two phases of the
SDLC.

These checkpoints indicate that the management decision to be made

after a phase is complete. The feasibility checkpoints in our project were as follows:
(i) Survey phase checkpoint
(ii) Study phase checkpoint
(iii) Selection phase checkpoint
(iv) Acquisition phase checkpoint
(v) Design phase checkpoint

We together started measuring project feasibility, which lasted two

week. During this period we have had consultation with our guide Mr. Ajay Kumar
(project leader of Gnix Infosoft) and the management of the organization. In this
course we conducted three tests for Project feasibility namely, Technical,
Economical, and Operational feasibilities.

7.4.1 Technical Feasibility: -

Technical feasibility determines whether the work for the project can
be done with the existing equipment, software technology and available personnel.
Technical feasibility is concerned with specifying equipment and software that will
satisfy the user requirement.

This project is feasible on technical remarks also, as the proposed

system is more beneficiary in terms of having a sound proof system with new
technical components installed on the system. The proposed system can run on any
machines supporting Windows and Internet services and works on the best software
and hardware that had been used while designing the system so it would be feasible in
all technical terms of feasibility.

Technical Feasibility Addresses Three Major Issues: -

(a) Is the proposed Technology or Solution Practical?

The technologies used are matured enough so that they can be applied
to our problems. The practicality of the solution we have developed is proved with the
use of the technologies we have chosen. The technologies such as JAVA (JSP,
Servlet), JavaScript and the compatible H/Ws are so familiar with the today’s
knowledge based industry that anyone can easily be compatible to the proposed
environment.

(b) Do we currently posses the necessary technology?

We first make sure that whether the required technologies are available
to us or nor. If they are available then we must ask if we have the capacity. For
instance, “Will our current Printer be able to handle the new reports and forms
required of a new system?

(c) Do we possess the necessary Technical Expertise and is the Schedule

reasonable?

This consideration of technical feasibility is often forgotten during

feasibility analysis. We may have the technology, but that doesn’t mean we have the
skills required to properly apply that technology.

As far as our project is concerned we have the necessary expertise so

that the proposed solution can be made feasible.

7.4.2 Economical Feasibility: -

Economical feasibility determines whether there are sufficient benefits

in creating to make the cost acceptable, or is the cost of the system too high. As this
signifies cost benefit analysis and savings. On the behalf of the cost-benefit analysis,
the proposed system is feasible and is economical regarding its pre-assumed cost for
making a system.

During the economical feasibility test we maintained the balance

between the Operational and Economical feasibilities, as the two were the conflicting.
For example the solution that provides the best operational impact for the end-users
may also be the most expensive and, therefore, the least economically feasible.

We classified the costs of Online Counseling according to the phase in

which they occur. As we know that the system development costs are usually one-
time costs that will not recur after the project has been completed. For calculating the
Development costs we evaluated certain cost categories viz.
(i) Personnel costs
(ii) Computer usage
(iii) Training
(iv) Supply and equipments costs
(v) Cost of any new computer equipments and software.

In order to test whether the Proposed System is cost-effective or not we

evaluated it through three techniques viz.

 Payback analysis
 Return on Investment:
 Net Present value

7.4.3 Operational Feasibility: -

Operational feasibility criteria measure the urgency of the problem

(survey and study phases) or the acceptability of a solution (selection, acquisition and
design phases). How do you measure operational feasibility? There are two aspects of
operational feasibility to be considered:

(a) Is the problem worth solving or will the solution to the problem work?

There are certain measures, which decide, the effectiveness of the

system. These measures can be collectively called as PIECES.

P (Performance): -

The online Counseling System provides adequate throughput and response time.

I (Information): -

The online Counseling System provides Student and Staff with tamely, pertinent,
accurate, and usefully formatted information.

E (Economy): -

The online Counseling System of reduce the cost of the Counseling or Student
reporting (selection).

C (Control): -
The online Counseling System offer globally controls to protect against fraud and to
guarantee the accuracy and security of the data and information.

E (Efficiency): -

The online Counseling System makes maximum use of available resources and
minimum processing delays.

S (Services): -

The online Counseling System provides desirable and reliable service to those who
need it. The online Counseling System is flexible and expandable.

(b) How do the students and staff feel about the problem (Solution)?

It is not only important to evaluate whether a system can work. We

must also evaluate whether a system will work. A workable solution might fail
because of Students, Staff resistance.

In case of our project Online Counseling System we have examined all

the concerns that can further affect its operational feasibility. The following points
will explore those concerns.

The Online Counseling System has complete support of the

Student/Staff as an online reporting and access the information.

The Online Counseling System has made the role of Student easiest one. The
Student /Staff feel comfortable and upgraded with this system.

7.5 Software Engineering Paradigm Applied: -

Problem
Solving
The development strategy that encompasses the process, methods, and
tools and the generic phases is called Software Engineering Paradigm. The s/w
paradigm for software is chosen based on the nature of the project and application, the
method and tools to be used, and the controls and deliverables that are required. All
software development can be characterized as a problem-solving loops (fig. 2) in
Technical
Statu Development
which four distinct stages are encountered: - status quo, problem definition, technical
s
development, and
Quosolution integration.

Solution
Integration
 (Figure - 2) Problem Solving Loop

Status quo represents the current state of affairs, Problem definition

identifies the specific problem to be solved, technical development solves the problem
through the application of some technology, and solution integration delivers the
results to those who requested the solution in the first place.

There are various software paradigms, but we used Waterfall model (the
linear sequential model), which states that the phases are organized in a linear order.
The Waterfall model suggests a systematic, sequential approach to s/w development
that begins at the system level and progresses through analysis, design, coding,
testing, and maintenance and support as shown in below fig.3.
System
Analysis

System Document & Project plan

Requirement
Design
System & Detailed
Coding
Design document
Programs
Testing and
Test plan,
Integration
Report & manuals
Installation

Operations
and
Support
 Installation
Report

(Figure- 3) Waterfall model

The sequence of activities performed in a software development project

with the Waterfall model is: system analysis, system design, coding, testing &
integration, installation, and maintenance. For a successful project resulting in a
successful product, all phases listed in the waterfall model must be performed. Any
different ordering of the phases will result in a less successful software product.

There are a number of project outputs in waterfall model that is produced

to produce a successful product:

 Requirement documents and project plan

 System and detailed design
 Programs (code)
 Test plan, test reports and manuals
 Installation reports

7.5.1 Limitations Of Waterfall Model: -

1. The waterfall model assumes that the requirements of a system can be baseline before
the design begins. This is possible for system designed to automate an existing
manual system. For our system, (Online Counseling System) this is a new system,
determining the requirement is difficult, as the user does not even know the
requirements.
2. Freezing the requirements usually requires choosing the hardware.
3. The waterfall model stipulates that the requirements be completely specified before
the rest of the development can proceed.
4. It is a document driven process that requires formal documents at the end of each
phase. This approach tends to make the process documentation-heavy and is not
suitable for many applications (interactive applications).
The waterfall model is the most widely used process model.

8. SYSTEM DESIGN
8.1. Introduction: -
The objective of the system design is to deliver the requirements as
specified in the feasibility report. System design involves first logical design (logical
design) and then physical construction (detailed design) of the system. The logical
design describes the structure and characteristics of features, such as the outputs,
inputs, files, databases, and procedures. The physical construction produces actual
program software, files, and a working system.
System design goes through two phases of development: -
1. Logical Design
2. Physical Design
Logical Design:-
We know that a data flow diagram shows the logical flow of a system
and defines the boundaries of the system. Logical design specifies the user need at a
level of details that virtually determine the information flow into and out of the
system and the required data resources. Logical design describes the inputs, outputs,
database and procedures .All in a format that meets the user’s requirements.
Physical Design:-
 It provides the working system by defining the design specification that
tells programmers exactly what that candidate system must do. In short it can state
that physical design is the implementation of the logical design.
Physical system design consists of the following-
1) Design the physical system
i. Specify input, output media
ii. Design the database and specify backup procedures.
iii. Design physical information flow through the system and a
physical design walkthrough.
2) Plan system implementation

8.2 Module Description:-

Online Counseling System with the fallowing modules: -
(1) Counseling – Helps in Category wise counseling
(2) Institute record –covering Details regarding Institute
(3) Student record - covering Details regarding Students

8.3 Data flow Diagram: -

Zero - Level DFD of Counseling Module: -

Level-1 DFD of Counseling Module: -
Level - 2 DFD of Counseling Module: -
8.4 Entity-Relationship Diagram:-

E - R Diagram of Counseling Module: -

 Category U_ name
U_ adds
Roll no Rank U_ code
Name

Student Counselin University

g

Selection College Affiliation

of
college

C_
C_ code adds
C_ name

8.5 Database Design: -

Usually, a collection of interrelated data is referring to as database.

The database contains information about one particular enterprise. Database system is
designed to shear and manage large volume of information .The management of data
involves both the manipulation of information .In addition ,the database system must
provide for safety information storage in the database ,despite system crashes or
unauthorized access.

1. Table Name: STUDENT RECORD: -

Field Name Data Type Size Constraints Description

ROLL_NO VARCHAR2 15 Primary Key STUDENT ROLL
NO.
NAME VARCHAR2 30 STUDENT NAME
CATEGORY VARCHAR2 5 STUDENT
CATEGORY
RANK VARCHAR2 5 STUDENT RANK
INSTITUTE_CODE VARCHAR2 25 STUDENT GIVEN
INSTITUTE
SEX VARCHAR2 1 STUDENT SEX
DETAIL
CCODE VARCHAR2(10)

2. Table Name: INSTITUTE RECORD: -

Field Name Data Type Size Constraints DESCRIPTION

INSITUTE_CODE VARCHAR2 25 Primary Key CODE OF THE
INSTITUTE
INSTITUTE_NAME VARCHAR2 50 NAME OF THE
INSTITUTE
CITY_NAME VARCHAR2 25 INSTITUTE CITY
NAME
GENERAL_SEATS NUMBER 2 GENERAL SEATS
OBC_SEATS NUMBER 2 OBC SEATS
SC_SEATS NUMBER 2 SC SEATS
ST_SEATS NUMBER 2 ST SEATS
TOTAL SEATS NUMVER 3 TOTAL SEATS IN
INSTITUTE

3. Table Name: TOTAL SEATS: -

FLIEDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION

INST_CODE VARCHAR2 25 REFERENCES INSTITUTE
INSTITUTE CODE
GENERAL_VACSEATS NUMBER 2 CHECK GENERAL
(GENERAL_VACSEATS)<46 VACANT SEATS
OF THE
INSTITUTE
GENERAL_OCCSEATS NUMBER 2 CHECK GENERAL
(GENERAL_OCCSEATS<46) OCCUPIED
SEATS
 OF THE
INSTITUTE
GENERAL_TOTALSEATS NUMBER 2 CHECK GENERAL
(GENERAL_TOTALSEATS<46) TOTAL SEATS
OF THE
INSTITUTE
SC_VACSEATS NUMBER 2 CHECK SC VACANT
(SC_VACSEATS<19) SEATS OF THE
INSTITUTE
SC_OCCSEATS NUMBER 2 CHECK SC OCCUPIED
(SC_OCCSEATS<19) SEATS OF THE
INSTITUTE
SC_TOTALSEATS NUMBER 2 CHECK SC TOTAL
(SC_TOTALSEATS<19) SEATS OF THE
INSTITUTE
ST_VACSEATS NUMBER 2 CHECK ST VACANT
(ST_VACSEATS<2) SEATS OF THE
INSTITUTE
ST_OCCSEATS NUMBER 2 CHECK ST OCCUPIED
(ST_OCCSEATS<2) SEATS OF THE
INSTITUTE
ST_TOTALSEATS NUMBER 2 CHECK ST TOTAL
(SC_TOTALSEATS<2) SEATS OF THE
INSTITUTE
OBC_VACSEATS NUMBER 2 CHECK OBC VACANT
(OBC_VACSEATS<25) SEATS OF THE
INSTITUTE
OBC_OCCSEATS NUMBER 2 CHECK OBC OCCUPIED
(OBC_OCCSEATS<25) SEATS OF THE
INSTITUTE
OBC_TOTALSEATS NUMBER 2 CHECK OBC TOTAL
(OBC_TOTALSEATS<25) SEATS OF THE
INSTITUTE
COMBINED_TOTALSEATS NUMBER 2 CHECK COMBINED
(COMBINED_TOTALSEATS<100) TOTAL SEATS
OF THE
INSTITUTE

4. Table Name: Student report: -

Field Name Data Type Size Constraints Description

ROLL_NO VARCHAR2 15 REFERENCES STUDENT ROLL NO.
STUDENT
RECORD
C_DATE DATE 10 COUNSELING DATE
F_NAME VARCHAR2 20 FATHER NAME
P_ADDS VARCHAR2 30 PERMANENT ADDS
P_CITY VARCHAR2 10 PERMANENT CITY
P_STATE VARCHAR2 10 PERMANENT STATE
P_PIN VARCHAR2 10 PERMANENT PIN
C_ADDS VARCHAR2 25 ALTERNATE ADDS
C_CITY VARCHAR2 20 ALTERNATE CITY
C_PIN NUMBER 8 ALTERNATE PIN
 PH_NO NUMBER 11 PHON NO.
M_NO NUMBER 11 MOBILE NO.
EMAIL VARCHAR2 20 E-MAIL ADDS
I_CODE1 VARCHAR2 10 INSTITUTE CODE 1
I_CODE2 VARCHAR2 10 INSTITUTE CODE 2
I_CODE3 VARCHAR2 10 INSTITUTE CODE 3
INAME1 VARCHAR2 20 INSTITUTE NAME 1
INAME2 VARCHAR2 20 INSTITUTE NAME 2
INAME3 VARCHAR2 20 INSTITUTE NAME 3
ILOCATION1 VARCHAR2 15 INST. LOCATION 1
ILOCATION2 VARCHAR2 15 INST. LOCATION 2
ILOCATION3 VARCHAR2 15 INST. LOCATION 3
QUALIFICATION1 VARCHAR2 10 QUALIFICATION 1
QUALIFICATION2 VARCHAR2 10 QUALIFICATION 2
QUALIFICATION3 VARCHAR2 10 QUALIFICATION 3
UNIVERSITY1 VARCHAR2 15 UNIVERSITY 1
UNIVERSITY2 VARCHAR2 15 UNIVERSITY 2
UNIVERSITY3 VARCHAR2 15 UNIVERSITY 3
PYEAR1 NUMBER 4 PASSING YEAR 1
PYEAR2 NUMBER 4 PASSING PYEAR 2
PYEAR3 NUMBER 4 PASSING PYEAR 3
PMARKS1 VARCHAR2 4.2 PASSING MARKS 1
PMARKS2 VARCHAR2 4.2 PASSING MARKS 2
PMARKS3 VARCHAR2 4.2 PASSING MARKS 3

8.6 Input-Output Design: -

 Input Design: -
The input design is a crucial part of any system errors. Inaccurate
input data are the most common cause of the errors in the processing. Data entry
errors can be controlled by input design. Input design is the process of converting
user-oriented inputs to computer –based formats .the goal of designing input data is to
make data entry as easy, logical and free from errors as possible.
 Output Design: -
Computer output is the most important and direct source of
information to the users. Efficient intelligible output design should improve the
 system’s relationship with the user and help in decision making. A major form of
output is a hard copy from the printer. In the system under consideration, the output is
in two forms, hard copy from the printer and output to the CRT screen in predefined
format.

 Input-Output Forms: -
 9. Code Design

Code design for the system follows the following pattern. The java programs for the
accessing the database server consists of functions that retrieve data and return that
data in the required format. These java functions are put into classes. These classes
are identified by the module which they service. The classes are all part of a package.
This package is used in the JSP scripting to declare objects of a particular class. Once
the objects have been declared, the functions of that object can be easily accessed by a
normal “objectName.functionName” kind of call to it. The function performs the
necessary tasks and then returns the data to the JSP script. The web server then
processes these data and prepares an HTML file to be displayed to the user. This
process is depicted in the figure.

Figure: - Code Design

The JSP script creates the

Class Object objects of the java class files
JSP file. as required

This object Java class file

embedded in the
HTML using JSP Function A ( )
scripting can now Function B ( )
access all the Function C ( )
functions of that JSP file calls the …
functions of that object …
particular java class.
…
Function n ( )

DATABASE SERVER

Java functions do the

database handling
 10. TESTING
10.1 System Testing: -

Prior to the actual implementation of the system it had to be tested comprehensively

and every possible error uncovered. Since it is not possible to test the system
exhaustively, the black box testing method was used for system testing. The black box
testing usually demonstrates that software functions are operational; that the input is
properly accepted and the output is correctly produced; and that integrity of external
information (databases) is maintained.

Table 10.1 outlines the tests that were performed on the system to ensure correctness
and unearth errors which were subsequently debugged.

Table 10.1:- Tests Conducted on the System: -

Testing Phase Objectives

Unit The various functions within each program and the program
Testing blocks are tested for proper working.

A module is composed of various programs related to that

Module
module. Module testing is done to check the module
Testing
functionality and interaction between units within a module

Integration Integration testing is done to test the functionality and interfacing

Testing between the modules.

Acceptance Acceptance testing is done after implementation to check if the

Testing system runs successfully in the customer environment/site.
 10.2 Unit Testing: -

Unit Testing will be done to test field validations, navigation, functionality of the
programs and its blocks. These tests are applied on various functions within each
program and other critical program blocks. Table 10.2 and 10.3 outline two sample
test cases for Unit Testing performed on the system

Table 10.2:- Unit Testing – Test Case 1: -

Test Case Description

This test case deals with the creation of Student information. The creation
program takes many inputs. The test should check for proper inputs and verify
whether the creation function is called properly with the correct input parameters.
Expected Inputs

 Student details for reporting from the user (Counseling).

Expected Outputs

 Alert window for erroneous inputs.

 Confirmation of Student Counseling.
Actual Test Results

 An alert window was shown whenever the user gave some erroneous
data, such as entering numbers in the name field, entering characters in numeric
fields.
 Confirmation of Insertion of details was displayed on submission to the
add function, implying that the function was called properly.
 Table 10.3:- Unit Testing – Test Case 2: -

Test Case Description

This test case deals with the Withdraw of counseling Student by the java
function for that does the Withdraw. The test will check if the java function
receives the Withdraw properly and checks if the Withdraw is performed
correctly.
Expected Inputs

 Withdraw Counseling Student from the web server.

Expected Outputs

 The java function should return the Student Withdraw Message with
correct Rank and Roll-on of student.
Actual Test Results

 The java function received the Withdraw Massage properly.

 10.3 Module Testing: -
Module testing will be done to test the interaction between the various programs
within one module. It checks the functionality of each program with relation to other
programs within the same module. It then tests the overall functionality of each
module. Table 10.4 and 10.5 outline two sample test case for Module Testing
performed on the system.

Table 10.4:- Module Testing – Test Case 1: -

Test Case Description

This test case deals with the module creation in the Counseling module.

Expected Inputs

 Student details for Counseling.

Expected Outputs

 This new module should appear in the insertion /Registration programs.

Actual Test Results

 The new module appears in the insertion /Registration programs.

 Table 10.5:- Module Testing – Test Case 2: -

Test Case Description

This test case deals with the Withdraw and Reconciling for the Withdraw
programs in the Withdraw and Reconciling Module.
Expected Inputs

 Withdraw and recounseling of student details.

Expected Outputs

 Student Withdraw Massage with correct Rank and Roll-on of student,

with provisions to Recounseling.
Actual Test Results

 Displayed the correctly Withdraw massage, with provisions to

Recounseling for the Student.

10.4 Integration Testing: -

Integration testing is done to test the functionality and interfacing between the
modules. The system is built up of various modules which work together to automate
the activities. These modules should work together in a seamless way to achieve the
desired results. Integration testing will test for this property of the modules. The
modules display a cause and effect relationship, if data in one module is changed, then
it affects the data to change in some other module also. Integration testing needs to
check if the modifications do not adversely affect some other modules.
 Table 10.6:- Integration Testing – Test Case 1: -

Test Case Description

This test case deals with the Counseling module. After the Student
Reporting and final counseling.
Expected Inputs

 Student Roll No, Rank and category for confirmation.

Expected Outputs

 The student must be confirmation Counseling.

Actual Test Results

 Once the details are registered Student and on seeing the details in the
Counseling module, the student record details are displayed.

10.5 Acceptance Testing: -

Acceptance testing was done after the implementation of the system. The acceptance
testing will check if the system works correctly in the user environment and if all the
user specified functionalities are present. It also tests if the system adheres to the
company policies and quality standard. The On-Line Counseling system was tested
and accepted by Gnix Infosoft after the acceptance testing.
 11. IMPLEMENTATION AND MAINTENANCE

11.1 Implementation:-
Implementation uses the design document to produce code. Demonstration
that the program satisfies its specifications validates the code. Typically, sample runs
of the program demonstrating the behavior for expected data values and boundary
values are required. Small programs are written using the model: -
Write/Compile/ Test
It may take several iterations of the model to produce a working program. As
programs get more complicated, testing and debugging alone may not be enough to
produce reliable code. Instead, we have to write programs in a manner that will help
insure that errors are caught or avoided.

Top-Down Implementation: -
Top down implementation begins with the user-invoked module and works
toward the modules that do not call any other modules. The implementation may
precede depth-first or breadth-first.

Bottom-Up Implementation: -
Implementation begins with modules that do not call any other modules and
works toward the main program. Test harness (see below) is used to test individual
modules. The main module constitutes the final test harness.

Stub Programming: -
 Stub programming is the implementation analogue of top-down and
stepwise refinement. It supports incremental program development by allowing for
error and improvement. A stub program is a stripped-down, skeleton version of a final
program. It doesn't implement details of the algorithm or fulfill all the job
requirements. However, it does contain rough versions of all subprograms and their
parameter lists. Furthermore, it can be compiled and run. Extensive use of procedures
and parameter are the difference between stub programs and prototypes. Quick and
dirty prototypes should be improved--they should be rewritten. A stub program helps
demonstrates that a program's structure is plausible. Its procedures and functions are
unsophisticated versions of their final forms, but they allow limited use of the entire
program. In particular, it may work for a limited data set. Often the high-level
procedures are ready to call lower-level code, even if the more detailed subprograms
haven't even been written. Such sections of code are commented out. The comment
brackets can be moved, call-by-call, as the underlying procedures are actually written.

Incremental Program Development: -

As program become more complex, changes have a tendency to introduce

unexpected effects. Incremental programming tries to isolate the effects of changes.
We add new features in preference to adding new functions, and add new function
rather than writing new programs. The program implementation model becomes:

------ Define types/compile/fix;

------ Add load and dump functions/compile/test;

------ Add first processing function/compile/test/fix;

------ Add features/compile/test/fix;

------ Add second processing function/compile/test/fix;

------ Keep adding features/and compiling/and testing/ and fixing.

11.2 Maintenance: -

Once the software is delivered and deployed, then maintenance phase

starts. Software requires maintenance because there are some residual errors remaining
in the system that must be removed as they discovered. Maintenance involves
understanding the existing software (code and related documents), understanding the
effect of change, making the changes, testing the new changes, and retesting the old
parts that were not changed. The complexity of the maintenance task makes
maintenance the most costly activity in the life of software product.
It is believed that almost all software that is developed has residual
errors, or bugs, in them. These errors need to be removed when discovered that leads
to the software change. This is called Corrective Maintenance. Corrective maintenance
means repairing, processing or performance failures or making alterations because of
previously ill-defined problems.
Software undergoes change frequently even without bugs because the
software must be upgraded and enhanced to include more features and provide more
services. This also requires modification of the software. The changed software
changes the environment, which in turn requires further change. This phenomenon is
called the “law of software evaluation”. Maintenance due to this phenomenon is called
adaptive maintenance. Adaptive maintenance means changing the program function.
Perfect maintenance means enhancing the performance or modifying the programs
according to the user’s additional or changing needs. The keys to reduce the need for
maintenance are:
1. More accurately defining the user’s requirement during system development.
2. Preparation of system documentation in a better way.
3. Using more effective ways for designing processing logic and communicating
it to project team members.
4. Making better use of existing tools and techniques.
5. Managing the system engineering process effectively.
11.3 COST ESTIMATION OF THE PROJECT: -

The objective of the cost estimation is to enable the client or developer

to perform a cost-benefit analysis and for project monitoring and control. The
accuracy of the estimate depends on the amount of reliable information about the final
product. When the product is delivered, the cost can be accurately determined, as all
the data about the project and the resource spent can be fully known by then. The
obtainable accuracy of the estimates as it varies with the different phases is shown in
below figure: -

Feasibility Requirement System Detailed Coding and

Accepted Analysis Design Design
Testing Software

(Figure – Accuracy of cost estimation)

 4.5
4
3.5
3
2.5
2
1.5
1
0.5
0
Feasibility Req. Ana. Sys. Des. Det. Des. Code & T. Accep.
S/w

(Figure – Graph of Accuracy of Cost Estimation)

Cost Of Correcting Errors: -

According to the established S/W Engineering standard of
estimating the cost of correcting errors the phase wise distribution of occurrences of
errors is as given below: -
Requirement Analysis 20%
Design 30%
Coding 50%

The cost of correcting errors of different phases is not the same and depends on when
the error is detected and corrected. The relative cost of correcting requirement errors
as a function of where they are detected is shown below figure-.
 1000

100

50

10

Requirements Design Code Development Acceptance

Operation
Test Test
Phase in Which Error Was Detected

(Figure - 10) Cost of correcting errors

One can perform cost estimation at any point in the software life cycle. As
the cost of the project depends on the nature and characteristics of the project, at any
point, the accuracy of the estimate will depend on the amount of reliable information
we have about the final product. The figure depicted below shows the accuracy of the
cost estimation.
On Size estimation of Schedule and Cost of the Project: this approach implies
that size is the primary factor for cost; other factors have lesser effect. Here we will
discuss one such model called the Constructive Cost Model (COCOMO) developed by
Boehm. This model also estimates the total effort in terms of person-months of the
technical project staff. The basic steps of this model are as follows: -

 Obtain the initial estimate of the development effort from the estimate
of thousands of delivered lines of source code (KDLOC).
 Determine a set of multiplying factors from different attributes of the
project.
 Adjust the effort estimate by multiplying the initial estimate with all the
multiplying factors.
The initial estimate also called nominal estimate is determined by an
equation of the form used in the static single-variable models, using KDLOC as the
measure of size. To determine the initial effort Ei in person-months the equation used
is of the type
Ei = a*(KDLOC)b
In COCOMO model the values of constants a and b are different with
different type of projects. As our project is Organic type the values of a and b are 3.2
and 1.05 respectively. The total thousand delivered code (KDLOC) of our system has
been estimated as around 2.
In order to determine the multiplying factors commonly known as cost
driver attributes we have taken rating of these attributes according to our requirements.
From these, the effort adjustment factor (EAF) of our project has been estimated as
1.16.

Now the final efforts estimate, E, of our project is obtained by multiplying

the initial estimate by the EAF.
i.e., E = EAF*Ei

The project duration is estimated for an Organic project by the formula

D = 2.5 * E0.38 and according to this formula I have estimated the project duration 6
months.
 12. CONCLUSIONS

This was the first considerably large and important project

undertaken by me during my MCA course. It was an experience that changed the way
I perceived project development. The coding could not be started before the whole
system was completely finalized. Even then there were so many changes required and
the coding needed to be changed. I attribute this to inadequate information gathering
from the user. Though there were many meetings with the user and most of the
requirements were gathered, a few misinterpretations of the requirements still crept in.
It made me realize how important the systems analysis phase is. The project is a
classic example for the adage that learning of concepts needs to be supplemented with
application of that knowledge.

On the whole it was a wonderful experience developing this

project and I would have considered my education incomplete without undertaking
such a project which allowed me to apply all that I have learnt.
 13. BIBLIOGRAPHY

The following books were used extensively for the project development and
implementation.

1. Chuck Musciano and Bill Kennedy (1998) “HTML: The Definitive Guide”
O’Reilly & Associates Ltd
2. George Koch and Kevin Loney. (1997) “Oracle 8, The Complete Reference”
Oracle Press Edition.
3. Herbert Schildt (2001) “The Complete Java Reference” Tata McGraw-Hill
Publishing Company Limited.
4. Marty Hall (2000) “Core Servlets and JavaServer Pages” Sun MicroSystem
Press.
5. Matthew Siple. (1998) “The Complete Guide to Java Database Programming”
Tata McGraw-Hill Publishing Company Limited.
6. Roger S. Pressman (1997) “Software Engineering, A Practitioner’s Approach”
Tata McGraw-Hill Publishing Company Limited.
7. Professional JSP, Wrox Publications.

The following Links were searched and exploited extensively for the project
development and implementation.

1. http://java.sun.com/products/jsp
2. http://www.aw.com/cseng/
3. http://jakarta.apache.org