Chapter -1

Introduction
The College Alumni Management System project, an innovative and
purpose driven platform that aims to establish and nurture a strong bond
between our esteemed educational institution and its esteemed alumni
community. With a vision to create a thriving ecosystem for graduates, this
system offers a seamless and user-friendly interface, empowering our alumni
to remain connected, share their achievements, and actively participate in
the college's continued growth and success. The College Alumni Management
System project is built on the foundation of fostering meaningful
relationships, knowledge sharing, and professional opportunities among our
graduates. Through inspiring galleries, interactive forums, and engaging
events, this project serves as a conduit for alumni to showcase their
accomplishments, provide mentorship, and collaborate with each other and
current students.

1. 1 Project overview
Our mission is to create a dynamic and vibrant alumni community,
where every graduate can take pride in their alma mater, stay updated with
the latest developments, and embark on a journey of lifelong learning. We
believe that by leveraging modern technologies and user-centric design,
our alumni management system will become a valuable resource for both
alumni and the college, strengthening our ties and collectively contributing
to a brighter future.
The newer methods have an advantage of accessing data from anywhere
around the globe. Modification and updating data become an easy
process. As it is a responsive two-way managing service, the data of the
individual is maintained by the admin as well as the alumni. Depending on
the requirement, the input of the data can be added or modified on timely
basis. Along with data management, additional interactive features can
also be added if required by the institution. The alumni management
system is build based on an ER diagram which provides a distributive

1
 knowledge about the scope of the website and also presents on how
different relationships can be accessed through one database [3]. This
method helps the institution to keep a track of an alumnus after
graduation and the student interaction with the institution for any
reference, guidance or mentorship can be made available.

1.2 Background of the project:

Each year numerous students graduated from their individual
universities or schools. It’s is incredibly arduous for the colleges and
universities to take care of their comprehensive knowledge and end in lack
of communication between alumni and their school. Institutes can also
facilitate current students by arranging regular events with alumnus. These
events can easily be maintained by a software system where alumnus and
students can virtually plan and organize the events (academia, 2020).
Some graduates can start their business right after graduation, but for
colleges to know that this alum is a good fit for their faculty, they must
have a connection with them.

1.2.1 Problem Area

The majority of grad student wasn't connation Alumni association
member, rather a number of them extremely don’t fathom this method.
This development occurred in our University. Though it's its own
administration workplace, it's long-faced with plenty of issues and doesn't
work properly. This was of association system is insufficient and doesn't
run within the right method. We can usually establish the issues that are
chiefly as:
• Service related problem and
• Human power related problem
Service related problem: Because most graduates travel to various parts
of the country and speak different languages, there is a challenge with
promoting scholarships and other educational opportunities to students
who live far away from the institution. Interaction with an alumna in their
local region necessitates a lot of services as well. As a result of entering

2
 into a diverse culture, this alumni office may find it challenging to provide
support to such graduating students.

Human capacity related problem: It is time-consuming to retrieve student

data, such as a graduate student's personality, address, and other
students' information from the institution. Retrieving the status of
graduates who have entered the workforce requires a significant amount
of strength. After they leave, the alumnus is not initiated to be enrolled as
a member. I.e. the system is physically operated (www.researchgate.net,
2017). Even if one is a member, it is difficult to keep track of the
organization, and there is no effective service that enables daily activation
of both memberships, as most significant information is put on the notice
board. It's also tough to figure out who is actively involved in the
organization.

1.2.2 Possible solution

The alumni association design and implementation will be
accessible to the general public via a web interface. A non-registered
visitor can browse the list of graduates by graduation year or subject of
study. He can also glance at the profiles of grads. The amount of
information on a person's profile that is visible to the general public is
limited. A public visitor can only view a graduate's name and surname, year
of graduation, and field of study by default. The faculty works hard to
spread the word about its alumni. As a result, during their studies,
graduates can submit information about themselves to the system, such
as job experience and knowledge. Graduates can choose to make this
information visible to the public on their profiles.

Keyword: Alumni, System, Student, Management, Dashboard

3
1.3 Technology Overview
Required Software & Hardware Used:-
Front End Technology: HTML, CSS, JavaScript, Bootstrap, CDN.
Backend technology: PHP/ MySQL Database,
Python Framework (Django)
Operating System: Windows 8 or later
Processor: intel core i3 1.8 – 2.9 GHz
RAM: 4GB RAM
HDD: 512 GB
Browser: Google Chrome, Internet Explorer
Tools: Notepad ++, VS Code, MySQL (Oracle)
Server: XAMPP Server or live server to host the web-page.

As this project mainly focuses on alumni database on web services it

uses methods based on web development tools like HTML, CSS, JavaScript
along with Python framework (Django). The existing database has to be
saved and modified using SQL. The HTML, CSS & JavaScript are considered
to be the front-end development tools. [1]

i. HTML
The HTML is used for the basic layout of the website which includes inputs
in the form of registration form, a log-in page and details of a particular
student using the HTML tags.
ii. CSS
The styling that includes designing of the web page for user attraction is
done using CSS. The CSS is used because of its easy and efficient access to
styling which is generally paired with HTML for most of the websites
available.

4
iii. JavaScript
It is paired with HTML and CSS for a responsive front-end (Client Side).
iv. Django – A Python based Framework
As Python is an easy programming language due to its rich
availability of resources for developing, the framework is preferred for
back-end (Developer’s Side). This is an individual framework that also
provides web extracting features for pulling out data in case of adding
automating techniques like web-scrapping tool (Beautiful Soup) [4] [7].
v. SQL
As we are using a structured data which is easy to handle in a
database management system, SQL is preferred over other databases. SQL
is said to be one of the oldest methods of storing large data in tables which
avoids duplication of data. RDBMS concept is used to provide relationship
between each table to fetch structured data across multiple tables [6].
vi. Express.js
Express.js is a free and open-source web application framework for
Node.js. It is used for designing and building web applications quickly and
easily. Web applications are web apps that you can run on a web browser.
Since Express.js only requires javascript, it becomes easier for
programmers and developers to build 17 web applications and API without
any effort. Express.js is a framework of Node.js which means that most of
the code is already written for programmers to work with. You can build a
single page, multi-page, or hybrid web-applications using Express.js.
Express.js is lightweight and helps to organize web applications on the
server-side into a more organized MVC architecture.
vii. PHP
PHP serves as the backbone of the Alumni Management System project,
enabling server-side scripting for dynamic content generation, database
interaction, user authentication, form handling, data validation, and
session management. Through PHP scripts, the system manages user
authentication, processes form submissions, interacts with the database
to perform CRUD operations on alumni profiles and event data, and

5
 maintains session variables to track user interactions. PHP's versatility and
seamless integration with databases make it essential for building robust
and scalable web applications like the Alumni Management System.

1.4 Project Organization

1.4.1 System Flow Chart:

The website focuses on user interaction and multifunctioning by

adding various features to increase reusability [5].
This system is divided into two sides –

• Admin side,
• Alumni/Student side.

Fig-1.1: Flow Chart of System & Methodology Diagram

6
 Fig-1.2: Flow Chart of System & Methodology Diagram

1.4.2 Objectives of The System

The proposed system is intended to meet the following objectives:

• Maintain the updated and current information of all alumni.

• Encourage, foster and promote close relations between the school and
the alumni and among the alumni themselves.
• Encourage the alumni to support and participate in programs, services
and events of the association.
• Obtain feedback and opinions from alumni for planning and
implementing the activities of the association.
• Provide a contemporary centralized base of information that is easy to
use by alumni committee members.
• Provide efficient standard reporting and ad hoc reporting capabilities.

Alumni are one of the most important assets to the school as they are
the people who represent the school in the real world. Alumni forms
associations to promote a spirit of unity and loyalty among former students
and to strengthen the ties between alumni, the community, and the school.
These associations gained added importance in the development of the
school because of their enormous outreach potential that benefits the school
and helps current students in their career paths.

7
 Chapter -2
System Analysis
2.1 Preliminary Investigation
The Alumni Management System project aims to develop a
comprehensive platform to manage and engage with alumni of an
educational institution effectively. This preliminary investigation
report outlines the initial analysis conducted to understand the
requirements, feasibility, and potential scope of the project.
Objectives:
• To assess the need for an Alumni Management System within the
educational institution.
• To identify key stakeholders and their requirements for the system.
• To evaluate the technical feasibility of implementing such a system.
• To outline the potential features and functionalities of the Alumni
Management System.

