A community‑scoped infrastructure management module within NICC that lets back‑office administrators and community partners view, add, and validate infrastructure assets for their own Indigenous communities.
Adnan
Backend and data validation lead
Ali
Deployment and infrastructure support
Amirreza
Frontend development lead
David
Frontend development and research support
Hamza
Backend and API/infrastructure lead
Mehedi
Product manager and UI/UX lead
Client
Client: Dr. Ahmad Teymouri
Part-Time Professor
University of Ottawa
Role in Project: Program Coordinator and Project Manager
Technical Advisor
Technical Advisor : Dr. Benjamin Eze
Adjunct Professor
The School of Engineering Design and Teaching Innovation, University of Ottawa
Role in Project:Technhical guidance
This course provided a rare combination of conceptual grounding and applied experience that was valuable for all members of our team. The lectures clarified how engineering design, requirements gathering, and validation fit together, and they gave us a vocabulary for thinking about problem statements, user needs, and iterative prototyping rather than jumping directly into coding or implementation details. That structure was important when we had to justify design choices to the client and to each other.
Working on the NICC Infrastructure Management Module gave us hands‑on practice with topics that are often only discussed in theory, such as scoping a minimum viable product, designing for specific user roles, and balancing new features with the need for robustness and testing. We learned how to translate community‑level needs into workflows like single‑asset entry, bulk upload with validation, and simple infrastructure hierarchies, and we experienced directly how client feedback can reshape both the user interface and the underlying data model. The project also forced us to coordinate frontend, backend, and data work across several people, which improved our teamwork, communication, and version‑control habits.
As a result, the course has strengthened our academic and professional development in several ways. It reinforced the importance of clear documentation and design reasoning, which will be useful for future research and capstone work. It also gave us a concrete example of a real system we can describe in portfolios or interviews, demonstrating experience with user‑centred design, geospatial data, validation logic, and collaboration with an external partner. Overall, the combination of lectures and project work has made us more confident in taking on complex, multi‑stakeholder software projects in our future studies and careers.