Based on area(s) Draw a polygon(s) on the map

Move all testing to cypress front end

Once WIP-5 is complete.

• Ensure that data is received from Backend to Frontend

Scaffold based off of Figma
Basic unit tests

Changing to Mapbox API due to Google Maps limited functionaility.

Task:

• Need to setup the Production environment on AWS.
• Discuss maybe setting up a a development environment with Digital Oceans (As there is $200 credit accredited by the university) This will be for the Development Branch once features are completed.
• Badges (Research what would work best)
  • Code Coverage
  • Monitoring

Research on the Wards and how it relates to the Loadshedding Groups

Acceptance Criteria:
Create mock of what the UI should look like.

Read updated Demo 1 spec

Description

Setup a Docker container for deployment.

For SRS Document

Tasks to be completed:

• Architectural design strategy
• Architectural strategies
• Architectural quality requirements
• Architectural design & pattern
• Architectural constraints
• Technology choices

We need to fix CodeCov so that we get coverage on the frontend side and also the cyprus stuff working

We intend on having 2 users.

1 user who is not registered and a user who is registered (can also login).

The idea is to make the app usable even if the user is not singed in.

Task:
List atleast 3 use case for each user. Then specify a high-level requirement.
Research Trace-ability matrix

Task when in meeting:
Draw the use case diagrams and further indicate subsystems

Integrate the backend with the AI Python script.

Acceptance Criteria:
Setup 2 host platforms one for production environment and one for development environment.

For SRS Document

BACKEND

• Create an ednpoint to retrieve mock data for area(s) in Pretoria
  What must be present
• Loadshedding stage
• Loadshedding times
• Area (and surrounding areas) Loadshedding

On Schedule page, The user must be able to select a location on the map and get that area correctly

We need to serve the GeoJSON for an area to the front-end from the back-end.

It would be a good idea to add SSL/TLS to the backend so that we can ensure all connections to the backend are properly encrypted.

Basic Requirements

• Stateless Authentication mechanism using JSON Web Tokens (JWTs).
• Users must be able to authenticate without being registered.
• Registered users may have specific permissions assigned to them, which need to be reflected in the token.
• Registered users must be able to request a cookie allowing them to obtain a JWT when they require one.

Security Requirements

• Stateless tokens must expire within 24 hours to mitigate token-stealing.
• Tokens must be client-readable and tamper-proof.
• JWT Token algorithm: RS256 (RSA signatures with SHA-256 digests)
• Server private key modulus length must be at least 4096 bits.

Setup a CI/CD pipeline.
Protect Development and Main Branch.
Make sure the integrity of the branching strategy is followed.
All pushes/merges to Main need to be deployed on Production Server and the same for Development (All pushes/merges to Development need to be deployed to Development).

For Every pull request made

• Run Linting
• Run Tests
• Check if Building passes

For Class project

Research on suburb coordinates(latitude, longitude) should be multiple in order to outline the area

Research different MAP APIs that can potentially go past the ward level

For SRS Document

Web Scrape Tshwane Loadshedding times.
Ensure the scraped data is normalised in the DB

A user should be able to see loadshedding statistics, uptimes, downtimes, reports?(leave for now) etc

• Effort estimation.
• Project planning and scheduling.
• Resource allocation.
• Risk management.