2.1.1 Identification of Need

The old manual system was suffering from a series of drawbacks.
Since whole of the system was to be maintained with hands the process of
keeping, maintaining and retrieving the information was very tedious and
lengthy. The records were never used to be in a systematic order. there
used to be lots of difficulties in associating any particular transaction with
a particular context. If any information was to be found it was required to
go through the different registers, documents there would never exist
anything like report generation. There would always be unnecessary
consumption of time while entering records and retrieving records. One
more problem was that it was very difficult to find errors while entering
the records. Once the records were entered it was very difficult to update
these records.

8
 The reason behind it is that there is lot of information to be
maintained and have to be kept in mind while running the business for this
reason we have provided features Present system is partially automated
(computerized), actually existing system is quite laborious as one has to
enter same information at three different places.

Following points should be well considered:

• Documents and reports that must be provided by the new system:
there can also be few reports, which can help management in decision-
making and cost controlling, but since these reports do not get required
attention, such kind of reports and information were also identified and
given required attention.
• Details of the information needed for each document and report.
• The required frequency and distribution for each document.
• Probable sources of information for each document and report.
• With the implementation of computerized system, the task of keeping
records in an organized manner will be solved. The greatest of all is the
retrieval of information, which will be at the click of the mouse. So the
proposed system helps in saving the time in different operations and
making information flow easy giving valuable reports.

A. Existing System
The former methods of data preservation were tabular forms, excel
sheets, documentations, etc. These system limits multiple accessing, easy
modification in the data, searching for records [2]. As we are moving
towards digitalization, techniques of data management have been
improved. One of these methods include, database management system.
The database management system works on the principle of data-keeping
using computerized technologies.
❖ Disadvantages of existing system
These current methods though provide global access considering
cloud-based word document such as Google Docs, Microsoft Word,
etc. they have to be modified manually by an individual. This results
9
 in time consumption as well as lack of consistency in maintaining the
data. The limitations of the current methods are that they are have
to be updated regularly to avoid loss of data and it becomes
inconvenient for every user to the same.
B. Proposed Model
Alumni Management System is a system which manages the records of
the students who are a part of the respective institution or were a part of
the institution. Alumni management is important as it keeps the records of
the previous students for keeping them in touch with the institution. The
alumnus can be a help to the college in their expertise files of study from
the outside world giving students guidance and updating them about the
current happenings. It particularly concentrates on the graduated students
of the institution and not on the students who are currently a part of the
institution.
❖ Benefits of Proposed Model over Existing system
The database management system is a collection of a particular data
depending on the requirement. It is easier to alter and implement
changes in the existing data. As the new software technology is
rising, we can store this data in a conventional and effective way
using these software’s and interfacing them in a proper functional
order which can be accessed remotely.

Fig-2.1: Proposed System Architecture Diagram

10
Scope of the work:
The following are some key elements within the scope:
• These systems have a feature for alumni to showcase their
achievements, accolades, and career milestones through images,
descriptions.
• The development team will create a platform for alumni to participate
in discussions, share knowledge, and interact with each other through
forum topics and real-time chat functionality.
• This system provides a catalogue of courses and resources for alumni to
engage in lifelong learning and professional development.
• This management system will incorporate a section where alumni can
explore job openings posted by employers within the alumni network,
fostering alumni employment and career growth.
• This system facilitates the organization and promotion of alumni events,
reunions, and networking opportunities.
• Implementing user authentication and access controls to ensure the
security and privacy of alumni data.
• Testing of the system to identify and rectify any bugs, errors, or usability
issues.

2.12 Feasibility Study

A feasibility study is an analysis of how successfully a project can be
completed, accounting for factors that affect it such as economic,
technological and operational. Project managers use feasibility studies to
determine potential positive and negative outcomes of a project before
investing a considerable amount of time and money into it.

During the stage of our feasibility study, we had to undergo the

following steps as described under:
• Identify the origin of data at different levels of the system.
• Identify the expectation of end user from the finished product/system.
• Analysis the drawbacks of the existing system.

11
➢ Technical feasibility study:

All projects are feasible, given unlimited resources and infinite time.
Unfortunately, the development of a computer-based system or
product is more likely suffered by a scarcity of resources and difficult
delivery dates. It is both necessary and prudent to evaluate the
feasibility of a project at the earliest possible time. However during the
development of our project we concentrate on the following feasibility
and lays out details on how a good or service will be delivered, which
includes transportation, business location, technology needed,
materials and labour.

➢ Economical feasibility study:

Economic justification is “bottom – line “consideration for most system.

Economic justification includes a broad range of concern that includes
cost-benefit analysis, long term corporate income strategies, and cost
of resources needed for development. As far as monetary matters are
concerned we need hard disk space of 2GB and a Pentium processor.
These are only requirements, which can be easily met. It is a projection
of the amount of funding or startup capital needed, what sources of
capital can and will be used and what kind of return can be expected
on the investment.

➢ Operational Feasibility study:

Operational feasibility is mainly concerned with issues like whether the

system will be used if it is developed and implemented. Whether there
will be resistance from users that will affect the possible application
benefits?

➢ Scheduling Feasibility study:

This assessment is the most important for project success; after all, a
project will fail if not completed on time. In scheduling feasibility, an
organization estimates how much time the project will take to
complete. When these areas have all been examined, the feasibility
analysis helps identify any constraints the proposed project may face,
including:

12
 Internal Constraints: Technical, Technology, Budget, Resource, etc.
Internal Corporate Constraints: Financial, Marketing, Export, etc.
External Constraints: Logistics, Environment, Laws, & Regulations, etc.

➢ Organizational feasibility study:

It is a definition of the corporate and legal structure of the business; this

may include information about the founders, their professional
background and the skills they possess necessary to get the company
off the ground and keep it operational.

Fig-2.2: Feasibility Diagram

13
 Chapter - 3
Requirement Analysis & Design

Before the development of this web-page, we should collect information

about Alumni and what they are doing now and which company they are
working. Now, the development of this web-page will help to know about
the alumni friends and we can be in touch with them. Through this web-site,
1.student side:
The student module can be used to browse through the site and access
alumni information. The students will be able to chat via the system with
the alumni, if the site.
2.Admin side:
The admin will be responsible for creating new login IDs for incoming
students. The admin will also have to ensure that graduating students are
shifted into the complaints from users. An alumnus of the college will be
able to access other alumni information and also will be able to view all their
contact information (unless it is made private). An alumnus can post any
information they deem relevant on the site.

3.1 Requirement Gathering Architecture

Requirement gathering for the Alumni Management System project
involves systematically collecting, analyzing and documenting the needs
and expectations of stakeholders to define the system's scope and
functionalities.
Here's a brief overview of the requirement gathering architecture:
1. Identifying Stakeholders: Identify all the relevant stakeholders involved
in the project, including college administrators, alumni
representatives, current students, faculty, and potential users of the
system.
2. Conducting Interviews and Surveys: Hold interviews and surveys with
the stakeholders to understand their perspectives, pain points, and

14
 expectations from the Alumni Management System. Gather feedback
on the current alumni management process and identify areas that
need improvement.
3. Organizing Focus Groups: Organize focus groups with key stakeholders
to facilitate open discussions and brainstorming sessions. This allows
for in-depth exploration of specific requirements and potential
solutions.
4. Analyzing Existing Data: Analyze existing data related to alumni
information, events, alumni engagement metrics, and previous
feedback. This helps in identifying patterns and trends that can inform
the system's design and functionalities.
5. Defining Use Cases and User Stories: Create use cases and user stories
to capture specific scenarios in which the Alumni Management System
will be used. These use cases and user stories help in defining the
system's functional requirements from the end-users' perspective.
6. Prioritizing Requirements: Work with stakeholders to prioritize
requirements based on their importance, feasibility, and impact on
alumni engagement and college objectives. This helps in creating a
roadmap for the system's development.
7. Architecture Design: Based on the gathered requirements, define the
high-level architecture of the alumni management system. This
includes identifying the necessary modules, data flow, and integration
points with other systems, if applicable.
8. Creating Functional and Non-Functional Requirements: Document
both functional requirements (what the system should do) and non-
functional requirements (qualities the system should possess, such as
security, scalability, and performance).
9. Review and Validation: Conduct regular review and validation sessions
with stakeholders to ensure that the documented requirements
accurately represent their needs and expectations.
10. Iterative Process: Keep the requirement gathering process iterative,
allowing for continuous feedback and updates as the project progresses
and new insights emerge.

