Defining the data model
Based on the requirements and app interactions discussed in the previous sections, you should be able to identify these four primary entities for your data model:
- Clients
- Properties
- Viewing slots
- Offers
Note
The preceding list is with an implied assumption that there is only one realtor. If we were to build this app for a realtor firm, we would also have a separate entity for the realtor.
Apart from these primary entities, we also need to be able to capture the different actions, types of clients and properties, and so on. In the previous chapters, we learned the benefit of keeping them as defined options in a table, and therefore, we will have to create tables for each of those.
Lastly, a realtor can map a single property on sale to multiple buyers. Similar to how we maintained OKR-Epic mapping in Chapter 13, Conducting Periodic Business Reviews Using Honeycode, in a separate table for scalability, we will apply the same rationale...
