sachin-54/studentmanagementsystem

Purpose and Runtime

This repository is a server-rendered Student Management System providing CRUD operations and search over MySQL-backed student records. It runs as a Python/Flask application, started through app.py, and serves HTML pages plus static CSS assets.

Core paths: app.py, requirements.txt, templates/

Application Entry and Routing

app.py is the application entry point and primary controller layer. It owns Flask route handling for the home page, student listing/search, creation, editing, and deletion. Routes accept browser form submissions, perform server-side validation, invoke persistence operations, set flash notifications, and redirect or render the appropriate page.

Core paths: app.py, templates/home.html, templates/students.html

Student CRUD Flow

The central domain object is a student record with id, name, age, gender, course, email, and phone, stored in the MySQL students table. Browser actions flow from add/edit/list pages to Flask handlers, then through the database layer for INSERT, SELECT, UPDATE, or DELETE; successful and failed operations return to page flows using redirects and flash messages.

Core paths: app.py, database.py, templates/add_student.html

Persistence Boundary

database.py encapsulates connection to the external MySQL service and is the repository’s database integration boundary. The deployment requires a reachable MySQL instance and a pre-created student_management database with its students table. Database credentials/configuration are materially coupled to this layer; config.py may provide application-level configuration.

Core paths: database.py, config.py, README.md

Server-Rendered Presentation

Jinja-rendered templates define the user-facing page states: landing page, student collection/search view, create form, and edit form. Templates are the interface boundary between Flask-provided data/flash state and browser interactions. The listing page is the likely integration point for search and per-record edit/delete controls.

Core paths: templates/home.html, templates/students.html, templates/edit_student.html

Frontend Assets and Interaction

CSS is organized per page and delivered as Flask static assets. Client-side JavaScript, where used, supports UI behavior such as delete confirmation and search interaction, while validation and persistence authority remain server-side in Flask.

Core paths: static/css/home.css, static/css/students.css, static/css/add_student.css

Operational Boundaries

The system is a local or server-hosted Flask process backed by MySQL; it has no indicated authentication, API layer, queue, object storage, or external SaaS dependency. Main trust boundaries are browser-to-Flask HTTP requests and Flask-to-MySQL database access. Authentication, authorization, pagination, exports, and advanced student-related modules are explicitly future work rather than current architecture.

Core paths: app.py, database.py, README.md