AUTOMATED STUDENT

REGISTRATION SYSTEM
A project Report for Industrial Training

Submitted by

AYUSH RAJ(16/ECE/108) [Uni roll :10300316108]

In Partial fulfilment of the requirement for the Degree

Of
BACHELOR OF TECHNOLOGY
In
ELECTRONICS AND COMMUNICATION ENGINEERING
At
HALDIA INSTITUTE OF TECHNOLOGY
1
 PREFACE
Industrial Training Report is the essential part of the Industrial Training
(EC781) of the B. Tech course offered by engineering or Technology
Institutes affiliated by Maulana Abul Kalam Azad University of Technology
i.e., MAKAUT

It is the great opportunity for me to have the BACHELOR OF TECHNOLOGY

(B. Tech) in
HALDIA INSTITUTE OF TECHNOLOGY, HALDIA.
In the accomplishment of this degree.

I am submitting Industrial Training Report written on

AUTOMATIC STUDENT REGISTRATION SYSTEM

Subject of the limitation of the time efforts and resources every possible
attempt has been made to study the problem deeply. The whole project is
the measured through the Questionnaire, the data further analyzed and
interpreted and the result was obtained.

2
 DECLARATION
I declare that this written submission represents my ideas in my own words
and where others ideas or words have been included. I have adequately
cited and referenced the original sources. I also declare that I have adhered
to all principles of academic honesty and integrity and have not miss
represented or fabricated or falsified any idea/data/fact/source in my
submission. I understand that any violation of the above will be cause for
disciplinary action by the institute and can also evoke panel action from the
sources which have thus not been properly cited or from whom proper
permission has not been taken when needed.

___________________
(Signature)

___________________
(Name of the student)

___________________
(Roll No.)

Date: _______________

3
 ACKNOWLEDGEMENT
I take this opportunity to express my deep gratitude and sincerest thanks to our
project mentor, Mr. Ratan Kumar for giving most valuable suggestion, helpful
guidance and encouragement in the execution of this project work.

The assignment cannot be completed without the effort and co-operation from our
group members. Last but not the least, we would like to express our gratitude to our
friends and respondents for the support and willingness to spend some times with us
to fill in the questionnaires.

4
 ABSTRACT
The system will be web based and will have two implementations i.e. client
side (student) and server side (J2EE,Servlets,Jsp) . The server side
implementation can only be accessed over the university intranet while the
client side can be accessed over the internet

Once a prospective student achieves an acceptable rank and accepts the

offer of admission they will be shifted to the new registration module and
allotted a unique roll number. The admin will scrutinize the documents of
users in the new registration module and notify them about discrepancies.
The new student will be able to pay initial fees through this module and will
be notified about the next process through this module. This module will
automatically update the student database with the details of the new
student.

5
 TABLE OF CONTENT
CONTENT Page no

Introduction 10

Project Scope 12

Requirement Specification

 Functional Requirement
13 - 15
 Hardware Requirement
 Software Requirement

Database Design

 Table: Clerk
 Table: Course 16 - 18

 Table: Student
 Table : Student Course

Screenshots 19 - 30

6
Application Work

 Using Case Diagram

 Using Case Description 31 - 41

Future Scope Of Improvement 42

Conclusion 43

INTRODUCTION
What is Advance Java?
"Core Java" AFAIK is not an official, well-defined term. It is, however, the title of a book from
Sun that introduces Java as a language and the most important parts of the Java SE Standard
API - and that's probably what most people think of when they hear the term.

"Advanced Java" is everything that goes beyond that - most importantly the APIs defined in
Java Enterprise Edition, i.e. Servlet programming, Web Services, the Java Persistence API, etc

"Core Java” means "stand -alone" java applications whereas “Advanced java” means java
applications that runs on servers i.e., these are the “web applications".

Advance java comprises mainly of three things:

1. JSP: JSP stands for Java Server Pages. JSP is used to build up forms. it’s used as a
view part of the MVC model. if somebody don’t know to wrote the code in JSP they
can directly use JavaScript or HTML with CSS
2. SERVLET: servlet is the controller part of MVC model. this is used to read the
content of data whatever is coming from the view part. Eg: reading form data. I
someone doesn’t know how to write servlet code then they can go for frameworks
like Spring MVC
3. JDBC: this is the model part of the MVC model. this is used for getting connected
with database and performing database operations like storing and retrieving data.
if someone doesn’t know how to write database code then they can go for a

