DYNAMIC ALUMNI WEBSITE

A Project Report
Submitted by
AANISHA ALMAAZ S
(Reg. No: 20384101)

In partial fullfilment of the requirements for the award of the degree of

MASTER OF SCIENCE (INTEGRATED) IN COMPUTER SCIENCE

Under the guidance of

Dr. Krishnapriya
(Asst. Professor, Department of Computer Science)

DEPARTMENT OF COMPUTER SCIENCE

PONDICHERRY UNIVERSITY
APRIL 2025
 BONAFIDE CERTIFICATE

This is to certify that the project work entitled "DYNAMIC ALUMNI

WEBSITE” is a Bonafide record of work done by AANISHA ALMAAZ
S (Reg. No. 20384101) in partial fulfillment of the requirements for
the award of the degree of Master of Science (Integrated) in Computer
Science, in the Department of Computer Science, School of Engineering
and Technology, Pondicherry University.
To the best of my knowledge, this work has not been submitted elsewhere
for the award of any degree.

PROJECT GUIDE HEAD OF THE DEPARTMENT

Dr. Krishnapriya Dr. S.K.V. Jayakumar
Assistant Professor Professor and HOD
Department of Computer Science Department of Computer Science
Pondicherry University Pondicherry University

Submitted for the Viva-Voce Examination held on 29-04-2025.

INTERNAL EXAMINER EXTERNAL EXAMINER

i
 Abstract

This project introduces an interactive alumni website for the Department

of Computer Science, Pondicherry University, aimed at fostering stronger
connections between alumni, students, and faculty. The platform supports
networking, mentorship, and the sharing of departmental updates, encour-
aging alumni to stay engaged and contribute back to the institution. A key
feature is the Alumni Directory, which helps reconnect former classmates,
and the Student Directory, where current students can showcase their skills
and projects as a digital portfolio. These profiles can also be presented to
recruiters during placement drives or when inviting companies to campus,
enhancing students’ career opportunities. The system additionally tracks
alumni career paths—such as higher studies or employment—for reporting
to accreditation bodies like NAAC. Overall, the platform enhances commu-
nity building and supports institutional growth.

ii
 Acknowledgements

I would like to express my deepest gratitude to my guide, Dr. Krish-

napriya for her valuable guidance, consistent encouragement, personal car-
ing, timely help and providing me with an excellent atmosphere for doing
research. All through the work, in spite of her busy schedule, she has
extended cheerful and cordial support to me for completing this project.

iii
Contents

1 Introduction 1
1.1 About The Project . . . . . . . . . . . . . . . . . . . . . . 1
1.2 About The Organization . . . . . . . . . . . . . . . . . . . 2

2 System Analysis 4
2.1 Requirement Analysis . . . . . . . . . . . . . . . . . . . . 4
2.1.1 Functional Requirements . . . . . . . . . . . . . . . 4
2.1.2 Non-Functional Requirements . . . . . . . . . . . . 5
2.1.3 User Requirements . . . . . . . . . . . . . . . . . . 6
2.1.4 System Requirements . . . . . . . . . . . . . . . . 7
2.2 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1 User Authentication . . . . . . . . . . . . . . . . . 8
2.2.2 Profile Management . . . . . . . . . . . . . . . . . 9
2.2.3 Admin Dashboard . . . . . . . . . . . . . . . . . . 10
2.2.4 Job/Internship Opportunity . . . . . . . . . . . . . 12
2.2.5 Alumni/Student Directory . . . . . . . . . . . . . . 13

3 System Design 15
3.1 UI design . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Architectural design . . . . . . . . . . . . . . . . . . . . . 17
3.3 Database Design . . . . . . . . . . . . . . . . . . . . . . . 17
3.4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . 22
3.6 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . 28

4 Implementation 29
4.1 Implementation Design . . . . . . . . . . . . . . . . . . . . 29
4.1.1 Frontend (React.js + Tailwind CSS) . . . . . . . . 29
4.1.2 Backend (Django REST Framework) . . . . . . . . 29

iv
CONTENTS v

