FULL-STACK / DEPLOYED

Residence Management Platform

Bring room reservations and administration of a student residence together.

STACK
ReactJavaScriptNode.jsExpress.jsPostgreSQL
STATUS

deployed

Residence booking and internal management interfaces
01 / CONTEXT

Context

UCAC-ICAM hosts students in its residence in Douala. Running it involves presenting available rooms, receiving and processing reservation requests, allocating rooms and following residents throughout their stay.

These operations relied on manual exchanges and multiple files. This fragmentation reduced staff efficiency, made request follow-up harder and weakened data consistency: the same information could exist in several versions or get lost between exchanges. Students therefore needed an online reservation journey, and staff a single management tool.

IMG-RES-01 · CONTEXT

Residence Management — context

Step 01 / 06 · Paused

UCAC-ICAM hosts students in Douala.

01 · SITUATION02 · IMPLICATIONS03 · FRICTION04 · NEEDUCAC-ICAM residenceDOUALAPresent roomsROOMSHandle requestsBOOKINGSTrack residentsSTAYManual exchanges⚠ EMAILS · CALLSMultiple files⚠ DUPLICATESInconsistent data⚠ ROOM 12 ≠ ROOM 15Online booking + single toolONE SOURCE
Paused8 nodes · 9 links · Hover a node
  • Actor / entity
  • Component / data
  • Friction point
  • Need
Hover or select a component to see its role and connections.
From the field to the need: the situation behind the project.
02 / PROBLEM

Problem

How can students book online while administrative staff have a separate, reliable space to manage residents?

03 / SOLUTION

Solution

Development of two complementary applications connected to one back-end, to centralise reservations and administrative management. The first, public, lets students and prospective residents discover the residence and submit a request. The second, internal, lets staff follow requests and residents using the same data.

IMG-RES-02 · SOLUTION

Residence Management — solution

Step 01 / 06 · Paused

Scattered requests, inconsistent data.

01 · PROBLEM02 · BUILD03 · HOW IT WORKS04 · OUTCOMEScattered requests⚠ MANUALInconsistent data⚠ DUPLICATESBooking appSTUDENTSManagement appSTAFFShared back-endEXPRESS · RULESOnline booking✓ PAPERLESSSingle source✓ CONSISTENCY
Paused7 nodes · 6 links · Hover a node
  • Co-developed
  • Friction point
  • Outcome
Hover or select a component to see its role and connections.
Elements in blue are my personal contribution; the rest was built by the project team.
04 / CONTRIBUTION

Contribution

Full-stack team development of both applications (React front-end and Express.js / PostgreSQL back-end), followed by maintenance and evolution over the documented period.

05 / FEATURES

Features

  • Students view residence information and accommodation options.
  • They submit their reservation request online.
  • Staff follow requests and residents from a dedicated interface.
  • All reservation and management data is stored in a shared database.

To verify: availability, allocation, payment and notification rules, and administrative roles.

06 / ARCHITECTURE

Architecture

When a student submits a request, the reservation interface sends it to the Express.js back-end, which applies business rules and stores it in PostgreSQL. Staff find the same request in the management interface, which queries the same back-end. Both audiences therefore work from a single data source.

IMG-RES-03 · ARCHITECTURE

Residence Management — overall architecture

Step 01 / 05 · Paused

The student browses and submits a request.

01 · USERS02 · INTERFACES03 · BACK-END04 · DATAStudentPROSPECTIVE RESIDENTStaffADMINISTRATIONBooking UIREACTManagement UIREACTExpress.js APIBUSINESS RULESPostgreSQLROOMS · REQUESTS · RESIDENTS
Paused6 nodes · 5 links · Hover a node
  • Actor / entity
  • Co-developed
Hover or select a component to see its role and connections.
Elements in blue are my personal contribution; the rest was built by the project team.
07 / STACK

Stack

React / JavaScript, Node.js / Express.js, PostgreSQL.

08 / BENEFITS

Benefits

  • Reservations are available online, without manual steps.
  • Staff have a dedicated tool, separate from the student journey.
  • A single database removes duplicates and improves data consistency.
  • Request follow-up becomes simpler and faster.
EDITORIAL NOTE

This case study distinguishes the overall project scope from my personal contribution. No undocumented result or metric is presented.