E Campus

1
E-Campus Synopsis
1. Introduction
In recent years, tragic events in coastal areas have made campus safety an ever-increasing
priority for the campuses of educational institutes along the costal line of the country.
Situation of the National Institute of Technology (NIT) was no different. A key facet of
risk and emergency management on school campuses is communication. With this
philosophy in mind, NIT decided to leverage information technology for creating
powerful and effective emergency management system, thereby reduce the risk and to
help effectively respond to a natural disaster. It was envisaged to develop a fully
integrated, scalable system that could instantly transmit a large number of messages via
various communication channels to first responders and everyone in the students
database, and also provide a tracking mechanism.
1.1 Existing System and its Limitations
No Prior Information about the Natural Disasters.
Communication to the students and the first responders are not much accurate and
quick.
High Risk compared to the New system ( E- Campus)
1.2Proposed System
Fastest way to communicate with students and the first responders.
Prior information regarding Natural Disasters and the Emergency situations.
Giving access to the users with User ID and Password to authenticate.
Using multiple alert types. (Ex : Mild, Moderate and severe)
Provide solutions to the problems reported by the user.
1.2.1 Advantages over Existing System

Speed: The speed in this system is more, to access the information quickly. And also it
takes less time to process (inserting, deleting, updating) the data into database.
Accuracy: Admin will authorize the employee based on employee id. Each employee
have only one employee id.
Secure accessing: Security is more because admin will create the employee ids. Based on
employee authority they can login.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
Availability of information: The employee information is available at the administrator
side.
Manage information: The admin and user both manage the database of the employee
based up on their ids . Firstly it provides online car service appointment facility.
Convenient and hassle free way to book car service appointment on the go. Best way to
avoid last minute car service appointment rush. User friendly can be access anywhere.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
2. Literature Survey
At this basic level it is particularly effective at getting a greater level of response. While it
may generate lots of applications than traditional print advertising, simply attracting more
candidates is only the part of the job. The current state is that truly effective online
recruitment can be as low as 10 percent of the top blue-chip corporate companies.
The original strength & power of online recruitment is when it is done properly, lie in
controlling internet technology to not just attract the candidates but to deal with them
also. In this sense it is also about streamlining the recruitment process, so busy human
resource departments can give a good recruitment service to their colleagues in finance,
marketing, sales and manufacturing and moreover it frees up more of their time for other
potential tasks.
2.1 Technologies Used

In this we briefly explain about the technologies used to develop the project like html,
java script, and java server pages.
2.1.1 Hypertext Markup Language (HTML)

HTML, an initialize of Hypertext Markup Language, is the predominant markup language
for web pages. It provides a means to describe the structure of text-based information in a
document by denoting certain text as headings, paragraphs, lists, and so on and to
supplement that text with interactive forms, embedded images, and other objects. HTML
is written in the form of labels (known as tags), surrounded by angle brackets. HTML can
also describe, to some degree, the appearance and semantics of a document, and can
include embedded scripting language code which can affect the behavior of web browsers
and other HTML processors.
Frequently used Tags
<form> </form>
The <form> tag is used to create an HTML form for user input.
To let the browser know where to send the content we add these properties to
the <form> tag:
<form ="form.jsp" method="get" or method=post >
.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
The address is the url of the cgi script the content should be sent to. The post and get
Methods are simply two different methods for submitting data to the script.
If a "GET" request is used, the form parameters are encoded in the URL in what is called
a query string.
Heres an example of the query string that would be generated if we were to use a "GET"
request:
www.someemailprovider.com/?login=joe@email.com&password=xxyz
A POST request, unlike a GET request, passes the form parameters in the body of the HTTP
request, not in the URL. This happens behind the scenes, in what can be thought of as an
HTTP dialogue between your web browser and a webserver.

<table> </table>
The HTML table element inserts a table in the document. Tables are a very
useful and powerful feature of the HTML language, as they give a solution
for inserting any type of tabulated data in the document.
This element is the main container of a table, but many other elements are needed to
define a table correctly. Other elements that constitute a table are:
Rows (HTML tr element)
Cells (HTML td element)
Header cells (HTML th element)
Caption or title (HTML caption element)
2.1.2 Java Script

Java Script is a script-based programming language that was developed by Netscape
Communication Corporation. Java Script was originally called Live Script and renamed
as Java Script to indicate its relationship with Java. Java Script supports the development
of both client and server components of Web-based applications.
On the client side, it can be used to write programs that are executed by a Web browser
within the context of a Web page. On the server side, it can be used to write Web server
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
programs that can process information submitted by a Web browser and then update the
browsers display accordingly.
Regular Expression
Regular expressions are patterns used to match character combinations in strings. In Java
Script, regular expressions are also objects. These patterns are used with the exec and test
methods of RegExp, and with the match, replace, search, and split methods of String.
Test(string)- Tests a string for pattern matches. This method returns a Boolean that
indicates whether or not the specified pattern exists within the searched string. This is the
most commonly used method for validation. It updates some of the properties of the
parent RegExp object following a successful search.
exec(string)- Executes a search for a pattern within a string. If the pattern is not found,
exec() returns a null value. If it finds one or more matches it returns an array of the match
results. It also updates some of the properties of the parent RegExp object.
2.1.3 Java Server Pages (JSP)

