Domain Storytelling
$12.00
Minimum price
$15.00
Suggested price

Domain Storytelling

Collaborative Modeling for Agile and Domain-Driven Design

About the Book

Domain Storytelling means that we let domain experts tell us stories about their tasks. While listening, we record the stories using a pictographic language. The domain experts can see immediately whether we understand their story correctly. After very few stories, we are able to talk about the people, tasks, tools, work objects, and events in that domain.

This book is an in-depth guide on how to use Domain Storytelling. It provides the means to use and adapt Domain Storytelling for different purposes, for example:

  • Crunch domain knowledge: Use Domain Storytelling to bring together domain experts from different departments, cross department boundaries and challenge assumptions. Work your way down from big-picture overviews to in-depth domain analysis.
  • Find good boundaries for your software: Domain Stories help to break down a domain into manageable slices. These are useful for splitting a monolith into modules, for designing microservices, and finding context boundaries in Domain-driven Design.
  • Domain Stories help you to determine which classes and methods you need to express your domain knowledge in code.
  • Derive requirements from Domain Stories to bridge the gap between domain knowledge and software development.
  • Support organizational change by making transparent how a new software system will change the way how people work.

About the Authors

Stefan Hofer
Stefan Hofer

Stefan is bad at drawing. However, he thinks he can build up domain knowledge by drawing Domain Stories. Stefan studied Software Engineering in Austria and has a PhD in computer science. Since 2005, he has been working for WPS – Workplace Solutions Ltd. in Hamburg. His job there is to help teams develop software that does the right job the right way.

Henning Schwentner
Henning Schwentner

Henning loves programming in high quality. He lives this passion as coder, coach, and consultant at WPS – Workplace Solutions in Hamburg, Germany. There he helps teams to structure their monoliths or to build new systems from the beginning with a sustainable architecture. Microservices or self-contained systems are often the result. Domain-driven Design as well as Domain Storytelling and other collaborative modelling methods help here. Henning is author of “Domain Storytelling – A Collaborative Modelling Method” and translator of “Domain-Driven Design kompakt”.

Table of Contents

  •  
    • A Note to our Readers
    • How to Read This Book
      • Limitations
      • The Other Book
    • Acknowledgement
      • The Book
      • The Approach
      • The Cover
  • Part One: Domain Storytelling Explained
    • Chapter 1: Introduction
      • What is Domain Storytelling?
      • Your First Domain Story
    • Chapter 2: The Pictographic Language
      • Actors
      • Work Objects
      • Activities
      • Annotations
      • Modeling Canvas
      • Groups
      • Colors
      • No Conditionals
      • Putting it all Together
      • Good Language Style
    • Chapter 3: Scenario-based Modeling
      • What are Scenarios?
      • Scenarios in Domain Storytelling
      • Concrete Examples as Scenarios
      • Keeping an Overview
    • Chapter 4: Scope
      • Granularity
      • Point in Time (As-Is vs. To-Be)
      • Domain Purity (Pure vs. Digitalized)
      • Combining the Scope Factors: A Typical Journey
    • Chapter 5: Modeling Tools
      • Modeling on Paper or Boards
      • Modeling with Software Tools
      • Choosing a Tool
    • Chapter 6: The Workshop Format
      • Before the Workshop
      • The Workshop
      • After the Workshop
      • To-Be Workshops
      • Remote Workshops
      • The Moderator
      • The Modeler as Separate Role
    • Chapter 7: Relationship to Other Modeling Methods
      • Domain-Driven Design (DDD)
      • EventStorming
      • User Story Mapping
      • Example Mapping
      • Storystorming
      • Use Cases
      • UML
      • BPMN
  • Part Two: Using and adapting Domain Storytelling for different purposes
    • Chapter 8: Case Study – Alphorn Car Leasing Inc.
      • Explore Alphorn – The Domain as a Whole
      • Drill Down into Risk Assessment – Understanding an Important Sub-Domain
      • Clear Up Risk Assessment – Avoid Technical Jargon
      • Optimize Risk Assessment – The To-Be Process
      • Introduce New Software – Combine Business Processes with IT-Support
    • Chapter 9: Learn Domain Language
      • Speaking and Listening to Understand Each Other
      • Organizations Speak Many Domain Languages
      • Natural Language
      • The Role of “Translators”
      • What Is Next? Where to Go From Here?
    • Chapter 10: Finding Boundaries
      • The Joy of Multiple Models
      • A Heuristic for Finding Sub-Domains
      • From Sub-Domains to Bounded Contexts
      • From Context Boundaries to Team Boundaries
      • What Is Next? Where to Go From Here?
    • Chapter 11: Modeling in Code
      • From Domain Stories to Domain Model
      • Implementing the Domain Model
      • What Is Next? Where to Go From Here?
    • Chapter 12: Working with Requirements
      • Software Development as a Series of Conversations
      • From Domain Stories to Requirements
      • Adapt the Recipe
      • Limitations
      • What Is Next? Where to Go From Here?
    • Chapter 13: Support Organizational Change
      • Changing People’s Workflows
      • Digitalizing Work
      • What Is Next? Where to Go From Here?
    • Chapter 14: Deciding Make or Buy and Choosing Off-The-Shelf Software
      • Understand Processes of Off-The-Shelf-Systems
      • What Is Next? Where to Go From Here?
    • Chapter 15: Finding Shadow IT
      • Not only Software Developers Develop Software
      • Making Hidden Software Systems Visible
      • What Is Next? Where to Go From Here?
  • Appendix
    • Appendix A: The History of Domain Storytelling
    • Bibliography
  • Notes

Authors have earned$10,346,017writing, publishing and selling on Leanpub, earning 80% royalties while saving up to 25 million pounds of CO2 and up to 46,000 trees.

Learn more about writing on Leanpub

The Leanpub 45-day 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub