Student Activity Management System

A project report submitted in partial fulfillment of the requirements for

the award of the degree of

Bachelor of Computer Application (BCA)

Submitted by
Joseph Thampy

St. George’s College, Aruvithura

Aruvithura PO, Erattupetta

Affiliated to

Mahatma Gandhi University

Kottayam
 St. George’s College, Aruvithura
Aruvithura PO, Erattupetta - 686122

CERTIFICATE

This is to certify that report entitled “Student Activity Management Sys-

tem” is a bonafide report of the main project (CA6CRP08 -Software Development
Lab II ( Main Project)) presented during VIth semester by Joseph Thampy, in
partial fulfillment of the requirements for the award of the degree of Bachelor of
Computer Application (BCA).

Staff in Charge Project Guide Head of the Department

Place:

Date:

External Examiner Internal Examiner

 ABSTRACT

The Student Activity Management System is an online platform designed

to help students keep track of their extracurricular activities. Students can
add new activities and view their previously added ones, along with the
date, venue, and uploaded certificate for proof of participation.
The system also features an admin panel to monitor student engage-
ment in extracurricular activities. This system simplifies the management
of extracurricular activities, making it easier for both students and the ad-
ministration to track participation and evaluate engagement.
 ACKNOWLEDGEMENT

I am very delighted to present this report describing the main project

I completed during the sixth semester of my BCA course. I’m so grateful
to our Project Coordinator and Head of Department, Dr. Jestin Joy,
Assistant Professor, Department of Computer Applications, for his constant
guidance and support. It is only because of his diligent efforts that my
endeavors have been successful.
My deep appreciation to our Project Guide, Dr. Anu Thomas,
Assistant Professor, Department of Computer Applications, for assisting
and guiding me on various features.
I extend my gratitude to our beloved Principal, Prof. Dr. Siby Joseph
for giving me this opportunity.
With deep appreciation, I extend my gratitude to my parents and mem-
bers of my family who have always supported me morally and economically.
Last but not least my gratitude is extended to all of my friends who
directly or indirectly helped me to complete this project.
Any omission from this brief acknowledgement does not mean a lack of
gratitude.

Joseph Thampy
 Contents

List of Figures iv

1 INTRODUCTION 1
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 DESIGN and IMPLEMENTATION 2

2.1 DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.1 Database Schema . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.2 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.3 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.1 Front-end technology . . . . . . . . . . . . . . . . . . . . . . 7
2.2.2 Back-end technology . . . . . . . . . . . . . . . . . . . . . . 7

3 TESTING 9

4 RESULTS 10
4.1 Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Student . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5 CONCLUSION 14

Appendices 16

A Snippet of code for adding activities 17

iii
 List of Figures

2.1 Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.2 Symbols for Use Case Diagram . . . . . . . . . . . . . . . . . . . . 3
2.3 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4 Symbols for Data flow Diagrams . . . . . . . . . . . . . . . . . . . . 4
2.5 DFD Level 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.6 DFD Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.1 Test Cases for SAMS . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.1 Admin Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2 Admin Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Active Students . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4 Student Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.5 Added Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.6 Activity Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.7 Student Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.8 Student Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.9 Add Activity Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.10 Saved Activities Page . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.11 Edit Account Details Page . . . . . . . . . . . . . . . . . . . . . . . 13

iv
 Chapter 1

INTRODUCTION

1.1 Overview
The Student Activity Management System (SAMS) is an innovative web applica-
tion designed to help students track and manage their extra-curricular activities.
With SAMS, students can easily enter details about the activities they participate
in, including the date, venue, and a certificate as proof of participation.
SAMS provides students with a user-friendly interface that allows them to add
new activities, view their added activities, and keep track of their accomplishments
over time. The system also provides an administrative view that allows authorized
personnel to access and review student activity data.
SAMS is a valuable tool for students who want to keep track of their extra-
curricular activities and showcase their achievements to potential employers or
academic institutions. The app is secure and reliable, ensuring that student data
is protected at all times. With its user-friendly interface and powerful features,
SAMS is the perfect solution for students looking to manage their extra-curricular
activities.

1.2 Problem Statement