Java server Pages is a simple, yet powerful technology for creating and maintaining
dynamic-content web pages. Based on the Java programming language, Java Server
Pages offers proven portability, open standards, and a mature re-usable component
model .The Java Server Pages architecture enables the separation of content generation
from content presentation. This separation not eases maintenance headaches; it also
allows web team members to focus on their areas of expertise. Now, web page designer
can concentrate on layout, and web application designers on programming, with minimal
concern about impacting each others work.
Frequently Used Tags
<c:choose>, <c:when> and <c:otherwise>
These tags are used together like switch-case and default statements in java. <c:choose>
is the one which acts like switch, <c:when> like case which can be used multiple times
inside <c:choose> for evaluating different-2 condition
<c:otherwise> is similar to default statement which works when all the <c:when>
statements holds false.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
Syntax:
The basic structure looks like this <c:choose>
<c:when test="${condition1}">
//do something if condition1 is true
</c:when>
<c:when test="${condition n}">
//do something if condition n is true
</c:when>
<c:otherwise>
//Statements which gets executed when all <c:when> tests are false.
</c:otherwise>
</c:choose>
<sql:setDataSource> </sql:setDataSource>
This tag is used to create a variable which holds the connectivity to a database.
We can use the variable in the page to establish a database connection
Example
<sql:setDataSource var="snapshot" driver="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/TEST"
user="root" password="pass123"/>
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
3. System Analysis
Systems analysis is a problem solving technique that decomposes a system into its
component pieces for the purpose of the studying how well those component parts work
and interact to accomplish their purpose.
3.1 Scope Of The Project

Provides a way for easy access for the users to search for certain files and update them.
Also provides secure way of handling different set of users like Administrator, User each
having their own functionalities.
3.2 Software Requirement Specification (SRS)

A software requirements specification (SRS) is a description of a software system to be
developed, laying out functional and non-functional requirements, and may include a set
of use cases that describe interactions the users will have with the software.
3.2.1 Software Development Life Cycle (SDLC) Methodologies

This document play a vital role in the development of life cycle (SDLC) as it describes
the complete requirement of the system. It means for use by developers and will be the
basic during testing phase. Any changes made to the requirements in the future will have
to go through formal change approval process.
The waterfall model, a project is divided into a set of phases (or activities). Each phase is
distinct, that is, there are clear lines of separation between the phases, with very clear
demarcation of the functions of each of the phases.
A project starts with an initial phase, and upon completion of the phase, moves on to the
next phase. On the completion of the phase, the project moves to the subsequent phase
and so on. Thus the phases are strictly time sequenced.
The project goes through a phase of requirements gathering. At the end of requirements
gathering, a system requirement specification document is produced. This becomes the
Input to the design phase.
During the design phase, a detailed design is produced in the form of a system design
description.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
With the SDD as input, the project proceeds to the development or coding phase, where in
programmers develop the programs required to satisfy the design. Once the programmers
complete their coding tasks, they hand the product to the testing team, who test the
product before it is released.
If there is no problem in a given phase, then this method can work, going in one direction
(like a waterfall). But what would happen if there are problems after going to a particular
phase? For example, you go into the design phase and find that it is not possible to satisfy
the requirements, going by the current design approach being used.
What could be the possible causes and remedies? You may try an alternative design if
possible and see if that can satisfy the requirements.
If there are no alternative design approaches possible, then there must be feedback to the
requirements phase to correct the requirements
Let us take the example one step further. Suppose a design was created for a given set of
requirements and the project passed on to the programming/ development phase. At this
point of time, it was found that it was not possible to develop the programs because of
some limitations.
What would you do? One approach would be to try out alternative strategies in the
development phase so that the design could still be satisfied. Another possibility could be
that there are flaws in design that cause conflicts during development and hence the
design has to be revisited.
When the design phase is revisited like in the previous case it may happen that the
problem may have to be dressed in the requirements phase itself. So, a problem in one
phase could potentially be traced back to any of the previous phase.
Since each phase has an output, the latter can be validated against a set of criteria. To
increase the effectiveness, the completion criteria for each output can be published a
priori.
Department of CSE
MREC (Autonomous)
E-Campus Synopsis
Before a phase starts, the completion criteria for the previous phase can be checked and
this can act as a verification mechanism for the phase.
This can minimize the kind of delays we discussed in the example above. The main
strength of the waterfall model is its simplicity. The model is very useful when a project
can actually be divided into watertight compartments.
But very few software projects can be divided thus. The major drawback in the waterfall
model arises from the delay in feedback among the phases, and thus the ineffectiveness of
verification and validation activities.
An error in one phase is not detected till at least the next phase .When a given phase
detects an error, the communications is only to the immediately preceding phase. This
sequential nature of communication among the phases can introduce inordinate delays in
resolving the problem.
The reduced responsiveness that is inherent in the model and the fact that the segregation
of phases is unrealistic severely restricts the applicability of this model.
A waterfall model is characterized by three attributes:
1. The project is divided into separate distinct phases.
2. Each communicates to the next through pre-specified out puts.
3. When an error is detected, it is traced back to one previous phase at a time, until it gets
resolved at some earlier phase.
Hybrid Model Application
Every software developed is different and requires a suitable SDLC approach to be
followed based on the internal and external factors. Some situations where the use of
Waterfall model is most appropriate are:
Requirements are very well documented, clear and fixed
Product definition is stable
Technology is understood and is not dynamic
There are no ambiguous requirements
Ample resources with required expertise are available to support the product.
Department of CSE
MREC (Autonomous)
10
E-Campus Synopsis
The following diagram shows how a model acts like:
Figure 3.1: Hybrid Model
3.2.2 Software Requirements