15
3.1.1 Functional requirements
Functional requirements for a Alumni Management System project
outline the specific features, capabilities, and functionalities the system must
possess to meet the needs of its users.

Here's a brief overview of functional requirements for the project:

1. User Registration and Authentication:

• The system should allow alumni to register with their essential details,
such as name, email, graduation year, etc.
• Alumni should be able to authenticate themselves securely using login
credentials or social media logins.
2. Alumni Profile Management:
• Each alumnus should have a dedicated profile page to manage
personal and professional information.
• Alumni should be able to update their contact details, employment
history, and other relevant data.
3. Alumni Gallery:
• The system should include a gallery page for alumni to showcase their
achievements, awards, and milestones through images and
descriptions.
4. Alumni Job Opportunities:
• The system should feature a jobs page where employers can post job
openings for alumni.
• Alumni should be able to search and apply for jobs within the alumni
network.
5. Alumni Events and Reunions:
• The system should provide an events page that displays upcoming
alumni events, reunions, and networking gatherings.

16
6. Alumni Forum and Chats:
• The system should host an interactive forum for alumni discussions,
knowledge sharing, and mentorship.
• Alumni should be able to engage in real-time chats with other
graduates and college representatives.
7. Alumni Courses and Continuing Education:
• The system should offer a course list containing educational resources,
webinars, and workshops for lifelong learning. 8. Account
Management and Privacy Settings:
• The system should allow users to manage their account settings,
including privacy preferences and communication options.
• Alumni should have control over who can view specific details on their
profile.
8. User Interaction and Networking:
• The system should facilitate networking and interaction among
alumni, such as adding connections and sending messages.
9. User Access Control and Roles:
• The system should define different user roles, such as alumni,
administrators, and faculty, each with specific access privileges.
Reporting and Analytics:
• The system should have reporting capabilities to track alumni
engagement metrics, course participation, event attendance, etc.

17
3.1.2 Non-functional requirements
Non-functional requirements specify the characteristics and qualities
that the Alumni Management System should possess, rather than specific
features and functionalities.

Here are some common non-functional requirements for such a system:

➢ Performance: - The system should have fast response times and handle
a large number of concurrent users without significant degradation in
performance.
• It should be able to handle the expected volume of alumni data, events,
and communication without performance bottlenecks.
• Response times for common operations, such as searching alumni
records or sending mass communications, should be within acceptable
limits.
➢ Security: - The system should implement robust security measures to
protect alumni data and ensure confidentiality, integrity, and
availability.
• Access controls should be in place to restrict unauthorized access to
sensitive information.
• Alumni personal data, such as contact details and financial information,
should be encrypted and stored securely.
➢ Scalability: - The system should be designed to accommodate future
growth and handle increasing numbers of alumni records and user
interactions.
• It should have the ability to scale up or scale out by adding more
hardware resources or utilizing cloud infrastructure as needed.
➢ Usability: - The system should have an intuitive and user-friendly
interface that is easy to navigate and understand for both
administrators and alumni.
• The system should support accessibility standards to ensure usability
for users with disabilities.

18
➢ Reliability and Availability: - The system should be highly reliable and
available, minimizing downtime and ensuring uninterrupted access for
administrators and alumni.
• Robust backup and recovery mechanisms should be in place to protect
against data loss and facilitate system restoration in case of failures.
• Disaster recovery plans should be established to mitigate risks and
ensure business continuity.
➢ Compatibility: - The system should be compatible with different web
browsers, operating systems, and devices to provide a seamless user
experience.
• It should adhere to relevant standards and protocols, enabling
integration with external systems or services.
➢ Compliance: - The system should comply with relevant data protection
regulations, privacy laws, and industry standards.
• It should adhere to ethical guidelines and best practices for handling
alumni data and respecting their privacy preferences.
• Compliance with accessibility standards, such as WCAG (Web Content
Accessibility Guidelines), should be considered.
➢ Performance Monitoring and Reporting: - The system should provide
monitoring and logging capabilities to track system performance,
identify issues, and facilitate troubleshooting.
• It should generate system performance reports, error logs, and usage
statistics to help administrators assess system health and make
informed decisions.

19
3.2 System Perspective Design

Fig-3.1: Basic Design Diagram

3.2.1 Modules and their descriptions

1. Admin:
Administrator in the operator who will take care of the system.
➢ Login
➢ Logout
➢ Change password
➢ Forgot password (Change password)
➢ Organize meeting
➢ View event and meeting
➢ Generate invitation
➢ View detail of students who has been placed.

20
 2. Student:
➢ Register
➢ View meeting
➢ View gallery
➢ Change his information
➢ Contact us

3.3 Data Flow Diagram (DFD)

Alumni Information System Data flow diagram is often used as a
preliminary step to create an overview of the Alumni without going into great
detail, which can later be elaborated.it normally consists of overall application
dataflow and processes of the Alumni process. It contains all of the user flow
and their entities such all the flow of Alumni, College, College Mates, Social
Network, Opportunity, Collage News, Student. All of the below diagrams has
been used for the visualization of data processing and structured design of
the Alumni process and working flow.

3.3.1 Context flow diagram (CFD)

Fig-3.2: CFD

21
➢ Level 0 (DFD):
High Level Entities and process flow of Level 0 DFD:
• Managing all the Alumni
• Managing all the College
• Managing all the register & search
• Managing all the Opportunity
• Managing all the Event News
• Managing all the updates
• Managing the current student

Fig-3.3: Level 0 DFD

22
➢ Level 1 (DFD):
Figure below presents the process on how users can access the system
and the system features. The developed system is composed of four
components namely:
• Online Registration (1.0),
• Information Services (2.0),
• Gallery (3.0), and
• Database Maintenance (4.0)

Fig-3.4: Level 1 DFD

23
➢ Level 2 (DFD) Online Registration (1.0):
Figure below shown above is the level 2 DFD explosion;
• The Online Registration (1.0) of the developed system.
• User is required to register online (1.1) in the system.
• The User is required to enter username and password in order to
access the features of the Alumni information system.
• Users can also update personal data (1.2) and can also change
their password (1.3) in the system.

Fig-3.5: Level 2 (DFD) Online Registration (1.0)

24
➢ Level 2 (DFD) Information Services (2.0)
• The Information Services (2.0) was designed to facilitate the Forum,
Calendar of Events, and Online Help.
• The Chat (2.1) feature of the system allows users to exchange
messages in “real time”.
• The Forum (2.2) provides a venue for alumni to share ideas, connect
to other alumni, and discuss topics that are related to the school or
school’s activities. The Calendar of Events (2.3) provides the
following:
announcement;
reminders;
schedule of activities; and
other important information on alumni activities.

Fig-3.6: Level 2 (DFD) Information Services (2.0)

25
➢ Level 2 (DFD) Explosion Gallery (3.0)
In the Level 2 DFD Explosion of Gallery (3.0) on Figure 3.7, the
Alumni and the Alumni Officer have access to this feature of the
developed system. The alumni and Alumni Association Officer can
upload photos and videos on the activities conducted by the school.

Fig-3.7: Level 2 DFD Explosion Gallery (3.0)

26
➢ Level 2 DFD Explosion Database Maintenance (4.0)
In the Level 2 DFD Explosion of Database Maintenance (4.0) on
Figure 3.8, system administrator has access to this feature of the
developed system. The administrator has direct access on tables to
maintain and manage them.

Fig-3.8: Level 2 DFD Explosion Database Maintenance (4.0)

27
 Chapter - 4
Software Design & Methodology

