Requirements

Functional Requirements:

List the key functional requirements for the system (Ask the AI for hints if stuck)...

1. As user i would like to display the current day high/low temperature conditions and display the weather condition as image like sunny, cloudy ,rainy, windy, Fog and under it display next 4 days which makes it easy to see and comfortable for children as well
2. As user i want the system to detect my current location by GPS and display the weather conditions according to my current location and to detect if my location is changed to display wright conditions
3. As user I would like to display a slide of conditions for every hour with the temperature and the condition as image so i can scroll and see the next hours what is going to happen
4. Notification user in following cases increase in temperature , decrease of temperature , bad weather conditions coming that should take caution
5. User can set in setting his temperature view Fahrenheit /Celsius and set on what conditions he wants to notified like temperature increase , temperature decrease, rain , wind , natural disasters
6. As a user if system cannot get current location I would like to be prompt to enter the country then city in the selected country to get the conditions according to city
7. As user if i cannot get last weather conditions I would like to have a message that latest conditions cannot be fetched and displays last fetched weather conditions so i can know that the displayed data is not the last updated conditions

Non-Functional Requirements:

List the key non-functional requirements (performance, scalability, reliability, etc.)...

1. Scalability : High expected millions of users to review daily and Notify millions of user on weather changes
2. Availability : high availability as system cannot go down and must notify user if something danger is coming up
3. Consistency : Not high as user can view stale data if nothing dangerous is happing
4. Reliability : must be high as user makes important decision according to weather conditions system must return a weather condition cached if not able to get last results

Database Design

1. Database Choice

• Go with No Sql Dynamo DB
• Redis as cache database

1. Data Model

• user

id, appId ,settings , location

• forecast

id, location , date, low, high, wind ,sunrise ,sunset, speed , humidity

API Design

Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...

1. GET /api/v1/weather?q='36.0 - 36.70'

• input: can be city or longitude/latitude
• output : weather condition , high/low temperatures ,wind speed , humidity , sunrise, sunset for three days

1. GET /api/v1/weatherhour?q='giza'

• input :
• output : every hour and weather condition

1. POST /api:

• input : user setting as C or F. and Notifications, location or city
• output : response saved ok

1. GET /api/v1/notification

GetWeatherConditions

Writ Path:

• system get current location
• system send location 36.6 - 180.0
• system call external weatherAPI giving location
• external API returns result
• save to cache so no need to call external API every time

Read Path:

• system get current location
• system send location 36.6 - 180.0
• if available in cache get result and display

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

• API Gateway for routing and rate limiting
• Weather Service Get weather date fro External API or from cache
• Setting Service saves and fetches user settings from Dynamo db
• Dynamo DB save user settings
• External API to Fetch Wether Data
• Message Queue for notifications
• Notification Service notifies user for weather changes

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.