Angelo Ponniah, Verrazzano Class of 2026, completed a major in Info Systems & Informatics and minors in Business and Design & Digital Media
For my capstone project, Data Driven Staten Island, was an opportunity to combine my academic interest in information systems with my desire to create something useful for my community. At its core, the project is a web-based economic dashboard and resource platform built to help Staten Island residents better understand local economic conditions and discover support services, jobs, and programs in one place. I chose this topic because Staten Island is often described as NYC’S forgotten borough, and I wanted to build a project that addressed the challenge of fragmented access to local information. Rather than treating the capstone as purely theoretical exercise, I wanted it to become a practical system that could actually support decision making for students, business owners, and community organizations.
The project grew out of a simple question: how can public
data be made more useful at the local level? I noticed that economic and
community information about Staten Island was spread across many different
sources, including government portals, public reports, and other datasets that
were not easy for an average user to interpret. That fragmentation creates a
barrier for people who need quick, understandable information. My capstone
addressed that problem by bringing together key indicators such as unemployment,
business activity, transit ridership, and rent into a single dashboard. I also
connected the data to community resources and application workflows so that the
project would not stop at visualizing information, but would also support
action.
One of the most valuable parts of the capstone was the
technical design process. I built the application using Flask on the backend,
SQLite for storage, and HTML,CSS, Javascript, and Chart.js on the front end.
This structure allowed me to keep the system manageable while still
demonstrating a complete full stack workflow. The backend provides routes for
the web pages and API endpoints for the dashboard, while the frontend retrieves
JSON data and renders charts dynamically. That separation helped me understand
how web applications move data from the database to the user interface. I also
learned the importance of planning for failure because public API’s are not
always available or consistent. I built fallback logic so the dashboard can
still function even when external services are down. That decision made the
project more resilient and taught me that reliability is just as important as
functionality.
Another important lesson came from thinking carefully about
the database structure. Instead of storing everything in one large table, I
organized the system so that dataset, time-series values, user accounts,
feedback, job applications, and program applications each have a distinct role.
This made the system easier to query, easier to maintain, and easier to explain
it. It also reinforced what I have learned as an information systems student:
good design is not only about making something work, but also making it
understandable, extendable, and efficient. I became more comfortable tracing
how data moves through the system, from the moment a user submits a form or
charges a filter to the point where the application stores or displays the
result.
The capstone also helped me grow personally. At the
beginning, I expected the project to be mostly about building a website, but it
became much more than that. It required research, planning, coding, debugging,
and documentation, all while keeping the needs of the user in mind. I had to
think about how a non technical person would use the dashboard, how a professor
would evaluate the technical depth, and how the project could be explained
clearly in both written and spoken form. That process strengthened my
communication skills and taught me how to defend my choices with evidence
rather than assumptions. I also learned how to manage a large project by
breaking it into smaller parts and focusing on one feature at a time instead of
trying to complete everything at once.
What surprised me the most was how much documentation mattered. The project was not only judged by the final website, but also by how clearly I could explain the design, data flow, and purpose behind it. The use cases, diagrams, and written reflection all became part of the overall argument for why the system was built the way it was. This made me realize that documentation is not extra work; it is part of the project itself. A well-documented system is easier to maintain, easier to debug, and easier for someone else to extend in the future.
If I continue developing Data Driven Staten Island, I would
expand the data pipeline so updates happen automatically on a schedule, improve
the application and resource management features, and add more analytics that
show how people are using the platform. I would also like to make the system
more interactive for community partners so that organizations could update
their own listings or upload new information directly. In a larger version of
the project, I would also consider expanding the model to other boroughs or
neighborhoods. Even so, I believe the current version already accomplishes
something meaningful: it shows how ISI can be used to transform public data
into a tool for local empowerment.
Overall, my capstone helped me connect technical skills with
community impact. It challenged me to think like a developer, a problem-solver,
and a designer at the same time. Most importantly, it showed me that technology
can make local information easier to access, easier to understand, and more
useful for the people who need it most. Through this project, I gained not only
a stronger understanding of web development and data handling, but also a
deeper appreciation for how technology can serve the community.