A PROJECT REPORT ON

e-SPARSH

SUBMISSION IN THE FULFILLMENT

FOR AWARD OF BACHELOR DEGREE IN
COMPUTER SCIENCE AND ENGINEERING
Pt. RAVI SHANKAR SHUKLA UNIVERSITY, RAIPUR

GUIDED BY:

Mr. RAMESH KUMAR Mr. PAWAN PATNAIK

HOD Computer Science Lecturer Dept. of MCA

SUBMITTED BY:

ASHISH NAMDEO
ANAND BILLAIYA
RAJEEV BOSE
AMIT KUMAR GUPTA
HARISH KUMAR DEWANGAN

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BHILAI INSTITUTE OF TECHNOLOGY, DURG.
 CERTIFICATE OF DISSERTATION ON ACCEPTANCE

This is to certify that the project entitled “e-SPARSH” was carried out by
Ashish Namdeo, Anand Billaiya, Harish Kumar Dewangan, Amit Kumar
Gupta and Rajeev Bose Computer Science and Engineering student 2003-2007
at BHILAI INSTITUTE OF TECHNOLOGY, DURG is hereby accepted and
approved after proper evaluation as a creditable work submitted in the
fulfillment for the award of the Degree of Bachelor of Engineering in
COMPUTER SCIENCE from Pt. RAVI SHANKAR SHUKLA UNIVERSITY,
RAIPUR (C.G.).

It is understood that by this approval, the undersigned do not necessarily

endorse or approve any statement made, opinion expressed on conclusion
therein, but approve the report for the purpose for which it is submitted.

Internal Examiner External Examiner

DATE:
 LETTER OF RECOMMENDATION

The report entitled “e-SPARSH” was carried out by Ashish Namdeo, Anand
Billaiya, Harish Kumar Dewangan, Amit Kumar Gupta and Rajeev Bose in
the fulfillment for the award of the Degree of Bachelor of Engineering in
COMPUTER SCIENCE from Pt. RAVI SHANKAR SHUKLA UNIVERSITY,
RAIPUR (C.G.)

The work is comprehensive and of sufficient standard, as found after proper

evaluation. It is recommended as a creditable work for the fulfillment of the
requirement for the award of the Degree of Bachelor of Engineering in
COMPUTER SCIENCE. However the statement made in the report are the
outcome of the project work carried out by the students and the undersigned
will not be responsible for them if this report is presented for purposes other
than the award of the degree.

Mr. RAMESH KUMAR Mr. PAWAN PATNAIK

HOD Computer Science Lecturer Dept. of MCA

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BHILAI INSTITUTE OF TECHNOLOGY, DURG.
 DECLARATION

We hereby declare that our group has completed the project entitled as
“e-SPARSH”. This work has not been submitted to any university / institute for
the award of any other degree / certificate.

ASHISH NAMDEO
ANAND BILLAIYA
RAJEEV BOSE
AMIT KUMAR GUPTA
HARISH KUMAR DEWANGAN
 ACKNOWLEDGEMENT
We would wish to acknowledge our profound sense of gratitude to our
project guide Mr. PAWAN PATNAIK, LECTURER MCA Dept., BHILAI
INSTITUTE OF TECHNOLOGY, for his remarkable guidance and many
valuable ideas during the preparation of this project. Indeed it was a matter of
great felicity and privilege for us to work under him. We express our
thankfulness to him for his dedicated inspiration, lively interest and patience
without which it would have being impossible to bring the project to
completion.

We would also like to thank Mr. RAMESH KUMAR, HOD

(COMPUTER SCIENCE) for his constructive criticism and continued
encouragement without which completion of this project would have been a
difficult task.

We wish to extend our hearty thanks to all the staff members and
colleagues who directly or indirectly helped us in this project work.

And lastly we express our sincere gratitude to Dr. M.K.KOWAR,

PRINCIPAL, B.I.T., DURG and Prof. B.S. NARANG, DIRECTOR, B.I.T.,
DURG with whose blessing this project was completed.

