Neighbourhood (RW) Information System

The Problem

At the neighbourhood (RW) level, population records, contribution tracking, and document handling were manual: paper forms, spreadsheets, and lots of back-and-forth. That meant lost documents, inconsistent data, and slow service for residents who just wanted a letter processed or their dues recorded.

My Role

As System Analyst, I owned the requirements and design side. I sat with the actual administrative needs, translated business needs into system specifications, and stayed involved through development to make sure what got built matched what was asked for.

Analysis and Documentation

I produced the specification package the build was based on:

• Software Requirements Specification (SRS) describing every functional requirement of the system
• Use case specifications for residents and administrators, mapping each task to its flow and access rights
• Database designs modeling residents, households, contributions, and documents with their relations

Writing these forced me to think from the user’s chair, especially for non-technical RW admins who would operate the system daily.

What I Built Together With the Team

I collaborated on the development of a Laravel-based web application using Tailwind CSS, Cloudinary, and MySQL:

Population Management

• Resident registration and profile management backed by the database schema I designed
• Structured population records replacing scattered spreadsheets, so admin lookups take seconds instead of minutes

Contribution Tracking

• Recording and tracking of neighbourhood dues per household
• Clear history of who paid what and when, visible to both residents and admins

Document Handling

• Residents can request administrative documents through the system instead of queuing in person
• Document uploads and storage handled via Cloudinary
• Status visibility so residents know where their request stands

Handover

I developed user manuals giving clear, step by step guidance for operating the system, written for readers with no technical background.

Technical Stack

• Backend: Laravel
• Frontend: Tailwind CSS
• Database: MySQL
• Media: Cloudinary

What I Learned

This project showed me how much adoption depends on documentation, not just code. A system for RW admins lives or dies on whether a non-technical user can open the manual and get their task done, and writing the SRS first meant development arguments were settled by the document instead of by opinion.