Off-Centre Online Counselling

Minor Project Submitted towards partial fulfillment of the

Degree of Bachelor of Engineering
(Year 2010)

Department of Information Technology

Guided By: Submitted By:

Prof. Anand Rajavat Sarthak Saxena (0802IT071049)
Lect. Ankit Dongre Satish Shukla (0802IT071050)
Lect. Anurag Golwelkar Shabbir Hussain (0802IT071052)
Lect. Rajesh K Chakrawarti Sourabh Rajput(0802IT071056)

Shri Vaishnav Institute of Technology and Science,

Indore
Shri Vaishnav Institute of Technology & Science,
1
 Indore

Certificate

This is to Certify that Mr. Sarthak Saxena, Mr. Satish Kumar Shukla , Mr. Shabbir
Hussain and Mr. Sourabh Singh Rajput working in a Group have satisfactorily
completed the Minor project titled “Off-Centre Online Counselling” towards the partial
fulfillment of the degree in Bachelor of Engineering (Information Technology)
Awarded by Rajiv Gandhi Technical University, Bhopal for the academic year
2010.

Project Guide Head of Department

Prof. Anand Rajavat Prof. Ashish Bansal
Lect. Ankit Dongre
Lect. Anurag Golwelkar
Lect. Rajesh K. Chakrawarti

Project in charge External

Prof. Jigyasu Dubey

Shri Vaishnav Institute of Technology and Science,

Indore
2
 ACKNOWLEDGEMENT

“We follow your foot-steps, we move on the path shown by you, we acknowledge
you, and we are proud to have guides like you.”

We feel it our proud privilege to express our deep sense of gratitude and Indebted -
ness to Prof. Ashish Bansal (Head of Department), Mr. Jigyasu Dubey (Project
In charge) Mr. Ankit Dongre and Ms. Rupali Bhartiya (Project Guide) for
providing their painstaking and untiring supervision. We own our deep sense of
gratitude and thanks for their constructive criticism, valuable suggestions and
constant encouragement at all stages of development of this project.

We wish to express our sincere thanks to all the faculty of Information Technology
Department, for providing a conductive environment for proper development of
project and the necessary facilities for completion of project.

We also express our sincere thanks and gratitude to all of them without whose
constant support and guidance, this project would not have been a success.

Sarthak Saxena (0802IT071049)

Satish Kumar Shukla (0802IT071050)
Shabbir Hussain (0802IT071052)
Sourabh Singh Rajput(0802IT071056)

INDEX
3
1. Introduction…………………………………………………………..8

1.1 Problem Statement……………………………………………………8

1.2. Objectives……………………………………………………………..8

1.3. Scope…………………………………………………………………..8

1.4.Platform Specification………………………………………………….9

1.4.1. Hardware………………………………………………………..9

1.4.2. Software………………………………………………………...9

1.4.3. Implementation Language………………………………………9

2. System Analysis…………………………………………………………….10

2.1. Identification of Need………………………………………………….10

2.2.Preliminary Investigation……………………………………………….10

3. Feasibility Study……………………………………………………………10

3.1. Technical Feasibility……………………………………………………11

3.2. Economical Feasibility………………………………………………….11

3.3. Operational Feasibility………………………………………………….11

4. Literature Survey…………………………………………………………….11

4.1. Work done By other…………………………………………………….11

4.2. Benefits………………………………………………………………….11

4.3. Proposed Solution……………………………………………………….12

4.4. Technology used………………………………………………………...12

5. Technical Part………………………………………………………………..13

5.1. Project Standards………………………………………………………..13

5.2. Proposed Tools…………………………………………………………..13

4
 5.3. Interfaces………………………………………………………………...13

5.4. Coding Language………………………………………………………..15

6. Software Engineering Approach……………………………………………..15

6.1. Software Engineering paradigm Applied………………………………...15

6.1.1. Description…………………………………………………………..15

6.1.2. Advantage & Disadvantages………………………………………...16

6.1.3. Reasons for use………………………………………………………17

6.2 Requirement Analysis……………………………………………………..17

6.2.1 Software Requirement Specification…………………………………17

6.2.1.1 Glossary…………………………………………………….…..17

6.2.1.2 Supplementary Specifications………………………………….17

6.2.1.3 Use Case Model………………………………………………..19

6.3 Planning Managerial Issues………………………………………………..20

6.3.1 Planning Scope………………………………………………...………20

6.3.2 Project Resources………………………………………………………20

6.3.3 Team Organization……………………………………………………..21

6.3.4 Project Scheduling……………………………………………………...22

6.3.5 Estimation………………………………………………………………..22

6.3.6 Risk Analysis………………………………………………………….....24

6.3.7 Security Plan…………………………………………………………….25

6.3.8 Configuration Management Plan………………………………………..25

6.4. Design……………………………………………………………………...26

6.4.1. Design Constraints…………………………………………………..26

6.4.2. Design Technique…....26

5
 6.4.3. Modeling……………………………………………………...…….27

6.4.3.1. Detailed Class Diagram……………………………...…….27

6.4.3.2. Interaction Diagram…..……………………………………28

6.4.3.2.1. Sequence Diagram ……………………..……….28

6.4.3.2.2. Collaboration Diagram…………………..………33

6.4.3.3. State Diagram…………………………………..………….39

6.4.3.4. Activity Diagram…………………………….…………….41

6.4.3.5. Deployment Diagram...…………………….……………...52

6.4.3.6. Component Diagram………………………………………53

6.5 Implementation Phase………...……………………………………………54

6.5.1. Language Used Characteristics………………………………………54

6.5.2. Code Efficiency……………………………………………………...54

