Rapidly Understand New Domains, So You Can Build Great Software for Them

Using Domain Storytelling, you can quickly gain clarity about a new domain's people, tasks, tools, work items, and events, avoiding costly misunderstandings and building better software. In Domain Storytelling, the method's inventors show how domain experts can clearly tell their stories, capture their insights with simple pictographs, show their work, get feedback, and get everyone on the same page.

Stefan Hofer and Henning Schwentner explain how and why Domain Storytelling works. They introduce the method's easy pictographic language, scenario-based modeling techniques, workshop format, and relationship to other modeling methods. And using step-by-step case studies, they guide you through solving many common problems, from creating new domain languages to deriving requirements, optimizing workflows to uncovering "shadow IT."

  • Fully align all project participants and stakeholders, both technical and business-focused

  • Master a simple set of symbols and rules for modeling any process or workflow

  • Use workshop-based collaborative modeling to find better solutions faster

  • Organize domains for manageability, and transform domain knowledge into requirements

  • Move your models from diagrams and sticky notes to code

  • Make better decisions about whether to build or buy software

  • Gain better visibility into your IT landscape so you can consolidate or optimize it

This guide is for everyone who wants more effective software -- from developers, architects, and team leads to the domain experts and executives who rely on it every day.

Table of Contents

  1. Cover Page
  2. Title Page
  3. Table of Contents
  4. Series Editor Foreword
  5. Foreword
  6. Preface
  7. About the Authors
  8. Part I: Domain Storytelling Explained
    1. Chapter 1. Introduction
    2. What Is Domain Storytelling?
    3. Your First Domain Story
    4. Chapter 2. The Pictographic Language
    5. Actors
    6. Work Objects
    7. Activities
    8. Sequence Numbers
    9. Annotations
    10. Modeling Canvas
    11. Groups
    12. Colors
    13. No Conditionals
    14. Putting It All Together
    15. A Grammar for Domain Stories
    16. Good Language Style
    17. Chapter 3. Scenario-Based Modeling
    18. What Are Scenarios?
    19. Scenarios in Domain Storytelling
    20. Concrete Examples as Scenarios
    21. Keeping an Overview
    22. Chapter 4. Scope
    23. Granularity
    24. Point in Time (AS-IS vs. TO-BE)
    25. Domain Purity (PURE vs. DIGITALIZED)
    26. Combining the Scope Factors: A Typical Journey
    27. Chapter 5. Modeling Tools
    28. Modeling on Paper or Boards
    29. Modeling with Software Tools
    30. Choosing a Tool
    31. Chapter 6. The Workshop Format
    32. Before the Workshop
    33. The Workshop
    34. After the Workshop
    35. TO-BE Workshops
    36. Remote Workshops
    37. The Moderator
    38. The Modeler as Separate Role
    39. Moderated Mode vs. Co-Op Mode
    40. Chapter 7. Relationship to Other Modeling Methods
    41. Domain-Driven Design
    42. EventStorming
    43. User Story Mapping
    44. Example Mapping
    45. Storystorming
    46. Use Cases
    47. UML
    48. BPMN
    49. Summary
  9. Part II: Using and Adapting Domain Storytelling for Different Purposes
    1. Chapter 8. Case Study—Alphorn Auto Leasing Inc.
    2. Explore Alphorn—The Domain as a Whole
    3. Drill Down into Risk Assessment—Understanding an Important Subdomain
    4. Clear Up Risk Assessment—Avoid Technical Jargon
    5. Optimize Risk Assessment—The TO-BE Process
    6. Introduce New Software—Combine Business Processes with IT Support
    7. Summary
    8. Chapter 9. Learning Domain Language
    9. Speaking and Listening to Understand Each Other
    10. Organizations Speak Many Domain Languages
    11. Using Natural Languages
    12. Lost in Translation
    13. What to Read Next?
    14. Chapter 10. Finding Boundaries
    15. The Joy of Multiple Models
    16. A Heuristic for Finding Subdomains
    17. From Subdomains to Bounded Contexts
    18. From Context Boundaries to Team Boundaries
    19. What to Read Next?
    20. Chapter 11. Working with Requirements
    21. Software Development as a Series of Conversations
    22. From Domain Stories to Requirements
    23. Adapt the Recipe
    24. Limitations
    25. What to Read Next?
    26. Chapter 12. Modeling in Code
    27. From Domain Stories to Domain Model
    28. Implementing the Domain Model
    29. What to Read Next?
    30. Chapter 13. Supporting Organizational Change
    31. Changing People’s Workflows
    32. Digitalizing Work
    33. What to Read Next?
    34. Chapter 14. Deciding Make or Buy and Choosing Off-the-Shelf Software
    35. Understand the Processes of Off-the-Shelf-Systems
    36. What to Read Next?
    37. Chapter 15. Finding Shadow IT
    38. Not Only Software Developers Develop Software
    39. Making Hidden Software Systems Visible
    40. What to Read Next?
    41. Chapter 16. Conclusion
    42. The Future of Domain Storytelling
    43. The Essence of Domain Storytelling
  10. Appendix. The History of Domain Storytelling
  11. Glossary
  12. Bibliography