Applications are groupings of use cases

All applications can be thought of as a grouping of use cases. That's all apps are anyways.

For example, in a simple Todo app, the use cases that the actor needs to be able to accomplish are: create todos, edit todos, delete todos, and get todos.

One could argue, "is it still a todo app if it doesn't have all the use cases that a todo app needs to have"?

While it might pose as a light-hearted theoretical discussion for another day, we can at least agree that the app is not complete until all of the agreed-upon use cases are built and working. You can see how…

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 solidbook.io 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 khalil@khalilstemmler.com.