DEPARTMENT AUTOMATION WEBSITE for the

Department of Computer Science and Engg.

DIBYA RANJAN BHUKTA (1101227185)

ISHA ARPITA MOHANTY (1101227192)
ANKUR (1101227164)
 A Report Submitted to the

Biju Pattnaik University of Technology, Rourkela

In partial fulfillment of the Award of the degree of

BACHELOR OF TECHNOLOGY
In
COMPUTER SCIENCE AND ENGINEERING
By

DIBYA RANJAN BHUKTA(1101227185)

ISHA ARPITA MOHANTY(1101227192)
ANKUR(1101227164)

Under the supervision of

Mr. MOHIT RANJAN PANDA

Department of Computer Science and Engineering

C.V. Raman College of Engineering, Bhubaneswar
April 2015.
April 2015
 CERTIFICATE OF APPROVAL
This is to certify that this report entitled, “DEPARTMENT AUTOMATION WEBSITE
FOR THE DEPARTMENT COMPUTER SCIENCE AND ENGG.”, submitted by DIBYA
RANJAN BHUKTA, ISHA ARPITA MOHANTY and ANKUR towards the partial
fulfillment for the award of the degree of Bachelor of technology is a web-based
work carried out by them under our supervision during the period 2014-
2015.The report/project has fulfilled all the requirements as per regulations of
the University.

Mr. MOHIT RANJAN PANDA DR. B. PATI

Project Guide External H.O.D CSE Dept
 DECLARATION

This project/report is a presentation of our original web-based work. Wherever

contributions of others are involved, every effort is made to indicate that clearly, with due
reference to Stack Overflow, w3schools and Google. The work was done under the guidance
of Mr. Mohit Ranjan Panda. The results embodied in this report have not been submitted to
any other university or Institute for the award of any degree or diplomas.

DIBYA RANJAN BHUKTA (1101227185)

ISHA ARPITA MOHANTY (1101227192)
ANKUR (1101227164)
Department of Computer Science and Engineering
C.V. RAMAN COLLEGE OF ENGINEERING
 ACKNOWLEDGEMENT
First and foremost, we would like to express our sincere gratitude to our guide
Mr. Mohit Ranjan Panda for spearheading the project. We are grateful to
him for having supporting us throughout the making of this project, giving us
intellectual freedom, yet showing a possible approach whenever we needed help.
Needless to say, without his guidance and support this work would not have been
possible.

We are grateful to our parents and friends for having supported us throughout the
journey in surpassing all odds and for being a constant source of motivation.

We would also like to thank Dr. B Pati for helping us to implement this idea and
keeping us motivated throughout the process.

Last but not the least we are grateful to God for helping us see through the darkest
of times.
 ABSTRACT

Department of Computer Science and Engineering, CVRCE, is concerned with both curriculum
and co-curricular activities. In this project, a website has been developed for the Department
of Computer Science and Engineering which helps in automating the department activities
online besides providing a common interactive interface to the students, parents, teachers
and admin.
The actors involved in the field are the students, teachers, parents and the admin. The
students can view their marks (both internal and semester), attendance, rank, performance
graph etc. This website mainly aims at bringing the parents, students and faculty members on
a common interactive platform. On successful registration; a student will be given a
conformation via e-mail and a SMS. On the contrary, parents do not have to register directly;
upon their ward’s registration, a system generated password will be sent to the parent to
facilitate their login.
On the other hand, the admin is fixed entity. He plays a crucial role in updating student’s
semester results and attending to the E- grievances. Additional facilities like blogging, online
payment and notifications have also been included.
Through this website, teachers can now upload the assignment and can view the list of
students who have downloaded it. The teachers and students can now share their experience
through the website’s blogging facility.
 LIST OF FIGURES/CONTENT
• Chapter 1-Introduction
• Chapter 2-Basic concepts
• Chapter 3-Software Requirement Specifications
 Admin
 Teacher
 Student
 Parent
• Chapter 4-Entity –Relationship Diagram
• Chapter 5-Use-Case Diagram
• Chapter 6-Activity Diagram
 Admin
 Teacher
 Student
 Parent
• Chapter 7-Sequence Diagram
• Chapter 8-Class Diagram
• Chapter 9-Data dictionary
• Chapter 10-Snap-Shots
• Chapter 11-Testing
• Chapter 12-Conclusion
 INTRODUCTION
In this project, a website has been developed for the Department of Computer Science and
Engineering which helps in automating the department activities online besides providing a
common interactive interface to the students, parents, teachers and admin.
The actors involved in the field are the students, teachers, parents and the admin. The
students can view their marks (both internal and semester), attendance, rank, performance
graph etc. This website mainly aims at bringing the parents, students and faculty members on
a common interactive platform. On successful registration; a student will be given a
conformation via e-mail and a SMS. On the contrary, parents do not have to register directly;
upon their ward’s registration, a system generated password will be sent to the parent to
facilitate their login.
On the other hand, the admin is fixed entity. He plays a crucial role in updating student’s
semester results and attending to the E- grievances. Additional facilities like blogging, online
payment and notifications have also been included.
Through this website, teachers can now upload the assignment and can view the list of
students who have downloaded it. The teachers and students can now share their experience
through the website’s blogging facility.
 BASIC CONCEPTS