Operating System
: Windows 7/XP or Linux/Solaris
User Interface
: HTML, CSS
Client-side Script
: JavaScript
Programming Language : Java

Web Applications
: JDBC, JSP
IDE/Workbench
: Eclipse
Database
: DB2
Server Deployment
: Apache Tomcat 7.0
3.2.3 Hardware Requirements

Processor
: Intel Core i5
Hard Disk
: 40 GB
RAM
: 2.00 GB
Department of CSE
MREC (Autonomous)
11
E-Campus Synopsis
3.3 Feasibility Study

Feasibility is defined as the practical extent to which a project can be performed
successfully. The objective of the feasibility study is to establish the reasons for
developing the software that is acceptable to users, adaptable to change and conformable
to established standards.
3.3.1 Economic Feasibility

Economic feasibility attempts to weigh the costs of developing and implementing a new
system, against the benefits that would accrue from having the new system in place.
The proposed system development is very easy and cost effective. By filtering the
candidates online we save the time and money for conducting interview and scrutinizing
those using present methodologies.
3.3.2 Operational Feasibility

Proposed project is beneficial only if it can be turned into information systems that will
meet the organizations operating requirements. Simply stated, this test of feasibility asks
if the system will work when it is developed and installed.
Are there major barriers to Implementation? Since the proposed system was to help
reduce the hardships encountered. In the existing manual system, the new system was
considered to be operational feasible.
3.3.3 Technical Feasibility

Technical feasibility is understanding the different technologies involved in the proposed
system. Before commencing to the project be very clear about what are the technologies
that are to be required for the development of the new system.
As the technical requirements of proposed system have been identified, the system is
technically feasible.
Department of CSE
MREC (Autonomous)
12
E-Campus Synopsis
4. System Design
System design is the process of defining the elements of a system such as the
architecture, modules and components, the different interfaces of those components and
the data that goes through that system. It is meant to satisfy specific needs and
requirements of a business or organization through the engineering of a coherent and
well-running system.
Systems design implies a systematic approach to the design of a system. It may take a
bottom-up or top-down approach, but either way the process is systematic wherein it takes
into account all related variables of the system that needs to be createdfrom the
architecture, to the required hardware and software, right down to the data and how it
travels and transforms throughout its travel through the system. Systems design then
overlaps with systems analysis, systems engineering and systems architecture.
4.1 Unified Modeling Language Diagrams

The unified modeling language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic
rules.
UML is specifically constructed through two different domains they are:
UML Analysis modeling, which focuses on the user model and structural model views of
the system.
UML design modeling, which focuses on the behavioral modeling, implementation
modeling and environmental model views.
The Unified Modeling Language (UML) is a language for specifying, visualizing
constructing, and documenting the artifacts of software systems, as well as for business
modeling and other non-software systems.
UML has become the de-facto standard for modeling object-oriented systems.UML is
extensible and method-independent.UML is not perfect, but it's good enough.
Department of CSE
MREC (Autonomous)
13
E-Campus Synopsis
4.1.1 System Use Case Diagrams

This is the use case diagram of the Customer where he can register into the website or
if he is already registered then he can directly enter into the website by clicking on
login button. After login to the website he can perform operations like Update profile ,
Report Problem , Check Previously Problems and check solutions in mail.
Figure4.1: Use Case Diagram of a User

This is the use case diagram of a Admin where he can be responsible for maintenance of
Database. The Admin can directly logon to his account provide solutions for the problems
reported by student and modify if necessary
Figure 4.2: Use Case Diagram of Admin
Department of CSE
MREC (Autonomous)
14
E-Campus Synopsis
4.1.2 Class Diagrams

