Architectural Requirements Document
This strategy breaks the system up into smaller factors which makes reasoning large complex problems easier
The application should work anywhere and at anytime.
The app should be usuable
The app should be reusable, such that users can use it more than once to find routes and access other services.
The application should be able to provide the user of his needs without the user having to wait for the application for a long time.
The user should be able to rely on the application to give accurate routes and accurate information on load shedding schedules.
One shouldn't be able to sniff and steal another's personal data.
The application needs to expand to in order to provide services for more areas. The database should be scalable to allow more data to come in.
Becuase of the project delivarable time, it is not feasable to map the application to the whole of South Africa.
Not all the data we have will be represented becuase of the lack of spatial data. This leads to following point: suburb extensions would be exluded.
Example: instead of showing the load shedding schedules for Menlopark extension 3, we would only show Menlopark as a whole.
We only have suburb data from the 2011 census
Figma – To design wireframes and mockups for planning purposes.
Angular Ionic – Develop Front-End for mobile and desktop web apps
Rust Rocket – API, Reason for using Rust Rocket is guaranteed type safety and speed.
MongoDB – Database to store everything needed.
AWS (Amazon Web Services) EC2 Hosting – Will do all our hosting needs on a virtual Linux machine.
GitHub – Used for version controlling the repository.
GitHub Project Board – For project management, issue tracking and user stories.