Demo: Larkspur's data landscape from sales floor to board report
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
work through the full data architecture for Larkspur as a design session; prepares ARC-023-LAB1.
Draft outline details
Step by step
- List the data sets from interviews: customers, products, prices, stock, orders, payments, returns, loyalty points.
- Assign a system of record to each: ERP for products, prices, and financials; CRM for marketing profile; platform for web and mobile orders; payment provider for card data.
- Draw the flow from 120 stores and the web shop into the platform, ERP, and a warehouse, and mark which arrows are copies.
- Planned mistake: point the board dashboard at the platform database "because it is quick". Fix: show checkout latency during a heavy query and move reporting to the warehouse fed by change capture.
- Fill the lifecycle table with retention per data set and a deletion trigger, including the warehouse and backup copies.
- Present the one-page data architecture view and note two decisions it already drives (warehouse choice, deletion plan).
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.