Design a Digital Campus Housing Application System with OOD Concepts

Digital Campus Housing Application System Design Using OOD Principles

The Digital Campus Housing Application System facilitates the process of applying for, managing, and assigning student housing in a university setting. This system is designed to handle multiple aspects, including room assignments, application processing, maintenance requests, and communication between students and housing administrators.

By following Object-Oriented Design (OOD) principles, we can ensure that the system is modular, scalable, and maintainable. The core objects of the system will be designed around real-world entities such as students, housing units, applications, and staff. Below is an overview of the design process:

1. Identifying Key Classes and Objects

The main objects in the system should encapsulate the different functionalities and user roles. Some of the primary entities include:

• Student

• Housing Unit

• Application

• Administrator

• Maintenance Request

• Room Assignment

Each object has its attributes and behaviors, making it a manageable unit of the system.

2. Class Design

1. Student Class

   The Student class represents a student applying for housing. It contains personal and academic information, application history, and the status of current housing assignments.

   Attributes:

   • studentID (String)

   • name (String)

   • email (String)

   • phoneNumber (String)

   • housingApplication (Application)

   • assignedRoom (HousingUnit)

   Methods:

   • submitApplication() — Submits an application for housing.

   • checkApplicationStatus() — Views the status of the housing application.

   • updateContactDetails() — Updates personal contact information.

   • submitMaintenanceRequest() — Submits a maintenance request.

2. HousingUnit Class

   The HousingUnit class represents each housing unit available on campus, whether it’s a dormitory room, apartment, or house. It tracks its availability, type, and assignment status.

   Attributes:

   • unitID (String)

   • roomType (String) — e.g., Single, Double, Suite.

   • isOccupied (Boolean)

   • occupants (List of Students)

   • maintenanceStatus (String) — e.g., Clean, Needs Repair.

   Methods:

   • assignStudent(student: Student) — Assigns a student to the housing unit.

   • releaseUnit() — Marks the unit as unoccupied.

   • getAvailableUnits() — Returns a list of available housing units.

3. Application Class

   The Application class represents the student’s application for housing. It tracks the submission status, selected preferences, and the approval process.

   Attributes:

   • applicationID (String)

   • student (Student)

   • desiredRoomType (String)

   • applicationDate (Date)

   • status (String) — e.g., Pending, Approved, Rejected.

   Methods:

   • submitApplication() — Submits the housing application for review.

   • approveApplication() — Marks the application as approved.

   • rejectApplication() — Marks the application as rejected.

4. Administrator Class

   The Administrator class handles the management of housing applications, room assignments, and general system oversight.

   Attributes:

   • adminID (String)

   • name (String)

   • email (String)

   Methods:

   • reviewApplication(application: Application) — Reviews student housing applications.

   • assignRoom(application: Application, unit: HousingUnit) — Assigns a housing unit to a student.

   • updateRoomAvailability(unit: HousingUnit) — Updates the status of a room after assignment.

5. MaintenanceRequest Class

   The MaintenanceRequest class allows students to submit maintenance requests for their assigned housing units.

   Attributes:

   • requestID (String)

   • student (Student)

   • room (HousingUnit)

   • requestDetails (String)

   • status (String) — e.g., Pending, Completed.

   Methods:

   • submitRequest() — Submits a maintenance request.

   • updateStatus() — Updates the status of a maintenance request.

   • viewRequests() — Allows administrators to view outstanding requests.

6. RoomAssignment Class

   The RoomAssignment class encapsulates the process of assigning and unassigning rooms to students.

   Attributes:

   • assignmentID (String)

   • student (Student)

   • housingUnit (HousingUnit)

   • assignmentDate (Date)

   • endDate (Date)

   Methods:

   • assignRoom() — Assigns a room to a student.

   • unassignRoom() — Unassigns a room when the student leaves or is reassigned.

3. Relationships Between Classes

The system follows a many-to-many relationship model between students and housing units, as multiple students can be assigned to a single unit, and a student can have multiple housing applications or assignments.

• Student ↔ HousingUnit: A student can be assigned to multiple housing units over time. A housing unit can have multiple students assigned during its lifecycle.

• Student ↔ Application: A student can submit only one application at a time, but the application can have multiple review statuses before a room is assigned.

• Administrator ↔ Application: The administrator interacts with applications for approval and room assignment.

• Administrator ↔ HousingUnit: The administrator updates room availability, assigns students to rooms, and checks the maintenance status of rooms.

4. UML Diagram

A UML (Unified Modeling Language) class diagram can be created to visualize the relationships between classes. It would include the following:

• Student — Association with Application (1-to-many), RoomAssignment (1-to-many).

• HousingUnit — Association with RoomAssignment (1-to-many), MaintenanceRequest (1-to-many).

• Application — Associated with Student (1-to-1) and Administrator (many-to-1).

• Administrator — Manages Application (1-to-many) and HousingUnit (many-to-many).

5. Design Patterns

To make the system robust and extensible, we could use a few well-known Design Patterns in the object-oriented design:

• Factory Pattern for creating instances of Application, Student, and HousingUnit.

• Singleton Pattern for managing the system’s administrative access (e.g., only one active admin at any given time).

• Observer Pattern for notifying students about the status of their housing applications.

6. Conclusion

This Digital Campus Housing Application System uses Object-Oriented Design principles to model a housing application platform that is both scalable and maintainable. The design breaks down the complex system into smaller, manageable classes with clear responsibilities, making it easy to update or extend in the future as the needs of the campus housing system evolve.

With a clear structure, role-based access control, and the ability to handle both applications and maintenance requests, this system would streamline the process for students and administrators alike, creating a more efficient campus housing experience.