6.5.3. Optimization of Code………………………………………………..54

6.5.4. Validation Check…………………………………………………….54

6.6 Testing……………………………………………………………………...55

6.6.1. Testing Objectives…………………………………………………...55

6.6.2. Testing Methods & Strategies used along with test data and the error listed for each
test case…………………………………………………………………..55

7. Conclusion & Discussion……………………………………………………………63

7.1.1. Limitation of Project…………………………………………………….63

7.1.2. Difficulties Encountered………………………………………………...63

7.1.3. Future Enhancement Suggestions………………………………………..63

8. Bibliography & References…………………………………………………………64

8.1.1. Reference Books…………………………………………………………64

8.1.2. Other Documentations & Resources……………………………………..64

6
7
1) Introduction

1.1) Problem Statement

Off-centre online Counselling software is software which alleviates the need for the student
to go to the specific allotted nodal centers for Counselling and provides a systematic
approach for the students in the allotment procedure for a college. In the current system, the
travelling needs of the student have to be elicited, the software needs to have minimal
information requirement from the student side, and allotment should be according to rank of
the student. The current system has only a single day slot which does not incorporate a delay
which can be disastrous for students.

1.2)Objective

The objective of the project is to develop a web application which enables the student to
choose a college of his her choice without going to the respective nodal centers. The
application will contain the list of all the students who have got a rank in the exam and will
allow the administrator to allot the college to the student from his/her selected choices.

This application has been made with the following objectives:-

1.2.1) To fulfill the basic requirements of the students.

1.2.2) To maintain the records of the student in an easy manner.

8
1.2.3) To allow the student to select ample number of colleges for allotment, depending upon
his rank.

1.2.4) To provide quick retrieval of information.

1.2.5) To allot the colleges for students.

1.3) Scope

1.3.1) Maintaining the profile of students.

1.3.2) Maintaining College lists.

1.3.3) Allotting the college to the student accordingly.

1.3.4) Tables have been provided already.

1.4) Platform Specification

1.4.1) Hardware Specification

1.4.1.1) Pentium IV Processor

1.4.1.2) 512 MB Ram

1.4.1.3) 17” colour monitor

1.4.1.4) 10 GB hard drive

9
1.4.1.5) Keyboard and an Optical Scroll Mouse.
1.4.1.6) NIC (Network Interface Card).
1.4.1.7) Modem.

1.4.2) Software Specification

1.4.2.1) Compatible operating system (Linux/Windows XP/Windows Vista)

1.4.2.2) Java supportable environment

1.4.2.3) Data source (JDBC-ODBC)

1.4.2.4) Web Browser like internet explorer, Mozilla Firefox

1.4.2.5) Database server-DB2 9.0

1.4.2.6) Implementation Language

1.4.3) Implementation Language

JAVA:

Java is used in a variety of computing applications and provides very unique features; this
was the driving force behind our reason of using java as the implementation language. The
significant features of java can be stated as:-

a) Simple: - Java was designed to be easy for professional programmer to use effectively.

b) Secure: - Java provides security by confining a Java program to the Java execution
environment and not allowing it to access other parts of the computer.

c) Portability: - Java provides the platform independence and hence provides portability.

d) Multithreaded: - Java supports multithreaded programming which allows you to write

programs that do many things simultaneously.

10
2) System Analysis

2.1) Identification of Need

Currently college allotment procedure is a process in which a student has to report at the
centre at a particular time. Also, the whole process of Counselling is cumbersome as it is
a long stepwise process. Need of this project is justified by its meaningful information
that it provides to its users and ease that it provides to its users. The need to report at a
particular instance has been removed with our site, also all the information regarding the
Counselling has been made available at the same place.

2.2) Preliminary Investigation

For preliminary investigation we referred to the present system available. WE found that
the process of allotment was not that easy, also as a student we realized what all problems
we had faced. Some of the problems were:-

2.2.1) The need to report at a particular instant on Counselling date was very
uncomfortable.

2.2.2) A lot of time and resource was also consumed at the Counselling centre.

2.2.3) The present Counselling procedure was also analyzed.

11
3) Feasibility Study

All projects are feasible- given unlimited resources and infinite time. Unfortunately the
development of a computer based system or product is more likely plagued by scarcity of
resources and difficult delivery dates. It is both necessary to evaluate the feasibility of a
project at the earliest possible time. A lot of effort and money can be saved if an ill
conceived system is recognized early in the definition phase.

The feasibility study includes the investigation of the information needs of the end user
and objectives, constraints, basic resource requirement and cost benefits. The main and
prime objective of feasibility study is not to solve the problem but to acquire a sense of
its scope. Based on this the feasibility of the proposed system can be evaluated in terms
of following major categories:

3.1) Technical Feasibility

It is the study of function performance and constraints that may affect the ability to
achieve an acceptance system. Our proposed application has minimum hardware
requirements

3.2) Economic Feasibility

This involves the calculation of money required to develop and operate the system and
also the returns that could be obtained from the system.

3.3) Operational Feasibility

12
 A development of an infringement, violations or liability that could result from the
development of the system makes it operationally feasible. It does not require its
installation on every system of its network.

4) Literature Survey

4.1) Work done by others:

Though this is a first of its kind project in this institute but this kind of approach is being
followed in A.I.E.E.E. Counselling.

4.2) Benefits
4.2.1) Overall ease in allocating a seat for the student.
4.2.2) Better utilization of time.
4.2.3) Easy access to all the information related to the Counselling.
4.2.4) Minimization of overall efforts.

4.3) Proposed Solution:

A successful solution would be an application that needs minimal input from the
student’s side so that those who are not comfortable with the computers can also use it.
The Counselling will also be done at home only and all the data related to Counselling
will be available at one place.

