Download - Project Documentation OHD
-
8/7/2019 Project Documentation OHD
1/80
1.1ABOUT ORGANIZATION
Organization Profile:
3Edge Solutions is an IT-industry sponsored initiative promoted byprofessionals from the IT domain with a combined experience of over 125+ years. The
company specializes in corporate training in technology, industry methodologies and
practices, business communication and soft skills. Over the years, 3Edge has built
strong tie-ups with reputed organizations such as Scope International, Cognizant
Technology Solutions, Serving Global Solutions and Oracle.
With the knowledge bank of experienced professionals in IT consulting,
3Edge Solutions have developed and continue to work on many domestic and global
Software Development projects. In the past, 3Edge Solutions has developed web based
application like online Trading portals, electronic Shareholders Forum and a Workflow
accounting portal for an accounting firm. Some of the ongoing projects include online
pharmacy and Web based clinical trials for US based client. 3Edge is also involved in
developing pedagogical tools such as e-Learning, course-ware and question banks for
various corporate. 3Edge Solutions has developed industry based curriculum for an
Engineering University based in Washington, USA.
3Edge Solutions has been recognized as a Knowledge Partner to Govt. of
Andhra Pradesh for enhancing employ-ability in IT and ITES sectors in the state.
3Edge is also assisting ICT Academy of Tamil Nadu (ICTACT) to train faculty in all
Engineering Colleges of Tamil Nadu in industry-oriented curriculum.
1
-
8/7/2019 Project Documentation OHD
2/80
1.2Existing System:
Since the facility head is the chief controlling authority in the department, a
schedule is to be prepared for him and to be maintained permanently.
The data is maintained manually where there is a possibility for loss of data.
It is a very tedious process
1.3 Proposed System:
This system is proposed for the work to be done in sophisticated
manner instead of investing their valuable time.
Using this system the Admin can maintain up to date information
without taking the risk of maintaining in manually.
This System will help the facility heads to perform their duties
effectively
2
-
8/7/2019 Project Documentation OHD
3/80
2. REQUIREMENT
2.1 Hard ware Specification:
Processor : Intel Pentium 4
RAM : 512 MB RAM
Hard Disk : 80 GB
Monitor : Standard color monitor
2.2 Software Requirements
Language : JAVA
Database System : MY-SQL
Operating System : Windows XP & latest Versions
2.3 Software Description
J2SE development kit overview:
There are two principal products in the Java SE platform family: Java SE Runtime
Environment (JRE) and Java Development Kit (JDK).
Java Runtime Environment (JRE)
The Java Runtime Environment (JRE) provides the libraries, the Java Virtual
Machine, and other components to run applets and applications written in the Java
programming language. In addition, two key deployment technologies are part of
the JRE: Java Plug-in, which enables applets to run in popular browsers; and Java
Web Start, which deploys standalone applications over a network. It is also the
foundation for the technologies in the Java 2 Platform, Enterprise Edition (J2EE)
for enterprise software development and deployment. The JRE does not contain
3
-
8/7/2019 Project Documentation OHD
4/80
tools and utilities such as compilers or debuggers for developing applets and
applications.
Java Development Kit (JDK)
The JDK is a superset of the JRE, and contains everything that is in the JRE, plus
tools such as the compilers and debuggers necessity.
Java Server Pages (JSP):
Java Server Pages (JSP) technology provides a simplified, fast way to create web
pages that display dynamically-generated content. The JSP specification, developed
through an industry-wide initiative led by Sun Microsystems, defines the interaction
between the server and the JSP page, and describes the format and syntax of the page.
JSPs have dynamic scripting capability that works in tandem with HTML code,
separating the page logic from the static elements -- the actual design and display of
the page -- to help make the HTML more functional(i.e. dynamic database queries).
Java Server Pages (JSP) technology enables us to rapidly develop and easily maintain,
information-rich, dynamic Web pages that leverage existing business systems. As part
of the Java technology family, JSP technology enables rapid development of Web-
based applications that are platform independent. JSP technology separates the user
interface from content generation, enabling designers to change the overall page
layout without altering the underlying dynamic content.
Benefits for Developers:
With a familiar background with HTML, we can:
Use JSP technology without having to learn the Java language: You can use
JSP technology without learning how to write Java scriptlets. Although scriptlets are
no longer required to generate dynamic content, they are still supported to provide
backward compatibility.
Extend the JSP language: Java tag library developers and designers can extend
the JSP language with "simple tag handlers," which utilize a new, much simpler and
cleaner, tag extension API. This spurs the growing number of pluggable, reusable tag
libraries available, which in turn reduces the amount of code needed to write powerful
Web applications.
4
-
8/7/2019 Project Documentation OHD
5/80
Easily write and maintain pages: The Java Server Pages Standard Tag Library
(JSTL) expression language is now integrated into JSP technology and has been
upgraded to support functions. The expression language can now be used instead of
scriptlet expressions.
Key Capabilities:
High Availability: Ensure business continuity with the highest levels of system
availability through technologies that protect your data against costly human errors
and minimize disaster recovery downtime.
Performance and Scalability: Deliver an infrastructure that can grow with your
business and has a proven record in handling today's large amounts of data and most
critical enterprise workloads.
Security: Provide a secure environment to address privacy and compliance
requirements with built-in features that protect your data against unauthorized access.
Manageability: Manage your infrastructure with automated diagnostics, tuning, and
configuration to reduce operational costs while reducing maintenance and easily
managing very large amounts of data.
Developer Productivity: Build and deploy critical business-ready applications more
quickly by improving developer productivity and reducing project life cycle times.
Tomcat server:
Apache Tomcat (formerly under the Apache Jakarta Project; Tomcat is now a top
level project) is a web container developed at the Apache Software Foundation.
Tomcat implements the servlet and the Java Server Pages (JSP) specifications from
Sun Microsystems, providing an environment for Java code to run in cooperation with
a web server. It adds tools for configuration and management but can also be
configured by editing configuration files that are normally XML-formatted. Because
Tomcat includes its own HTTP server internally, it is also considered a standalone
web server.
Environment:
Tomcat is a web server that supports servlets and JSPs. Tomcat comes with the Jasper
compiler that compiles JSPs into servlets.
5
-
8/7/2019 Project Documentation OHD
6/80
The Tomcat servlet engine is often used in combination with an Apache web server
or other web servers. Tomcat can also function as an independent web server. Earlier
in its development, the perception existed that standalone Tomcat was only suitable
for development environments and other environments with minimal requirements for
speed and transaction handling. However, that perception no longer exists; Tomcat is
increasingly used as a standalone web server in high-traffic, high-availability
environments.
Since its developers wrote Tomcat in Java, it runs on any operating system that has a
JVM.
Features:
Tomcat 5.x (later versions)
Implements the Servlet 2.4 and JSP 2.0 specifications
Reduced garbage collection, improved performance and scalability
Native Windows and UNIX wrappers for platform integration Faster JSP
parsing
6
-
8/7/2019 Project Documentation OHD
7/80
Online Help Desk (OHD) for the facilities in the campus. This is an Intranet based
application that can be accessed throughout the campus. This system can be used to
automate the workflow of service requests for the various facilities in the campus.
The list of modules incorporated with ONLINE HELP DESK FOR THE
FACILITIES IN THE CAMPUS is
1. 1. Administrator Module: The administrator will first creates the members of
organization. The administrator will check the quires and then update the status
and assigns the query to their respective facility to solve it.
In this module Administrator will
Creating user accounts:
The administrator will create the users of the organization which includes employees
and students. Each member in the organization were given username and password for
the login into their account. The username will be their email-id.
Updating the status posted by employee:
The administrator will update the status of the query by giving the description of it
whether he is approving or rejecting the query with appropriate description
Assigning the task:
The administrator In this the administrator will assign task to the employee(facility
members) with the specific description what action he has to be performed.
Viewing the profiles of the students and employees:
The administrator will view all the details of the students and employees who are the
members of the organization.
Authentication:
The administrator will provide a good authentication to the members of the
organization by providing the username and password to them and they are provided
with facility of changing their details like password, name etc this will provide a good
authentication to the members.
Maintenance of data base:
The administrator will maintain the database so that there will be no problems while
the members of the organization are performing the quires.
7
-
8/7/2019 Project Documentation OHD
8/80
2. End-User Module: The End-User module contains the members of
organization like employees and students.
In this module parent will
Login:
The End-User is given a username and password by the administrator. The username
used is the Email-id and password is given by the administrator and later the users can
change the password and username if required.
Create new request:
In this the Students and the employees will post the request regarding their queries by
selecting the corresponding facility type and writing the description about the query.
View the status:
In this the Students and the employees will view the status that is updated by the
Administrator and they can know whether the admin has approved the request or
rejected the request.
Access books and softwares:
The In this will Students and the employees can have a special access to the eBook
library and softwares so that they can download and view the corresponding books
and softwares.
3. Facility module: The facility module will contain the employees who are
assigned with the corresponding facility types.
Login to system:
The facility members are just like the employees they are also registered by the
administrator and can login with the username and password given to them.
View and perform task assigned by administrator:
According to the queries of the students and employees the admin will approve or
reject them .If he had approved then he has the action has to be performed so, the
admin will assign the required task to the facility members and when the facility
members will login to their account they can view the task assigned by the
administrator and they perform them accordingly.
Update the status of student: The student will post the request to
the facility the status is updated by the corresponding employee or the facility.
8
-
8/7/2019 Project Documentation OHD
9/80
Unified Modeling Language (UML)
It is a language to specifying, visualizing and constructing the artifacts of software
system as well as for business models. GRADY BOOCH, IVAR JACCOBSON and
JAMES RUMBUGH found it. The UML notation is useful for graphically depicting
Object Oriented Analysis and Object Oriented Design (OOA and OOD) modules.
The unified modeling language is a standard language for specifying,
Visualizing, Constructing and documenting the software system and its components. It
is a graphical language that provides a vocabulary and set of semantics and rules. The
UML focuses on the conceptual and physical representation of the system. It captures
the decisions and understandings about systems that must be constructed. It is used to
understand, design, configure, maintain and control information about the systems.
Visualizing:
Through UML we see or visualize an existing system and ultimately
we visualize how the system is going to be after implementation. Unless we think
we cannot implement. UML helps to visualize how the components of the system
communicate and interact with each other.
Specifying:
Specifying means building models that are precise, unambiguous and
complete UML addresses the specification of all the important Analysis Design,
Implementation decisions that must be made in developing and deploying a software
system.
Constructing:
UML models can be directly connected to a variety of programming
language through mapping a model from UML to a programming language like Java or
C++ or VB.
Forward Engineering and Reverse Engineering is possible through UML.
Documenting:
The deliverables of a project apart from coding are some artifacts
which are critical in controlling, measuring and communicating about a system during
its development viz. Requirements, Architecture, Design, Source code, Project plans,
Tests, Prototypes, Releases etc.
9
-
8/7/2019 Project Documentation OHD
10/80
DIAGRAMS IN UML:
Diagrams are graphical presentation of set of elements. Diagrams project a
system, or
visualize a system from different angles and perspectives. The UML has nine
diagrams these
diagrams can be classified into the following groups:
1) Static or structural diagrams
2) Dynamic or behavioral diagrams
1) STATIC OR STRUCTURAL DIAGRAMS:
Class Diagram: This shows a set of classes, interfaces, collaborations and their
relationships. There are the most common diagrams in modeling the object oriented
systems and are used to give the static view of a system.
2) DYNAMIC OR BEHAVIORAL DIAGRAMS:
Use case Diagram: Shows a set of use cases and actors and their relationships. These
diagrams illustrate the static use case view of a system and are important in organizing
and modeling the behaviors of a system.
Sequence Diagram: Sequence diagram is an interaction diagram which focuses on the
time ordering of messages it shows a set of objects and messages exchange between
these objects. This diagram illustrates the dynamic view of a system.
Collaboration Diagram: This diagram is an interaction diagram that stresses or
emphasizes the structural organization of the objects that send and receive messages. It
shows a set of objects, links between objects and messages send and received by those
objects. There are used to illustrate the dynamic vies of a system.
10
-
8/7/2019 Project Documentation OHD
11/80
4.1 Use case diagram
c r e a te u s e r s
v ie w r e q u e s t s
u p d a t e s ta t u s o f r e q u e s t o f e m p l o y e e
a s i g n t a s k t o f a c i l i ty
v ie w a l l p r o f i l e s
A d m i n
l o g i n
p o s t n e w r e q u e s t
v ie w s t a t u s o f re q u e s t
v i e w t h e t a s k s a s s i g n e d b y a d m i n
u p d a t e t h e s ta t u s o f s tu d e n tE m p l o y e e s
s t u d e n t s
a c c e s b o o k s a n d s o f t w a r e s
11
-
8/7/2019 Project Documentation OHD
12/80
4.2 Class Diagram
Administrator
user nam e : varchar
pass word : varchar
updates status()
assign tasks()
view profiles ()
request
request id : int
faculty type : varchar
description
status : varchar
post request()
upation of status of request()
Employees
employee id : int
name : varchar
address : varchar
emai l : varchar
password : :varchar
gender : varchar
role : varchar
post request()
view s tatus()
access boks and s/ws()
view tasks assigned by admin()
facilitates
posts
students
student id : int
name : varchar
address : varchar
dob : int
gender : varchar
emai l : varchar
pass word : varchar
post request()
view s tatus()
access books and s/ws()posts
facilitates
12
-
8/7/2019 Project Documentation OHD
13/80
4.3 Sequence Diagram of student:
login page ohd:system home
page:student
enter username and pass word
validation
display student page
post new request
view s tatus
logout
display ohd home page
access books and softwares
13
-
8/7/2019 Project Documentation OHD
14/80
4.4 Collaboration Diagram of student:
login
page
ohd:syst
em
home
page:student
2: validation
1: enter username and password
8: display ohd home page
3: display student page
4: post new request5: view s tatus
7: logout6: access books and softwares
14
-
8/7/2019 Project Documentation OHD
15/80
4.3.1 Sequence Diagram of Employee:
u p d a te s ta t u s fo r s t u d e n t r e q u e s t
l o g i n p a g e o h d :s ys te m h o m e
p a g e :E m p l o ye e
e n te r u s e r n a m e a n d p a s s w o r d
v a l i d a t i o n
d i s p l a y o h d h o m e p a g e
d i s p l a y E m p l o ye e p a g e
p o s t n e w re q u e s t
v i e w s t a tu s
l o g o u t
a c c e s s b o o k s a n d s o ftw a r e s
v ie w t a s k s a s s i g n e d b y a d m in
15
-
8/7/2019 Project Documentation OHD
16/80
4.4.1 Collaboration Diagram of employee:
login
page
ohd:syst
em
home
page:Employee
2: validation1: enter username and password
10: display ohd home page
3: display Employee page
5: post new request6: view status
9: logout
7: access books and softwares8: view tasks ass igned by admin
4: update status for student request
16
-
8/7/2019 Project Documentation OHD
17/80
4.3.2 Sequence Diagram of Administrator:
login page ohd:system home
page:admin
enter username and password
validates
display admin page
view requests
update status
ass ign task to facility
view all profiles
logout
display ohd home page
create users
17
-
8/7/2019 Project Documentation OHD
18/80
4.4.2 Collaboration Diagram of administrator:
login
page
ohd:syst
em
home
page:admin
2: validates
1: enter username and password
10: display ohd home page
3: display admin page
5: view requests6: update status
7: assign task to facility8: view all profiles
9: logout
4: create users
18
-
8/7/2019 Project Documentation OHD
19/80
4.5 State chart diagram for administrator:
start
logins
register new users
validation
view new requests
update the status of requests
assign task to facility
logout
19
-
8/7/2019 Project Documentation OHD
20/80
4.5.1 State chart diagram for student:
stop
start
login
access s/ws and books
post new request
view s tatus of requests
logout
20
-
8/7/2019 Project Documentation OHD
21/80
4.5.2 State chart diagram for Employee:
start
login
update status
access softwares and books
view status
logout
post new request
view reques t post by student
validation
stop
21
-
8/7/2019 Project Documentation OHD
22/80
5.6 E-R Diagram
22
-
8/7/2019 Project Documentation OHD
23/80
4.7 Data Dictionary
Employee Table:
Table No: 1
Table Name Employee
Table description This table contains the employee details.
Attribute name Data types constraints Sample values
Employee id Int Primary key 1
Name varchar(50) Not-null siddartha
Address varchar(50) Not-null balasamudram
Email varchar(50) Not-null [email protected]
Password Varchar(50) Not-null siddu
Gender varchar(50) Not-null maleRole id int Not-null 1
contact varchar(50) Not-null 9491821187
Employee Request Table:
Table No: 2
Table Name Employee request
Table description This table contains the details of employee requests.
Attribute name Data types constraints Sample valuesEmployee req id Int Primary key 1
Employee id int Forigen key 1
Faculty type id int Not-null 1
description varchar(50) Not-null xyz
Request status id int Forigen key 1
Facility Table:
Table No: 3Table Name Facility
Table description This tables contains the facility details
Attribute name Data types constraints Sample values
Facility id Int Primary key 1
Facility type id Int Foreign key 1
Incharge id Int Foreign key 1
description varchar(50) Not-null xyz
23
-
8/7/2019 Project Documentation OHD
24/80
Facility Type Table:
Table No: 4Table Name Facility type
Table description This table contains various facilities present in college.
Attribute name Data types constraints Sample values
Facility type id Int Primary key 1
name varchar(50) Not-null venkatesh
description varchar(50) Foreign key abcd
Request Status Table:
Table No: 5
Table Name Request status
Table description This table contains details of request.
Attribute name Data types constraints Sample values
request status id Int Primary key 1
name varchar(50) Not-null Siddartha.k
description varchar(50) Not-null bbhggt
Role Table:
Table No: 6
Table Name role
Table description This table contains the roles of various employees
Attribute name Data types constraints Sample values
Role id Int Primary key 1
name varchar(50) Not-null Siddartha.k
Description varchar(50) Not-null Maintain labs
24
-
8/7/2019 Project Documentation OHD
25/80
Student Table:
Table No: 7
Table Name student
Table description This table contains the details of student.
Attribute name Data types constraints Sample valuesStudent id Int Primary key 1
name varchar(50) Not-null Siddartha.k
DOB varchar(50) Not-null 1/2/1990
DOJ varchar(50) Not-null 2/5/2007
email Varchar(50) Not-null [email protected]
password varchar(50) Not-null sid
address varchar(50) Not-null hnk
gender varchar(50) Not-null male
Student Request Table:
Table No: 8
Table Name Student request
Table description This table contains the requests posted by student
Attribute name Data types constraints Sample values
Srudent request id Int Primary key 1
Student id Int Foreign key 1
Facility type id varchar(50) Foreign key 1
description varchar(50) Not-null I need exam timetable
Request status id Int Foreign key 1
25
-
8/7/2019 Project Documentation OHD
26/80
Connection.java:
package com.connection;
import java.sql.*;
public class Crp_system {
public static Connection get_con() {
Connection c = null;
try {
Class.forName("com.mysql.jdbc.Driver");
c = DriverManager.getConnection("jdbc:mysql://localhost:3306/olhd", "root",
"root");
} catch (Exception e) {
System.out.println(e);
}
return c;
}
}
26
-
8/7/2019 Project Documentation OHD
27/80
Registration.java
In the registration page ,the administrator will register the students and employees .He
will enter all the details of the students and employees they are stored into the
database.
EMPLOYEE REGISTRATION:
package com.registeration;
import com.connection.Crp_system;
import java.io.IOException;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
*
* @author Rajesh
*/
public class Employee_registration extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
Connection conn = Crp_system.get_con();try {
String str = "insert into
employee(name,address,email,password,gender,role_id,contact) values(?,?,?,?,?,?,?)";
PreparedStatement ps = conn.prepareStatement(str);
ps.setString(1, request.getParameter("name"));
ps.setString(2, request.getParameter("address"));
ps.setString(3, request.getParameter("email"));
ps.setString(4, request.getParameter("password"));
ps.setString(5, request.getParameter("gender"));ps.setString(6, request.getParameter("role_id"));
27
-
8/7/2019 Project Documentation OHD
28/80
ps.setString(7, request.getParameter("contact"));
ps.executeUpdate();
conn.close();
response.sendRedirect("success.jsp");
} catch (SQLException e) {e.printStackTrace();
}
}
}
STUDENT REGISTRATION:
package com.registeration;
import com.connection.Crp_system;
import java.io.IOException;
import java.sql.Connection;import java.sql.PreparedStatement;
import java.sql.SQLException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
** @author Rajesh
*/
public class Student_registration extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
Connection conn = Crp_system.get_con();
try {
String str = "insert into student(name,dob,doj,email,password,address,gender)
values(?,?,?,?,?,?,?)";
PreparedStatement ps = conn.prepareStatement(str);ps.setString(1, request.getParameter("name"));
28
-
8/7/2019 Project Documentation OHD
29/80
ps.setString(2, request.getParameter("dob"));
ps.setString(3, request.getParameter("doj"));
ps.setString(4, request.getParameter("email"));
ps.setString(5, request.getParameter("password"));
ps.setString(6, request.getParameter("address"));
ps.setString(7, request.getParameter("gender"));ps.executeUpdate();
conn.close();
response.sendRedirect("success.jsp");
} catch (SQLException e) {
e.printStackTrace();
}
}
}
29
-
8/7/2019 Project Documentation OHD
30/80
Postquery.java:
package com.registeration;
import com.connection.Crp_system;
import java.io.IOException;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
*
* @author Rajesh
*/
public class Student_registration extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.
* @param request servlet request* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
Connection conn = Crp_system.get_con();
try {
String str = "insert into student(name,dob,doj,email,password,address,gender)
values(?,?,?,?,?,?,?)";
PreparedStatement ps = conn.prepareStatement(str);
ps.setString(1, request.getParameter("name"));
ps.setString(2, request.getParameter("dob"));
ps.setString(3, request.getParameter("doj"));
ps.setString(4, request.getParameter("email"));
ps.setString(5, request.getParameter("password"));
ps.setString(6, request.getParameter("address"));
ps.setString(7, request.getParameter("gender"));
ps.executeUpdate();
conn.close();
30
-
8/7/2019 Project Documentation OHD
31/80
response.sendRedirect("success.jsp");
} catch (SQLException e) {
e.printStackTrace();
}
}
}
31
-
8/7/2019 Project Documentation OHD
32/80
Replyquery.java:package com.replyquery;
import com.Viewstatus.PostStatusbean;
import com.connection.Crp_system;
import com.mysql.jdbc.Connection;import com.mysql.jdbc.Statement;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.ResultSet;
import java.util.ArrayList;
import javax.print.DocFlavor.STRING;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
/**
*
* @author admin
*/
public class ReplyQuery extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
Statement st;ArrayList statuspost = new ArrayList();
HttpSession session = request.getSession();
try {
Connection conn = (Connection) Crp_system.get_con();
String query = "select
sr.student_request_id,s.name,sr.description,ft.name,r.name,sr.request_status_id,"
+ "sr.student_id,f.incharge_id,r.name from student_request sr,"
+ "facility f,facility_type ft,requeststatus r,student s where "
+ "sr.facility_type_id=f.facility_type_id and "
+ "ft.facility_type_id=f.facility_type_id and "
+ "sr.request_status_id=r.requeststatus_ID and "+ "s.studentid=sr.student_id and "
32
-
8/7/2019 Project Documentation OHD
33/80
+ "r.requeststatus_ID=1 and "
+ "f.incharge_id='" + (String) session.getAttribute("posterid") + "'";
st = (Statement) conn.createStatement();
ResultSet rs = st.executeQuery(query);
while (rs.next()) {
PostStatusbean fac = new PostStatusbean();// fac
fac.setStudent_request_id(rs.getInt(1));
fac.setStudentname(rs.getString(2));
fac.setDescription(rs.getString(3));
fac.setFaclity_type(rs.getString(4));
fac.setStatus(rs.getString(5));
statuspost.add(fac);
}
session.setAttribute("statuspost", statuspost);
response.sendRedirect("query.jsp");
conn.close();
st.close();
rs.close();
} catch (Exception e) {
e.printStackTrace();
} finally {
out.close();
}
}
//
/**
* Handles the HTTP GET method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
/**
* Handles the HTTP POST method.
* @param request servlet request* @param response servlet response
33
-
8/7/2019 Project Documentation OHD
34/80
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {processRequest(request, response);
}
/**
* Returns a short description of the servlet.
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// }
34
-
8/7/2019 Project Documentation OHD
35/80
Taskassign.java:package com.facility;
import com.connection.Crp_system;
import java.io.IOException;import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
*
* @author Rajesh
*/
public class Taskassign extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs* @throws IOException if an I/O error occurs
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
Connection conn = Crp_system.get_con();
try {
String str = "insert into facility(facility_type_id,incharge_id,description)
values(?,?,?)";
PreparedStatement ps = conn.prepareStatement(str);
ps.setString(1, request.getParameter("facility_type_id"));
ps.setString(2, request.getParameter("employee_id"));ps.setString(3, request.getParameter("description"));
ps.executeUpdate();
conn.close();
response.sendRedirect("Tasksuccess.jsp");
} catch (SQLException e) {
e.printStackTrace();
}
}
}
35
-
8/7/2019 Project Documentation OHD
36/80
Logincontroller.java:package com.login;
import com.connection.Crp_system;
import java.sql.Connection;import java.sql.ResultSet;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.PreparedStatement;
import java.sql.Statement;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;import javax.servlet.http.HttpSession;
/**
*
* @author admin
*/
public class LoginController extends HttpServlet {
/**
* Processes requests for both HTTP GET and POST
methods.* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
PrintWriter out = response.getWriter();
String username = request.getParameter("username");String password = request.getParameter("password");
String role_id = request.getParameter("role_id");
HttpSession session = request.getSession(true);
if (role_id.equalsIgnoreCase("1")) {
if (username.equalsIgnoreCase("Admin") &&
password.equalsIgnoreCase("Admin")
&& role_id.equalsIgnoreCase("1")) {
response.sendRedirect("adminhome.jsp");}
36
-
8/7/2019 Project Documentation OHD
37/80
} else if (role_id.equalsIgnoreCase("2")) {
PreparedStatement st;
try {
Connection conn = Crp_system.get_con();
st = conn.prepareStatement("select name, employee_id, role_id "
+ "from employee where email=? and password=?");
st.setString(1, username);
st.setString(2, password);
ResultSet rs = st.executeQuery();
if (rs.next()) {
System.out.println("##################################12");
String name = rs.getString(1);String studentid = rs.getString(2);
String roleid = rs.getString(3);
session.setAttribute("roleid", roleid);
session.setAttribute("posterid", studentid);
response.sendRedirect("employee_home.jsp");
}
conn.close();
st.close();
rs.close();
} catch (Exception e) {
e.printStackTrace(out);
}
} else if (role_id.equalsIgnoreCase("3")) {
Statement st;
try {
Connection conn = Crp_system.get_con();
String query = "select name,studentid from student where email='" +
username + "' and password='" + password + "'";
st = (Statement) conn.createStatement();ResultSet rs = st.executeQuery(query);
if (rs.next()) {
String name = rs.getString(1);
String studentid = rs.getString(2);
session.setAttribute("roleid", "3");
session.setAttribute("posterid", studentid);
response.sendRedirect("user_home.jsp");
}
conn.close();
st.close();rs.close();
37
-
8/7/2019 Project Documentation OHD
38/80
} catch (Exception e) {
e.printStackTrace();
}
}
}}
38
-
8/7/2019 Project Documentation OHD
39/80
Viewstatus.jsp
Insert title here
Task AssignEmployee~
Student~
Reply Query
Log Out
Hi!
SELECT
39
-
8/7/2019 Project Documentation OHD
40/80
Employee Name
Description
Facility Type
Status
40
-
8/7/2019 Project Documentation OHD
41/80
Home|
Register |
Forum|
Comments |About Us
Designed by :
Siddartha
41
-
8/7/2019 Project Documentation OHD
42/80
Homepage.jsp:
ONLINE HELP DESK
Home
About us
Email Id:
Employee
StudentsAdmin
42
-
8/7/2019 Project Documentation OHD
43/80
About Online Help Desk ?
This system can be used to automate the workflow of service requests
for the various facilities in the campus. This is one integrated system that covers
different kinds of facilities like class-rooms, labs, computer center, faculty club
etc.
Home|
Forum|
Comments |
About Us
Designed by :
Siddartha.K
43
-
8/7/2019 Project Documentation OHD
44/80
6.1 Testing:
Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing are used
later on during maintenance also.
6.2 Types of Testing
Unit Testing
6.2.1 Unit Testing
Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications testing is done touncover errors within the boundary of the module. All modules must be successful in
the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, Admin module, customer module, Normal User,. Giving different
sets of inputs has tested each module. When developing the module as well as
finishing the development so that each module works without any error. The inputs are
validated when accepting from the user.
In this application developer tests the programs up as system. Software units in
a system are the modules and routines that are assembled and integrated to form a
specific function. Unit testing is first done on modules, independent of one another to
locate errors. This enables to detect errors. Through this error resulting from
interaction between modules initially avoided.
6.3 Integration Testing
After the unit testing we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing interfaces
between modules. This testing activity can be considered as testing the design and
hence the emphasis on testing module interactions.
In this project integrating all the modules forms the main system. When
integrating all the modules I have checked whether the integration effects working of
any of the services by giving different combinations of inputs with which the two
services run perfectly before Integration.
44
-
8/7/2019 Project Documentation OHD
45/80
6.4 Acceptance Testing
Acceptance Test is performed with realistic data of the client to demonstrate
that the software is working satisfactorily. Testing here is focused on external
behavior of the system; the internal logic of program is not emphasized.
In this project Network Management Of Database System I have collected
some data and tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an
equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations and
also a complete verification to determine whether the objectives are met and the user
requirements are satisfied.
45
-
8/7/2019 Project Documentation OHD
46/80
ACCEPTANCE TESTING:
46
S.NO Test Case
Name
Test Procedure Pre
Condition
Expected
Result
Output
(Result)
Specification
Document
1 Registration
Form1
Enter all the
details of the
registration forms
Admin Home
page
Message
Registered
Successfully
Success Registration
Validation
22 2 Registration
Form2
Enter some fields
of registration
form
Admin Home
Page
Enter the
specific field
(validation
error)
Success Registration
Validation
3 Login Form1 Enter valid User
name, password
Home Page Display the
respectivehome pages
Success Login form1
Validation
4 Login Form2 Enter invalid
User name,
password
Home Page Blank screen Success Login form2
Validation
5 Post new
query
Select facility
type, description
End-user
home page
Display
posted
successfully
message
Success Post query
Validation
6 View status Click on view
status
End-user
home page
Display all the
status of
requests
Success View status
Validation
7 Access data Click on eBook
and softwares
End-user
home page
Display all e
books & s/ws
for download
Success Access data
Validation
8 Update status Enter the
description and
update the status
Admin Home
page
Display
updated
sucessfully
Success Update status
Validation
9 Assign task Enter facility
type, name and
description
Admin Home
page
Display
assigned
sucessfully
Success Assign task
Validation
10 Viewregistered
members
Click on viewemployee and
view students
End-userhome page Display all theregistered
members
Success Viewregistered
members
Validation
-
8/7/2019 Project Documentation OHD
47/80
TESTING SCREENS
47
-
8/7/2019 Project Documentation OHD
48/80
Entering Registration of Employee into Database:
The administrator will register the employee details into the OHD database.
After entering the values into the database we get a message updation successful .
48
-
8/7/2019 Project Documentation OHD
49/80
49
-
8/7/2019 Project Documentation OHD
50/80
Entering Registration of Employee into Database:
The administrator will register the employee details into the OHD
database. after entering the values into the database we get a message updation
successful.
50
-
8/7/2019 Project Documentation OHD
51/80
51
-
8/7/2019 Project Documentation OHD
52/80
APROOVING OR REJECTINGTHE REQUEST:
In this the administrator will update the status of the query by giving
the description of it whether he is approving or rejecting the query with appropriate
description.
52
-
8/7/2019 Project Documentation OHD
53/80
VIEWING THE STUDENT DETAILS:
In this the Admin can view the details of the students and employees registered
in the OHD
53
-
8/7/2019 Project Documentation OHD
54/80
STUDENT POST QUERIES PAGE:
In this the Students and the employees will post the request regarding their
queries by selecting the corresponding facility type and writing the description about
the query.
54
-
8/7/2019 Project Documentation OHD
55/80
55
-
8/7/2019 Project Documentation OHD
56/80
HOME PAGE:
This is the home page of online help desk.
56
-
8/7/2019 Project Documentation OHD
57/80
ABOUT US PAGE:
This is the About us page of Online Help Desk. All the viewers can know about
the organization.
57
-
8/7/2019 Project Documentation OHD
58/80
LOGIN PAGE:
This is the login page of the Online help Desk .Here all the users like
employees , students and admin can login into their account.
58
-
8/7/2019 Project Documentation OHD
59/80
ADMIN HOME PAGE:
This is the Admin home page where he can Assign task, Registers users and
reply to the query.
59
-
8/7/2019 Project Documentation OHD
60/80
ASSIGNING TASK TO EMPLOYEE:
Here the Admin will assign task to the employees by specifying the facilitytype and employee name and tell them about what action to be performed.
60
-
8/7/2019 Project Documentation OHD
61/80
SUCESSFULLY ASSIGNED TASK:
Here after assigning we get the message successfully assigned
61
-
8/7/2019 Project Documentation OHD
62/80
VEWING THE POSTED QUERY BY EMPLOYEE AND STUDENTS:
Here the admin will view the queries or request that are sent by the employees .
62
-
8/7/2019 Project Documentation OHD
63/80
APROOVING OR REJECTINGTHE REQUEST:
Here admin will give reply to the requests along with the description whether to
approve or reject the request.
63
-
8/7/2019 Project Documentation OHD
64/80
VIEWING THE STUDENT DETAILS:
Here admin can view all the student details and the people who are registered.
64
-
8/7/2019 Project Documentation OHD
65/80
VIEWING EMPLOYEE DETAILS:
Here admin can view all the employee details who are registered into the
Online help Desk.
65
-
8/7/2019 Project Documentation OHD
66/80
EMPLOYEE REGISTRATION PAGE:
Here is the registration page of the employee the admin will register the
employees emailed specifying their username.
66
-
8/7/2019 Project Documentation OHD
67/80
REGISTRATION PAGE OF STUDENT:
Here is the registration page of the Students the admin will register the
employees emailed specifying their username.
67
-
8/7/2019 Project Documentation OHD
68/80
EMPLOYEE HOME PAGE:
This is an employee home page where he can post the request ,reply to the
queries posted by students, access softwares etc..
68
-
8/7/2019 Project Documentation OHD
69/80
EMPLOYEE QUERY STATUS PAGE:
This is the employee status page ,he can view the status of the requests he has
posted.
69
-
8/7/2019 Project Documentation OHD
70/80
EMPLOYEE POST QUERIES PAGE:
This is the employee request page ,where he can post the request to the admin
if there are any queries.
70
-
8/7/2019 Project Documentation OHD
71/80
SUCESSFULLY QUERY POSTED:
After posting he will receive this message.
71
-
8/7/2019 Project Documentation OHD
72/80
EMPLOYEE REPLY QUERY PAGE:
This is the employee reply query page where the students post the request and
the employee will approve or reject the request.
72
-
8/7/2019 Project Documentation OHD
73/80
EMPLOYEE CHANGE PASSWORD PAGE:
Here the employee can change the password and update the new email id and
mobile number.
73
-
8/7/2019 Project Documentation OHD
74/80
STUDENT HOME PAGE:
This is the student home page where students can post the request and view the
status.
74
-
8/7/2019 Project Documentation OHD
75/80
STUDENT QUERY STATUS PAGE:
This is the status page of the student where he can view whether the request is
approved or rejected by the employee.
75
-
8/7/2019 Project Documentation OHD
76/80
STUDENT POST QUERIES PAGE:
Here the students can post the query to the employees.
76
-
8/7/2019 Project Documentation OHD
77/80
SUCESSFULLY QUERY POSTED:
After pressing the post we can see the message posted successfully.
77
-
8/7/2019 Project Documentation OHD
78/80
STUDENT CHANGE PASSWORD PAGE:
Here the employee can change the password and update the new email id and
mobile number.
78
-
8/7/2019 Project Documentation OHD
79/80
8. Conclusion:
Therefore we are able to successfully reach the targets and goals of the
project.
This project provides an excellent support for the users in order to provide all
the members of organization directly interacting with the person in the
organization.
The Administrator is the whole controller of the project he can update
everything in the project.
To the extent that it overcomes the loopholes of manual system and achieve the
benefits of the computerized system. Here after deploying this application there is no need of wasting time to gather
the relevant and required information manually.
So we, conclude that our project Online Help Desk, will be found
to be most useful and also we expect a better vision for a campus in near future.
Future Scope:
The scope of the project work is not limited to developing a web server
and providing services to the client but also can be extended to
More Security:by continuing to establish a firewall at the server, protecting the client
systems from access to unauthorized or virus probed sites.
It can be enhanced to include uploading a file giving message.
It can be enhanced to include give common alerts to group of people.
79
-
8/7/2019 Project Documentation OHD
80/80
REFERENCES
1. SOFTWARE ENGINEERING - By Roger .S. Pressman
2. SQL FOR PROFESSIONALS - By Jain
3. JAVA2 THE COMPLETE REFERENCE - By Herbert schmidt
WEBSITES
1. www.support.microsoft.com
2. www.java.sun.com
3. www.w3schools.com
4. www.freetutes.com