ASHISH NAMDEO

ANAND BILLAIYA

RAJEEV BOSE

AMIT KUMAR GUPTA

HARISH KUMAR DEWANGAN

 PREFACE

The project was done as the part of core-curriculum of the syllabi of B.E.
8th semester COMPUTER SCIENCE. The project report encapsulates all the
information associated with the construction of the project which involves the
detailed description of all the phases of the project. These details include the
project model used, print screens of the user interfaces, the data flow diagrams,
flow charts, entity relationship diagrams, the bibliography, the references.

“e-SPARSH”

Any suggestions on the aptness of the project report would be heartily

accepted and acknowledged by students who have put their efforts in the
implementation of the project and changes would be implemented if possible
depending on the knowledge level of the students.
 TABLE OF CONTENTS

1.Introduction

• Objective
• Users of the project

• Software & Hardware Requirements

2. Problem Statement
• Current System
• Proposed System

3. System Analysis
• Software Development Lifecycle
• Further Enhancement

• Security Features

4. Project Details
5. System Design
• Data Flow Diagrams
• E-R Diagrams
• Tables

6. User Interfaces
7. Bibliography
 Introduction
Objective

e-SPARSH is an electronic information system aimed to reduce the paper

works in educational organizations through the use of computer technology.
The project uses intranet facility available in the organization for its
information requirements and distributions.

Users of the project

The project is basically for educational organization with three levels of users,
they are as follows:
Student
Employee
Administrator.

Software and Hardware Requirements

• H/W requirements include the use of Pentium III and above for clients
Pentium IV for server, 128 MB of RAM for client and 256 MB and
above for server.
• No external H/W accessory required.
• S/W requirements include the existence of jdk1.5.0, Apache tomcat
5.5.17 server, Mozilla firefox browser, Microsoft Access.

Netbeans5.0 has been used as the IDE for the development of JSP & Servlets.
Dreamweaver has been used for creating Javascript files & HTML files.
 Planning
Current System

The Current System involves a lot of manual and individual working scenario.
Each working department has its own complexity and the total system
becomes very tedious. Information transfer among departments is very tough.
Application system involves person going to the respective authority for
submission and confirmation.

Proposed System

In this electronic era where everything is heading towards digital system we

need a mechanism to convert our entire working method from manual to
automatic, a mechanism which is efficient enough to perform in different and
difficult working conditions. The condition in our case is an educational
organization which needs to be automated for its entire official works. As all
the organizations are frequently employing different networking techniques to
integrate their different departments. This is done in order to do everything in
a systematic manner, to make the work flow more smooth and efficient.
After going through the study of current system we can propose a
system which is fully automated and paperless. In an educational organization
we can implement software which can automate all its official work. Software
which enables the personnel as well as the student to do their work from
remote machines. We can consider following points in a general proposed
system:-
• The system should be an integrated one.
• The system should fulfill the requirements of all the level of hierarchy
of the organization.
• The system should be interactive as well as user friendly so that even a
naïve can also use it.
• The system should be scalable as well as expandable to meet the
continuous change in the field of technology and system of
organization.
• The system should follow all the standard formats.
• Transparency should be the compulsory feature of the system.
• The system should be the flexible enough to face the changes of the
dynamic world.
• Software should be able to tackle the problems of concurrency.

Now we can consider features for a specific system which can be

employed in an educational organization.

• The system should integrate all the departments of the college i.e.
different departments like administrative dept., examination dept.,
account sections, libraries, and individual branch related dept. of
college.
• The system should be interactive so that if a new student comes and
uses the system he must not face any problem.
 System Analysis

Software development life cycle model

The duration of time that begins with conceptualization of software being

developed and end after the system is discarded after its usage is denoted by
software development life cycle. The life cycle model that we have
implemented for the project is “Incremental Model”. This model is one of the
most popularly used models. In this model we release the product partially in
the beginning and slowly add increased functionality to the system. Each new
release enhances the functionality of the previously released system thereby
reducing the cost of the product.

