How isavb03/university_result_management_system works
Project Type and Purpose
• This is a full-stack Java web application (“University_Result_Management_System”) built with JSP/Servlets and backed by a MySQL database.
• It provides a web interface for administrators and students to login, add/view results, and manages persistence via JDBC.
File Structure Analysis
• src/main/java/project/ConnectionProvider.java → Business/data‐access layer (JDBC connection helper).
• src/main/webapp/ → Presentation layer
• JSPs (addNewStudent.jsp, adminHome.jsp, studentHome.jsp, etc.)
• HTML assets (adminLogin.html, index.html, header.html)
• Static resources: /assets/css, /assets/js, /assets/fonts, /images
• WEB-INF/web.xml and WEB-INF/lib/mysql-connector-java.jar → Deployment descriptors & libraries
README Insights
• Confirms use of Java servlets/JSP and MySQL.
a. Presentation Layer
• Web Browser (Client)
• JSP/HTML pages and static assets served by the web container (Tomcat/Jetty)
b. Business Logic Layer
• JSP pages with embedded servlet logic (e.g. adminLoginAction.jsp)
• Servlet container
• ConnectionProvider.java for managing DB connections
c. Data Layer
• MySQL Database
• JDBC Connector (mysql-connector-java-5.1.48.jar)
Relationships and Data Flows
• User → HTTP request → JSP/Servlet (Presentation → Business)
• JSP/Servlet → uses ConnectionProvider via JDBC (Business → Data)
• MySQL → returns resultset → ConnectionProvider → JSP for rendering (Data → Business → Presentation)
Architectural Patterns and Principles
• Three-Tier Architecture (Presentation, Business, Data)
• Separation of concerns:
• Presentation: JSP + static resources
• Business: minimal Java code (ConnectionProvider + JSP logic)
• Data: MySQL accessed via JDBC
• MVC influence: JSPs act as both View and Controller; ConnectionProvider as Model/data-access.
Technologies and Frameworks
• Java Servlet container (e.g., Apache Tomcat)
• JSP (JavaServer Pages)
• JDBC with MySQL Connector/J
• MySQL RDBMS
• Frontend: HTML5, CSS3, JavaScript