KPD closed beta Sign inRequest access

2. Draw the domain map

A Sales domain with a Store orders sub-domain, their owners and contacts, and the pipeline linked to them.

Part 2 of 10 in the Hello World tutorial · Follow this part in the guided wizard · Printable version

The domain map records which part of the business owns the data, and who to talk to. Pipelines link to it, and their data products then take their domain, sub-domain, owner and contact from it automatically (you will see this in Part 5). We use one domain, Sales, with one sub-domain, Store orders.

Open the domain map

  1. In the explorer, click Domain map (just under the project name).
Domain map in the explorer.
Domain map in the explorer.
  1. A Domain map tab opens with a Draw your domains card. Click Add a domain.
The empty domain map. Its palette (right) has only Domain, Sub-domain, Group box and Note.
The empty domain map. Its palette (right) has only Domain, Sub-domain, Group box and Note.
  1. In the list that appears, choose Domain.
Choose Domain.
Choose Domain.

Describe the Sales domain

A domain appears on the map, selected, with its settings in the properties panel. Fill in:

FieldType
NameSales
CodeSAL
DescriptionEverything about selling coffee: orders in our shops and on the app, payments and loyalty.
OwnerSales Data Team
ContactsClick to add a contact, then name Priya Shah, role Domain owner, contact priya.shah@hello-coffee.example
The Sales domain with its owner and contact. The fields scroll: Name and Code are above the description.
The Sales domain with its owner and contact. The fields scroll: Name and Code are above the description.

Add the Store orders sub-domain

  1. With Sales selected, a + appears on its right-hand edge. Click it.
The + beside the domain is quick add.
The + beside the domain is quick add.
  1. KPD offers only what can connect there: Sub-domain. Choose it. The sub-domain appears to the right, already wired to Sales.
Quick add suggests Sub-domain.
Quick add suggests Sub-domain.
  1. Fill in the sub-domain:
    FieldType
    NameStore orders
    CodeSAL-ORD
    DescriptionOrders placed in our coffee shops and on the app, and the customers who place them.
    OwnerStore Orders Team
    ContactsTom Reed, Product owner, store-orders@hello-coffee.example
Store orders, linked to Sales. Its References list shows the domain it belongs to.
Store orders, linked to Sales. Its References list shows the domain it belongs to.
The finished domain map: Sales and its sub-domain Store orders.
The finished domain map: Sales and its sub-domain Store orders.
  1. Click the data-product.kpd tab above the canvas to go back to the pipeline.
  2. Click an empty part of the canvas so nothing is selected. The properties panel shows the pipeline's General tab.
  3. Domain: choose Sales (SAL). Sub-domain: choose Store orders.
  4. Anchor statement: one sentence saying why the pipeline exists, in the DPCF form <domain> needs to <answer a question / take action> so that <business outcome>. Type:
    Sales needs to see every store order as it happens so that customers can see their order history and store managers can spot big orders straight away.
The pipeline linked to Sales / Store orders, with its anchor statement. It leads the design document in Part 8.
The pipeline linked to Sales / Store orders, with its anchor statement. It leads the design document in Part 8.

Save with Ctrl/⌘+S. Next: 3. Set up dev, test and prod.