4.1.3 Database(MySQL) . . . . . . . . . . . . . . . . . . 29
4.1.4 Image Handling . . . . . . . . . . . . . . . . . . . 30
4.1.5 Hosting . . . . . . . . . . . . . . . . . . . . . . . 30

5 Testing 31
5.1 Testing Types . . . . . . . . . . . . . . . . . . . . . . . . 31

6 Conclusions and Future Work 32

6.1 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2 Future work . . . . . . . . . . . . . . . . . . . . . . . . . 32

7 Codes 34

References 36

Appendices 37

A Codes) 37

B Screenshots 38
Chapter 1

Introduction

1.1 About The Project

This project focuses on developing an interactive alumni website for the De-
partment of Computer Science, Pondicherry University, to strengthen
the connection between alumni and the department. The platform is de-
signed to facilitate ongoing engagement, foster a sense of community, and
maintain meaningful relationships with former students. Beyond serving as
a hub for networking and communication, the system also collects data on
alumni career paths—specifically, whether graduates pursue higher studies
or enter the workforce. This data is especially important for departmental
reporting to accreditation bodies such as the National Assessment and
Accreditation Council (NAAC). Maintaining an updated alumni database
also allows current students to connect with graduates for mentorship, in-
ternships, and career guidance.

Some of the key modules such as Events, News, Blogs, Payement, Men-
torship, User profile, Admin Dashboard(populated by analytics of the
student/alumni profile data) a dynamic Home page, Gallery and much
more. Each of these components is integrated with a backend API to en-
sure content is current and delivered dynamically. Staying informed about
departmental events, even after leaving campus, can evoke a sense of nos-
talgia among alumni. Access to updates such as research papers published
by faculty, student achievements, and departmental milestones helps alumni
stay connected and may encourage them to contribute back to the insti-
tution that helped shape their careers. The information is organized using
category-based filtering, allowing users to easily navigate the updates and
highlights that interest them.

1
CHAPTER 1. INTRODUCTION 2

A key feature of the platform is the Alumni Directory, which enables

alumni to reconnect and catch up with old classmates, fostering stronger
bonds within the department’s extended community. In addition, the plat-
form introduces a Student Directory, where current students can up-
load their profiles, including skills, projects, and links to GitHub or GitLab
repositories. This acts as a digital portfolio, providing a more interactive
and modern alternative to traditional résumé formats. It can also serve as
a centralized space to showcase student talent to prospective recruiters
and companies during placement drives.

The platform is built using React.js for the frontend and Django REST
Framework for the backend. It emphasizes responsiveness, user experience,
and secure data handling, offering a robust and scalable solution that sup-
ports the department’s outreach goals and long-term alumni and student
engagement.

1.2 About The Organization

The platform is specifically tailored to PUDoCS – Pondicherry Univer-

sity Department of Computer Science, a premier academic department
within Pondicherry University, known for its excellence in teaching, research,
and innovation in the field of computer science. The department offers in-
tegrated and postgraduate programs that combine theoretical depth with
practical skills, helping students build a strong foundation for careers in
academia, industry, and research.

Over the years, the department has produced a diverse group of grad-
uates who have gone on to contribute in various sectors across India and
abroad. While these alumni remain an important part of the department’s
legacy, there has been no dedicated digital platform to maintain regular
communication, facilitate networking, or support collaboration between the
department and its alumni.

This lack of a centralized system has also limited opportunities for current
students to benefit from alumni guidance, mentorship, and career support.
Recognizing this gap, the department initiated the development of a dy-
namic alumni platform aimed at strengthening connections, supporting
student-alumni interaction, and preserving institutional history. This project
CHAPTER 1. INTRODUCTION 3

not only addresses a long-standing need, but also aligns with the depart-
ment’s larger goals of building community, supporting student growth, and
improving institutional outreach.
Chapter 2

System Analysis

System analysis involves studying the current limitations (such as the lack
of a unified platform for alumni engagement) and identifying how a new
system can overcome these through structured planning, design, and inte-
gration of various components. It also helps in modeling how data flows
through the system and how different users interact with it.

The goal is to develop a scalable, secure, and user-friendly platform that

connects alumni, students, and administrators efficiently, while also sup-
porting backend administrative needs and front-end user engagement.

2.1 Requirement Analysis