The software team that works for the best of the project chooses
software development techniques for a successful project and effective
project management. Each methodology has its own set of strengths and
weaknesses, and each one ends for a different reason. The success rate of
development is frequently determined by the approach used for
development aims. With sufficient study and knowledge (sparklyn, 2021), this
chapter will comprehensively examine the chosen methodology and the
Software design’s right explanation for adopting the technique.
Findings of the requirement analysis phase was taken into
consideration when designing the system. A good design leads to a successful
implementation. This chapter describes the desired features and the
operations of the system in detail, using screen layouts, process diagrams and
database diagrams.
4.1 Software Requirement Specification (SRS) Documentation:
• Define the functional requirements of the Alumni Management
System, including user roles and permissions, features, and
workflows.
• Specify the non-functional requirements, such as performance,
security, scalability, and usability criteria.
• Document the system's use cases, detailing the interactions between
users and the system to achieve specific goals or tasks.
• Outline the system's data requirements, including data sources,
formats, storage, retrieval, and processing mechanisms.
• Define acceptance criteria and validation procedures to ensure that
the system meets stakeholders' expectations and quality standards.

1. Architecture Design:
• Define the high-level architecture of the Alumni Management
System, including its components, layers, and interfaces.
28
 • Choose appropriate technologies, frameworks, and platforms for
system development based on requirements, scalability, and
maintainability considerations.
• Design the system's modular structure, ensuring that components
are loosely coupled and independently deployable to facilitate
flexibility and extensibility.
2. Database Design:
• Design the database schema for the Alumni Management System,
including tables, fields, relationships, and constraints.
• Optimize the database design for performance, scalability, and data
integrity, considering factors such as indexing, normalization, and
denormalization.
• Define data migration and transformation strategies to ensure
seamless integration with existing data sources and systems.
3. User Interface Design:
• Develop user interface wireframes and mock-ups to visualize the
layout, navigation, and interaction flow of the Alumni Management
System.
• Design intuitive and user-friendly interfaces that prioritize usability,
accessibility, and consistency across different devices and screen
sizes.
• Incorporate feedback from stakeholders and usability testing to
refine the user interface design and enhance the overall user
experience.

4. Security Design:
• Identify potential security threats and vulnerabilities associated with
the Alumni Management System, such as unauthorized access, data
breaches, and malware attacks.
• Implement security measures, including authentication,
authorization, encryption, and data validation, to protect sensitive
information and ensure data privacy and integrity.

29
 • Conduct security testing and vulnerability assessments to identify
and mitigate security risks throughout the development lifecycle.
5. Scalability and Performance Design:
• Design the Alumni Management System to be scalable and
performant, capable of handling increasing volumes of data, users,
and transactions over time.
• Optimize system performance by employing techniques such as
caching, load balancing, and asynchronous processing to minimize
response times and maximize throughput.
• Conduct performance testing and capacity planning to validate the
system's scalability and identify potential bottlenecks or
performance issues.
6. Integration Design:
• Define integration points and interfaces for connecting the Alumni
Management System with external systems, such as CRM software,
email platforms, and social media networks.
• Implement standard protocols and APIs to enable seamless data
exchange and interoperability between the system and external
applications.
• Develop data migration and synchronization mechanisms to
facilitate the transition from legacy systems and ensure data
consistency across disparate sources.

7. Usability and Accessibility Design:

• Design the user interface of the Alumni Management System to be
accessible to users with diverse abilities and assistive technologies,
complying with relevant accessibility standards and guidelines.
• Conduct usability testing and heuristic evaluations to assess the
system's ease of use, learnability, efficiency, and satisfaction among
target users.

30
 • Incorporate feedback from usability testing to iteratively refine the
user interface design and improve the overall usability and
accessibility of the system.
By following a systematic methodology and comprehensive software
design approach, the College Alumni Management System project can
effectively address the needs and requirements of stakeholders while
ensuring the development of a robust, scalable, and user-friendly software
solution.

4.2 Work Methodology & Techniques

Alumni portal connects with both staff, juniors, seniors and with
management. Alumni portal runs on a backend server using node-js and
express-js. It has 3 types of users with specified permissions i.e Admin,
Alumni, Student. Each user has separate 21 permissions to modify or add
any type of data. There are several endpoints to make every action.

Fig-4.1 System Architecture

In the front end There are Login/Logout, Signup pages. Form data
will be validated by the front-end before being sent to the back-end. This
reduces the useless requests to the backend. Depending on User‘s roles

31
(admin, moderator, user), Navigation Bar changes its items automatically.
When the request is passed to backend, backend contacts server and the
node.js server validates the username and password. As this is one time
authentication, a jwt token is generated and passed back to front which is
used for further authentication purposes. This technique reduces the load
on database and server as jwt carries auth details for the user every time.
JWT token is being stored in local storage of the browser and used on
every api call. If the credentials are rejected by the server, front-end handles
the issue by showing 22 an error pop-up the user by appropriate error
message that is passed the back-end. Once the user is logged in, each
subsequent request will include the JWT, allowing the user to access routes,
services, and resources that are permitted with that token. Single Sign On is
a feature that widely uses JWT nowadays, because of its small overhead and
its ability to be easily used across different domains.

Fig 4.2 Sequential Diagram

32
 In the back-end there are 3 types of endpoints
1. User Endpoints
2. Admin Endpoints
3. Dev Endpoints.
User Endpoints are used to have basic auth and any user with a valid
auth token can access these endpoints. Admin endpoints can only be
accessed by the users with valid admin token this adds additional security
to prevent any user from manipulating the database. Admins can ban the
users and the 23 front end keeps checking the ban endpoint to make sure
the user has access to the token. Search uses. Indexes are special data
structures that store a small portion of the collection's data set in an easy to
traverse form. The index stores the value of a specific field or set of fields,
ordered by the value of the field. The ordering of the index entries supports
efficient equality matches and range-based query operations. In addition,
MongoDB can return sorted results by using the ordering in the index. The
returned items are then rendered on the front end to show the users that
relate to the search parameters.

4.3 SDLC – System development life cycle

For product development, a variety of methodologies are employed.
Because the project is IT-related, the agile technique would be beneficial.
In many prior multinational initiatives, the agile approach was important in
the project's success. The DSDM framework is one of the agile
methodologies that may be applied. I'll outline two methodologies, together
with their benefits and drawbacks.

➢ A Waterfall Model:
A waterfall model is exemplified by a sequential model. The
software development activity is organized into distinct phases in this
paradigm, with each phase consisting of a sequence of activities and
achieving different goals (tutorials-point, 2018).
The several phases of the Waterfall Model are depicted in the following
diagram:
33
 Fig-4.3: A Waterfall Model Diagram

Waterfall Model – Advantages

• It's easy to grasp and implement.
• Thanks to its stiffness, the model is straightforward to handle. There are
precise deliverables and a review mechanism for every step.
• Every step is restricted and accomplished one by one.
• This methodology is best suited to smaller come with well-defined
specifications.
• Stages that is distinct and well-defined.
• Milestones that are clear and well-defined (studentprojects, 2021).

Waterfall Model – Disadvantages:

• Until the tip of the life cycle, no functioning software package is

developed.
• There may be a heap of danger and uncertainty.
• For refined and object-oriented applications, this is often not
associate degree acceptable paradigm.
• For long-run comes, this paradigm is insufficient.
• Not acceptable for comes with a moderate to high risk of
modification in needs. As a result, this method model contains a
high level of risk and uncertainty. Changes in requirements cannot
be accommodated.

34
 • Changes in needs can't be accommodated (studentprojects, 2021).
• Changing the scope of a project throughout its life cycle would
possibly cause its termination.

➢ Dynamic System Development Method (DSDM):

The dynamic system development technique is a way for quickly
developing applications. Throughout the iterative and incremental process,
this method places a premium on simultaneous user involvement (digite,
2016). With continual customer feedback, DSDM always takes the right
approach to generating a fantastic project

Fig-4.4: DSDM Diagram

35
 Advantages of the DSDM:
• There is a high level of user interaction.
• Basic functions are delivered more swiftly and on a more consistent
basis.
• Projects are finished on time and on budget.
• Enables developers to communicate with end-users (ukessays, 2001).
Disadvantages of the DSDM:
• One-time projects and small enterprises are not eligible.
• It is not as well recognized or understood as earlier classic versions
such as the waterfall because it is a newer model.
• When compared to other agile development software approaches,
DSDM's strictness and eight principles may make it challenging to
work with. (ukessays, 2001).

4.4 Module description design