7
 framework called Hibernate. Other frameworks include Spring, Apache Struts, Spark,
Vaadin etc

8
 PROJECT SCOPE
Project “Automated Student Registration System” while doing this Project we faced
lots of challenges but our ultimate goal was to satisfy all functionality demanded by
stakeholder and make the project user friendly such that non-technical User easily
understand and access. We have also 15 days’ time deadlines to complete this project
and we complete project within this deadline. We deals this project on basis of our
three types of Users Admin,Student,Clerk. All these users have certain responsibility
and limitations or accessibility which we have to implements.

9
REQUIREMENT SPECIFICATION
 Functional Requirement
Function id Requirement Must/Optional Comment
statement
FR01 This web application Must This Home Page
must require a requirement is must
Home Page whether
the user visiting is
new one or existing
one

FR02 This web app Must

required a login
where three kind
user may access
which have different
accessibility or
restriction to access
and manipulation of
data

FR03 Different Home Must

page for
Student,Admin and
Clerk so that they
easily access to their
information’s they
required

FR04 In the case of Must

database design we
required 5 Tables
mention below to
store the details in

10
 our database so that
our user can easily
access those details
when they required

FR05 We have many Must

functionalities for all
our 3 users .Student
can registered to
any courses
available ,Clerk can
access student
,Admin can access
all the details they
can even manipulate
all the courses
available

 Hardware Requirement
Client Machine Server Machine
HDD 200 MB HDD 320 GB
Processor Dual Core or newer Processor Dual Core or newer
processor processor
Memory 1 GB Memory 4 GB

11
 Software Requirement

 Front End
 Html
 Cascading Style Sheet (CSS)
 Java Script
 Back End
 Java
 Java Database Connectivity (JDBC)
 Java Server Pages (JSP)
 Servlet
 Application Server
 Apache Tomcat
 Database Server
 MySQL

12
DATABASE DESIGN
name address
roll

mobile
student
duration
email
Course
course Name
password
Student
capacity roll
fee

Clerk
password email

Registe
Admin r
user
name

course
name

salary
id

password
clerk