Requirement analysis is a crucial phase in the software development lifecy-

cle where the needs and expectations of users are gathered, analyzed, and
documented. It helps in understanding what the system should accomplish
and lays the foundation for designing, developing, and testing the applica-
tion.

In this project, requirement analysis defines the scope of the alumni platform
for the Department of Computer Science, Pondicherry University. It ensures
that all user roles—students, alumni, and administrators—have their needs
addressed through clearly defined system behavior.

2.1.1 Functional Requirements

Functional requirements define the core operations of the system—what it

should do. These are directly related to the features and functionalities
provided to different users.

4
CHAPTER 2. SYSTEM ANALYSIS 5

• Users should be able to register and log in securely.

• The system shall allow users to view, edit, and update their personal
profiles.
• Admins should be able to post news and events.
• Admins should be able to add students and handle student to alumni
transition.
• The dashboard shall display analytics on user demographics, activity,
and engagement.
• The system shall allow users to register for events.
• Users shall be able to browse news articles by category or date.
• Admins and authorized users shall be able to post job or internship
openings.
• Users shall be able to create discussion threads.
• The system shall notify users of newly added events, announcement
by sending an Email.
• Users can view event galleries, read blogs, and browse the alumni
directory.
• The system shall support online payments for event registration or
donations.
• The homepage shall provide quick navigation to major modules (Di-
rectory, Events, Blogs, etc.).
• Alumni directory shall display employment and education details.
• Student directory shall display skills and projects.
• Users shall be able to send connection or mentorship requests.

2.1.2 Non-Functional Requirements

Non-functional requirements describe how the system performs, focusing

on its quality attributes rather than behaviors.
• Data should be securely transmitted (e.g., HTTPS, JWT).
CHAPTER 2. SYSTEM ANALYSIS 6

• The system should have a user-friendly interface.

• The system should be responsive across devices.
• Optimized SQL Query for fast retrieval of data.
• The platform should support concurrent users without performance
issues.

2.1.3 User Requirements

User requirements represent what different stakeholders expect from the

system. Each user type has distinct needs and expectations:

Alumni
• Stay updated with departmental news and events.
• Reconnect with old classmates through the Alumni Directory.
• Can request to become mentors by submitting a mentor request form.
• Can be part of a forum discussion.
• Requests Letter of Recommendation from PUDoCS
Student
• Explore events and department activities through the Gallery and News
sections.
• Create and maintain digital profiles highlighting their skills, projects,
and repository links.
• Can view mentor profiles and reach out through the platform or via
provided contact links.
• Can be part of a forum discussion.
• Requests Letter of Recommendation from PUDoCS
Alumni
• Post news, blogs, and event announcements.
• Can review, approve, or reject mentor requests.
CHAPTER 2. SYSTEM ANALYSIS 7

• Moderate content submitted by users.

• Can view analytics based on alumni and student profile data.
• Handles student to alumni transitions.

2.1.4 System Requirements

These are the technical requirements needed to develop, deploy, and main-
tain the system effectively.

Hardware Requirements
• Minimum 8 GB RAM (for development and testing environments).
• Minimum 50 GB storage (for server hosting and media)
• Hosting: VPS or cloud hosting (e.g., AWS, DigitalOcean)
Software Requirements
• Operating System:GNU/Linux or Windows 10/11.
• Backend: Python 3.x, Django REST Framework.
• Frontend: React.js, Tailwindcss
• Database: MySQL
• Version Control: Git and GitLab
• Testing Tool: Insomnia for API testing
CHAPTER 2. SYSTEM ANALYSIS 8

2.2 Use Cases

Use case diagrams visually represent how users interact with a system. They
help identify key system functionalities and user roles (like alumni, students,
admins), focusing on what the system should do rather than how it’s done.

The goal is to clearly define system requirements and ensure all user inter-
actions are considered during design, making the system more user-focused
and efficient.

2.2.1 User Authentication

Actors
• User
• Computer System
Use Cases
• Register
• Login
• Details verification
• Email Verification
• Registration Confirmation
Relations
• User can register, login, and access their profile.
• Register includes verification of PU alumni/student, email verification
and registration confirmation.
• Computer System handles email verification and confirmation.
CHAPTER 2. SYSTEM ANALYSIS 9