The lack of an efficient system to manage extracurricular activities can create dif-
ficulties for students and administrators. Students may have a hard time keeping
track of their activities, while administrators may find it challenging to monitor
and evaluate student engagement. The absence of a standardized system to track
extracurricular activities can lead to inaccuracies, loss of documentation, and dif-
ficulties in evaluating students’ accomplishments.
To address these issues, a Student Activity Management System is required to
streamline the management of extracurricular activities and ensure the effective
monitoring and evaluation of student participation.

1
 Chapter 2

DESIGN and IMPLEMENTATION

2.1 DESIGN

2.1.1 Database Schema

A database schema specifies how data is organized within a relational database;
logical constraints like table names, fields, data types, and their relationships are
defined. In an organization’s data management discipline, schema serve as the
basis for communicating the database’s architecture.

Figure 2.1: Database Schema

Tables in the above database schema include:

Users
This table stores the details of all the users. The primary key is the user id.

Activity
This table stores the activity details such as venue, date and certificate of par-
ticipation. user id in this table is a foreign key.

Profile
This table stores the department and semester details of the student. user id
in this table is a foreign key.

2
2.1.2 Use Case Diagram
A use case diagram can summarize the details of your system’s users (also known as
actors) and their interactions with the system. The purpose of a use case diagram
is to demonstrate the different ways that a user might interact with a system.
The different symbols in a use diagram are:

Figure 2.2: Symbols for Use Case Diagram

In the use-case diagram here, there are two users: admin and user.
The student has the following processes:

• Login to the system

• Add new activity

• View added activities

• Edit account details

The admin has the following processes:

• Login to the system

• Edit account details

• View student details

• View student activities

3
 Figure 2.3: Use Case Diagram

2.1.3 Data Flow Diagram

A data flow diagram (DFD) maps out the flow of information for any process
or system. It uses defined symbols like rectangles, circles and arrows, plus short
text labels, to show data inputs, outputs, storage points and the routes between
each destination. Data flowcharts can range from simple, even hand-drawn process
overviews, to in-depth, multi-level DFDs that dig progressively deeper into how
the data is handled. They can be used to analyze an existing system or model a
new one.
The different symbols used in a DFD are:

Figure 2.4: Symbols for Data flow Diagrams

4
 Levels or layers are used in DFDs to represent progressive degrees of detail
about the system or process. These levels include:

• Level 0: It is also known as a context diagram. It’s designed to be an

abstraction view, showing the system as a single process with its relationship
to external entities. It represents the entire system as a single bubble with
input and output data indicated by incoming/outgoing arrows.

• Level 1: Level 1 DFDs are still a general overview, but they go into more
detail than a context diagram. In level 1 DFD, the single process node from
the context diagram is broken down into sub-processes. As these processes
are added, the diagram will need additional data flows and data stores to
link them together.

Figure 2.5: DFD Level 0

The following processes are included in the Level 1 DFD of this project:

1. Student Management: The system administrator is responsible for adding

new users to the system. The user details are stored in a User table.

2. Activity Management: Students can add new activities to the system.

These activities are stored in an Activity table. The system administrator
can view all activities in the system.

3. Profile Management: Students can add new activities to the system.

These activities are stored in an Activity table. The system administrator
can view all activities in the system.

5
Figure 2.6: DFD Level 1

6
2.2 IMPLEMENTATION
An overview of the technologies are mentioned below:

2.2.1 Front-end technology

HTML
HTML or HyperText Markup Language is a markup language that defines
the structure of your content. HTML consists of a series of elements, which you
use to enclose, or wrap, different parts of the content to make it appear a certain
way, or act a certain way. The enclosing tags can make a word or image hyperlink
to somewhere else, can italicize words, can make the font bigger or smaller, and so
on. One of the biggest advantages of using HTML is that it is free, and no special
software is required. HTML does not require any plugins, so one should not have
to deal with them when working with any software.

CSS
CSS or Cascading Style Sheet or the second pillar of front-end development
after HTML is a language used for describing the presentation of web pages, which
includes the layout of the page, fonts of elements and color, animation, a lot else
as well. Thus making our web page beautiful to the user. Let us breakdown the
word CSS or Cascading Style Sheet.

• Cascading: means that styles can fall (or cascade) from one style sheet to
another. That is, there can be multiple CSS files linked to the same HTML
document, where the last one matters the most.

• Style: Adding Styling our HTML tags

• Sheets: Writing our style code in different documents

CSS is designed to make style sheets for web pages. It is independent, i.e., it can
be used with any XML-based markup language.

