Domain Storytelling: A Collaborative, Visual, and Agile Way to Build Domain-Driven Software
- Downloads：8476
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-10-09 08:51:42
- Update Date：2025-09-07
- Status：finish
- Author：Henning Schwentner
- ISBN：0137458916
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
Build Better Business Software by Telling and Visualizing Stories
From a story to working software--this book helps you to get to the essence of what to build。 Highly recommended！
--Oliver Drotbohm Storytelling is at the heart of human communication--why not use it to overcome costly misunderstandings when designing software？ By telling and visualizing stories， domain experts and team members make business processes and domain knowledge tangible。 Domain Storytelling enables everyone to understand the relevant people， activities， and work items。 With this guide， the method's inventors explain how domain experts and teams can work together to capture insights with simple pictographs， show their work， solicit feedback， and get everyone on the same page。
Stefan Hofer and Henning Schwentner introduce the method's easy pictographic language， scenario-based modeling techniques， workshop format， and relationship to other modeling methods。 Using step-by-step case studies， they guide you through solving many common problems:
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 Draw clear boundaries to organize your domain， software， and teams Transform domain knowledge into requirements， embedded naturally into an agile process Move your models from diagrams and sticky notes to code 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， product owners， and executives who rely on it every day。
Register your book for convenient access to downloads， updates， and/or corrections as they become available。 See inside book for details。
From a story to working software--this book helps you to get to the essence of what to build。 Highly recommended！
--Oliver Drotbohm Storytelling is at the heart of human communication--why not use it to overcome costly misunderstandings when designing software？ By telling and visualizing stories， domain experts and team members make business processes and domain knowledge tangible。 Domain Storytelling enables everyone to understand the relevant people， activities， and work items。 With this guide， the method's inventors explain how domain experts and teams can work together to capture insights with simple pictographs， show their work， solicit feedback， and get everyone on the same page。
Stefan Hofer and Henning Schwentner introduce the method's easy pictographic language， scenario-based modeling techniques， workshop format， and relationship to other modeling methods。 Using step-by-step case studies， they guide you through solving many common problems:
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 Draw clear boundaries to organize your domain， software， and teams Transform domain knowledge into requirements， embedded naturally into an agile process Move your models from diagrams and sticky notes to code 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， product owners， and executives who rely on it every day。
Register your book for convenient access to downloads， updates， and/or corrections as they become available。 See inside book for details。
Reviews
Ozgur
，
To achieve DDD， you must extract domain model using some methodology。 Domain Storytelling is a promising one for this purpose。 It enables actors， work objects and activities to be captured much more efficiently in the context of real world domain stories told by domain experts。 Domain Storytelling can be used in conjunction with other methodologies like Use Cases， User Story Mapping or Event Storming。 The book clearly explains all these topics very well。 Authors have solid experience in many pro To achieve DDD， you must extract domain model using some methodology。 Domain Storytelling is a promising one for this purpose。 It enables actors， work objects and activities to be captured much more efficiently in the context of real world domain stories told by domain experts。 Domain Storytelling can be used in conjunction with other methodologies like Use Cases， User Story Mapping or Event Storming。 The book clearly explains all these topics very well。 Authors have solid experience in many projects and the book seems to be the reflection of that experience; it is an easy-to-read and very enlightening book。 。。。more
Rafael Gorski
，
A simple way to describe domains and stories about it。 Should be very applicable in workshops with engineering teams and business customers。A good composition of common practices around requirements engineering， system thinking， and software modeling prior explored by other authors。 Good to see references to UML and BPML。 I see the need to have auxiliary diagrams to express clear state changes which is a common task during customer workshops。 OPN comparison is not explored， however I would recom A simple way to describe domains and stories about it。 Should be very applicable in workshops with engineering teams and business customers。A good composition of common practices around requirements engineering， system thinking， and software modeling prior explored by other authors。 Good to see references to UML and BPML。 I see the need to have auxiliary diagrams to express clear state changes which is a common task during customer workshops。 OPN comparison is not explored， however I would recommend to system level modeling。 I missed a specific support for problem modeling， the use of “coarse-grained， Pure， As-Is” is not prescriptive。 I would suggest Problem-Based SRS approach on this case in exchange with domain storytelling design。My review is based on the rough cuts version。 。。。more
Ignacy
，