C
A A A
B B

Release 1. Release 2. Release 3.

INCREMENTAL MODEL
Further Enhancements
• Feedback Management
• Daily attendance scheme
• Official report generation

Security features
We have provided the feature of loginId and password. This pre security check
is provided to prevent a group of users from accessing information about
another group of users. Selection of the group of users is also provided along
with the specifications of the loginId and password. For the first time these
values have to be collected from the updater. Thereafter login the user can
change his/her password.

We are only allowing the user to change only the password field in his/her
personal details section. Other fields can only be modified by the updater after
official procedures.

We have utilized the concept of session tracking for embedding security to

access of the pages. Only a logged on user can have access to the pages. The
code for checking the logging information is embedded at the beginning of
each page.

The checking of logging is done by using an attribute value state. The state
value is set to true during logon. During the sign-out operation this state value
is set to false. When the server encounter a false value for the state then it does
not displays the requested page instead it displays an error message, and tells
the user to logon again.
 Project Details

e-SPARSH is web based solution involving set of web pages designed

in Java Server Pages & Servlets. The use of JSP and Servlets make it platform
independent due to platform independence of JAVA.

The databases are maintained in MS Access and modified through the web
pages. We have also used concepts such as session tracking for user
authentication. There are four main modules in our project, each representing
some specific personal in the organization.

Updater module:
This is the most important module in the project. The updater is a
person with administrative rights responsible for the maintenance, handling,
updation of the entire database.

HOD module:
HOD is responsible for answering applications of students and teachers,
see the students details

Employee module:
Employee is responsible for entering attendance & marks of students
upload study materials, viewing notices, writing applications etc.

Student module:
Student is the main client using this software, who is provided with
facilities like submitting online application, viewing attendance & marks,
Downloading notes, notices & academic calendars, can search a friend & not to
mention he can view his own personal details.
 Updater Module
Updater is the most important entity in our project. He is the person with
administrator rights, having access to all the passwords of all the users and all
the user information including students, employees etc. It is function of the
updater to distribute the LoginId and passwords to the users. These are then
utilized for first login by the users, and then they can change their passwords
only. The various functions which an updater performs are as follows:-

• Create Batch
• Update Student Details
• Update Employee Details
• Update Notices
• Update Schedule
• Update Calendar
• Update Semester Subjects
• Update Batch Semester

The working details of each of the fields as described below:-

• Create Batch
In this the updater creates the table for storing the database of students for
a specified batch for example 2003-2007. This creates a table with name
2003_s. This process also enters a value of 2003-2007 in the batch table.

• Update Student Details

In this module the updater enters a value for the student id and then he is
made available with a form for entering or updating details of a student.
This operation updates the table for the batch whose student details are
being entered.
• Update Employee Details
This module has the working similar to the updation of the student’s
details. Only the table in which the data is updated is an employee table.

• Update Notices
This module includes the uploading of a notice in the form of a text or
word document. The file is copied from the specified location to a location
at the server. The address of the uploaded file is stored in the database
along with the title of notice and for which group of users having access to
these notices.

• Update Schedule
This module is used to update the schedules/time table for students. The
updation is done through a form where the periods are entered directly into
textboxes.

• Update Calendar
Updating calendar includes uploading a file containing the calendar for the
current session for the current batch.

• Update Semester Subjects

This is used to update the subjects taught in each semester. This is used
because with each changing semester the subjects may change. Both the
theory and practical subjects can be specified.

• Update Batch Semester

This is used by the updater to update the semester of the all students of a
complete batch after a new semester begins.
 Employee Module

The following operations can be performed by an employee.

• Personal Details
• Application
• Confirmation
• Attendance
• Upload Study Material
• Marks Entry
• Notices
• Academic Calendar

The working details of each of the fields as described below:-

• Personal Details
An employee can access his/her personal information through this
module. He/She can change their password also.

• Application
An employee can write application to their respected HODs.

• Confirmation
This module is used to get confirmation about the sent application.
After getting the confirmation they can keep or delete the same.