2.2.2 Back-end technology

Django
Django is a high-level Python web framework that is used to build web applications
quickly and easily. It is designed to be modular and scalable, making it an excellent
choice for building complex web applications.
Django has a lot of built-in features that make it easy to create dynamic web
applications. It includes a powerful URL routing system, a robust database ORM,
and an easy-to-use administration interface.

7
 One of the key features of Django is its ability to handle a wide range of web
development tasks, including user authentication, content management, and e-
commerce functionality. It is also highly customizable, with a large number of
third-party packages available to extend its functionality.
Django is an open-source framework, and it has a large and active community
of developers who contribute to its ongoing development and support. It is widely
used by developers all over the world to build a wide range of web applications,
from small personal projects to large-scale enterprise websites.

MySQL

MySQL is an open-source relational database management system (RDBMS) that

uses Structured Query Language (SQL) to manage and manipulate data. It is
widely used in web applications and is a popular choice for database management
due to its ease of use, reliability, and scalability.
MySQL can store and manage large amounts of data, and it is highly customiz-
able, with a wide range of storage engines available. It supports transactions,
which ensure data integrity and consistency, and it can be used in conjunction
with other programming languages and frameworks, such as PHP, Python, and
Ruby on Rails.
MySQL is also known for its performance, with fast read and write speeds, and
it can handle high-volume applications with ease. It is a cost-effective solution for
businesses and organizations of all sizes, as it is open-source and free to use.
Overall, MySQL is a powerful and reliable database management system that
is widely used in web applications and other software projects. Its ease of use,
scalability, and reliability make it an excellent choice for developers and businesses
alike.

8
 Chapter 3

TESTING

Software testing is the process of evaluating and verifying that a software product
or application does what it is supposed to do. The benefits of testing include
preventing bugs, reducing development costs and improving performance.
Software testing is used to assess the feature of a software item. The testing
process ensures the quality of the product. Testing is the process that should be
done during the development of software. In other words, software testing is a
verification and validation process. Manual testing is done with given data. The
test cases and results are given below.

Figure 3.1: Test Cases for SAMS

9
 Chapter 4

RESULTS

4.1 Admin

Figure 4.1: Admin Login Page

Figure 4.2: Admin Home Page

10
Figure 4.3: Active Students

Figure 4.4: Student Details

Figure 4.5: Added Activities

11
 Figure 4.6: Activity Details

4.2 Student

Figure 4.7: Student Login Page

Figure 4.8: Student Home Page

12
 Figure 4.9: Add Activity Page

Figure 4.10: Saved Activities Page

Figure 4.11: Edit Account Details Page

13
 Chapter 5

CONCLUSION

The student activity management system developed is an innovative and user-

friendly application that provides an effective way for students to document and
manage their extra-curricular activities. The application enables students to up-
load certificates as proof of their participation in different activities, and record
essential information such as venue and date of the activity. Additionally, the
application allows the admin to view the activities of individual students, which
can be helpful in assessing their overall performance.
The system is designed to be simple, yet comprehensive, with features that
enable students to add new activities and view their previously added activities. It
provides a centralized platform for managing student activities and allows students
to showcase their talents and achievements beyond academics.
Overall, this student activity management system offers a valuable tool for
educational institutions and students alike, promoting the importance of extra-
curricular activities and helping students build a well-rounded portfolio of accom-
plishments that can benefit them in their future careers.

14
 Bibliography

[1] Django Software Foundation. (2021). Django documentation. Retrieved from

https://docs.djangoproject.com/

15
Appendices

16
 Appendix A

Snippet of code for adding activities

@login required
def c r e a t e a c t i v i t y ( r e q u e s t ) :
i f r e q u e s t . method == ’POST ’ :
form = ActivityForm ( r e q u e s t . POST, r e q u e s t . FILES )
i f form . i s v a l i d ( ) :
a c t i v i t y = form . s a v e ( commit=F a l s e )
a c t i v i t y . user = request . user
a c t i v i t y . save ( )
messages . s u c c e s s ( r e q u e s t , ” Saved S u c c e s s f u l l y ” )
return r e d i r e c t ( ’ c r e a t e a c t i v i t y ’ )
else :
form = ActivityForm ( )
return r e n d e r ( r e q u e s t , ’ c r e a t e a c t i v i t y . html ’ , { ’ form ’ : form })

17