4.4) Technology Used:

4.4.1) JSP: - Java Server Pages allows you to easily create web content with both static
and dynamic components. JSP technology provides separation of content and display
logic. JSP technology projects all the dynamic capabilities of Java Servlet technology but
provides a more natural approach to creating static content. Java Server Pages (JSP)
technology provides a simplified, fast way to create dynamic web content. JSP technology
enables rapid development of web-based applications that are server- and platform-
independent.
4.4.2) Servlet: - Servlets are Java programming language objects that dynamically process
requests and construct responses. A Servlet is an object that receives a request and
generates a response based on that request. The basic servlet package defines Java objects
to represent servlet requests and responses, as well as objects to reflect the servlet's
13
 configuration parameters and execution environment. The package javax.servlet.http
defines HTTP-specific subclasses of the generic servlet elements, including session
management objects that track multiple requests and responses between the Web server
and a client. Servlets may be packaged in a WAR file as a Web application. Servlets can
be generated automatically by Java Server Pages (JSP) compiler.
4.4.3) DB2: - DB2 is a rational database management system developed by IBM. There
are various editions available in DB2. It primarily runs on UNIX, Linux, system –I
(formerly known as /400), z/OS and windows server.
4.4.4) Netbeans: - The Netbeans IDE is a free, open-source Integrated Development
Environment for software developers. The IDE runs on many platforms including
Windows, Linux, and Solaris. It is easy to install and use straight out of the box. The
netbeans IDE provides developers with all the tools they need to create professional cross-
platform desktop, enterprise, web and mobile applications. Netbeans, along with Eclipse,
is one of the most widely used Java IDE (Integrated Development Environment). The
purpose of this document is to describe the steps needed to run Netbeans 6.0.1 on a net
based system, using Linux Java Virtual Machine and Linux compatibility mode.

4.4.5) JDBC: - The JDBC API was designed to keep simple things simple. This means
that the JDBC makes everyday database tasks easy. This trail walks you through examples
of using JDBC to execute common SQL statements, and perform other objectives
common to database applications.

The Java Database Connectivity (JDBC) API is the industry standard for database-
independent connectivity between the Java programming language and a wide range of
databases – SQL databases and other tabular data sources, such as spreadsheets or flat
files. The JDBC API provides a call-level API for SQL-based database access.

JDBC technology allows you to use the Java programming language to exploit "Write
Once, Run Anywhere" capabilities for applications that require access to enterprise data.
With a JDBC technology-enabled driver, you can connect all corporate data even in a
heterogeneous environment.

5) Technical Part

5.1) Project Standard

14
Project standard defines the type of project. Our project is web based project.

5.2) Proposed Tool

We will make use of JSP programming language as a software tool for the development
of application.

Platform Independence: This feature helps our software to run on various operating
systems.

Safe and Secure: This security feature helps in confining our software to the Java
Environment and not allowing it to access the other parts of computer.

Object Oriented: This feature allows us to design our software from any blank state.
This feature of java makes it simple and easy to extend.

Faster response: As JSP engine compiles the JSP into corresponding servlet so after this

compilation when any other time JSP is accessed its response is very fast

5.3) Interfaces

5.3.1) User Interface

For the user to use our application easily and efficiently, we have provided a user
friendly GUI that contains text fields, buttons, boxes and hyperlinks. The menus and
buttons will provide options for the user to select a particular operation. Hyperlinks will

15
provide a user interface to specify the option while selecting an action. The selection box
and list boxes will specify other options.
User Interfaces
1) Homepage/ Login Screen
2) Student Information Page
3) Preference Selection Page
4) Admin Homepage
5) Update student Information
6) Update college Information
7) Seat Allotment by admin
8) College List
9) Last Year Status
10) Vie w allotted seats

5.3.2) Hardware Interfaces

5.3.2.1) Network Interface Card

5.3.2.2) Modem

5.3.2.3) Pentium 3 or equivalent AMD processor

5.3.2.4) 10 GB hard disk space

5.3.2.5) 256 MB RAM

5.3.2.6) 17” Monitor

5.3.2.7) Supportable Mouse and keyboard

16
 5.3.3) Software Interfaces

5.3.3.1) JDBC 3.0 API – This is API used for database connection.

5.3.3.2) DSN – We have to configure the ODBC manager by creating Data Source
Names.

5.3.3.3) JDBC-ODBC Bridge – Open Database Connection provided by Microsoft. JDBC

drivers provide a bridge between the JDBC API and the ODBC API.

5.3.3.4) DB2 as database.

5.3.3.5) Web Browsers like Internet Explorer, Firefox Mozilla, etc.

5.3.3.6) Compatible HTTP and TCP/IP protocol versions.

5.3.3.7) Compatible Operating System Linux or Windows Xp/Vista.

5.3.3.8) Java Supportable Environment.

Communications Interfaces
Browser – Microsoft Internet Explorer, Firefox Mozilla etc.
HTTP/HTTPS – Hyper Text Transfer Protocol.
TCP/IP – Transmission Control Protocol / Internet Protocol.
Data Transfer Rate is depend on internet connection.
Java Synchronize mechanism is used to control security and complexity.

5.4) CODING LANGUAGE

We have used HTML, JAVA and Java Scripts in our project.

6) Software Engineering Approach

17
To produce a solution for any client specific problem the team of software engineers must
adopt a development strategy that encompasses the processes, tools and layers. This
strategy is called process modeling. We have selected in our case incremental model.

Incremental Model:

The incremental model combines the elements of the linear sequential model with iterative
philosophy of prototyping.