A web Application can be divided basically in 2 big parts or sections, the Application layer
which encapsulates the business logic and backed processing, and the Presentation Layer
which function is to present the user with a Graphic User Interface (GUI) to see the results of
the backend processing. One goal in Web Applications Development is to "separate" the
application layer from the presentation layer as much as possible to achieve modular and
robust systems.

Here in the designing part, as a front end we have used HTML5 and CSS, while in the backend
we have used Oracle 11g. For establishing connection between back-end and front –end we
have used JSP and Servlet as well some concepts of advance java. In a standard Java
EE web application, the client will typically call to the server via a web form. The information is
then either handed over to a Java Servlet which interacts with a database and produces
an HTML-formatted response, or it is given to a Java Server Pages (JSP) document that
intermingles HTML and Java code to achieve the same result.

There are two key components in a web application:

– the data and business logic performed on this data

– the presentation of data
This separation between presentation, business logic and control is achieved by implementing
the Model-View-Controller (MVC) Design Pattern Model View Controller or MVC as it is
popularly called, is a software design pattern for developing web applications. A Model View
Controller pattern is made up of the following three parts:
• Model - The lowest level of the pattern which is responsible for maintaining data.
• View - This is responsible for displaying all or a portion of the data to the user.
• Controller - Software Code that controls the interactions between the Model and View.
The model

The model is responsible for managing the data of the application. It responds to the request
from the view and it also responds to instructions from the controller to update itself.

The view

A presentation of data in a particular format, triggered by a controller's decision to present the

data. They are script based templating systems like JSP, ASP, PHP and very easy to integrate
with AJAX technology.

The controller

The controller is responsible for responding to user input and perform interactions on the data
model objects. The controller receives the input, it validates the input and then performs the
business operation that modifies the state of the data model.

Java Servlets are mostly used for backend processing tasks, such as connections with
databases and other servers, hard programming and business logic implementation. Those
activities defines the Application Layer of a System. Java Servlets are Java Classes (compiled
into .class files) that are accessible through the web (using a web server like tomcat or resin).
Servlets must extend the HttpServlet abstract class.
Java Server Pages (JSP) basic purpose was to address the presentation layer of web
applications and NOT the application business logic or Backend Logic. JSP syntax consists of
tags intermixed with html tags to generate the appropriate user interface dynamically. In the
end, JSP are compiled into servlets.
In theory we must use JSP pages to show the results of what servlets do in the backend. In
practice, many people forget about this separation and end up putting a lot of unnecessary
code in JSP pages, making web applications hard to maintain and update.

COMMON STRUCTURE OF A SERVLET

import java.io.*;
import javax.servlet.http.*;
import javax.servlet.*;

public class hello extends HttpServlet

{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException
{
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.print("Hello World from GET method ");
}
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws IOException
{
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.print("Hello World from POST method ");
}
}
 SOFTWARE REQUIREMENT SPECIFICATION
1. Login page:
Description: It contains the common interface of the Society of Computer Science and
Engineering with student, parent, admin and teacher login area and event registration tab.

1.1 – Student Login:

Input - Student User Id and Password.
Output – Directed to Student Profile Page on the entry of a valid combination of user id and
password else a Log-in error message is flagged.
 
1.2 - Faculty Login:
Input – Faculty User Id and Password.
Output – Directed to Faculty Profile Page on the entry of a valid combination of user id and
password else a Log-in error message is flagged.
 
1.3 – Parent Login:
Input – Parent User Id and Password.
Output – Directed to Parent Profile Page on the entry of a valid combination of user id and
password else a Log-in error message is flagged.

1.4 - Register page:

Input- Enter the student’s details viz.
• first name
• middle name
• last name
• gender
• semester
• branch
• university registration number
• email id
• phone number
Output-
• A unique participant id/registration number.
• Email to the participant with the participant id
• SMS to the participant with the participant id

1.5 - Admin login area:

Input-
• Username
 • Password
Output- Admin profile page on the entry of a valid combination of user id and password else a
Log-in error message is flagged.
 
 
2. Admin Profile page:
 Description: All the privileges provided to the admin are shown.
 
2.1 - Personal information entry:
Input – Enter the personal details of admin viz.
• Employee id
• First name
• Middle name
• Last name
• Gender
• Email id
• Phone
Output-
• Details get into database
• Corresponding message will be shown.
 
2.2 - Change password:
Input –
• Current/old password
• New password
• Confirm new password
Output –
• Password updated in the database
• Corresponding message will be shown.
 
2.3- Upload Semester Marks:
Input-
• Uploads the semester marks and corresponding registration number.
Output-
• Marks updated in database.
• Result displayed in the corresponding student’s profile page.