This is the class diagram which gives complete idea of functioning of E-campus
Synopsis. The three main things are Registration, Login and report problem provide
solutions and modifications of details if required. The operations and variables of each
Registration, Login and user have been mentioned in the class diagram.
.
Figure 4.3: Class Diagram for E-Campus Synopsis
Department of CSE
MREC (Autonomous)
15
E-Campus Synopsis
4.1.3 Activity Diagrams
This is the activity diagram for operations user can perform. A valid login of a user takes
him to his homepage from where he can perform operations like add Update profile,
report problem , check previous problems and modify details. Invalid Login brings him
back to login page with message wrong user id or password.
Figure 4.4: Activity Diagram for User
Department of CSE
MREC (Autonomous)
16
E-Campus Synopsis
This is the activity diagram for operations a Admin can perform. A valid login of an
Administrator takes him to his homepage from where he maintains all the database regarding
students and perform operations like provide solutions , modify details and delete the
information of organization. Invalid Login brings him back to login page with message
wrong user id or password.
Figure 4.5: Activity Diagram for Admin
Department of CSE
MREC (Autonomous)
17
E-Campus Synopsis
4.1.4 Sequence Diagrams

This is the sequence diagram for process a user registers for an account. The Process of
user registering for an account has been explained in detail and at last submit the details.
.
Figure 4.6: Sequence Diagram for Customer Registration
Department of CSE
MREC (Autonomous)
18
E-Campus Synopsis
This is the sequence diagram for process a user logins into the system. The Process of
customer Logging into the system has been explained. The customer can be logged in
only with valid user id and password.
Figure 4.7: Sequence Diagram for Customer Login
Department of CSE
MREC (Autonomous)
19
E-Campus Synopsis
4.1.5 Component Diagram

Component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.
Figure 4.8: Component Diagram
Department of CSE
MREC (Autonomous)
20
E-Campus Synopsis
4.1.6 Deployment Diagram

A deployment diagram in the Unified Modeling Language models the physical
deployment of artifacts on nodes. To describe a web site, for example, a deployment
diagram would show what hardware components ("nodes") exist (e.g., a web server, an
application server, and a database server), what software components ("artifacts") run on
each node (e.g., web application, database), and how the different pieces are connected
(e.g. JDBC, ODBC).
Figure 4.9: Deployment Diagram
Department of CSE
MREC (Autonomous)
21
E-Campus Synopsis
4.2 Data Dictionary

A data dictionary is a collection of descriptions of the data objects or items in a data model
for the benefit of programmers and others who need to refer to them. A first step in
analyzing a system of objects with which users interact is to identify each object and its
relationship to other objects.
For most relational database management systems (RDBMS), the database management
system software needs the data dictionary to access the data within a database. For example,
the Oracle DB software has to read and write to an Oracle DB.
1) Student Login Table
Key
Primary
Name
Data Type
Length
Nullable
Email id
Varchar
20
No
Password
Varchar
20
No
Table 4.1: Student Login Table

2) Admin Login Table
Key
Primary
Name
Data Type
Length
Nullable
Userid
Varchar
20
No
Password
Varchar
20
No
Table 4.2: Admin Login Table
Department of CSE
MREC (Autonomous)
22
E-Campus Synopsis
3) Student Registration Table
Key
Primary
Name
Datatype
Length
Nullable
Uname
Varchar
50
No
Contact
Varchar
10
No
Emailid
Varchar
50
No
Address
Varchar
100
No
Password
Varchar
20
No
Table 4.3 Student Registration Table

4) Report Problem Table
Key
Name
Data type
Length
Nullable
Primary
Id
Integer
No
Primary
ReportProblem
Varchar
100
No
Emailid
Varchar
15
No
Solution
Varchar
100
No
Table4.4: Report Problem Table
Department of CSE
MREC (Autonomous)
23
E-Campus Synopsis
5. System Implementation
System implementation is the construction of the new system and the delivery of that
system into production. Implementation is the carrying out, execution, or practice of a
plan, a method, or any design, idea, model, specification, standard or policy for doing
something. As such, implementation is the action that must follow any preliminary
thinking in order for something to actually happen
5.1 Modules Description

The following user roles will primarily use the system
NIT Management / Administrator.
Students / users.
First Responders.
5.1.1 NIT Management / Administrator
An Information Technology professional.
Maintaining Database.
Giving access to the Users.
Provide solutions to the problems reported by students.
Updating
the information and sending alerts to the students and the first
responders.
5.1.2 Students / users
Logging in and using the system.
Report the problem.
Receiving alerts from the system.
These are the End Users.
5.1.3 First Responders
First responders are rescue teams like Police Dept., Fire Dept. Etc
These will Rescue the students and the rest from the Natural disasters or in any
emergency situations.
Department of CSE
MREC (Autonomous)
24
E-Campus Synopsis
5.2Sample Code
Registration Page
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
HTML
4.01
Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>signup</title>
<meta charset="utf-8">
<meta name = "format-detection" content = "telephone=no" />
<link rel="icon" href="images/favicon.ico">
<link rel="shortcut icon" href="images/favicon.ico" />
<link rel="stylesheet" href="booking/css/booking.css">
<link rel="stylesheet" href="css/camera.css">
<link rel="stylesheet" href="css/owl.carousel.css">
<link rel="stylesheet" href="css/style.css">
<script src="js/jquery.js"></script>
<script src="js/jquery-migrate-1.2.1.js"></script>
<script src="js/script.js"></script>
<script src="js/superfish.js"></script>
<script src="js/jquery.ui.totop.js"></script>
<script src="js/jquery.equalheights.js"></script>
<script src="js/jquery.mobilemenu.js"></script>
<script src="js/jquery.easing.1.3.js"></script>
<script src="js/owl.carousel.js"></script>
<script src="js/camera.js"></script>