• Attendance
This module is used by employee to feed the attendance of students of
a particular branch and semester. In this module they have to choose
the maximum number of working days.
• Upload Study Material
This module is to upload any text, PDF or DOC files from the local or
remote location for students.

• Marks Entry
This module is used by employee to feed the marks of students of a
particular branch and semester. In this module they have to choose
the maximum number of marks for tests.

• Notices
This module is used to see notices that are concerned to them.

• Academic calendar
This module is used to see academic calendar.
 HOD Module
The following operations can be performed by a HOD.

• Personal Details
• Application View
• Student Details
• Academic Calendar

The working details of each of the fields as described below:-

• Personal Details
An employee can access his/her personal information through this
module. He/She can change their password.

• Application view
This is used to view & replies to the applications sent by students and
employees. HOD can also see the details about the applicants directly
from the application module itself. HOD can add their comments to
the applications which can further be accessed by the applicants.

• Students Details
This module is used by HOD to see details about any student
irrespective of their branch and batch.HOD has to select the batch and
branch of the students for accessing their information.

• Academic calendar
This module is used to see academic calendar.
 Student Module

The student module is developed for the students. The students are provided a
lot of facilities that are of there daily needs (e.g. Time Table) and specific
needs like searching of a friend. Various modules are separated for the
students needs.
A student is provided the following facilities;
• Personal Details view
• Application Writing
• Confirmation view
• Attendance view
• Study Material
• Find Friend
• Notices
• Schedules
• Academic Calendar

Now we can see them one by one:

• Personal Details view
This is the facility by which a student can see his own personal
information that is maintained by the college. In this student can only
change his password rest are only for retrieve because they are so
sensitive for the college.

• Application Writing
 With this facility the student can write an application to the HOD’s of
concerned branch or any other department. This user interface provides
the actual feel of the application as it starts from the ‘To’ and ends with

the addition of the ‘Student’s Name’. The student is provided the space
for writing the subject of the application and the body of the
application. The student can also select the department for which he is
writing the application.

• Confirmation’s view
In this the student can see that is any reaction regarding his application
has been done by the HOD of the dept to whom he has written the
application. If the application is not seen the student will be seen a
message that “Your application yet not read” along with the respective
subject in a tabular form.

• Attendance View
In this part the student can see his attendance is it is updated by the
respective Lecturers of the subjects of the current semester.

• Study Material
This part facilitates the student to download the study material from the
server (where concerned teacher has uploaded the notes regarding to the
subjects) by just clicking a hyperlink on his page.

• Find Friend
 This part facilitates the students to find some details of another student
studying in the college to make a contact with him. For this student has
to enter his name (approx.) and the batch in which he is reading.

• Notices
In this section each student is provided a link to the notices related to
their respective branch or the circular. This reduces the overhead of the
student to go to the notice board.

• Schedules
In this field the student can view his daily schedules in the form of
table. These tables basically show the subject name along with day and
time.

• Academic Calendar
Each university and college has its plan about every session. These
plans also useful for the students in order to prepare for the exams and
celebration of holidays. Student can view such plans by just clicking a
hyperlink which links an already stored page.
 System Design
Data Flow diagram

HOD
(R/W/Update)
REQUEST

TEACHER
(R/W/Update) WEB
SERVER R/W/U DATABASE
p
(INFORMATIO
N
STUDENT RESPONSE PROCESSING
(R/APPLY) SYSTEM)

CLIENT

Student Table:
 Password 12th %
Student id
Name
Address

Father’s
Name
Student Table Branch
Mother’s
Name
Semester

10th % E-mail id

Batch
Phone
DOB
No.

Updater Table :

Updater table
password
loginid

Employee Table :
 Employee
id Password
Name
Address

Father’s Employee Table Department

Name

DOB
Mother’s
Name

E-mail id
Qualification
Phone No.
Designatio
n

Application Table :

Subject

User id

Application Table

Application no
Matter
confirmation
 Notice Table :

date

Ref Notices / notes

no Table branc
h