There are two parts of our project, one is the Admin panel, and the other
one is the Alumni panel. Each panel has been divided into several modules.

Admin Panel:
The Alumni Management System project is a comprehensive platform
designed to enhance alumni engagement and communication within the
college community. Here's a brief overview of each page:

• Login Page: The login page is the gateway to the system, where alumni,
administrators, and other users can authenticate their credentials to
access the platform.

• Home Page: The home page serves as the central hub of the system,
offering a dashboard with relevant updates, announcements, and
personalized content for each user. It provides quick links to different
sections, including the gallery, course list, alumni list, jobs page, events
page, forum page, user page, and system settings.

• Gallery Page: The gallery page showcases alumni achievements, success

stories, and milestones through images and descriptions. It allows

36
 alumni to create and manage their profiles and share inspiring content
with the college community.
• Course List: The course list page displays a catalog of courses,
workshops, webinars, and educational resources available to alumni.

• Alumni List: The alumni list page presents a directory of all registered
alumni, offering options for search and filters to find specific graduates
based on graduation year, field of expertise, and more. It encourages
networking and reconnecting among alumni.

• Jobs Page: The jobs page features job opportunities posted by employers
within the alumni network. Alumni can explore and apply for relevant
positions, fostering career growth and networking within the
community.

• Events Page: The events page highlights upcoming alumni events,

reunions, and networking opportunities. It allows alumni to RSVP and
stay informed about gatherings and activities.

• Forum Page: The forum page is an interactive platform for alumni

discussions and knowledge sharing. It includes various categories for
different topics, encouraging alumni to engage in meaningful
conversations and mentorship.

• User Page: The user page provides a personalized space for each user to
manage their account settings, profile information, and communication
preferences. It enables users to control their interactions within the
platform.

• System Setting Page: The system setting page is accessible to

administrators and allows them to configure and customize the
platform. It includes options for managing user roles, privacy settings,
email notifications, and other system-related configurations.

➢ Alumni Panel:
• The Alumni Management System alumni side offers a user-friendly
interface and a range of features that empower graduates to stay
37
 connected, showcase their achievements, explore job opportunities,
participate in discussions, and manage their profiles efficiently.

• Home Page: The alumni home page serves as the central hub of the
system for graduates. It offers a personalized dashboard with relevant
updates, announcements, and quick links to various sections, such as
the gallery, jobs page, forum, and account settings. The home page
provides a user-friendly and intuitive interface for easy navigation.

• Signup Page: The signup page allows alumni to create their accounts
within the system. Alumni provide essential details such as their name,
email, graduation year, and preferred login credentials. Successful
signup grants access to the alumni portal and its features.

• Gallery Page: The gallery page enables alumni to showcase their

achievements, career milestones, and personal experiences through
images and descriptions. Each alumnus has a dedicated profile to
manage and share their content with the college community.

• Login Model: The login modal appears whenever an alumni user

accesses the system. It allows for secure authentication with
email/username and password.

• Jobs Page: The jobs page provides a platform for alumni to explore job
opportunities posted by employers within the alumni network. Alumni
can browse through job listings, filter them based on preferences, and
apply for suitable positions.

• About Page: The about page offers an overview of the Alumni

Management System, detailing its purpose, benefits, and how it
facilitates alumni engagement.

• Forum Page: The forum page allows alumni to engage in discussions,

share knowledge, and seek advice from fellow graduates. Alumni can
participate in different categories or start new threads on various topics,

38
 encouraging meaningful interactions and mentorship within the alumni
community.

• Account Management Page: The account management page empowers

alumni to control their profile and preferences. Alumni can update
personal information, manage privacy settings, and customize
communication preferences.

• Chat Page: The Chat Page is a real-time communication feature that

enables alumni to connect and interact with each other directly through
private messages and group chats.

4.5 Database design

Designing the database for the Alumni Management System (AMS)
involves defining the structure and relationships of data entities such as
alumni profiles, events, donations, communications, and administrative data.
A well-designed database ensures efficient data storage, retrieval, and
management, supporting the functionality and performance requirements of
the system. Let's elaborate on the database design components:
4.5.1. Entity-Relationship (ER) Diagram:
An ER diagram visually represents the entities, attributes, and
relationships within the database schema. It provides a clear understanding
of how different data entities are related to each other. In the context of the
AMS, the ER diagram might include the following entities:
• Alumni Profile: Contains information about individual alumni, such as
name, contact details, graduation year, degree obtained, employment
history, skills, and interests.
• Events: Represents events organized by the college, including alumni
reunions, networking sessions, workshops, and seminars. Attributes may
include event name, date, location, description, and attendees.
• Donations: Stores information about financial contributions made by
alumni to the college or specific programs. Attributes may include

39
 donation amount, donor name, donation date, purpose, and payment
method.
• Communications: Tracks interactions between the college and alumni,
including emails, newsletters, notifications, and announcements.
Attributes may include communication type, content, sender, recipient,
and timestamp.
• Administrative Data: Includes metadata and administrative information
about the AMS, such as user accounts, roles, permissions, audit logs, and
system settings.
The ER diagram illustrates the relationships between these entities, such as
one-to-one, one-to-many, or many-to-many relationships, helping to define
the database schema accurately.

Fig-4.5: E-R Diagram

4.5.2. Table Structure:

Based on the entities identified in the ER diagram, the table structure
for the AMS database can be defined. Each entity corresponds to a database

40
table, and each attribute corresponds to a table column. Here's an example
of table structure for some of the entities:
• Alumni_Profile Table:
• alumni_id (Primary Key)
• first_name
• last_name
• email
• graduation_year
• degree_obtained
• employment_history
• skills
• interests
• Events Table:
• event_id (Primary Key)
• event_name
• event_date
• location
• description
• attendees
• Donations Table:
• donation_id (Primary Key)
• alumni_id (Foreign Key)
• donation_amount
• donation_date
• purpose
• payment_method

41
 • Communications Table:
• communication_id (Primary Key)
• communication_type
• content
• sender
• recipient
• timestamp
• Administrative_Data Table:
• user_id (Primary Key)
• username
• password_hash
• role
• permissions
• last_login_timestamp
Each table's primary key uniquely identifies records within the table, while
foreign keys establish relationships between tables. For example, the
alumni_id in the Donations table references the alumni_id in the
Alumni_Profile table, linking each donation record to the respective alumni
profile.

4.5.3 Data Constraints and Integrity:

In addition to table structure, data constraints and integrity rules ensure
data consistency and accuracy within the database. Constraints such as
unique constraints, foreign key constraints, and check constraints enforce
data integrity by preventing invalid or inconsistent data from being entered
into the database.
For example:
• Unique constraints ensure that each alumni profile has a unique email
address.
42
 • Foreign key constraints enforce referential integrity between related
tables, ensuring that donations are associated with existing alumni
profiles.
• Check constraints validate data values against predefined criteria, such
as ensuring that donation amounts are positive numbers.
4.5.4 Indexing and Optimization:
To optimize database performance, indexing can be applied to
frequently queried columns, improving data retrieval speed and query
efficiency. Indexes can be created on columns used in search, filter, or join
operations, reducing the time required for data retrieval.
For example, indexes can be created on the alumni_id column in the
Donations table to facilitate fast lookup of donations associated with specific
alumni profiles.

4.6 Unifying Modelling Language (UML) view

Designing a UML view for an Alumni Management System involves
creating various diagrams to represent the system's structure, behavior, and
interactions. Below, we have elaborate on each UML diagram and its
components in a more descriptive manner:
4.6.1 Use-Case Diagram:
➢ Description: Use case diagrams illustrate the interactions between actors
(users or external systems) and the system to accomplish specific tasks
or goals.
➢ Components:
• Actors: Represent the different types of users or external systems
interacting with the Alumni Management System (e.g., alumni,
administrators, staff).
• Use Cases: Describe the functionalities or services provided by the
system from the perspective of actors.
• Relationships: Connect actors to use cases to indicate which
functionalities are accessible to each actor.

43
Fig-4.6: Use-Case diagram for Alumni & Admin Side