<script src="js/jquery.mobile.customized.min.js"></script>

<script src="booking/js/booking.js"></script>
<script>
$(document).ready(function(){
jQuery('#camera_wrap').camera({
Department of CSE
MREC (Autonomous)
25
E-Campus Synopsis
loader: false,
pagination: false ,
minHeight: '444',
thumbnails: false,
height: '28.28125%',
caption: true,
navigation: true,
fx: 'mosaic'
});
$().UItoTop({ easingType: 'easeOutQuart' });
});
</script>


</head>
<body>
<div class="main">
<header>
<div class="menu_block ">
<div class="container_12">
<div class="grid_12">
<nav class="horizontal-nav full-width horizontalNav-notprocessed">
<ul class="sf-menu">
<li><a href="index.jsp">home</a></li>
Department of CSE
MREC (Autonomous)
26
E-Campus Synopsis
<li class="current"><a href="signup.jsp">sign up</a></li>
<li><a href="login.jsp">login</a></li>
<li><a href="services.jsp">Services</a></li>
<li><a href="contact.jsp">Contacts</a></li>
</ul>
</nav>
<div class="clear"></div>
</div>
</div>
</div>
</header>
<div class="slider_wrapper ">
<div id="camera_wrap" class="">
<div data-src="images/slide.jpg" ></div>
<div data-src="images/slide1.jpg" ></div>
<div data-src="images/slide2.jpg"></div>
</div>
</div>
<div class="banner">
<div class="maxheight">
<div class="banner_title">
<img src="images/icon1.png" alt="">
<div class="extra_wrapper">Fast&
<div class="color1">Safe</div>
</div>
</div>
Dorem
ipsum
dolor
sit
amet,
consectetur adipiscinger elit. In mollis erat mattis neque facilisis, sit ameter ultricies erat
rutrum. Cras facilisis, nulla vel viver auctor, leo magna sodales felis, quis malesuad
<a href="#" class="fa fa-share-square"></a>
</div>
</div>
Department of CSE
MREC (Autonomous)
27
E-Campus Synopsis
</div>
<div class="extra_wrapper">Best
<div class="color1">Prices</div>
</div>
</div>
Hem ipsum dolor sit amet, consectetur adipiscinger elit. In mollis erat
mattis neque facilisis, sit ameter ultricies erat rutrum. Cras facilisis, nulla vel viver auctor,
leo magna sodales felis, quis malesuader
</div>
</div>
</div>
<div class="extra_wrapper">Package
<div class="color1">Delivery</div>
</div>
</div>
Kurem
ipsum
dolor
sit
amet,
consectetur adipiscinger elit. In mollis erat mattis neque facilisis, sit ameter ultricies erat
rutrum. Cras facilisis, nulla vel viver auctor, leo magna sodales felis, quis malesuki
</div>
</div>
</div>
</div>
<div class="content"><div class="ic">More Website Templates @
TemplateMonster.com - April 07, 2014!</div>
Department of CSE
MREC (Autonomous)
28
E-Campus Synopsis
<center>
<h3>SIGN UP</h3>
<form action="RegisterServlet" method="post">
<label>email id </label><input type="email" name="mail"><br><br>
<label>password </label><input type="password" name="pass"><br><br>
<label>contact </label><input type="text" name="cont"><br><br>
<label>address </label><input type="text" name="addr"><br><br>
<label>uname </label><input type="text" name="uname"><br><br>
<input type="submit" value="submit">
<input type="reset">
</form>
</center>
</div>
</div>
</div>
</div>
<footer>
<div class="f_phone"><span>Call Us:</span> + 1800 559 6580</div>
<div class="socials">
<a href="#" class="fa fa-twitter"></a>
<a href="#" class="fa fa-facebook"></a>
<a href="#" class="fa fa-google-plus"></a>
</div>
<div class="copy">
</div>
</div>
</div>
</footer>
Department of CSE
MREC (Autonomous)
29
E-Campus Synopsis
<script>
$(function (){
$('#bookingForm').bookingForm({
ownerEmail: '#'
});
})
$(function() {
$('#bookingForm input, #bookingForm textarea').placeholder();
});
</script>
</body>
</html>
Reschedule Program
<%@ page import="java.sql.*" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
HTML
4.01
Transitional//EN"
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<%
try
{
String bookingid=request.getParameter("bid");
Class.forName("com.ibm.db2.jcc.DB2Driver");
Connection
con=DriverManager.getConnection("jdbc:db2://localhost:50000/major","marty","srisamar
t");
PreparedStatement ps=con.prepareStatement("select * from booking where bookingid=?
");
ps.setString(1,bookingid);
Department of CSE
MREC (Autonomous)
30
E-Campus Synopsis
ResultSet rs=ps.executeQuery();
%>
<body bgcolor="navyblue">
<%
while (rs.next()){
%>
<center>
<font color="red" size="6">${msg}</font><br>
<h2>RESCHEDULE</h2><hr color="red">
<form method="post" action="RescheduleServlet">
<label>Bookingid</label><input type="integer" name="bid" value="<%=rs.getString(1)
%>" readonly><br><br>
<label>Userid</label><input
type="text"
name="uid"
value="<%=rs.getString(2)
type="text"
name="cno"
%>"><br><br>
<label>Carno</label><input
%>"><br><br>
<label>Carbrand</label>
<select name="brand">
<option value="Default">select a brand</option>
<option
%>"disabled="disabled"><%=rs.getString(4)
%></option>
<option value="Honda">Honda</option>
<option value="Maruthi Suzuki">Maruthi Suzuki</option>
<option value="Hyundai">Hyundai</option>
<option value="Toyoto">Toyoto</option>
<option value="Skoda">Skoda</option>
<option value="Benz">Benz</option>
<option value="BMW">BMW</option>
<option value="Tata">Tata</option>
<option value="Renault">Renault</option>
<option value="Nissan">Nissan</option>
</select>
<label>Time</label><input
type="time"
name="tim"
%>"><br><br>
Department of CSE
MREC (Autonomous)
31
E-Campus Synopsis
<input type="submit" value="submit">
<input type="reset" value="reset">
</form>
<form action="Res.jsp">
<input type="submit" value="back">
</form>
</center>
<%
}
}
catch(Exception e)
{
e.printStackTrace();
}
%>
</body>
</html>
Cancel Program
<%@ page import="java.sql.*" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
HTML
4.01
Transitional//EN"
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<%
try
{
Class.forName("com.ibm.db2.jcc.DB2Driver");
Department of CSE
MREC (Autonomous)
32
E-Campus Synopsis
Connection
con=DriverManager.getConnection("jdbc:db2://localhost:50000/major","marty","srisamar
th");
PreparedStatement ps=con.prepareStatement("select * from booking");
ResultSet rs=ps.executeQuery();
%>
<body bgcolor="navyblue">
<%
while (rs.next()){
%>
<table>
<h2
align="left">&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&n
bsp
&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp
Booking
Id&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspUserId
&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspCarno
&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspCarbrand&nbsp
&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspTime</h2>
<form method="post" action="CancelServlet">
<tr>
<td><input
type="text"
name="bid"
size="20"
%>"
name="uid"
size="20"
%>"
name="cno"
size="20"
%>"
readonly></td>
<td><input
type="text"
readonly></td>
<td><input
type="text"
readonly></td>
<td><input type="text" name="brand" size="20" value="<%=rs.getString(4) %>"
readonly></td>
<td><input
type="text"
name="time"
size="20"
%>"
readonly></td>
Department of CSE
MREC (Autonomous)
33
E-Campus Synopsis
<td><a href="delete.jsp?bookingid=<%=rs.getString(1) %>">delete</a><br><br></td>
</tr>
</form>
</table>
<%
}}catch(Exception e)
{
e.printStackTrace();
}
%>
</body>
</html>
Department of CSE
MREC (Autonomous)
34
E-Campus Synopsis
6. System Testing
Software Testing is the process used to help identify the correctness, completeness,
security, and quality of developed computer software. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is intended to reveal qualityrelated information about the product with respect to the context in which it is intended to
operate. This includes, but is not limited to, the process of executing a program or
application with the intent of finding errors. Quality is not an absolute; it is value to some
person. With that in mind, testing can never completely establish the correctness of
arbitrary computer software; testing furnishes a criticism or comparison that compares the
state and behavior of the product against a specification. An important point is that
software testing should be distinguished from the separate discipline of Software Quality
Assurance (SQA), which encompasses all business process areas, not just testing.
6.1 Test Cases:

A test case is a set of conditions or variables under which a tester will determine whether a
system under test satisfies requirements or works correctly. The process of developing test
cases can also help find problems in the requirements or design of an application.
6.1.1 Guidelines for Test Cases:
1) GUI Test Cases:
Total no of features that need to be check Look & Feel Look for Default values if at all
any (date & Time, if at all any require) Look for spell check
Test case name
1.GUI test
2.GUI test
Test case
description
Check for all
the features in
the screen.
Check for the
alignment of
the objects as
per the
validations.
Expected
value
The screen
must contain
features.
The alignment
should be in
proper way.
Actual value
The result we
get on
checking.
The result we
get on
checking.
Result
True/False
True/False
Table 6.1: Example for GUI Test Cases
Department of CSE
MREC (Autonomous)
35
E-Campus Synopsis
2) Positive Test Cases:
The positive flow of the functionality must be considered Valid inputs must be used for
testing Must have the positive perception to verify whether the requirements are justified.
Test case name
1.Positive Case
Test case
description
Check for the
update
available.
Expected value
Actual value
The available
update in the
web site it must
be displayed.
The update are

displayed
Result
True.
Table 6.2: Positive Test Cases

3) Negative Test Cases:
Must have negative perception.