location
Subject

Marks Table :

Sub3 Sub4
Sub2 Sub5

Sub6

Sub1

Marks

Student id

Subject Table:
 Sub3 Sub4
Sub2 Sub5

Sub6
Sub1

Subject
Table Sub7
Sub10

Sub9 Sub8

sem_branch

Description of Tables

The main part of our project is database. The tables that we have used are
described below with the field names and description.

Student Information Table

s_id: - stores unique id of the student.

s_name: - stores name of the student.
s_fname: - stores father’s name of the student.
s_mname: - stores mother’s name of the student.
s_pass: - stores the password of the student.
s_gen: - stores gender of the student.
s_date: - stores the date of birth of the student.
s_branch: - stores the branch of the student.
s_sem: - stores the current semester of the student.
s_address: - stores the temporary address of the student.
s_email: - stores the email of the student.
s_tno: - stores the telephone number of the student.
s_mno: - stores the mobile number.
s_paddress: - stores the permanent address of the student.

Employee Information Table

e_id: - stores unique id of the employee.

e_name: - stores name of the employee.
e_fname: - stores father’s name of the employee.

e_mname: - stores mother’s name of the employee.

e_pass: - stores the password of the employee.
e_gen: - stores gender of the employee.
e_dob: - stores the date of birth of the employee.
e_doj: - stores the date of joining.
e_post: - stores the designation of the employee.
e_address: - stores the temporary address of the employee.
e_email: - stores the email of the employee.
e_special: - stores the specialty of the employee.
e_qualify: - stores the qualification of the employee.
e_tno: - stores the telephone number of the employee.
e_mno: - stores the mobile number.
e_paddress: - stores the permanent address of the employee.

Updater Information Table

login id: - stores the login id of the updater.
password: - stores the password of the updater.

Batch Table

batch_name: - stores the name of all the batches.

Subject Table

sem_branch: - specifies the semester and branch.

sub1 to sub6: - stores the names of the theory subject.
sub7 to sub10: - stores the names of the practical subject.

Application Table

id: - stores the unique id of the application file.

dpt: - stores the department for which the application is.
subject: - specifies the subject of the application.
matter: - stores the matter of the application.
confirmation: - stores the comment given by the HOD.

Attendance Table

s_id: - stores the unique id of the student.

sub1 to sub6: - stores the attendance in the theory subject.
sub7 to sub10: - stores the attendance in the practical subject.
max_sub1 to max_sub6: - stores the names of the theory subject.
max_sub7 to max_sub10: -stores the names of the practical subject.
CT1 Table

s_id: - stores the unique id of the student.

sub1 to sub6: - stores the marks of class test 1 in the theory subject.

CT2 Table

s_id: - stores the unique id of the student.

sub1 to sub6: - stores the marks of class test 2 in the theory subject.

Calendar Table
location: - stores the location address of the calendar file.
date: - stores the date on which the file was uploaded.

Notices Table
refno: - stores the unique reference no. of the notice file.
subject: - stores the subject of the notice.
location: - stores the location address of the notice file.
branch: - stores the branch for which the notice is.
date: - stores the date on which the file was uploaded.

Notes Table
refno: - stores the unique reference no. of the notes file.
subject: - stores the subject of the notes.
location: - stores the location address of the notes file.
branch: - stores the branch for which the notes is.
date: - stores the date on which the file was uploaded.
Quotation table
sno: - stores the serial no. of the quotations.
quoatations: - stores the quotations.

Time Table
class_id:- stores the unique id of each class.
1 to 8:- stores the names of subject of that period.

BIBLIOGRAPHY

i. Core Java2- Volume II-Advanced Features

By Cay S. Horstmann & Gary Cornell
On Pearson Education
ii. Java2 Black Book
By Steven Holzner
On Dreamtech Press
iii. JavaScript Bible
By Danny Goodman
On IDG BOOKS
iv. Core Servlets and JavaServer Pages Volume 1:Core Technologies
By Marty Hall & Larry Brown
On Pearson Education