AcademiQ Student Management System

Prepared by
GROUP NUMBER: Q

M.S DAMRUWAN & 34880

M.A.B INDUWARA & 35316
S.M WEERASINGHE & 35705
R.M.A.U RATHNAYAKA & 35704
V.N JAYASINGHA & 34940
W.D.S.L.J FERNANDO & 35439
P.D NANAYAKKARA & 29506
K.G.T KULARATHNE& 34730
M.I.F ASHFA & 35342
V.R.R RODRIGO & 34594

Submitted in partial fulfillment of the

CS107.3 – Object Oriented Programming with C#
May – 2025
 TABLE OF CONTENTS

1. INTRODUCTION.................................................................................................................................................................2
1.1 Background.............................................................................................................................................................. 2
1.2 Objectives..................................................................................................................................................................2
1.3 Significance of the Project................................................................................................................................. 2
2. METHODOLOGY................................................................................................................................................................. 3
2.1 Description............................................................................................................................................................... 3
2.2 Development Steps............................................................................................................................................... 3
2.3 System Design......................................................................................................................................................... 3
2.4 Testing and Validation........................................................................................................................................ 3
2.5 Diagram..................................................................................................................................................................... 4
2.5.1 Flowchart............................................................................................................................................................. 4
2.5.2 Uml Diagram...................................................................................................................................................... 5
3. REQUIREMENTS................................................................................................................................................................ 6
3.1 Tools & Technologies...........................................................................................................................................6
3.2 Hardware.................................................................................................................................................................. 6
4. RISK & CHALLENGES...................................................................................................................................................... 6
4.1 Database Connectivity.........................................................................................................................................6
4.2 Manual Code Implementation..........................................................................................................................6
4.3 Debugging and Validation................................................................................................................................. 6
5. CONCLUSION...................................................................................................................................................................... 7
6. REFERENCE LIST.............................................................................................................................................................. 7

i
 1. INTRODUCTION

1.1 Background

School Management Systems are essential tools in modern education to help organize academic
data and processes. Many schools still use manual methods to maintain records, which often
results in errors, delays, and poor organization. This project presents a solution called Student
LMS, a desktop-based system developed using C# WinForms. It is specifically designed for
managing student-related information, such as course enrollment, attendance records, and
timetables. The application is built entirely on the .NET Framework and uses a MySQL database
for data storage. It aims to streamline common academic tasks within a simple, secure
environment. The focus is to make student information management more structured and
efficient, especially for educational institutions that currently rely on paper-based systems.

1.2 Objectives
 To create a user-friendly desktop application for students to manage academic
information.
 To implement core features such as login, course selection, attendance tracking, and
timetable access.
 To use MySQL as the back-end database for storing and retrieving data.
 To ensure the application is stable, modular, and easy to maintain or expand in the future.

1.3 Significance of the Project

This system provides a foundation for organizing student-related processes in a consistent and
efficient way. It eliminates the dependency on paper records and allows students to interact with
academic data directly from a desktop application. With features such as secure login, timetable
display, and attendance viewing, it becomes easier for users to manage their academic
responsibilities. Although the system is limited to local use, it serves as a powerful base that can
be expanded over time. Its structure demonstrates how essential student services can be digitized
using basic desktop technologies and open-source databases.

2
 2. METHODOLOGY

2.1 Description

The Student LMS was developed as a standalone Windows application using C# and the .NET
Framework. It follows a modular approach where each core functionality—such as login, course
handling, and attendance—is implemented in separate forms. The system interacts directly with a
MySQL database using SQL queries and ADO.NET for database connectivity.

2.2 Development Steps

The development process began with identifying the basic needs for a school-oriented system:
managing student logins, viewing timetables, tracking attendance, and selecting courses. After
designing the database schema, the interface was developed using Windows Forms. SQL queries
were integrated to enable data retrieval and updates through the application. During
development, each module was tested separately to ensure that it worked independently. After
building all modules, they were combined into a unified interface that guides the student through
each process.

2.3 System Design

The application is built entirely using WinForms for the graphical interface and ADO.NET for
database connectivity. The database consists of relational tables for register, attendance, courses.
Each form in the application performs a specific task, like allowing students to log in, view their
course information, and access class schedules. The system is structured to reduce code
repetition and make future updates easy to implement. No third party libraries or frameworks
were used in the development process.

2.4 Testing and Validation

Testing was performed on each module individually and then on the system as a whole. The
login feature was tested with both valid and invalid inputs to ensure correct behavior. The course
and attendance features were validated against the database to confirm that changes made
through the application were correctly saved and displayed. All forms were tested for input
validation to prevent empty or incorrect entries. Errors such as database disconnections, incorrect

3
queries, or null fields were caught using try-catch and message blocks. The system was tested
using sample data to simulate real usage.

2.5 Diagram

The flowchart and Uml diagram, Future Plan Road Map illustrates the entire process of the
Student Management System.

2.5.1 Flowchart

This flowchart illustrates the overall

workflow of the Student Management
System application, beginning with the
user starting the system and arriving at the
login interface. At this stage, the system
checks if the user is already registered. If
the user is not registered, they are
redirected to a registration form where
they can create a new account. Once the
user is confirmed to be registered, they are
taken to the login page after that it will
redirect user to the dashboard, which
serves as the central navigation area of the
application.

From the dashboard, the user can choose

between three main functions: accessing
their courses, managing attendance, or
viewing the timetable. Under “My
Courses,” users have the option to select
and save course modules relevant to their
studies. In the “Manage Attendance”
section, users can either mark their
attendance for current sessions or view
their attendance history to track their
participation over time. The “Time Table”
section allows users to check their
academic schedule by viewing their
assigned class times.

Each of these features is organized into

clear, independent paths that guide the
student to complete specific tasks,
ultimately leading to the end of the
session.
4
2.5.2 Uml Diagram

The ababaabbaababa dapan mekata uml eka

5
 3. REQUIREMENTS

3.1 Tools & Technologies

 Programming Language: C#
 Framework: .NET Framework (Windows Forms)
 Database: MySQL
 IDE: Visual Studio
 Database Tool: MySQL Workbench
 Localhost database setup: XAMPP

4. RISK & CHALLENGES

Developing the Student Management System involves several risks and challenges

4.1 Database Connectivity

The initial connection between the application and the MySQL database faced issues due to
driver mismatches and incorrect connection strings. These were solved by installing the correct
MySQL .NET Connector and using consistent configurations across all forms.

4.2 Manual Code Implementation

Since the project did not use APIs or third-party libraries, all features—from login to data
retrieval—had to be implemented from scratch. This increased the development time but also
provided a clearer understanding of how C# interacts with databases directly.

4.3 Debugging and Validation

Debugging SQL errors and form validations posed challenges, especially in handling unexpected
inputs. Implementing proper error messages and using breakpoints in Visual Studio helped
resolve issues efficiently.

6
 5. CONCLUSION
The Student LMS project achieved its goal of providing a functioning desktop-based school
management tool tailored for student use. Built entirely with C# and MySQL, the application
includes key features like login, attendance tracking, and course viewing within a user-friendly
interface. Although it is a local desktop application with no external connectivity, it lays the
groundwork for a larger system that could include online access, grade tracking, and more. The
project also helped in developing skills in software design, data handling, and application testing.
It stands as a reliable and simple solution for managing academic data at a student level.

6. REFERENCE LIST

1. Mach, D., Networking for Beginners (2019). – reference dapan