Roles, boundaries, and Conway's Law in Use Case Design

Starting with role, let me ask you a question. If you were doing this by yourself for the first time, would you have labeled Visitor or Member as User? I know I would have.

So why didn't we?

Why didn't we just label User as the primary actor?

/book-assets/Software Design and Architecture Wiki 16ec9c6a09b3410ca7be7920be75e128/Part IX Building Web Applications with Domain-Driv 899ba58a83f04bc5ab3e41f3966d2110/11 Building a Real-World DDD app 6cf5f590a32b43f3bf8eebf5eb126bf9/How to plan a new project 0da832842455460482b064478998c7eb/Planning with UML Use Case Diagrams da9ed922628b45a5811c87ba131e49c7/Roles,%20boundaries,%20and%20Conway's%20Law%20in%20Use%20Case%20De%2074b49ecb2657448f99447c2acbc7b90b/4-use-cases-3-transparent.svg

It's because role dictates responsibility.

Role dictates responsibility

While we could call everyone a User, that could be unproductive to the ubiquitous language

Howdy 👋

This is an online wiki and book about the basics of software design and architecture with TypeScript by Khalil Stemmler, Developer Advocate @ Apollo GraphQL .

This book’s mission is to teach developers the essential skills and practices to write testable, flexible, and maintainable code.

You can read more about the learning journey in the "Software Design and Architecture Roadmap 🖼️".

Already bought it?

If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.

Want access?

You can read the intro to the book for free and visit to buy the book/wiki (it's currently on pre-sale for 33% off)! For recent updates, click here. To get an idea of my writing, read some of my best free content here and here.

Need help?

Something not working? Have a question? You can reach me on Twitter or