| Functional Requirements | ||
| SN | Requirements | Description |
| 1 | Display up-to-date information about CSO/Community in an intuitive and interactive UI/UX | Users should be able to browse the directory of CSOs on their mobile devices in a well presented UI/UX |
| 2 | Collect and upload details of CSO/Community Group to the backend so that it can be displayed in the platform | CSO/Community Groups should have the ability to enter their information and send it to the system in order for it to be displayed in the platform for everyone to see |
| 3 | Search CSO per keyword | The system should enable users to search for data using keywords |
| 4 | Display CSO location on a map | Users should be able to locate the CSOs on a map, and be able to get directions on how to physically locate the CSOs |
| Non-Functional Requirements | ||
| 1 | Security/Authentication | The system should allow authenticated users to access its APIs. Also user passwords should be salted and hashed instead of being stored in plain text in the database |
| 2 | Privacy | The system should not share user data without express consent. In addition, the system should request for user’s consent before collecting sensitive data such as a user’s location |
| 3 | Accessibility | The system should be easy to use and access |
| 4 | Maintainability | The system should be easily maintainable |
| 5 | Scalability | The system should be designed in such a way that when users increases, the system can also be scaled up to accommodate the increased number of users. This has been achieved by reducing coupling between the different modules of the system |