TCS Internal

Student Management System Case

study

Introduction to Student Management System Case Study

The Student Management System (SMS) presented in this case study is a robust solution
designed to meet the diverse needs of both students and administrative personnel.
The SMS leverages modern web technologies, including Java Server Pages (JSP) and Servlets, to
create a user-friendly and secure platform for student data management. This system caters to two
primary user roles: students and administrators (admin). Students can utilize the SMS to register
themselves, update their personal information, and access vital academic details. On the other hand,
administrators have advanced privileges, enabling them to manage student records, courses, and
more.

Frontend
1. Main Page: This page will be reflected on running the application. The User should be able
to view Home, Student Registration and Admin/Student Login.

2. Admin/Student Login: According to the ID and password entered user will be taken to
Admin or Student portal
TCS Internal

3. Admin Portal:

Home page for admin. This page will display a welcome message

Admin Operations:

The admin can:

 Add/register students
 Add courses
 Update courses
 Update student details
 Delete courses
 Delete students

4. Add Student: Add student tab in Admin portal will take the user/admin the below shown
page here user/admin will be able to add the students in the database
TCS Internal

5. Add Course: Add course tab in Admin portal will take the user/admin the below shown page
here user/admin will be able to add the course specifications in the database

6. Course Update/Delete: Course update/delete tab will take the user/admin to this page
where the user/admin will get the option to update the course specifications or delete the
course altogether
TCS Internal

7. Student Update/Delete: Student update/delete tab will take the user/admin to this page
where the user/admin will get the option to update the student details or delete the student
altogether

8. Update course

9. Student home page: The student is taken to the student home page after login, where the
student can click on:
TCS Internal

10. My Data: My data tab will take the user/student to below page where the user/student will
be able to view and update his/her details namely:
 Student First Name
 Student Last Name
 Student Email
 Gender
 Birthdate
 Student SSN ID
 Branch Code

11. Update student

TCS Internal

12. View Course: The user/student will be able to view the courses he/she is enrolled in.

13. Update Password: The Update password tab will allow the user/student to update his/her
password.
14. Logout: Clicking on logout button will take the user back to the main page (index page)
logging out the user

Backend
The backend of the Student Management System (SMS) serves as the core engine that handles data
processing, storage, and business logic. It consists of Servlets handling HTTP requests, a relational
database for data storage, a data access layer for database interaction, and business logic governing
user authentication, data validation, and access control.

The architecture follows the Model-View-Controller (MVC) pattern, where the Bean Classes
represent the Model (data), the DAO Layer manages data access, and the Controllers act as the
Controllers (business logic) that interface with the Views (JSP files).
TCS Internal

 The index.jsp file refers to the main or the home page.

 add.jsp allows the admin to register a new student.

TCS Internal

 Add-course.jsp allows the admin to add new course for the students
 Update-passwd.jsp allows the students to update their own passwords
 Update-course.jsp allows the students to update courses
 Update-student.jsp allows the students to update their own passwords
 Login-failed.jsp will display an error message when the user inputs the wrong password
 Login-success.jsp will authenticate and authorize the user to the respective home pages.

 The below highlighted controllers and JSP files are corresponding to Admin
TCS Internal

 Example: In the below shown screenshot we can see that the updateStudentController.java
is used when user with Admin access wants to update student details.

 The below highlighted controllers and JSP files are corresponding to Student
TCS Internal

 Example: In the below shown screenshot we can see that the StudentControllerServlet.java
is used when user with student access wants to update student details.
TCS Internal

 Rest all JSP pages and controllers for e.g., index.jsp , login.jsp, LogoutServlet.java etc. Will be
common to all.

Log Configuration:

Inside Src folder you will find a log4j.properties file as highlighted in the below screenshot. Kindly
change the log path to your system path. This can either be done by just replacing the highlighted
part by your Emp ID or you can go ahead and change the whole path to you desired location.

Database
The database for the student management system will be containing three tables namely student,
student_login, course. Please refer the screenshots shown below for specification details.

 Student Table - studentId is primary key of type integer, not null and start with 10001 and is
auto-incremented by 1

 course Table - courseId is primary key of type varchar

 student_login Table - studentId is primary key of type integer referencing to

studentId(Foreign key) from student table
TCS Internal

Setting up Derby database:

Before running the application, you will need to create a Derby database. You will find the sql file in
the case study folder itself as shown in below screenshot.

Step to create Database:

1. Go to database explorer, right click on Database connection and click on new

2. Now select Derby and click on next

TCS Internal

3. Now test connection for ping succeeded and click on finish

TCS Internal

4. Copy the URL path for your database and paste in helper class
TCS Internal

5. Connect with the New Derby created

6. Open the SQL file given in the case study and select the type to Derby and name to New
Derby (the new Derby created by you) and execute the entire SQL scrapbook
7. Your DB is created. Now disconnect the Derby and run the application on server.