6.1) Software Engineering Paradigm Applied

6.1.1) Description

The incremental build model is a method of software development where the model is
designed, implemented and tested incrementally (a little more is added each time) until
the product is finished. It involves both development and maintenance. The product is
defined as finished when it satisfies all of its requirements. This model combines the
elements of the waterfall model with the iterative philosophy of prototyping.

The product is decomposed into a number of components, each of which are

designed and built separately (termed as builds). Each component is delivered to the
client when it is complete. This allows partial utilization of product and avoids a long
development time. It also creates a large initial capital outlay with the subsequent long
wait avoided. This model of development also helps ease the traumatic effect of
introducing completely new system all at once.

18
6.1.2) Advantages & Disadvantages

Advantages

1) Easy to explain to users.

2) Stages and activities are well defined.

3) Ease in scheduling and managing project.

4) The model delivers an operational quality product at each stage, but one that satisfies
only a subset of the client’s requirements and this resulted into a quality product.

5) Verification at each stage ensured early detection at each stage.

Disadvantages

1) Addition of successive build was not easy and straight forward.

2) Each phase of iteration is rigid and may not overlap each other.

19
3) Problems may arise pertaining to system architecture because not all requirements
are gathered up front for the entire software life cycle.

4) Incorporating the additional built can sometimes prove to be difficult.

6.1.3) Reasons for use

The incremental model is easy to understand and use. As the project progressed, at each
level we had to go through analysis, design, code and test. Since the number of
developers was less and we had to start from the scratch, incremental model provided us
a proper template for each increment. Also, at each stage there was testing due to which
errors were detected at an early stage. For further improvements future increments can
be planned to manage technical risks and enhancements.

6.2) Requirement Analysis

6.2.1) Software Requirement Specification

6.2.1.1) Glossary

1) Administrator: - Administrator maintains all the details of the students, colleges and
also allots the college seats to the students.

2) Password: - It is a sequence of characters unique to each user, provided to verify the

genuine users.

3) Registration: - This is the process by which the students who have secured a rank
register them in the system.

4) Allotment: - Through this the administrator allots the seats to the students.

5) Database: - A highly structured set of data that is indexed and searchable.

6.2.1.2) Supplementary Specification

20
 Scope: Our web-based project allots the seats to the rank holding students. It is
accessible at any time for both users and administrator. In this the seats are allotted to
the students by the administrator according to their ranks.

Reference: None

Functionality: The application first authenticates the user and then provides him with
various options to select from the given list of colleges. After the time for registration
has expired the administrator starts the allotment function and the seats are allocated
according to the rank and priority of the student.

Usability: It is applicable in the situations where seats are to be allocated for colleges.

Reliability: The system is reliable because as it is an online system, it does not depend
on any specific system.

Performance: The performance of the system is measured in terms of maintaining

information and managing simultaneous entries in the database efficiently.

Security: WE have tried to incorporate the security feature in this application, by

providing a password to every user and even the administrator

6.2.1.3) Use Case Diagram

21
 < < e xte n d > >
E d it Vie w L a s t Ye a r S ta tu s
< < e xte n d > >
U p d a te

< < e xte n d > >

Vie w
< < in c lu d e > > < < e xte n d > > Vie w L is t o f C o lle g e
< < in clu d e > >

< < e xte n d > >

User
Vie w S tu d e n t In fo rm a tio n

L o g in

< < in clu d e > > Allo tm e n t

Vie w S tu d e n t Allo tm e n t
< < in c lu d e > >

C h o ic e S e le c tio n

Ad m in
Ve rify U s e rn a m e /P a s s w o rd

6.3) Planning Managerial Issues

6.3.1) Planning Scope

The objective of software project planning is to provide a framework that enables the
manager to make reasonable estimates of resource, cost and schedule. These estimates are
made at the beginning of the software project and should be updated regularly as the
project progresses.
22
6.3.1.1) Functions Evaluated and Redefined:

(i) Display the status of last year’s college seats.

(ii) Display the list of seats and colleges.

(iii) Register the students who have a rank.

(iv) Allot the seats for the registered students according to their rank and priority of the
college.

6.3.1.2) Constraints: The project was to be completed in three months time.

6.3.1.3) Interfaces

1) Hardware-Hardware

There is no hardware- hardware interface.

2) Hardware-Software

There is no such interface unless explicitly needed by the user.

3) Person Devices:

Input Devices: Keyboard and mouse

Output Devices – monitor

6.3.2) Project Resources

The project resources can be categorized as: -

1) Human Resource

23
 The human resources contain a necessary description of the skills required to
complete the development, the specialty of developers and the organizational
hierarchy in terms of the organizational position of each person involved in
development.

2) Specialty & Skills

The project is an application development project and thus calls for the
specialty of the developers in selected programming language which is JAVA
for our project. Good programming skills and proper handling of related
operation is the requirement for human resources.
3) Hardware Resources

Hardware Resources required for our project are as given under:-

• 16-bit computer.
• Network Interface Card.
• 64 MB Ram.
• LAN.

4) Software Resources

We need Net beans software development kit, Windows O/S, Editors for writing JSP
& HTML. We also require the tools like Rational Rose so as to incorporate practices
of RUP in our software.

6.3.3) Team Organization

Structure of our team is Democratic Decentralized (DD). Our team has no permanent
leader. Rather we have task coordinators. Decisions on problems and approach are made
by group consensus. Communication among team members is horizontal.

The democratic decentralized team has the following features:

6.3.3.1) There is no permanent leader.

6.3.3.2) Task coordinators are applied for short duration and then replaced by others.

24
 6.3.3.3) Decision taking is a group activity.

6.3.3.4) Communication is horizontal.

