> Home > Solution Background < Prev | Next >
Conceptual System Design
The following show the conceptual design for the Farmacy Family system. More information about C4 modelling can be found in the C4 Models section of this documentation.
C4 Model Key
Farmacy Family Context Diagram
The Context diagram shows how the Farmacy Family system interacts with people and systems outside of the Farmacy Family system, and how it fits in to the overall landscape.
Four types of user have been identified; Transactional Customer, Engaged Customer, Dietician and Administrator. These are further defined in Actors, Actions & Significant Scenarios, with full definitions in the Glossary.
- The Administrator is required in order to manage other users, settings and data within the system. These privileges should only be given to specific, trusted employees of Farmacy Family.
- The Dietician is a user employed by a Clinic. The link to the Clinic gives the Dietician permission to access medical profiles and messages that have been shared with / sent to the Clinic. It is expected that there will be fine-grained authorisation controls so that a Dietician can be authorised to have this access, partial access (e.g. just read messages or see the inbox), or not have access at all.
- A Transactional Customer receives an invitation from Farmacy Foods to become an Engaged Customer of Farmacy Family.
Farmacy Family Container Diagram
The Container diagram shows elements/domains (containers) within the Farmacy Family system and how they relate to each other and to people and systems outside of the Farmacy Family system. Domains within the system are further broken down into Component diagrams at the next level, and so the Container diagram hides implementation details in order to see the larger picture.
Architecturally Significant Component Diagrams
The following are the most architecturally significant Component diagrams for the Farmacy Family system. Further Component diagrams can be created when other domains in the system are required to be developed in the Roadmap.
Medical Management
Relevant ADRs
User Management
Relevant ADRs
Analytics
Relevant ADRs
