System requirements

Functional:

List functional requirements for the system (Ask the chat bot for hints if stuck.)...

being able to login/off

being able to set goals on different activities

being able to track goals and send notifications/reminders

Non-Functional:

List non-functional requirements for the system...

scalability (the server should be able to handle large number of users)

consistency (if user login with different device, it should show same progress)

availability (user should still be able to access it if there is no network)

Capacity estimation

Estimate the scale of the system you are going to design...

user will mainly send data like below estimate:

userid (32 bytes)

activities {

item {

value,

ativity_type

}

}

API design

Define what APIs are expected from the system...

get_activities(user_id)

add_activity(user_id, type, unit, name)

update_record(user_id, activity_id, value)

check_goal(user_id, activity_id)

set_goal(user_id, activity_id, value)

set/get_reminder(user_id, activity_id, time)

Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...

activity table

• activity_id
• user_id
• unit
• name

user table

• user_id
• name

goal table

• goal_id
• activity_id
• goal_value
• progress_value
• start_date
• end_date

reminder

• reminder_id
• time
• recursive
• recursive_type

High-level design

You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...

client -> api_gateway

api_gateway -> core_server

core_server -> database

mointor_server -> database

Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...

user add activities ---> add activity

user check activities ---> get_activities

user add goals ---> on activity

perordically phone will send data passively ---> update_record

mointor server ---> check_goal

mointor server ----> send notification to client

Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.

Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?