How chamikakarunarathna/data-structures-campus-manager works
This is a Java console application for student records, service requests, recent-action history, and campus routes. The main workflow is menu-driven: users manage student records, queue and process student requests, inspect recent actions, or maintain campus locations and connections and run BFS traversal. Student records live in a linked list, with a search index providing sorted tree display and hash lookup; the list keeps the index synchronized on additions and deletions. The excerpts show Main coordinating these structures. CampusGraph is partial, so its detailed internal wiring is not expanded beyond documented operations.
Main entry points: Main.java Menu Controller · StudentLinkedList.java Student List · StudentSearchIndex.java Search Index · Student.java Student Record
Components 10
Student Records
- Student List
src/StudentLinkedList.java - Student Record
src/Student.java - Search Index
src/StudentSearchIndex.java - List Node
src/StudentNode.java
Requests And History
- Service Request
src/ServiceRequest.java - Request Queue
src/ServiceRequestQueue.java - Recent Actions
src/RecentActionStack.java
Campus Routes
- Campus Graph
src/CampusGraph.java
Console Application
- Menu Controller
src/Main.java
Other components
- Console User
Connections 10
- Console User → Menu Controller: chooses menu actions
- Menu Controller → Student List: manages records
- Menu Controller → Student Record: creates records
- Student List → List Node: links records
- Student List → Search Index: adds and removes
- Menu Controller → Search Index: searches via list
- Menu Controller → Service Request: creates requests
- Menu Controller → Request Queue: enqueues and dequeues
- Menu Controller → Recent Actions: records and displays
- Menu Controller → Campus Graph: manages and traverses