All software projects are special and there can never be a "one size fits all" approach, but as we have seen, a lot of thought has gone into all kinds of different approaches to development. A project goes through many stages of development, often it starts out exploring the basic ideas, sometimes we can not even be sure at that stage what the domain of the project will be. We then begin to factor out a certain core competency of the application and a core domain starts to evolve. At this stage the involvement of the business experts is crucial to make sure the domain aligns with the business needs, and the project does not get sidetracked due to misunderstandings, while the ubiquitous language is evolving along the way. The project tends to grow from one or two developers to a larger team, and team organization becomes more important since we need to start thinking about the communication overhead involved in the development as the assumption that...
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