44
4.6.2 Class Diagram:
➢ Description: Class diagrams depict the static structure of the system,
including classes, attributes, methods, and their relationships.
➢ Components:
• Classes: Represent the entities or objects in the system (e.g., Alumni,
Event, Communication).
• Attributes: Describe the properties or characteristics of each class (e.g.,
AlumniID, Name, Email).
• Methods: Define the operations or behaviors associated with each
class (e.g., registerForEvent(), sendCommunication()).
• Relationships: Specify the associations, dependencies, and multiplicity
between classes (e.g., one-to-many relationship between Alumni and
Event).

4.6.3 Activity Diagram:

➢ Description: Activity diagrams model the flow of activities or processes
within the system, including decision points, parallel flows, and loops.
➢ Components:
• Initial Node: Marks the starting point of the activity flow.
• Activities: Represent tasks, actions, or operations performed within the
system.
• Decision Nodes: Specify branching points based on conditions or
criteria.
• Merge Nodes: Combine multiple branches of activity flow back into a
single path.
• Final Node: Indicates the end of the activity flow.

45
Fig-4.7: Activity Diagram for Alumni Side

46
 Fig-4.8: Activity Diagram for Admin Side

4.6.4 Sequence Diagram:

➢ Description: Sequence diagrams illustrate the interactions and message
exchanges between objects or components in a chronological order.
➢ Components:
• Lifelines: Represent the objects or components participating in the
sequence of interactions.
• Messages: Describe the communication between lifelines, including
method calls, return values, and asynchronous events.

47
• Activation Bars: Indicate the duration of time during which an object is
actively engaged in processing a message.

Fig-4.9: Sequence Diagram for User Side

48
Fig-4.10: Sequence Diagram for Admin Side

49
4.6.5 State Machine Diagram:
➢ Description: State machine diagrams model the dynamic behavior of
objects or entities in the system, depicting their states and state
transitions.
➢ Components:
• States: Represent the conditions or modes that an object can be in
(e.g., Active, Inactive, Pending).
• Transitions: Define the events or triggers that cause an object to
change from one state to another.
• Initial State: Marks the initial state of the object when it is first created.
• Final State: Indicates the termination or completion of the object's
lifecycle.
4.6.6 Component Diagram:
➢ Description: Component diagrams illustrate the physical or logical
components of the system and their dependencies.
➢ Components:
• Components: Represent the modular units or building blocks of the
system (e.g., User Interface, Database, Communication Module).
• Interfaces: Define the contracts or protocols for interaction between
components.
• Dependencies: Show the relationships and dependencies between
components, such as uses, provides, or requires relationships.
4.6.7 Deployment Diagram:
➢ Description: Deployment diagrams depict the physical deployment of
software components and their relationships to hardware nodes.
➢ Components:
• Nodes: Represent the hardware devices or execution environments on
which software components are deployed (e.g., Server, Client).

50
 • Components: Depict the software modules or artifacts deployed on
nodes.
• Associations: Connect components to nodes to show deployment
relationships and dependencies.
By creating and analyzing these UML diagrams, stakeholders can gain a
comprehensive understanding of the Alumni Management System’s
structure, behavior, and interactions, facilitating effective communication,
requirements elicitation, and system design.

51
 Chapter - 5
Testing
5.1 Testing Methodologies :
Testing a web application is a comprehensive process that involves
several methodologies to ensure that the application functions correctly, is
secure, performs well under load, and provides a good user experience. These
methodologies ensure a comprehensive evaluation of the web application,
making it robust, reliable, and user-friendly. Each testing type serves a unique
purpose and collectively they ensure the quality of the web application.
5.1.2 Functional Testing
Functional testing ensures that the web application works as expected. It
involves testing the functionality of the application by verifying that each
function of the software application operates in conformance with the
requirement specification.
• Unit Testing: Testing individual components or modules of an
application. Typically done by developers to ensure that each unit
functions correctly.
o Tools: JUnit, NUnit, PHPUnit.
• Integration Testing: Ensures that integrated modules work together as
expected. This can be done using various integration techniques like Big
Bang, Top Down, Bottom Up, and Sandwich.
o Tools: JUnit, TestNG.
• System Testing: Testing the complete and integrated software product
to evaluate the system’s compliance with the specified requirements.
o Tools: Selenium, QTP.
• Acceptance Testing: Validation from the user's perspective. Ensures the
system meets the business requirements and is ready for deployment.
o Tools: Cucumber, JBehave.

52
5.1.2 Non-Functional Testing
Non-functional testing focuses on the quality attributes of the software
like performance, usability, reliability, etc.
• Performance Testing: Determines how the system performs in terms of
responsiveness and stability under a particular workload. It includes:
o Load Testing: Simulates multiple users accessing the application
simultaneously to ensure the system can handle the expected load.
o Stress Testing: Tests the system beyond its normal operational
capacity to determine the breaking point.
o Tools: JMeter, LoadRunner.
• Security Testing: Ensures the application is secure from external threats
and vulnerabilities. This involves:
o Penetration Testing: Simulating attacks to identify vulnerabilities.
o Vulnerability Scanning: Identifying and assessing vulnerabilities in
the system.
o Tools: OWASP ZAP, Burp Suite.
• Usability Testing: Evaluates the user interface and user experience to
ensure the application is easy to use.
o Techniques: User surveys, A/B testing, heatmaps.
• Compatibility Testing: Ensures that the web application works across
different browsers, devices, and operating systems.
o Tools: BrowserStack, CrossBrowserTesting.
• Reliability Testing: Ensures the application performs consistently over
time without failures.
o Techniques: Reliability growth models, stability testing.
• Scalability Testing: Determines the application's ability to scale up or
down according to user needs and loads.
o Tools: Apache JMeter, BlazeMeter.

53
 • Maintainability Testing: Ensures that the application can be maintained
(fixed, improved, or enhanced) easily.
o Techniques: Code reviews, static analysis.

5.2 System Testing :

No matter how carefully a system is designed and implemented, problems
can occur. Rigorous testing can detect errors during implementation (Rogers
et al., 2011). The main objective of the testing process was to uncover the
errors in the system. This errors would later be corrected through the
debugging process.

5.2.1 Unit Testing

The testing of an individual program or module is called unit testing. The
objective is to identify and eliminate execution errors that could cause the
program to terminate abnormally, and logic errors that could have been
missed during desk checking (Rogers et al.,2011). This testing was done as the
team traversed through the coding phase. Every finished module of
functionality was tested just after completion to enable early debugging.

5.2.2 Integration Testing

Testing two or more programs that depend on each other is called
integration testing according to Rogers et al. (2011). This was carried at the
integration of the different subsystems. The aim of the integration test was to
ensure that the various sub-systems functioned as expected upon integration.

5.2.3 Compatibility Testing

This test was done to establish how the system appears on devices with
different screen sizes. We established that the system scales well to the
different displays (small, medium, large and extra-large interfaces).

54
5.2.4 Acceptance Testing
An acceptance test includes all typical processing situations. During an
acceptance test, users enter data, including samples of actual, or live data,
perform queries, and produce reports to simulate actual operating
conditions. All processing options and outputs are verified by users and the
IT project development team to ensure that the system functions correctly
(Rogers et al., 2011). This test was carried with various users of the system.
After user recommendations and suggestions were picked, changes were
made to provide the system users with the interfaces and functionality they
highlighted.

5.2.5 System Validation

The system was checked to ensure that it does exactly what it was
designed to do. This involved having a group of end users interact with it so
as to assess the system accuracy and usability to ensure system
completeness. The respondents in this section were selected using purposive
sampling. These involved students and alumni of Maker University.

55
 Chapter - 6
Implementation & Results
6.1 Characteristics of Coding Language used :
• Front-end Design: HTML, CSS, Bootstrap
Hypertext Markup Language (HTML) is the standard markup
language for creating web pages and web applications. With Cascading
Style Sheets (CSS) and JavaScript, it forms a triad of cornerstone
technologies for the World Wide Web. Web browsers receive HTML
documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes the structure of
a web page semantically and originally included cues for the appearance
of the document.
Cascading Style Sheets (CSS) is a style sheet language used for
describing the presentation of a document written in a markup language
like HTML. CSS is a cornerstone technology of the World Wide Web,
alongside HTML and JavaScript.CSS is designed to enable the separation
of presentation and content, including layout, colors, and fonts. This
separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple
web pages to share formatting by specifying the relevant CSS in a separate
.css file, and reduce complexity and repetition in the structural content.
Bootstrap is a free and open-source front-end library for
designing websites and web applications. It contains HTML- and CSS-
based design templates for typography, forms, buttons, navigation and
other interface components, as well as optional JavaScript extensions.
Unlike many web frameworks, it concerns itself with front-end
development only.
• Client side validation: JavaScript, jQuery
JavaScript often abbreviated as JS, is a high-level, interpreted
programming language. It is a language which is also characterized as
dynamic, weakly typed, prototype-based and multi-paradigm. Alongside
HTML and CSS, JavaScript is one of the three core technologies of the

