Domain Storytelling
Domain Storytelling is a collaborative modeling technique that captures domain knowledge through visual stories of actors, activities, objects, and interactions in a process.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A domain story is a visual representation of a precise domain process expressed as a single flow of activities and interactions.
- How it is used
- Explores future domain processes to identify valuable modernization requirements and improve the conceptual domain model.
- How deep it goes
- Defines the notation and develops workshop scoping and facilitation guidance, while keeping alternative scenarios in separate stories.
- Examples
- Illustrates a future-state prescription-validation process and a workshop replay of a partially modeled story.
- What you can do after
- Practice/perform a scoped, single-flow modeling workshop to explore a process and clarify modernization requirements.
Collaborative Software Design: How to facilitate domain modeling decisions
Domain Storytelling is a collaborative modeling technique that captures domain knowledge through illustrated stories of activities and interactions.
- How it is used
- Captures and visualizes business processes and cooperation during collaborative modeling conversations.
- How deep it goes
- Explains notation, facilitation, flexibility, and validation, but stops short of prescribing a complete modeling process.
- Examples
- Uses BigScreen’s ticket-reservation scenario, pictograms, numbered arrows, and views with or without legacy systems.
- What you can do after
- Evaluate conversations and cooperation by drawing, validating, and refining shared visual stories.
What to know first
- software design EventStormingSoftware design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
Related concepts
- software design EventStormingcontrasts with · Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
- actorhas part · An actor is a person, system, process, or computational entity that performs actions or participates in interactions within a system.
- workflowuses · A workflow is an organized sequence of coordinated activities or tasks through which work progresses toward a defined outcome.
Questions about Domain Storytelling
What is Domain Storytelling?
Domain Storytelling is a collaborative modeling technique that captures domain knowledge through visual stories of actors, activities, objects, and interactions in a process.
Which Manning books explain Domain Storytelling?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure and Collaborative Software Design: How to facilitate domain modeling decisions.
What should I know before learning Domain Storytelling?
Manning books that teach Domain Storytelling usually introduce software design EventStorming, stakeholder and system first.
What is the difference between Domain Storytelling and software design EventStorming?
Domain Storytelling is a collaborative modeling technique that captures domain knowledge through visual stories of actors, activities, objects, and interactions in a process. Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
What are the parts of Domain Storytelling?
Domain Storytelling includes programming task and actor.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

