So far we have been focused on getting the prerequisites for the project ready. We focused on creating a mental model for ourselves and confirmed that our understanding of the domain matched the understanding of our domain expert. By doing this, we started to create a shared language between all the people involved so that all parties can communicate about the project while avoiding most misunderstandings. With all this in place, we were able to identify a starting point for the project, and now that we know where to start and how to name our objects according to the domain, we can set up the project to fit this. Robert C. Martin says in his talk Architecture the lost years: Architecture is about intent that architecture is not created for the sake of itself but actually to state what the project is about and make it clear for the next person what each level covers. As we set up our application, we want to express what the application...
JavaScript Domain-Driven Design
JavaScript Domain-Driven Design
Overview of this book
Table of Contents (15 chapters)
JavaScript Domain-Driven Design
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
A Typical JavaScript Project
Finding the Core Problem
Setting Up a Project for Domain-driven Design
Modeling the Actors
Classification and Implementation
Context Map – The Big Picture
It's Not All Domain-driven Design
Seeing It All Come Together
Index
Customer Reviews