56
 World Wide Web. JavaScript enables interactive web pages and thus is an
essential part of web applications. The vast majority of websites use it,
and all major web browsers have a dedicated JavaScript engine to execute
it.
JQuery is a cross-platform JavaScript library designed to simplify
the client- side scripting of HTML. It is free, open-source software using
the permissive MIT License. Web analysis indicates that it is the most
widely deployed JavaScript library by a large margin.
• Server side validation: Ajax
Ajax is not a single technology. Ajax is a set of Web development
techniques using many Web technologies on the client side to create
asynchronous Web applications. With Ajax, Web applications can send
and retrieve data from a server asynchronously (in the background)
without interfering with the display and behavior of the existing page. By
decoupling the data interchange layer from the presentation layer, Ajax
allows Web pages, and by extension Web applications, to change content
dynamically without the need to reload the entire page.
• Business logic: PHP
PHP: Hypertext Preprocessor (or simply PHP) is a server-side
scripting language designed for web development but also used as a
general-purpose programming language. It was originally created by
Rasmus Lerdorf in 1994, the PHP reference implementation is now
produced by The PHP Group. PHP originally stood for Personal Home
Page, but it now stands for the recursive acronym PHP: Hypertext
Preprocessor. PHP code is usually processed by a PHP interpreter
implemented as a module in the web server or as a Common Gateway
Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data,
including images, with the generated web page. PHP code may also be
executed with a command-line interface (CLI) and can be used to
implement standalone graphical applications.

57
• Database: MySQL
MySQL is an open source relational database management
system. For proprietary use, several paid editions are available, and offer
additional functionality. In this project MySQL has been used to store,
update, retrieve and delete related to user’s data and other additional
data about projects.
• Web Server: Apache
The Apache HTTP Server, colloquially called Apache, is a free and
open- source cross-platform web server, released under the terms of
Apache License 2.0. Apache is developed and maintained by an open
community of developers under the auspices of the Apache Software
Foundation. The Apache HTTP Server is cross- platform; as of 1 June 2017
92% of Apache HTTPS Server copies run on Linux distributions. Version 2.0
improved support for non-Unix operating systems such as Windows and
OS/2. Old versions of Apache were ported to run on OpenVMS and
NetWare.

• CodeIgniter: PHP framework

CodeIgniter is a popular open-source PHP framework used for
developing web applications. It is known for its simplicity, speed, and
flexibility, making it a preferred choice for developers looking to build
dynamic websites and applications efficiently. And it is loosely based on
the popular model–view–controller (MVC) development pattern. While
controller classes are a necessary part of development under CodeIgniter,
models and views are optional. CodeIgniter can be also modified to use
Hierarchical Model View Controller (HMVC) which allows the developers
to maintain modular grouping of Controller, Models and View arranged in
a sub-directory format.
CodeIgniter is most often noted for its speed when compared to
other PHP frameworks. In a critical take on PHP frameworks in general,
PHP creator Rasmus Lerdorf spoke at frOSCon in August 2008, noting that
he liked CodeIgniter "because it is faster, lighter and the least like a
framework."[11]

58
6.2 Implementation plans
The first step is to create the front-end for the application. Design the
web application with the features like Home, Alumni Login/ Signup, Alumni
Home, About us, Events, Gallery, Admin Login, Admin Dashboard etc., All the
front-end things can be done using basic technologies like HTML, CSS and
JavaScript. Then for the backend PHP is used to make the connection with
MySQL database and to connect with the server. The website can be hosted
locally using the XAMPP server localhost.
There are two main users of this system. They are alumni and admin.
The alumni will be able to register in the alumni portal if they don’t have an
account. Post successful registration they will be able to login to the system.
If they have registered already they 8 will be redirected to the login page.
After login the Home page will be displayed with a welcome message. The
about us page will have the messages from the alumni council and higher
authorities of the institution. The alumni will be able to browse through the
campus photo gallery. The events page will display all the upcoming events
for the alumni. The user will be able to view the event poster. The alumni
assist will have four components; send query – using which the alumni can
send queries , request academic transcripts, request to campus visit etc., ;
post a job- alumni will be able to post the job opportunities by giving the job
details so that it can be shared with the students of the institution; share
achievements- this allows the users to share their career achievements; be a
mentor- alumni can send the request to conduct events like webinars, resume
review sessions, contests etc.,

The admin will be able to login to the system. They will be able to see
the number of requests in their dashboard. All the data will be fetched from
the database and displayed as a table to the admin. The admin will be able to
download the job opportunities posted by the alumni as an excel file. After
this they can share that with the placement department of the institution.
The admin will be able to update the upcoming alumni events which has been
displayed on the events page of the alumni side. They will be able to add and
delete events. The project mange the fresh as well as old graduate students
with their respective information in actively participating in making
registering, searching, managing the alumni information for sharing their
expertise, network, jobs opportunities and resources.

59
 This participation has evolved into multiple dimensions; and is now
eager to formally enter into the domain of mentorship to students through a
regular program. Alumni registration management system (Alumni
Dashboard) is a step towards this, creating multidimensional interactions
between current and past students of college.

6.2.1 Possible problem break down

The entire project must be divided down into discrete jobs to make
system development easier and more effective. The following are some
possible breakdowns for the proposed project:
o Development of an admin panel
o Database design and analysis
o Select and organize the System template.
o Create a system supplier panel.
o Create a customer panel for the System.
➢ Design database:
o Determine the system's needs.
o Finish the normalizing procedure.
o Create a diagram of entity relationships.
o Design the database schema for the system.
➢ Develop admin panel:
o Create the necessary pages.
o Develop a method for admin manipulation.
o Create all resource management pages necessary for the vehicle Alumni
Management system.
➢ Alumni panel development:
o Front-end design.
o Login and Registration system.
o Manipulation is requested by alumni

60
6.2 Core Module Coding Samples: Admin side -
o Index.php code -

61
o Login.php Code –

62
o Home.php Code

o Course.php Code –

63
o Forums.php code -

64
o Events.php Code -

65
6.2.1Core Module Coding Sample: Alumni/User side –
o Login Code –

66
o Home page code-

67
o Alumni list code -

68
o My-acount Login Code-

69
o Sign-Up page Code –

70
o CSS file Code -

71
o Java-Script file Code –

72
o Database file Code –

73
6.3 Application Result: Admin Side –

74
75
6.3.1 Application Result: Admin Side –

76
77
78
 Chapter - 7
Conclusion & Discussion

7.1 Limitations of System

1. Scalability Issues
As the number of users grows, the system may face challenges in handling
increased load, resulting in slower performance or even downtime.
• Database Overload: The database might struggle to handle a large
number of concurrent queries, leading to slow response times.
• Server Load: If the server infrastructure is not adequately scaled, it
might not handle the increased traffic, leading to downtime or
degraded performance.
• Solution: Implementing load balancing, optimizing database queries,
and using scalable cloud infrastructure can help mitigate these issues.

2. Security Vulnerabilities
The system could be susceptible to various security threats, putting user data
at risk.
• Data Breaches: Without proper encryption and security measures,
sensitive user data (e.g., personal information, contact details) could be
exposed.
• Unauthorized Access: Weak authentication mechanisms could allow
unauthorized users to gain access to the system.
• Solution: Implement robust security protocols, such as SSL/TLS for data
transmission, regular security audits, and strong authentication
mechanisms (e.g., multi-factor authentication).

