← Part 05: Plan the architecture From Idea to Product · Part 5 · Exercise 4 · 10 minutes

Exercise 4 · Design your architecture: Architecture Diagram and Capabilities Checklist

Time10 minutes, after the P · Plan the architecture slides
Blueprint sections9 Architecture
You needYour AI assistant; your Blueprint with section 8, Product requirements, filled in
You leave withArchitecture Diagram v1, a list of the data you need, the main risks, and your Capabilities Checklist
Safety tipPlan to collect as little personal data as possible. Data you never collect can never leak

Where you are

You know what the first version should do. Now you look at what a real version would need behind the scenes. You will not write code or choose programming languages. You will learn enough to understand the parts, brief a developer or an AI tool, and spot risks early.

What you will make

A simple architecture diagram that shows the main parts and what each one is responsible for:

  • Frontend: the screens people see and use.
  • Backend: the rules and logic behind the screens.
  • Database: where information is stored.
  • External services: things you use rather than build, such as email or payments.
  • Security, hosting and monitoring: keeping it safe, keeping it online and knowing when something breaks.

You also list the data you need, the main security, privacy and operational risks, and tick the capabilities your MVP needs from a checklist of ten.

For TutorDesk: the frontend is a booking page for parents and a simple calendar for the tutor; the backend checks that a slot is free; the database stores tutors, lesson slots and bookings; an email service sends confirmations. Data needed: tutor name and email, slot times, and a parent's first name and contact email. Main risk: lessons involve children, so TutorDesk should never ask for a child's name or details.