Figure 2.1: User Authentication Use Case Diagram.

2.2.2 Profile Management

Actors
• Registered Users - Alumni, Student, Staff
• Admin
• Database System
Use Cases
• Edit Profile (add/delete education, skills, etc.)
• Change Password
• Upload Resume
• Add Blogs
• Request Mentorship / LOR
• Approval (Admin)
CHAPTER 2. SYSTEM ANALYSIS 10

Relations
• Registered users manage their profiles, upload resumes, and submit
requests.
• Admin approves mentorship, blogs, and LORs.
• System stores and manages user data.

Figure 2.2: Profile Management Use Case Diagram.

2.2.3 Admin Dashboard

Actors
• Admin
• System (Computer System)
CHAPTER 2. SYSTEM ANALYSIS 11

Use Cases
• Add Batches
• Add/Delete Students/Alumni
• Handle Student to Alumni Transition
• Content Management (Events, News, Blogs)
• Approve/Reject Requests (LOR, Mentor)
• View Analytics
• Filter User Details
Relations
• Admin manages batches, users, and transitions.
• Admin handles content and approvals.
• System supports data handling and automation.
CHAPTER 2. SYSTEM ANALYSIS 12

Figure 2.3: Admin Dashboard Use Case Diagram.

2.2.4 Job/Internship Opportunity

Actors
• Faculty
• Alumni
• Student
• System (Database)
CHAPTER 2. SYSTEM ANALYSIS 13

Use Cases
• Post Job Opportunity
• Search Job Opportunity
• View Job Opportunity
• Bookmark Opportunity
• Job Details (included in posting)
Relations
• Faculty and Alumni can post jobs.
• Students can search, view, and bookmark opportunities.
• The system manages and stores job-related data.

Figure 2.4: Job/Internship Opportunity Use Case Diagram.

2.2.5 Alumni/Student Directory

Actors
• Registered Users
• Non-Registered Users
CHAPTER 2. SYSTEM ANALYSIS 14

• System
Use Cases
• Search Alumni/Student
• View Alumni/Student Profiles
• Register/Login (included for non-registered users)
Relations
• Registered users can search and view profiles directly.
• Non-registered users must register/login before accessing profiles.
• The system manages and secures user access and profile data.

Figure 2.5: Alumni/Student Directory Use Case Diagram.

Chapter 3

System Design

The system design defines the architecture, components, data flow, and
interactions within the Dynamic Alumni Website. It ensures the scalability,
maintainability, and performance of the platform while enabling seamless
collaboration between different user roles such as students, alumni, faculty,
and administrators.

3.1 UI design

The User Interface (UI) of the Dynamic Alumni Website has been carefully
designed to offer a user-friendly, intuitive, and responsive experience across
various devices. The primary goal of the UI design is to make navigation
seamless, maintain consistency, and provide easy access to features for
different user roles such as students, alumni, faculty, and administrators.

Figure 3.1: Navbar

Figure 3.2: Footer

15
CHAPTER 3. SYSTEM DESIGN 16

Figure 3.3: Dropdown Design

Figure 3.4: Forms Design

Figure 3.5: Sidebar

CHAPTER 3. SYSTEM DESIGN 17

Figure 3.6: Table Design

3.2 Architectural design

The system follows a layered architecture with distinct separation between

Presentation (Frontend), Application (Views/Serializers), and Data (Mod-
els/Database) layers. Each layer interacts only with its adjacent layers, pro-
moting modularity, scalability, and ease of maintenance across the Django
backend and React frontend.

Figure 3.7: 3-tier Architectural Design

3.3 Database Design

Database Design is the process of organizing data into structured tables

with clear relationships to ensure efficient storage, access, and integrity. It
helps maintain consistency and supports future scalability.
CHAPTER 3. SYSTEM DESIGN 18

Figure 3.8: User Management Database

CHAPTER 3. SYSTEM DESIGN 19

Figure 3.9: Student/Alumni with Batch Database

CHAPTER 3. SYSTEM DESIGN 20

Figure 3.10: User Profile Database

CHAPTER 3. SYSTEM DESIGN 21

3.4 Class Diagram

A Class Diagram is a type of static structure diagram in UML (Unified

Modeling Language) that describes the structure of a system by showing
its:

• Classes
• Attributes
• Methods (Operations)
• Relationships (like inheritance, association, aggregation)

Figure 3.11: Class Cluster from Admin’s Application

CHAPTER 3. SYSTEM DESIGN 22

Figure 3.12: Class Cluster from User’s Application

3.5 Sequence Diagram

A Sequence Diagram is a type of interaction diagram in UML that shows

how objects interact with each other in a specific order (sequence) over
time.
CHAPTER 3. SYSTEM DESIGN 23

Figure 3.13: User Authentication Sequence Diagram

Description: This sequence diagram captures the process through which a user logs into the system.
The user submits their login credentials, which are then sent to the authentication API. The API
verifies the credentials by querying the database. If the information is valid, a session or token is
generated and sent back to the user, granting access. If invalid, an error message is returned,
preventing login.
CHAPTER 3. SYSTEM DESIGN 24

Figure 3.14: User Profile Sequence Diagram

Description: This diagram represents how a user interacts with their profile. When a user wants to
view or edit their profile, they send a request to the profile API. The API fetches the relevant
information from the database and returns it for display. For updates, the new information is
validated and then saved in the database. A confirmation or error message is returned based on the
operation’s success.
CHAPTER 3. SYSTEM DESIGN 25

Figure 3.15: Admin Dashboard Sequence Diagram

Description: The admin dashboard sequence outlines how administrative users manage the system.
After logging in, the admin can retrieve summaries and statistics, such as user counts or reports, via
the admin API. The admin can also perform actions like activating or deactivating users, approving
content, or managing job posts. All interactions are routed through the API to the database,
ensuring secure and organized control.
CHAPTER 3. SYSTEM DESIGN 26

Figure 3.16: Job/Internship Sequence Diagram

Description: This diagram illustrates the flow for posting and accessing job or internship
opportunities. Admins or verified users can submit new postings, which are stored in the database
through the job API. Regular users can browse or search for these listings, and the API filters and
returns relevant results. Users may also apply for positions, with their application details saved and
possibly linked to their profiles.
CHAPTER 3. SYSTEM DESIGN 27

Figure 3.17: Student/Alumni Directory Sequence Diagram

Description: The student and alumni directory sequence shows how authenticated users explore and
connect with others in the system. A user sends a search or filter query to the directory API, which
accesses the database and returns a list of matching profiles. Users can then view detailed profile
information to initiate networking, mentorship, or collaboration opportunities.
CHAPTER 3. SYSTEM DESIGN 28

3.6 Activity Diagram

Chapter 4

Implementation

4.1 Implementation Design

The alumni website follows a modular and component-based architecture

using React.js for the frontend and Django REST Framework for the back-
end. The communication between frontend and backend is handled via
RESTful APIs, and the MySQL database stores all relevant data.
The alumni portal system follows a modular design with a clear separa-
tion between frontend and backend, ensuring scalability and maintainability.

4.1.1 Frontend (React.js + Tailwind CSS)

The frontend is developed using React.js with reusable components for

major sections like News, Events, Blogs, and Gallery. Styling is handled
using Tailwind CSS, ensuring a clean, responsive interface. Dynamic pages
like NewsByCategory.jsx and BlogList.jsx utilize hooks such as useState and
useEffect for managing state and making API calls in real-time.

4.1.2 Backend (Django REST Framework)

The backend uses the Django REST Framework to create secure, scalable
APIs. JWT-based authentication ensures safe user access. Each module
(e.g., News, Events, Mentorship) has dedicated models and serializers. An
admin panel is provided to manage and approve content before it’s displayed
on the site.

4.1.3 Database(MySQL)

Data is stored in a MySQL database, with well-structured tables linked to

Django models. The schema supports content management, user authen-

29
CHAPTER 4. IMPLEMENTATION 30

tication, and alumni/student directories.

4.1.4 Image Handling

All images (e.g., event posters, gallery uploads) are stored in Cloudinary,
allowing efficient cloud-based image hosting. Images are fetched and dis-
played dynamically using their URLs.