Our team comprises of four members :-

Satish Kumar Shukla

Sarthak Saxena

Shabbir Hussain

Sourabh Singh Rajput

6.3.4) Project Scheduling

25
6.3.5) Cost Estimation

Cost estimation is part of the planning phase of any engineering activity. The cost of software
can be calculated based on the following factors:

• Size
• Complexity
• Level of Reliability
• Level of Technology Utilized
26
Availability, Feasibility & Stability of the system used to produce the product.
Software cost estimation has two uses in software management:
1. During the planning stage, one needs to decide how many engineers are needed for the
project and develop a schedule.
2. In monitoring the project’s progress, one needs to assess whether the project is
progressing according to schedule and take corrective action if necessary.

6.3.5.1) COCOMO Model:

For estimating the cost of our project, we have used the COCOMO model. Constructive
cost model (COCOMO model). It is a hierarchy of software estimation model. It uses empirically
derived formulas to predict efforts as a function of LOC estimated. It consists of three different
models of increasing complexity and levels of detail. A brief description of the three models is
presented below:
Basic COCOMO or Model 1:
In this model, the cost is estimated solely on the basis of the delivered source instructions, or
lines of code measured in thousands (KLOC).
The equation for the basic COCOMO model is as follows:
E = a0 * (KLOC)b0
where,
E = Effort
KLOC = Lines of Code expressed in thousands
a0 and b0 are constants
Effort can be calculated in Semidetached mode for as follows:
E = 3.0* (KLOC)1.12 P-M
= 3.0 * (8.451) 1.12 P-M
= 32.754 P-M
Duration can be calculated as:
D = 2.5* (E)0.35 months
= 2.5 * (32.754)0.35
27
 = 8.477 months
Number of persons can be calculated as:
N = E/D persons
= 32.754 / 8.477
= 3.86 ~ 4 persons
The calculated value of number of persons is found to be 4 & the value of duration comes out to
be approx. 8.4 months which is more than actual values
This is because the COCOMO model is used with respect to LOC based calculations which vary
from one programming language to other for the same project.

6.3.5.2) Cost/Benefit Analysis:

Intangible Cost: The intangible cost related to our project comprises of the labor put in, study
hours devoted, in making the project and the advice given to us by our guide in making this
project. The intangible benefits involved in our project are the satisfaction of our guide and
colleagues who will test and use our project.
Indirect Cost: The indirect expenses related to our project are: electricity consumed
depreciation of the computer systems and other equipment that are used in the development of
the project. It also includes the cost of gathering the information regarding the project.
Variable Cost: Variable cost includes the cost of the stationary used for project report and also
the cost of the auxiliary storage media required as a backup of our project. Variable cost also
includes the traveling expense that was done for the project

6.3.6) Risk analysis

Risk analysis is a series of steps that helps a software team to understand and manage
uncertainty. Many problems can plague a software project. A risk is potential problem – it might
happen, it might not. But, regardless of outcome, it’s a really good idea to identify it, assess its
probability of occurrence, estimate its impact, and establish a contingency plan should the
problem actually occur.
Risk always involves two characteristics:
Uncertainty: The risk may or may not happen; that is, there are no 100% probable risks.
Loss: If the risk becomes reality, unwanted consequences or losses will occur.
Risks for our project can be:

28
• New concept may impose difficulties in implementation.

• Lack of training in tools, as it is the first application based web project we have worked, may
consume comparatively more time.

• Cost may exceed as the work progresses.

• Most significantly, database might not response in a way as expected

• Slow speed of page generation may lead to poor performance.

6.3.7). Security plan

It manages sensitive information or causes actions that can improperly harm individual is or
target for improper or illegal penetration, during security testing, tester place the role of the
individual to desire to penetrate the system.
Project Specific Security Plan:
This software system is prepared in JAVA which is known for its security management. Java
created software has no access to the other parts of system and memory etc. It has access to only
those memory areas which is allocated to the system. Thus it is one way to ensure security. It
has no threat to the network and its resources.
6.3.8) Configuration management plan
Software configuration management is an important element of software quality assurance. Its
primary responsibility is the control of change.
We are using Java in which modular mechanism can be implemented easily and modular
mechanism is very helpful for the future enhancements. So if any further enhancements being
happen than with the slightly change in the related module the new functions can be
implemented easily. Any changes occur in the system is acceptable, our system is not limited to
certain functionality only.
Each and every models (MODULE) contains the object which can be easily identify by there
name and the type of object. The whole description of the object is given in very clear and
precise way
6.4.) Design
Design describes a final system and the by which it is developed It refers to the technical
specification that will applied in implementing the candidate system. This section includes both
procedural and data design.

29
6.4.1) Design constraints
A set of fundamental software design constraints has evolved over past three decades. Each
provides the software designer with a foundation from which more sophisticated design methods
can be applied.

6.4.1.1) Design and Implementation Constraints

• GUI is only in English.

Login and password is used for identification.
There is no maintainability of back up so availability will get affected.
Limited to HTTP/HTTPS.
Operating environment is compatible to efficiently run the application like java, oracle etc.

6.4.1.2) Technology Constraints

1. License: Only licensed applications to be used.
2. Development Language: The popular suggestion for language of development is Java. Java
has been suggested for its platform independence and built in networking abilities.
3. RDBMS: The database API should be sufficiently abstracted so that it can be generalized to
use a database of the user's choice as the application matures.
6.4.2) Design techniques
The data Design transforms information model created analysis into the data structures that will
be required to implement the software. More detailed data design occurs as the software
component is designed
In our project we followed top-down design methodology. There are various reasons for this.
A top-down design approach starts by identifying the major components of the system,
decomposing them into their lower-level components and iterating until the desired level of
detail is achieved. Top-down design methods often result in some form of Stepwise Refinement.
Starting from an abstract design, in each step the design is refined to a more concrete level, until
we reach a level where no more refinement is needed and the design can be implemented
directly.
A top-down design approach is suitable only if the specifications of the system are clearly
known and the system development is from scratch. Hence, it is a reasonable approach if a
waterfall type of process model is being used