2.4- Upload Notice:

Input-
• A notice with content and date is inserted.
Output-
• Notice gets uploaded in database.
 • Gets displayed in all the profiles.

2.5- Tracks payment status:

Input-
• Inputs the registration number.
Output-
• Payment status displayed.

3-Teacher profile page:

Description: All the privileges provided to the teacher are shown.

3.1- Assignment Sharing:

Input –
• Assignment Date
• Assignment Body
• About the event
 Output –
• New assignment will get added to the database.
• Corresponding message will be displayed.
 
3.2 – Attendance Updation:
Input-
Attendance percentage
Output-
• Parent can view their respective wards attendance
• Students can view their attendance.
• If attendance gets less than 75, an email is sent to the registered parent E-mail id.

3.3 - Update Internal marks:

Input-
• Exam date
• Student’s name
• Registration number
• Subject
Output-
• Internal marks updated in database.
• Parent can view their wards marks.

 3.4 - Update Blog:

Input-
Content uploaded by teacher.
Output-
• Content by teacher will be updated in the database.
• Corresponding status message will be shown.
• Content by teacher gets reflected in the teacher’s message page.

 3.5- Inserts time-table:

Input- Time table uploaded by teacher.
Output-Students can view the time table.

3.6 – Send-Mail:
Input- Teacher gives the email-id and content.
Output-
• Message by Faculty Advisor will be updated in the database
• Message reflects in student’s profile page.
 
3.7 –Contact Parent:
Input- Teacher gives the email-id and content
Output-
• Message by teacher will be updated in the database
• Corresponding status message will be shown.
• Message by teacher gets reflected in the parent Message page.

3.8 – Logout:
Input- Click on the Log out link
Output-Directed to the home page.

4. Student profile page:

Description: All the privileges provided to the student are shown.

4.1- Write blog:

Input:
• Blog Content along with date is uploaded.
Output:
• Blog displayed in the recent blogs list in main page.
• Gets updated in the database.

4.2- Online Payment:

Input:
• Chooses the payment reason, gives account details and required amount.
Output:
• Money deducted from account.
 • Payment status changed.

4.3-Send-mail:
Input:
• Chooses the email-id of the respective teacher or the admin.

Output:
• E-mail gets updated in database and reflected in the person’s profile page.

5. Parent profile page:

Description: All the privileges provided to the parent are shown.

5.1- View Student Details:

Input:
• Parent can provide the registration number of the student other than their own ward.
Output:
• All the details can be viewed.

5.2-Send-mail:
Input:
• Chooses the email-id of the respective teacher or the admin.
Output:
• E-mail gets updated in database and reflected in the person’s profile page.

ENTITY-RELATIONSHIP MODEL
USE CASE DIAGRAM
ACTIVITY DIAGRAM
Administrator
Parent

Teacher
Student
SEQUENCE DIAGRAM

CLASS DIAGRAM
DATA DICTIONARY
 STUDENTS DATABASE

TEACHERS DATABASE

Branch Subjects Allocation

Auto-generated SGPA Table

Blog Table
Assignment Table

SNAPSHOTS
Admin (Teacher Allocation Page)

Login Page

Registration Page
 Employee Search

Teacher Profile Page

Class Test Mark Updation

TESTING
Testing a program consists of providing the program with a set of test inputs (test cases) and
observing if the program behaves as expected. If the program fails to behave as expected,
then the conditions under which failure occurs are noted for later debugging and correction.
Some commonly used terms associated with testing are:
• Failure: This is a manifestation of an error (or defect or bug). But, the mere presence
of an error may not necessarily lead to a failure.
• Test case: This is the triplet [I,S,O], where I is the data input to the system, S is the
state of the system at which the data is input, and O is
the expected output of the system.
• Test suite: This is the set of all test cases with which a given software product is to be
tested.
Here we have adopted the technique of validation and verification. Verification is the process
of determining whether the output of one phase of software development conforms to that of
its previous phase, whereas validation is the process of determining whether a fully developed
system conforms to its requirements specification. Thus while verification is concerned with
phase containment of errors, the aim of validation is that the final product be error free.
 We have analyzed the usage of variables and have tried our best to reduce the time
complexity.
 Proper validation has been provided for fields like password to ensure security, like the
system will display a message if the password is less than 8 characters etc.
 The messages that are sent to parents and admin are kept safe, and their delivery to any
unauthorized person is restricted.
 We have provided sufficient number of test cases to ensure that this project is suitable
for practical adaptation.

CONCLUSION
This report emphasises on the need for the project, the tools used to make the project and the
functionalities included in the project.

This project has been built to serve the purpose of making the people aware of different
ventures being taken by the department of Computer Science & Engineering and providing an
interactive interface to the students, teachers, parents and the admin to ensure a holistic
approach towards the accomplishment of transparency and robustness in the education
system.

It is our hope that this project will simplify the work of the department and keep everyone
updated with the latest happenings and as per our vision will ensure proper interaction
between students, teachers and parents.