Aadhya Sinha Centralized College Database Report Final
Aadhya Sinha Centralized College Database Report Final
SCHOOL
SESSION : 2025-26
PROJECT REPORT
SUBMITTED BY:
_______________________ _______________________
S.NO. TOPICS
1. Introduction
2. Objective
3. Methodology
4. Data Modeling
6. ER Diagram
8. Limitations
9. Conclusion
10. Bibliography
INTRODUCTION
In this system, each student and staff member is assigned a unique identification
code, and all associated data is recorded and stored centrally. This allows
authorized users to access, retrieve, and update information such as student
details, academic records, attendance, faculty data, course schedules, and more,
from any authorized terminal within the college network.
OBJECTIVE
This system will handle the organization, retrieval, processing, and reporting of
data related to students, faculty, staff, academic records, and institutional
resources. It eliminates the need for manual handling of departmental data by
offering an integrated, secure, and user-friendly solution.
The goal of this project is to build a comprehensive and centralized system that
simplifies everyday tasks, reduces redundancy, and enhances productivity
through the use of reliable and modern computing methods. It focuses on
replacing outdated manual systems with a smart, automated framework that
offers real-time access to accurate data for better decision-making.
Scope
The Presentation Layer is responsible for designing the user interface of the
system. It ensures that users, including students, faculty, and administrators, can
easily interact with the application using intuitive layouts and navigation options.
The Logic Layer handles the core functionality of the system. This includes
processing user inputs, enforcing business rules, managing workflows such as
student registration, attendance tracking, examination processing, and
generating reports.
The Database Layer involves the analysis, design, and development of a robust
database schema to store all institutional data. This layer ensures data
consistency, integrity, and secure storage.
To design the interface, tools like Visual Basic, .NET Framework, or modern web
technologies like React or Angular are used depending on the platform selected.
The interface is kept user-friendly and adaptive to support both novice and
experienced users.
➢ Requires only basic computer knowledge, making it accessible for all staff
members and students.
➢ Fully customizable and adaptable to institutional needs, whether large or
small colleges.
➢ A built-in settings module allows for easy configuration of roles,
permissions, academic structures, and workflows.
➢ Supports multilingual capabilities, offline sync options (if needed), and
role-based dashboards for faculty, admin, and students.
➢ Designed to scale with additional modules such as biometric attendance,
fee payment gateways, or e-learning platforms.
DATA MODELING
Course Table
Enrollment Table
Attendance Table
Logic Model
Inputs
1. The Centralized College Database must accept input data from various
users including administrators, faculty, and students.
2. Entry of new student records including personal and academic details.
3. Faculty registration and department assignments.
4. Entry of subject-wise attendance and performance data.
5. Providing search features for quick retrieval of student or faculty records.
6. Entry of fee details, dues, and payment status.
Process Logic
Hardware Requirements
Software Requirements
Language to be Used
Since users can interact with any component in any order, VB requires each
component (e.g., buttons, forms, lists) to be programmed individually to respond
to specific events. Therefore, a Visual Basic application consists of multiple
independent subprograms, each handling a specific user action, and all
working together cohesively.
Output
After processing and validating the data within the Centralized College
Database system, the following outputs will be generated:
LIMITATION
This application performs limited operations of a Centralized College Database.
The current limitations are as follows:
CONCLUSION
The Centralized College Database System has been designed keeping in mind the
requirements of small to medium-sized educational institutions. It is a reliable software
that supports all core functionalities such as storing and updating student records,
faculty details, course allocations, attendance tracking, and examination results. It allows
the administrator to manage departments, enrollments, and class schedules efficiently.
In addition, features like login authentication and role-based access ensure that different
types of users—such as admin staff, faculty, and students—can perform only their
respective tasks. Students can check their academic records, attendance status, and fee
dues, while faculty members can view class allocations and submit attendance or
grades. Though basic in nature, this application provides a structured and centralized
environment for managing key college data in an organized manner.
BIBLIOGRAPHY
➢ Hoffer, Jeffrey A., Ramesh Venkataraman, and Heikki Topi. Modern Database
Management. Pearson Education, 2016.
➢ www.geeksforgeeks.org
➢ www.w3schools.com
➢ Rob, Peter, and Carlos Coronel. Database Systems: Design, Implementation, and
Management. Cengage Learning, 2012.
➢ Maimon, Oded, and Lior Rokach. Data Mining and Knowledge Discovery
Handbook. Springer, 2010.