30
6.4.3) Modeling

6.4.3.1) Detailed Class Diagram

Ad m in is tra to r
L o g in Id : va rch a r
P a s s w o rd : va rch a r

Ad d S tu d e n t()
E d it In fo rm a tio n ()
S e a t Allo tm e n t() A d d e d n e w co lle g e b y

C o lle g e
Ma n a g e b y C o lle g e C o d e : in te g e r
N u m b e r O f S e a t : in te g e r

V ie w C o lle g e L is t b y

S tu e n t
L o g in ID : va rc h a r
P a s s w o rd : va rc h a r
R a n k : in te g e r

R e g is te r P re fe re n ce s ()
E d it In fo ()
Vie w L a s t Ye a r S ta tu s ()

31
6.4.3.2) Interaction Diagram

6.4.3.2.1) Sequence Diagram

(i) Admin Login

Login If Valid Database

: Admin

Enter Id & Password

Submit

If Invalid

If Valid

Grant Access

(ii) Add student

32
 Options Add Student Database

: Admin

Available Options

Select Add Student Option

Student is added into Database

(iii) Add College

Options Add College Database

: Admin

Available Options

Select Add College Option

College is added into Database

(iv) Seat Allocation

33
 Options Allocation Database

: Admin

Available Options

Allocation is Done

Allocated seats are store in database

(v) Admin Update student Information

Options View Student Update Student Database

Info Info
: Admin

Available Options

View Student info

Edit Student Info

Updated info is Stored in Database

(vi) Admin Update college Information

34
 Options View College Update College Database
Info Info
: Admin

Available Options

View College info

Edit College Info

Updated info is Stored in Database

(vii) View Option

Options View Option Database

: Student
Option Select

Chose View Option

View College Info/Last year Status

(viii) Student Login

35
 Login Check Login Databas e Regis ter
: Student Prefrences

Enter Id & Pas s word

Subm it

If Invalid

If Valid

Regis ter Prefrences

6.4.3.2.2) Collaboration Diagram

(i) Admin Login

36
 1: Enter Id & Password
Login

: Admin

2: Submit
3: If Invalid
5: Grant Access

4: If Valid
If Valid Databas
e

(ii) Add student

1: Available Options
Options

: Admin

2: Select Add Student Option

3: Student is added into Database

Add Databas
Student e

(iii) Add College

37
 1: Available Options
Options

: Admin

2: Select Add College Option

3: College is added into Database

Add Databas
College e

(iv) Seat Allocation

1: Available Options
Options

: Admin

2: Allocation is Done

3: Allocated seats are store in database

Allocation Databas
e

(v) Admin Update student Information

38
 1: Available Options 2: View Student info
Options
View Student
Info

: Admin

3: Edit Student Info

4: Updated info is Stored in Database

Update Databas
Student Info e

(vi) Admin Update college Information

1: Available Options 2: View College info

Options
View College
Info

: Admin

3: Edit College Info

4: Updated info is Stored in Database

Update College Databas
Info e

(vii) View Option

39
 2: Chose View Option View
Option
Options

1: Option Select

: Student

3: View College Info/Last year Status

Databas
e

(viii) Student Login

40
 2: Submit Check
Login
Login
Register
Prefrences
5: Register Prefrences

1: Enter Id & Password

4: If Valid
: Student

Databas
e

6.4.3.3) State Diagram:

41
 (i)Updation is done by Admin

Admin Login Sucessful Display

login Options

Option selected

Updation unsucessful

Relevant page Updates Updation

displayed performed

(ii)Allotment is done by Admin:

42
 Admin Login Successfully Display
Login Option

Option Selected

Relevant Page Allotment is done Allotment is

Displayed done

(iii)Registration is done by Student

Student Login Succesful Displayed

Login Option

Option Selected

Seat Prefrence Register Succesful

Register

6.4.3.4) Activity Diagram

43
1) Student:
Student selects the name of colleges from the list according to his/her preference,
checks the last year status of seats in the colleges, checks own rank status & at last views the seat
allotment in the college for him/her.

1.1) Name of Use Case: Login

Description: This use case describes how a student/administrator logs into the System. The use
case takes in the user name and password to logon and checks for its validity

Preconditions: Student/administrator needs a valid user name and password to logon to the
system.

Normal flow of events:

 Student enters his/her roll number as id and provided password.
 After pressing enter student is logged in.

Serial Number Actor Description Condition Location

1) Student Entry of username Validate Respective

and password Homepage

2) Administrator Entry of username Validate Administrator

and password Homepage

Alternate flow of events: if the user id or password is wrong then error will be generated and
 Student/administrator will be redirected to login page again.

Serial Number Actor Description Condition Location

1) Student Entry of username Invalidate Login Page

and password

2) Administrator Entry of username Invalidate Login Page

and password

44
 Login Activity:

Login Page

Enter the ID and

Password

Invalid User Redirect to

Validates Login Page

Valid User

Switch to
Home Page

Name of Use Case: Update Students Information

Precondition: Student should be logged on to the system.

Normal Flow Of Events:

 Student selects the edit option & updates the information.
 Now clicks on update & data will be updated.

45
Alternate Flow: None

Serial Number Actor Description Condition Location