Invalid inputs must be used for test.
Test case name

1.Negative
Case
Test case
description
Try to modify
the information
inside web site
description.
Expected value
Modification
should not
be allowed.
Actual value
Modification is
allowed
Result
False.
Table 6.3: Negative Test Cases

4) Login Page Test Case:
Test case
name
1.Login
Test case
description
Leave the user
id empty and
click submit
button.
Enter user id &
password and
click submit
button.
Expected
value
Error Message
If user id and
password are
correct, then
redirect to
homepage
otherwise, an
error message
is displayed.
Actual value
An error
message User
Id Is emptycis
displayed.
Login
successful and
homepage is
displayed.
Result
True
True
Table 6.4: Login Page Test Cases
Department of CSE
MREC (Autonomous)
36
E-Campus Synopsis
4)
Registration Validation for Empty Field Page Test Cases:
Test Case
Name
1. Registration
(Empty fields
validation)
Department of CSE
Test Case
Description
To verify that
first name of
user on
registration
form is entered
or left empty.
To verify that
Last name of
user on
registration
form is entered
or left empty.
To verify that
Contact
number of user
on registration
form is entered
or left empty.
To verify that
Email id of
user on
registration
form is entered
or left empty.
To verify that
password of
user on
registration
form is entered
or left empty.
To verify that
confirm
password of
user on
registration
form is entered
or left empty.
To verify that
security
question of
user on
Expected
value
Actual value
Error message
if field is
empty
First name is
mandatory
message is
generated.
Error message
if field is
empty
Last name is
mandatory
message is
generated.
Error message
if field is
empty
Contact number
is
mandatorymessa
ge is generated.
Error message
if field is
empty
Email id is
mandatory
message is
generated.
Error message
if field is
empty
Password is
mandatory
message is
generated.
Error message
if field is
empty
Confirm
password is
mandatory
message is
generated.
Error message
if field is
empty
Security
question is
mandatory
message is
Result
True
True
True
True
True
True
True
MREC (Autonomous)
37
E-Campus Synopsis
registration
form is entered
or left empty.
To verify that
security
answer of user
on registration
form is entered
or left empty.
To verify that
captcha on
registration
form is entered
or left empty.
generated.
Error message
if field is
empty
Security answer
is mandatory
message is
generated.
Error message
if field is
empty
Captcha field is
mandatory
message is
generated.
True
True
Table 6.5: Registration Validation for Empty Field Page Test Cases
6) Registration Page Validation for Valid Data Test Cases:
Test Case
Name
Registration
(Data
Validation)
Test Case
Description
To verify that
mobile number
is valid or not.
To verify
password
To verify
emailid
To verify name
fields.
Expected
values
Error message
if mobile
number entered
is not equal to
10 digits.
Error message
if password and
confirm
password are
indifferent.
Error message
if email id is
not in proper
format.
Error message
if name fields
are in improper
format.
Actual values
Invalid phone
number
message is
generated.
Passwords
didnt match
message is
generated.
Invalid
emailid
message is
generated.
Name should
be alphabetical
only message
is generated.
Result
True
True
True
True
Table 6.6: Registration Page Validation for Valid Data Test Cases
Department of CSE
MREC (Autonomous)
38
E-Campus Synopsis
6)
Registration Page Validation for Valid Data Test Cases:

Test Case
Test Case Description
Test Steps
Expected
Name
Registration
(Validation Of
Result
Actual
To verify that Fname
Error Message if
An error message
valid or not
Fname entered
Fname must be
contains otherthan
alphabet character
To verify that Lname
Alphabets.
Error Message if
only
An error message
valid or not
Lname entered
Fname must be
contains otherthan
alphabet character
To verify that Contact
Alphabets.
Error Message if
only
An error message
valid or not
Contact entered is
Contact must be
otherthan numeric
numeric only and True
Data)
True
True
and length not equal length should be

to 10
10
Table 6.6: Registration Page Validation for Valid Data Test Cases
Department of CSE
MREC (Autonomous)
39
E-Campus Synopsis
7. Output Screens
This is the home page of our application where the user can login to his existing account or
register into new account.
Figure 7.1: Home Page
By clicking on SIGN UP on homepage we can navigate to the page where we can find the list
of details.
Department of CSE
MREC (Autonomous)
40
E-Campus Synopsis
Figure 7.2: Register page
Department of CSE
MREC (Autonomous)
41
E-Campus Synopsis
By clicking on LOGIN on homepage we can navigate to the page to login into the system.
Figure 7.3: User Login
Department of CSE
MREC (Autonomous)
42
E-Campus Synopsis
By clicking on Log in tab we can navigate to the page where we can view the user profile for
updating and uploading files.
Figure 7.4: User Profile
Department of CSE
MREC (Autonomous)
43
E-Campus Synopsis
By clicking on Update Profile tab we can navigate to the page where the user details will be
displayed and then he can update the required fields.
.
Figure 7.5: Update Profile List
Department of CSE
MREC (Autonomous)
44
E-Campus Synopsis
By clicking on Forgot Password in Login tab we can navigate to the page where The security
question, security answer and email id will also given in forgot password.
.
Figure 7.6: Forgot Password
Department of CSE
MREC (Autonomous)
45
E-Campus Synopsis
By clicking on upload in upload photo tab we can navigate to the page where browse the
photo and upload the file.
Figure 7.7: Upload Photos
Department of CSE
MREC (Autonomous)
46
E-Campus Synopsis
By clicking on upload files the will be appeared as follows:
Figure 7.10: Photos Display
Department of CSE
MREC (Autonomous)
47
E-Campus Synopsis
By clicking on LOGIN on homepage we can navigate to the page to login into the system. Here
we choose to logout from the list and redirect to home page.
Figure 7.11: Logout
Department of CSE
MREC (Autonomous)
48
E-Campus Synopsis
8. Conclusion and Future Enhancements

