> Home > Problem Background < Prev | Next >
The Actors on the system (typically the human users but can also include other systems) and the actions they take help to form the key scenarios, or flows, of the system. The following identifies the significant actors, actions and key scenarios that will inform the architecture of the Farmacy Family system.
The identified actors of Farmacy Family and their actions are as follows:
| Actor | Actions |
|---|---|
| Transactional Customer | * Places meal order on Farmacy Foods * Registers on Farmacy Family to become an engaged customer |
| Engaged Customer | * Creates Farmacy Family profile/account (onboarding) * Shares medical profile with Clinic/Dietician * Interacts with fellow Engaged Customer * Interacts with Dietician * Registers for Event * Registers for Class |
| Dietician | * Interacts with Engaged Customer * Accesses health data of the Engaged Customer * Gives customized diet plan to the Engaged Customer |
| Administrator | * Manages Class * Manages Event * Manages Farmacy Family User (Clinic, Dietician, Customer, Admin) |
| Clinic | * Provides analytics data to Farmacy Family, to improve engagement * Accesses health data of the Engaged Customer (as Dietician user) |
The following are the most architecturally significant scenarios/flows, derived from the Actors and Actions above, which will shape the architecture of the Farmacy Family system.
A Transactional Customer (Farmacy Foods customer) joins Farmacy Family to become an Engaged Customer.
An Engaged Customer (Farmacy Family customer), chooses to share their medical data with a specific Clinic.
An Engaged Customer (Farmacy Family customer) requests advice from a Clinic, based on the Engaged Customer's medical profile.