1) Student Change Of Change Edit Page

Information

2) Student Update Update Edit Page

Edit Activity:

Logged In

Edit the
Inform ation

Update the
Inform ation

Information
Update

46
1.3)Name of Use Case: View

Description: Student can view all the information available in the counseling by accessing the
lists and data provided for different purposes.

Precondition: Student should be logged on to the system.

Normal Flow of Event:

 User clicks on List of Colleges.
 List of colleges will be displayed to the user.

Alternate Flow: None

Post Condition: None

Serial number Actor Description Condition Location

1) Student View The List View Homepage

Of Colleges

2) Student View The Last View Homepage

Year’s Status

3) Student View Seat View Homepage

Allotment

4) Student View Personal View Homepage

Information

47
View Activity:

48
 Logged in

View Personal
Information

Personal Information
Displayed

Login

List of
College

Display List

of Colleges

49
View Activity:

50
 Logged in

Last Year Status

Last Year Status

Displayed

1.4)Name of Use Case: Choice Selection

Description: Student can select their choices of colleges according to their preference for
allotment of seat. In this student has the facility that he/she can change their preferences, but
within a specified time duration.

Precondition: Student should be logged on to the system.

Normal Flow of Event:

 Student selects the colleges from the given list according to their preference.

51
  After it student clicks on Done & the data will be updated.
 Student will be directed to homepage

Alternate Flow:
#) The choices selected are cancelled and not saved, the student will be directed to the
homepage.

Post Condition: None.

Serial Number Actor Description Condition Location

1) Student Selection Of Select Choice Selection

Choices Page

2) Student Save the selected Save Choice Selection

Choices Page

Serial Number Actor Description Condition Location

1) Student Choices not Cancel Choice Selection

Saved Page

Choice Selection Activity:

52
 Logged in

Select the Colleges

Information Stored

Administrator:
Administrator manages all the information about last year seat allotment
status in the colleges & also manages the list of colleges available in the counseling. At last
administrator will allot the seats for students according to their ranks.

Name of Use Case: Login as Administrator

Description: Administrator can login in the system.

Normal flow of events:

 Administrator the admin id & password.
 He can start the process of allocating the seats.

Alternate flow of events: None

Serial number Actor Description Condition Location

1) Administrator Logging on Enter username Login Page

& password

53
2) Administrator Allotment Of Allot Seat Allotment
Seats Page

3) Administrator No Allotment Of Cancel Seat Allotment

Seats Page

Allotment Activity:

54
 Logged In

Selects the Option

Seat Allotment

Return to
Alloted
Same Page

List of Seat Allotment

Displayed

6.4.3.5) Deployment Diagram

55
 User(Student or
Adminstrator) Lo... Application and
server Databas
e

preemptive

6.4.3.6) Component Diagram

56
 Add
Student

Add
Administr College
ator

Update
College Info

Allocatme
nt
DB2

Update
Student Student info

View
College

View Last
Year Status

Register
Prefrences

6.5 Implementation Phase

57
6.5.1) Language used characteristics

The language used is JAVA and the characteristics of JAVA are:-

• Platform Independence
• Object Oriented
• Robust
• Interpreted
• Distributed
• Dynamic
• Safe and Secure
• Multithreading

6.5.2) Code Efficiency

In an effort to maintain computational efficiency and to allow the eventual adaptation of the
algorithm to face tracking applications, intense optimization of the code has been performed.
Although further development is in progress, the algorithm is currently fast and compact enough
to run interactively on most generic platforms

6.5.3) Optimization of Code

Optimization of Html code:

6.5.4. Validation Check
Validation checks that the product design satisfies or fits the intended usage (high-level
Validation confirms that the product, as provided, will fulfill its intended use. Validation ensures
that ‘you built the right thing’.
Validation Check is implemented in the project wherever necessary

6.6) TESTING

6.6.1. Test Objectives

58
 Errors may begin to occur at the very initial stage of the process where the objectives
may be imperfectly specified, as well as in the later design and development stages. Because of
human inability to perform and communicate with perfection, software development is
accompanied by a quality assurance activity.
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. And it is needed to be done in almost every phase of
product development cycle not just before a product is handed to a consumer.

6.6.2) Testing Methods & Strategies used along with test data and the error listed for
each test case

Any engineered product can be tested in one of two ways:

• Black Box Testing –

o Knowing that a product has been designed to perform, tests can be

conducted that demonstrate each function is fully operational, at the same
time searching for errors in each function.

CASE 1

Project Online Offcenter Module Dialog/Screen

Na Counselling Name Name
me
Shabbir
Hussain,Satish
Tester Testing
Shukla,Sarthak Test Plan No. 1.0
Name Date
Saxena,Sourabh
Rajput

Reviewer Review
Name Date

CASE 2:When the user is at home page

Test case no. Action Expected Success Comments

Result
59
1.0 Do not enter data No action is Yes The Action Was
in any of the perform. Home Successfully
fields and press page appears tested.
the Button Go.
1.1 Enter Valid User Show the Yes This Action was
Name and information of Successfully
Password as a student if tested.
Student and click allotment is not
on Submit done yet and if
Button. allotment is done
then allotment
information of all
Student
displayed.
1.2 Enter Valid User Show the Admin Yes This Action was
name and page containing Successfully
Password as a links Update tested.
Admin Student
Information,
Update College
Information,
Allot the seats
for students
1.3 Click the Link College List Yes The Action was
Show the Displayed. Successfully
College List. tested.
1.4 Click Show the Last Year Status Yes The Action was
Last Year Status. Displayed. Successfully
tested.

CASE 3:When the Student Logged in Successfully and allotment is not done yet.

