How samithreddychinni/university-management-system works
Project Overview & Type
• The project is a console-based, CRUD application developed using Java procedural programming.
• It covers four major domain modules – Student Portal, Cafe Management System, Library Management System, and Transport Management System.
• The system relies on file handling (text files stored in a hierarchy of directories) for data persistence, and the user interacts via the console while both user-level and admin-level operations exist.
Main Architectural Components
a. User Interfaces and Controllers:
• Main Entrance (Main.java) – Acts as the primary controller initiating the program.
• Separate interfaces for User operations (e.g., signing up, logging in, course registration) and Admin operations (viewing or modifying stored data).
b. Domain Modules:
• Student Portal Module – Handles user registrations, course registration (CourseRegistration.java, Courses.java), and student records.
• Cafe Management Module – Manages functionalities such as displaying menus, item selection (DrinkSelection.java, FoodSelection.java, Displaymenu.java), bill generation, and payment processing. Use files under the "cafe" directory to illustrate storage of menus and bills.
• Library Management Module – Covers book searches, borrowing, returns, and fines (LibraryManagement.java, Library.java). Representation should include files like AvailableBooks.txt and BorrowedBooks.
• Transport Management Module – Deals with bus registrations, route information, and fee handling (TMS.java, TransportManagement.java). The "transport" directory (including Bus ID files and registration data) is key to illustrating data persistence.
c. Data Persistence (File Handling Subsystem):
• File-based storage for each module (e.g., "cafe", "courses", "library", "transport", and additional files like "roll_numbers" and "students_data").
• Configuration files and naming patterns (each student or transaction is stored as a reg_number.txt or similar naming convention).
Relationships and Interactions
• The Main controller directs flow to the appropriate module based on user type (Admin vs. Student) and selected operation.
• Each module performs CRUD operations on its respective data store (resolved through file-handling operations).
Architectural Patterns and Design Principles
• Separation of Concerns – Each domain (Student Portal, Cafe, Library, Transport) is neatly separated into its own set of classes and file directories.
• Procedural Programming – Note that the application is not object-oriented in the full enterprise sense but is organized into discrete functions across Java files.
• Data Persistence via File System – Instead of a database, the design relies on directories and text files. This can be indicated as an I/O subsystem that all modules interact with.
Including Relevant Technologies and Libraries
• Java for the core logic.
• Basic file I/O operations (using Java’s standard libraries such as java.io.*).
• Since it is a console-based application, no GUI frameworks are involved.
Final Recommendations
• Even though the system is primarily file-based and procedural, showing the “layers of responsibility” (user input, processing logic, and data storage) will benefit future development or maintenance.
• Double-check that the square aspect ratio and decreased overall width are maintained so that your design remains visually balanced when presented.