Combining Event Modeling + Behavior Driven Development + AI
Learn how to model complex business rules with Given / When / Then in an event-driven system — step by step. In this video, I’ll walk you through a complete example using bank account management: from opening accounts to enforcing rules like “a user can only have one account” and updating read models when accounts are deactivated.
You’ll see how to:
Create commands, events, and screens in your model
Keep your system information complete at all times
Use Given / When / Then to describe behavior in a clear, testable way
Add test data and instantly validate rules (even with AI assistance)
Build and update read models from events
Model deactivation flows and reflect them in your UI
By the end, you’ll understand how to go from idea → model → specification → implementation without guesswork — and how AI can help validate your design.
If you’ve ever struggled to keep requirements, behavior, and implementation in sync, this method will change the way you design software.
#EventModeling #EventSourcing #GivenWhenThen #DomainDrivenDesign #SoftwareArchitecture #CQRS #AI