Test case no. Action Expected Success Comments

Result
60
1.0 Student Edit his Information of Yes The Action Was
information and Student is Successfully
click on update Updated. tested.
button

1.1 If Student remain Alert is raised Yes The Action Was

any field blank. asking Please Successfully
Don’t Left Any Tested.
Field Empty and
information is
reset
1.2 Click on next Preference page Yes The Action Was
button is open Successfully
tested.

CASE 4: When Student click on next button.

Test case no. Action Expected Success Comments

Result
1.0 No preferences is Alert is raised Yes The Action Was
chosen in any asking Required Successfully
Dropdown list Field Are tested.
Empty…Please
Fill Them First
1.1 Preference is Register is done Yes The Action Was
chosen and click Successfully
on Register tested.
me/Update
Preferences
button

CASE 5:After Logged in by Admin:

Test case no. Action Expected Success Comments

Result
61
1.0 Click on link Corresponding Yes The Action Was
Update Student page open having Successfully
Information links Add new tested.
Student, Edit
information of an
existing
Information
1.1 Click on link Corresponding Yes The Action Was
Update College page open having Successfully
Information links Add new tested.
College, Edit
information of
existing one
1.2 Click on link Corresponding Yes The Action Was
Change Deadline page open. Successfully
for Registration. Tested.

1.3 Click on link Corresponding Yes The Action Was

Allot the seats page open. Successfully
for the student tested.

1.4 Click on Exit Home page is Yes The Action Was

Button Displayed Successfully
tested.

CASE 6:When Admin click on Update Student Information Link

Test case no. Action Expected Success Comments

Result
62
1.0 Click on link Corresponding Yes The Action Was
Add a new page open Successfully
Student tested.

1.1 Click on link Corresponding Yes The Action Was

Edit information page open Successfully
of an existing tested.
Student

CASE 7: After click on Add a new Student:

Test case no. Action Expected Success Comments

Result
1.0 Do not enter data SQLException is Yes The Action Was
in any of the Generated Successfully
fields and press tested.
the Button
Submit.
1.1 Adding full Information is Yes The Action Was
information and stored in Successfully
click on submit database and tested.
button conform whether
you want to add
more student or
not

CASE 8: After click on Edit information of an existing Student:

Test case no. Action Expected Success Comments

Result

63
1.0 Do not enter data Invalid Cursor Yes The Action Was
in given field and State Error Successfully
press the OK tested.
Button.

1.1 Entering valid Student Yes The Action Was

student roll no Information Successfully
and press on OK Displayed and tested.
button there is buttons
of update
information and
delete from list.

CASE 9: After Entering a valid roll no.

Test case no. Action Expected Success Comments

Result
1.0 Click on update New information Yes The Action Was
information is added into Successfully
button after database tested.
editing some successfully.
information
1.1 Enter Delete Information is Yes The Action Was
button deleted from Successfully
database tested.

CASE 10: After click on Add a new College:

Test case no. Action Expected Success Comments

Result

64
1.0 Do not enter data SQL Error is Yes The Action Was
in any of the Generated Successfully
fields and press tested.
the Button
Submit.
1.1 Adding full Information is Yes The Action Was
information and stored in Successfully
click on submit database and tested.
conform whether
button
you want to add
more College or
not

CASE 11: After click on Edit information of an existing College:

Test case no. Action Expected Success Comments

Result
1.0 Do not enter data Invalid Cursor Yes The Action Was
in given field and State Error Successfully
press the OK tested.
Button.

1.1 Entering valid College Yes The Action Was

College code Information Successfully
and press on OK Displayed and tested.
button there is buttons
of update
information and
delete from list.

CASE 12: After click on Edit Change Deadline for Registration:

Test case no. Action Expected Success Comments

Result

65
1.0 Chose the value Deadline of the Yes The Action Was
of Set Date, Set allotment date is Successfully
Month, Set Year update tested.
from Dropdown successfully
List and press ok
button

CASE 13: After Entering a valid College code.

Test case no. Action Expected Success Comments

Result
1.0 Click on update New information Yes The Action Was
information is added into Successfully
button after database tested.
editing some successfully.
information
1.1 Enter Delete Information is Yes The Action Was
button deleted from Successfully
database tested.

CASE 14:After click on link Allot the Seats for Students.

66
Test case no. Action Expected Success Comments
Result
1.0 Click on Sure Allotment is Yes The Action Was
button done and stored Successfully
in database tested.

1.1 Enter back Previous page Yes The Action Was

button opens Successfully
tested.

7) Conclusion & Discussion

7.1.1) Limitation of the Project

(i) The project does not account for the allocation of seats according to the branch.
(ii) The project does not account for the Counselling of the reserved category students.

7.1.2) Difficulties encountered

(i) The first and foremost difficulty encountered was that of learning an entirely new
language. (ii) Interaction between different modules.

7.1.3) Future Enhancement

The project can be extended by adding new features to it:-

(i) The project can be enhanced by providing branch wise allotment.
(ii) The project can have the feature of virtual Counselling where the student can have an
elementary idea of which seat can he get in real Counselling.

8. Bibliography & References

8.1.1. Reference Books
Following books were consulted:
67
1. Herbert Schildt, Java2 Complete Reference. McGraw-Hill Osborne Media; 7
edition (December 1, 2006)

2. Roger S. Pressman, Software engineering: A Practitioner's Approach. McGraw-

Hill Science/Engineering/Math; 6 edition; 6th edition (April 2, 2004).

8.1.2. Other Documentations & Resources

Websites visited were:

1. www.w3schools.com

2. www.codeproject.com

3. www.google.com

4. www.daniweb.com

68