Skip to content

Modules and features

A real system has too many behaviors to draw on one flat timeline. Studio organizes them in layers, so that a team can find its way and so that each part of the business keeps its own space. This page explains the layers from the outside in.

Layer What it is Acme Commerce example
Organization Your company or team in Studio. It holds the people, the AI setup and the billing. Cratis
Project The top level of the work, typically one per team. Everything the team builds lives inside it. Acme Commerce
Application One system the team builds. Acme Shop
Domain One area of the business inside an application. It owns the boards and canvases that describe that area. Storefront
Event model The board itself: the timeline of that domain. Storefront
Module A whole area of the business inside a board. Shop
Feature A group of related behavior inside a module. Features can nest. Basket, Checkout
Slice One behavior. AddToBasket

Acme Commerce has five applications, one for each part of the company: Acme Catalog, Acme Shop, Acme Sales, Acme Purchasing and Acme Warehouse. They never share a database. They only tell each other what happened, through public events.

ORGANIZATION PROJECT APPLICATION DOMAIN EVENT MODEL MODULE FEATURE SLICE Cratis Acme Commerce Acme Catalog Acme Shop Acme Sales Acme Purchasing Acme Warehouse Storefront Storefront Shop Browse Basket Checkout My orders AddToBasket ChangeBasketQuantity RemoveFromBasket BasketView
From the organization down to one slice. Each layer holds the one below it.

A domain is more than a board. It is the home of everything that describes one area of the business:

  • Event models: the timelines.
  • Brainstorming boards: free-form boards for the early, messy thinking.
  • Personas: the people who use the area. See Screens and personas.
  • Concepts and constraints: the typed values and the things that must never happen twice.
  • State machines and workflows: the stages something goes through, and what happens step by step once something starts.
  • Event sources: the kinds of thing the domain keeps a history of, such as a basket or an order.
  • Given contexts and seed data: named starting situations for specifications and the sample data for a running model.

Some things belong to the whole application rather than to one domain: the policies that say who may do what, the UI profile that decides how the application looks, the design canvas with all its screens, and the application-wide list of events. The context map shows how the domains of an application relate through the events they publish and consume.

Inside a board, a module is one area of the business. The Storefront’s board has a module called Shop. If the board also described, say, payments, payments would get a module of its own beside it.

The rule of thumb is short: different area, different module. Two modules share nothing except events. A module can announce a fact, and another can reference it, so you can see a flow cross from one area to the next without one reaching into the other.

A feature groups the slices that belong together. The Shop module holds the features Browse, Basket, Checkout and My orders. A feature can contain sub-features when it grows too big to read.

Features are also where a team tracks progress and focus:

  • A feature can be raised to Draft, Analysis or Ready for implementation. Working statuses such as In progress are set on each slice.
  • You can focus on a feature, so that only it is drawn and the rest of the board stays out of the way.
  • A feature can be assigned, and its content can be generated or suggested for in one go.

A large model is read in layers too. Start with the modules to see the areas. Open a feature to see its behaviors. Read one slice to see exactly what happens. The Overview detail level and the focus view exist so that you never have to see everything at once.