4.1.5 Hosting

During development, APIs were tested using Postman on localhost:8000/api

to ensure smooth backend functionality.
Chapter 5

Testing

Testing is a vital phase to ensure the functionality, reliability, and usability of

the system. The alumni website underwent various levels of testing during
development to validate that each module works as expected.

5.1 Testing Types

The Discussion and Analysis chapter evaluates and analyses the results. It
interprets the obtained results.
Table 5.1: Example of a table in LATEX

Testing Types Description

Unit Testing Individual components and backend APIs were tested i
Integration Testing Interaction between frontend and backend was tested u
System Testing Complete workflows such as registration, blog submissi
User Acceptance Testing (UAT) Feedback was taken from peers and mentors to ensure
API Testing Django REST APIs were tested using Postman to verif

Table 5.2: Example of a table in LATEX

Bike
Testing Types Description
Unit Testing black 700
Hybrid blue 500
Road blue 300
Mountain red 300
Folding black 500

31
Chapter 6

Conclusions and Future Work

6.1 Conclusions

Typically a conclusions chapter first summarizes the investigated problem

and its aims and objectives. It summaries the critical/significant/major
findings/results about the aims and objectives that have been obtained by
applying the key methods/implementations/experiment set-ups. A conclu-
sions chapter draws a picture/outline of your project’s central and the most
signification contributions and achievements.
A good conclusions summary could be approximately 300–500 words
long, but this is just a recommendation.
A conclusions chapter followed by an abstract is the last things you write
in your project report.

6.2 Future work

This section should refer to Chapter ?? where the author has reflected
their criticality about their own solution. Concepts for future work are then
sensibly proposed in this section.
Guidance on writing future work: While working on a project, you
gain experience and learn the potential of your project and its future works.
Discuss the future work of the project in technical terms. This has to be
based on what has not been yet achieved in comparison to what you had
initially planned and what you have learned from the project. Describe
to a reader what future work(s) can be started from the things you have
completed. This includes identifying what has not been achieved and what
could be achieved.
A good future work summary could be approximately 300–500 words

32
CHAPTER 6. CONCLUSIONS AND FUTURE WORK 33

long, but this is just a recommendation.

Chapter 7

Codes

Write a short paragraph on the substantial learning experience. This can

include your decision-making approach in problem-solving.
Some hints: You obviously learned how to use different programming
languages, write reports in LATEXand use other technical tools. In this sec-
tion, we are more interested in what you thought about the experience.
Take some time to think and reflect on your individual project as an expe-
rience, rather than just a list of technical skills and knowledge. You may
describe things you have learned from the research approach and strategy,
the process of identifying and solving a problem, the process research in-
quiry, and the understanding of the impact of the project on your learning
experience and future work.
Also think in terms of:
• what knowledge and skills you have developed
• what challenges you faced, but was not able to overcome
• what you could do this project differently if the same or similar problem
would come
• rationalize the divisions from your initial planed aims and objectives.
A good reflective summary could be approximately 300–500 words long,
but this is just a recommendation.

Note: The next chapter is “References,” which will be automatically

generated if you are using BibTeX referencing method. This template uses
BibTeX referencing. Also, note that there is difference between “Refer-
ences” and “Bibliography.” The list of “References” strictly only contain
34
CHAPTER 7. CODES 35

the list of articles, paper, and content you have cited (i.e., refereed) in
the report. Whereas Bibliography is a list that contains the list of articles,
paper, and content you have cited in the report plus the list of articles,
paper, and content you have read in order to gain knowledge from. We
recommend to use only the list of “References.”
References

36
Appendix A

Codes)

Some lengthy tables, codes, raw data, length proofs, etc. which are very
important but not essential part of the project report goes into an
Appendix. An appendix is something a reader would consult if he/she needs
extra information and a more comprehensive understating of the report.
Also, note that you should use one appendix for one idea.
An appendix is optional. If you feel you do not need to include an
appendix in your report, avoid including it. Sometime including irrelevant
and unnecessary materials in the Appendices may unreasonably increase the
total number of pages in your report and distract the reader.

37
Appendix B

Screenshots

...

38