address
name
13
 TABLE DESIGN

 `Table: Clerk

Field Type Null Key Default

Id Varchar (200) NO PRI NULL

Name Varchar (20) YES NULL

Age Varchar (20) YES NULL

Address Varchar (20) YES NULL

Salary Varchar (20) YES NULL

Email Varchar (20) YES NULL

Password Varchar (20) YES NULL

 Table: Course
Field Type Null Key Default Extra

courseName varchar(12) NO PRI NULL

courseDuration varchar(12) YES NULL

courseFee int(11) YES NULL

courseStartDate varchar(12) YES NULL

Capacity int(11) YES NULL

14
Avail int(11) YES NULL

 Table: Student
Field Type Null Key Default

Roll Int (11) NO PRI NULL

Name Varchar (20) YES NULL

Address Varchar (20) YES NULL

Mobile Varchar (20) YES NULL

Email Varchar (20) YES NULL

Password Varchar (20) YES NULL

 Table: Student Course

Field Type Null Key Default

Roll Int (11) YES NULL

courseName Varchar (20) YES NULL

15
 SCREEN SHOTS
Home Page: index.jsp

16
Login Page: loginPage.jsp

Admin Home: AdminHome.jsp

Add New Course: addCourse.jsp

17
Couse Update Success: courseSuccess.jsp

18
Get Course Details: getCourse.jsp

Course Details: courseDetail.jsp

All Course Detail: allCourse.jsp

19
Course Update: courseUpdate.jsp

Course Updated Successful: updateCourseSucess.jsp

20
Register Clerk: ClerkRegister.jsp

21
Clerk Registration success: clerkRegSuccess.jsp

Get Clerk Detail: getClerk.jsp

22
Clerk Detail page: clerkDetails.jsp

Get All Clerk Detail: allClerk.jsp

23
Clerk Update Form: clerkUpdate.jsp

Clerk Details updated Successfully: updateClerkSucess.jsp

24
 studentRegister.jsp

regSuccess.jsp(student registered successfully)

studentHome.jsp

25
clerkHome.jsp

updatePassword.jsp
26
allStudentdetails.jsp

27
enrollStudents.jsp

APPLICATION WORKFLOW
 USING CASE DIAGRAM

Case 1: Admin Case Diagram

28
 Register
Clerk View/mod
ify clerk

Add
course

View/mod
ify course

Admin logout

29
 Case 2: Clerk Case Diagram

Enrol
Student View/mod
ify profile

View all
student

View all
courses

Clerk logout

30
 Case 3: student case Diagram

View
profile Update
profile

View
course
details

Enrol
course
Student logout

31
 USING CASE DESCRIPTION
Admin
Case I: Login Description

CASE Login

Goal All users logging into the system should be authenticated using a
unique login-id and password (operations to be supported based
on type of user)
Preconditions If the user type is ‘Admin’, credential details should exist.
If the user type is ‘Clerk’, he/she should be registered by the
admin.
If the user type is ‘Student’, he/she should be registered by the
himself or clerk.
Success End Condition If the user type is ‘Admin’, then redirect to the Admin page.
If the user type is ‘Clerk’, then redirect to the Clerk page.
If the user type is ‘Student’, then redirect to the Student page.
Failed End Condition The end user is redirected to an Error Page, and/or is asked to re-
enter login credentials.

Primary, Secondary Admin, Clerk, Student.

Actors
Trigger Login button

DESCRIPTION Step Action

1 Enter Login credentials (id & password)
2 Click on Login button
3 If id & password is Success, then identify user type
Display appropriate(Admin/Clerk/student) home page
Step Branching Action
1 If 'id' is not existing then return with requesting for
registration
2 If password is not matching return with suitable error
message say 'Re-enter id & password'
Related Not Applicable
Information/Use cases
Priority P1
Performance 5 seconds
Frequency 10 / hour
Assumptions Admin/Customer/Student login credentials are available in the
database and others are already registered with their credentials

32
 Case Description to Add new courses

USE CASE The admin should be able to add new course and its detail.
Goal To enable Administrator to create and add new course.
Preconditions Administrator must be logged in to be able to create a new course.
Success End Condition “Redirect to Admin home page”

Failed End Condition "Redirect to Error Page"

Primary, Secondary Administrator
Actors
Trigger 'Add course button’
DESCRIPTION Step Action
1 Provide appropriate course details
2 Click on Add course button
Step Branching Action
1 If failed to add more course details
2 Display appropriate message to the admin
Related Not applicable
Information/Use cases
Priority P1
Performance Approx. 4 sec
Frequency 2 / Month
Assumptions Course Table is available in the database

Case Description to get all course Detail

USE CASE # The admin should be able to get a course detail.
Goal To enable Administrator to get course detail using course name.
Preconditions Administrator must be logged in to be able to fetch course detail.
Success End Condition “Redirect to Course Detail Page”

Failed End Condition "Redirect to No course Exist"

Primary, Secondary Administrator
Actors
Trigger 'Get Course Detail Button’
DESCRIPTION Step Action
1 Provide appropriate Course Name
2 Click on Get course Detail Button
Step Branching Action
1 If failed to no course exist
2 Display appropriate message to the admin
Assumptions Course Details are available in the database

33
 Case Description to get all course Detail
USE CASE # The admin should be able to get all course detail and modify it.
Goal To enable Administrator to get All course Detail.
Preconditions Administrator must be logged in to be able to fetch course detail.
Success End Condition “Redirect to Course Detail Page”

Failed End Condition "Redirect to Admin home Page"

Primary, Secondary Administrator
Actors
Trigger 'Get All Course Detail Link’
DESCRIPTION Step Action
1 Select Get all courses link.
Step Branching Action
1 If failed to Admin Home Page.
2 Display appropriate message to the admin
Assumptions Course Details are available in the database

Case Description to Update Course Detail

USE CASE # The admin should be able to modify a course.
Goal To enable Administrator to get update a particular course.
Preconditions Administrator must be logged in to be able to fetch course detail.
Success End Condition “Redirect to Update course page with its initial details”

Failed End Condition "Redirect to Couse Updating Fails"

Primary, Secondary Administrator
Actors
Trigger 'Update link in the table’
DESCRIPTION Step Action
1 Click Get all course Detail link, from Admin home Page
2 Click on Update button on the particular course needs
to be updated
3 Fill the necessary course details
4 Select update Button to update
Step Branching Action
1 If failed to Updating Fail Page
2 Display appropriate message to the admin
Assumptions Course Details are available in the database

34
 Case Description for Register Clerk
USE CASE # The admin should be able to register a clerk
Goal To enable Administrator to register a clerk with its details required.
Preconditions Administrator must be logged in to be able register a clerk.
Success End Condition “Redirect to Clerk Registered Successfully”

Failed End Condition "Redirect to Clerk Registration Fail Page"

Primary, Secondary Administrator, clerk
Actors
Trigger 'Register Clerk Button’
DESCRIPTION Step Action
1 Click on Register Clerk Link from Admin Home page
2 Give the credentials needed to register a clerk.
3 Click on Register button to register
Step Branching Action
1 If failed to Registration Fails Page
2 Display appropriate message to the admin
Assumptions Clerk table is present in the database

Case Description to get Clerk Detail

USE CASE # The admin should be able to get a clerk detail.
Goal To enable Administrator to get clerk detail using clerk Id.
Preconditions Administrator must be logged in to be able to fetch clerk detail.
Success End Condition “Redirect to Clerk Detail Page”

Failed End Condition "Redirect to No clerk Exist"

Primary, Secondary Administrator
Actors
Trigger 'Get Clerk Detail Button’
DESCRIPTION Step Action
1 Provide appropriate Clerk Id number
2 Click on Get clerk Detail Button
Step Branching Action
1 If failed to no clerk exist
2 Display appropriate message to the admin
Assumptions Clerk details are available in the database

35
 Case Description to get all Clerk Detail
USE CASE # The admin should be able to get all clerk detail and modify it.
Goal To enable Administrator to get All clerk Detail.
Preconditions Administrator must be logged in to be able to fetch clerk detail.
Success End Condition “Redirect to Clerk Detail Page”

Failed End Condition "Redirect to Admin home Page"

Primary, Secondary Administrator
Actors
Trigger 'Get All Clerk Detail Link’
DESCRIPTION Step Action
1 Select Get all courses link.
Step Branching Action
1 If failed to Admin Home Page.
2 Display appropriate message to the admin
Assumptions Clerk Details are available in the database

Case Description to Update Clerk Detail

USE CASE # The admin should be able to modify a clerk.
Goal To enable Administrator to get update a particular clerk.
Preconditions Administrator must be logged in to be able to fetch clerk detail.
Success End Condition “Redirect to Update clerk page with its initial details”

Failed End Condition "Redirect to Clerk Updating Fails"

Primary, Secondary Administrator
Actors
Trigger 'Update link’
DESCRIPTION Step Action
1 Click Get all clerk Detail link, from Admin home Page
2 Click on Update button on the particular clerk needs to
be updated
3 Fill the necessary clerk details
4 Select update Button to update
Step Branching Action
1 If failed to Updating Fail Page
2 Display appropriate message to the admin
Assumptions Clerk Details are available in the database

36
 Student
Case I: Login Description

CASE Login

Goal All users logging into the system should be authenticated using a
unique login-id and password (operations to be supported based
on type of user)
Preconditions If the user type is ‘Admin’, credential details should exist.
If the user type is ‘Clerk’, he/she should be registered by the
admin.
If the user type is ‘Student’, he/she should be registered by the
himself or clerk.
Success End Condition If the user type is ‘Admin’, then redirect to the Admin page.
If the user type is ‘Clerk’, then redirect to the Clerk page.
If the user type is ‘Student’, then redirect to the Student page.
Failed End Condition The end user is redirected to an Error Page, and/or is asked to re-
enter login credentials.
Primary, Secondary Admin, Clerk, Student.
Actors
Trigger Login button

Case Description to View & Update profile

USE CASE Student can able to view their details when they are successfully login
and even they update some of the details of their profile
Goal To view the student details and even they update their some of the
details
Preconditions Student must be logged in to be able to update their profile.
Success End Condition “Redirect to StudentProfile page or Studentprofileupdate page”

Failed End Condition "Redirect to Error Page if update is not able to done"
Primary, Secondary Administrator ,student,clerk
Actors
Trigger 'Add update button’
DESCRIPTION Step Action
1 Click on view profile their update profile button
2 Click on Update
Step Branching Action
1 If failed to update the profile
2 Display appropriate message to the student
Related Not applicable
Information/Use cases
Priority P1
Performance Approx. 4 sec

37
 Case Description to View all courses and Register
USE CASE # Student can view all the courses available and register in them
and they can even view the courses they had already registered
full details
Goal To enable student to register for the courses
Preconditions Student can be able to register on a particular courses
Success End Condition “Redirect to Registration success”

Failed End Condition "Redirect to Not available in place of Register"

Primary, Secondary Admin,student,clerk
Actors
Trigger 'Get All enroll course details’,’register’
DESCRIPTION Step Action
1 Select Register link.
Step Branching Action
1 If failed to Not applicable
2 Display appropriate message to the student
Assumptions Course Details are available in the database

Clerk
Case I: Login Description

CASE Login

Goal All users logging into the system should be authenticated using a
unique login-id and password (operations to be supported based
on type of user)
Preconditions If the user type is ‘Admin’, credential details should exist.
If the user type is ‘Clerk’, he/she should be registered by the
admin.
If the user type is ‘Student’, he/she should be registered by the
himself or clerk.
Success End Condition If the user type is ‘Admin’, then redirect to the Admin page.
If the user type is ‘Clerk’, then redirect to the Clerk page.
If the user type is ‘Student’, then redirect to the Student page.
Failed End Condition The end user is redirected to an Error Page, and/or is asked to re-
enter login credentials.
Primary, Secondary Admin, Clerk, Student.
Actors
Trigger Login button

38
 Case Description to View & Update profile

USE CASE Clerk can able to view their details when they are successfully login
and even they update some of the details of their profile
Goal To view the clerk details and even they update their some of the
details
Preconditions Clerk must be logged in to be able to update their profile.
Success End Condition “Redirect to ClerkProfile page or Clerkprofileupdate page”

Failed End Condition "Redirect to Error Page if update is not able to done"
Primary, Secondary Administrator , clerk
Actors
Trigger 'Add update button’
DESCRIPTION Step Action
1 Click on view profile their update profile button
2 Click on Update
Step Branching Action
1 If failed to update the profile
2 Display appropriate message to the student
Related Not applicable
Information/Use cases

Case Description to get all course Detail

USE CASE # The clerk should be able to get all course detail and modify it.
Goal To enable Clerk to get All course Detail.
Preconditions Clerk must be logged in to be able to fetch course detail.
Success End Condition “Redirect to Course Detail Page”

Failed End Condition "Redirect to Clerk home Page"

Primary, Secondary Administrator ,clerk
Actors
Trigger 'Get All Course Detail Link’
DESCRIPTION Step Action
1 Select Get all courses link.
Step Branching Action
1 If failed to clerk Home Page.
2 Display appropriate message to the admin
Assumptions Course Details are available in the database

39
 Case Description to enroll any Student
USE CASE # The clerk should be able to enroll any student to a particular
courses if he/she not registered
Goal To enable Clerk to enroll a particular student on a course
Preconditions Clerk must be logged in to be able to fetch course detail.
Success End Condition “Redirect to Enroll student screen Page”

Failed End Condition "Redirect to Clerk home Page"

Primary, Secondary Administrator ,clerk
Actors
Trigger 'Get Enroll Link’
DESCRIPTION Step Action
1 Select Enroll link.
Step Branching Action
1 If failed to clerk Home Page.
2 Display appropriate message to the clerk
Assumptions Course Details are available in the database

40
 FUTURE SCOPE OF IMPROVEMENT
Since the project has been done using html, css, Java Script for the front-
end development. And the back-end is developed using JDBC, Java, JSP i.e.;
using Apache tomcat server.
The technologies used are in high demand in the current scenario with the
scope of enhancement.
So, therefore this project can be further enhanced using more advance java
technologies.

41
 CONCLUSION

This new system is surely to benefit the organization, with various

registration and modification methodology. The system has various level of
access restriction. The addition or modification is directly reflected in
database design to the handle multiple query demanded by various level of
accessor.

42
 APPENDICES

 MVC: Model View Controller

 JDBC: Java Database Connectivity
 JSP: Java Servlet Page

43
REFERENCES/BIBLIOGRAPHY
 https://javatpoint.com/java-tutorial
 https://stackoverflow.com/
 https://w3schools.com/
 https://geekforgeeks.com/

44