79
3. User Privacy Concerns
Handling and protecting user data is critical, and any mismanagement could
lead to privacy issues.
• Data Misuse: There could be concerns about how user data is used,
stored, and shared.
• Compliance: Ensuring compliance with privacy regulations (e.g., GDPR,
CCPA) can be challenging.
• Solution: Develop clear privacy policies, obtain user consent for data
collection, and implement data protection measures to comply with
relevant regulations.
4. User Experience and Usability
A poorly designed user interface or a non-intuitive user experience can deter
users from using the system.
• Complex Navigation: If the system is not user-friendly, users may find it
challenging to navigate and use its features.
• Accessibility Issues: Not all users may be able to use the system if it is
not accessible to people with disabilities.
• Solution: Conduct thorough usability testing, gather user feedback, and
follow accessibility guidelines (e.g., WCAG) to ensure the system is easy
to use and accessible to all users.
5. Integration Challenges
Integrating the Alumni Management System with other systems (e.g.,
university databases, third-party services) can be difficult.
• Incompatibility: There could be issues with data format compatibility
and integration protocols.
• Data Synchronization: Keeping data consistent and synchronized across
different systems can be challenging.
• Solution: Use standardized APIs, data formats (e.g., JSON, XML), and
middleware solutions to facilitate seamless integration.

80
6. Maintenance and Support
Ongoing maintenance and support can be resource-intensive.
• Technical Debt: Over time, the system might accumulate technical debt,
making it harder to maintain and update.
• Resource Allocation: Ensuring that there are enough resources (e.g.,
developers, support staff) to maintain and support the system can be
challenging.
• Solution: Implement regular code reviews, refactoring, and allocate
dedicated resources for maintenance and support.
7. Data Management and Quality
Ensuring the accuracy and quality of data within the system is crucial.
• Data Entry Errors: Manual data entry by users can lead to inaccuracies.
• Data Duplication: Duplicate records can clutter the system and lead to
confusion.
• Solution: Implement validation checks, data cleansing procedures, and
de-duplication algorithms to maintain data quality.
8. Cost Constraints
Developing, deploying, and maintaining the system can be expensive.
• Initial Development Costs: The upfront costs of developing a robust
system can be high.
• Ongoing Costs: Maintenance, updates, and scaling the system can incur
significant ongoing costs.
• Solution: Carefully plan and budget for both initial development and
ongoing maintenance, and explore cost-effective solutions such as
cloud services.
9. Dependency on Technology
The system may rely on specific technologies that could become obsolete.
• Obsolete Frameworks: Using outdated frameworks or libraries can
pose risks as they may no longer be supported or secure.

81
 • Vendor Lock-in: Dependence on specific third-party services or
technologies can limit flexibility.
• Solution: Use widely adopted, well-supported technologies and design
the system to be as modular and independent as possible to mitigate
these risks.

7.1.1 Discussion on Drawbacks:

• We have not implemented several analysis reports such as: The system
does not send email or in-app notifications to inform alumni about
relevant updates, events, job opportunities, forum activities, and many
more.
• The system doesn’t provide a platform for alumni to contribute
donations to the college or specific causes. Alumni should receive
information on fundraising campaigns and initiatives.
• A video calling portal among the alumni can be implemented in the
future for more convenience for the students.
• This system is basically run on localhost only, it needs deployment.

7.2 Result & Conclusion

At the conclusion of the project, the produced application is made
available for usage. Before the new system can be utilized, any issues with it
must be recognized and remedied. The release criteria, settings, and
techniques are all determined in this section. The new system will be
implemented if all goes well. Admittedly, alumni are valuable assets of the
institutions of higher education. Thus, the more alumni communication is
intact the greater opportunities for feedback and knowledge development.
An alumni portal facilitates the promotion of research, the exchange of
experience, in addition to providing personal, professional and academic
networking. The developers decided to create the Alumni Portal System to
help the university to track the alumni and to gather their information thru
online portal without hassle. Alumni can use their own personal computers
devices to add, monitor and update their current status. In view of the above,
the developers would like to recommend that additional verification
procedures be made to ensure that Only bonafide alumni can register in the
system.
82
 Main innovations encompass the inclusion not only of the alumni, but
also the current students to the alumni portal, therefore, the link with the
university is strengthened from the beginning with a tendency to bolster the
bond between the students (current and alumni) and the educational
institution.

7.2.1 CONCLUSION
Our project is only a humble venture to satisfy the needs to manage
their project work. Several user friendly coding have also adopted. This
package shall prove to be a powerful package in satisfying all the
requirements. The objective of software planning is to provide a frame work
that enables the manager to make reasonable estimates made within a
limited time frame at the beginning of the software project and should be
updated regularly as the project progresses The tremendous popularity of
using the social media networking could never have been realized before. In
fact, social media have become an important tool of marketing in true sense
of customer orientation. But this kind of social networking site which can
access only for college campus not from outside the college will make a
dramatically changes inside the college campus.
College can be expensive and we all know it‘s hard work. People may
not realize it, but education is so much more than just the qualifications you
receive at the end. It‘s about the lessons you learn, the people you meet, and
the relationships you build. So why would you expect to leave all of that
behind after graduation? Alumni networks provide long-term value to an
educational institution by giving alumni the chance to stay in contact and
continue to learn from each other long after they have left school. Support
networks are hard to come by out there in the world and having a ready-made
one full of people with shared experiences just waiting to connect is a luxury
that few can afford to turn down. When you can, join your college‘s alumni
network.
Due to the need to connect all alumni (students who have already
passed) to the organization, it was possible to share their perspectives,
experiences, orientations, ideas, strategies and motivations. The focus of the
alumni portal app is on the interaction between graduates and current
students at the university. In this way, students or alumni can get to know

83
each other and their current activities. This portal focuses on the
interaction/communication feature that allows the current students to
interact with the alumni of the university or organization to get various
updates on current industry trends, internship opportunities, project
sponsorships and multiple references opening up in the company World.
Therefore, in this project, we developed a dynamic alumni portal design
that enables two-way interaction between all students and all students.

7.3 Future Enhancements

The proposed work in the Alumni Portal will make the Alumni data
available in an organized web application which will help current students and
college staff members to know instantly about them. However there are some
other further plans like including current students as future alumni in this
portal, engagement point system, referral system for current students to get
their internship/job which makes effort much more easier.
7.3.1 FUTURE SCOPE
o This alumni portal would provide a common platform for interaction of
college related members.
o Virtual alumni meetings.
o Job posting.
o Internships.
o Industry sponsored projects.
o Entrepreneurial guidance.
o Portal provides active user status, chat rooms, personal chatting &
messaging.
7.3.2 Data Collection and Verification
Future researchers should look into LinkedIn website, investigate
how LinkedIn restructures its web elements, identify the constants and
scrapable elements to develop a better, more efficient, and most importantly
durable and reliant scraping algorithm against new updates without violating
any terms of service, or getting temporary and even permanent account
suspensions. This can improve the accuracy and reliability of data source for
alumni placement analysis and mentor matching algorithm, as well as
minimize the risk of legal or ethical issues from LinkedIn scraping.
84
7.3.3 Industry Classification Model
There are a few directions future research can proceed with the design
of industry classification machine learning models. In terms of model design,
future work should consider other pre-trained models that are trained both
within and outside of the job description and industry classification context,
and experiment with test and sentence embeddings for classification. It will
also be beneficial if future research adopts a more rigorous feature selection
process to train and evaluate models from scratch to boost results.
In terms of data, future work could explore other potential data
sources that augment the data for our model for better performance. Another
potential strategy could be a combination of predictions from both models.
In particular, one could compare the results from each model and select the
prediction from the model with the better performance on the given industry
category. For instance, it might be a good idea to try using the pre-trained
DistilBERT model for IT, Business/Finance, and healthcare job postings and the
self-trained model for other job categories. This approach could improve the
overall accuracy and reliability of the task

85
❖ References :-
The following websites have helped us for developing the web application:
• https://www.javatpoint.com/php-tutorial
• https://www.w3schools.com/php/
• https://www.w3schools.com/howto/default_page5.asp
• https://www.geeksforgeeks.org/php-tutorial/
• https://www.youtube.com/watch?v=at19OmH2Bg4&list=PLu0W_
9lII9aikXkRE0WxDt1vozo3hnmtR
• https://www.youtube.com/watch?v=6mbwJ2xhgzM&list=PLu0W_
9lII9agiCUZYRsvtGTXdxkzPyItg

86