The Generic Uploader Frame Work is a web-based application to reduce the efforts of
an user in the process. This application software has been computed successfully and was
also tested successfully by taking test cases. It is user friendly, and has required options,
which can be utilized by the user to perform the desired operations.
The software is developed using Java as front end and Oracle as back end in Windows
environment. The goals that are achieved by the software are:
Instant access.
Improved productivity.
Optimum utilization of resources.
Efficient management of records.
Simplification of the operations.
Less processing time and getting required information.

User friendly.
8.1 Limitations Of The System

Who will login into the website that person can only enter into the website.
This website provides security.
8.2 Future Enhancements

It is not possible to develop a system that makes all uploads of the user. User can upload
and update keep changing as the system is being used. Some of the future enhancements
that can be done to this system are:
As the technology emerges, it is possible to upgrade the system and can be adaptable to
desired environment.
Because it is based on object-oriented design, any further changes can be easily adaptable.
Based on the future security issues, security can be improved using emerging
technologies.
Department of CSE
MREC (Autonomous)
9. Bibliography
Books:
[1] Gary Cornell: Core Java, Volume II--Advanced Features, Pearson Education Sun
th
Microsystems, 9 Edition, Published in 2013.

[2] George Reese: Database Programming with JDBC and Java, O'Reilly Media, 2
Edition, Published in 2010.
nd
[3] Grady Booch, James Rumbaugh, Ivar Jacobson: The Unified Modeling Language
nd
User Guide, Pearson Education 2
[4] Roger S Pressman: Software engineering (A practitioners approach), McGrawth
Hill Education 6 Edition, Published in 2012.

[5] Joshua Bloch: Effective Java Programming Language Guide, Addison-Wesley
nd
Professional 2
Websites:
[1]
http://www.w3schools.com/
[2]
http://www.cafevida.net/
[3] http://stackoverflow.com/
[4] http://en.wikipedia.org/wiki/Main_Page

E Campus

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E Campus

Uploaded by

Copyright:

Available Formats

1

1.1 Existing System and its Limitations

No Prior Information about the Natural Disasters.

High Risk compared to the New system ( E- Campus)

Fastest way to communicate with students and the first responders.

Prior information regarding Natural Disasters and the Emergency situations.

Giving access to the users with User ID and Password to authenticate.

Using multiple alert types. (Ex : Mild, Moderate and severe)

Provide solutions to the problems reported by the user.

1.2.1 Advantages over Existing System

2.1 Technologies Used

2.1.1 Hypertext Markup Language (HTML)

HTTP dialogue between your web browser and a webserver.

2.1.2 Java Script

2.1.3 Java Server Pages (JSP)

3.1 Scope Of The Project

3.2 Software Requirement Specification (SRS)

3.2.1 Software Development Life Cycle (SDLC) Methodologies

Requirements are very well documented, clear and fixed

Product definition is stable

Technology is understood and is not dynamic

There are no ambiguous requirements

Figure 3.1: Hybrid Model

3.2.2 Software Requirements

: Windows 7/XP or Linux/Solaris

Programming Language : Java

: Apache Tomcat 7.0

3.2.3 Hardware Requirements

3.3 Feasibility Study

3.3.1 Economic Feasibility

3.3.2 Operational Feasibility

3.3.3 Technical Feasibility

4.1 Unified Modeling Language Diagrams

4.1.1 System Use Case Diagrams

Figure4.1: Use Case Diagram of a User

Figure 4.2: Use Case Diagram of Admin

4.1.2 Class Diagrams

Figure 4.4: Activity Diagram for User

Figure 4.5: Activity Diagram for Admin

4.1.4 Sequence Diagrams

Figure 4.7: Sequence Diagram for Customer Login

4.1.5 Component Diagram

Figure 4.8: Component Diagram

4.1.6 Deployment Diagram

Figure 4.9: Deployment Diagram

4.2 Data Dictionary

Table 4.1: Student Login Table

Table 4.2: Admin Login Table

Table 4.3 Student Registration Table

Table4.4: Report Problem Table

5.1 Modules Description

NIT Management / Administrator.

5.1.1 NIT Management / Administrator

An Information Technology professional.

Giving access to the Users.

Provide solutions to the problems reported by students.

5.1.2 Students / users

Logging in and using the system.

Report the problem.

Receiving alerts from the system.

These are the End Users.

5.1.3 First Responders