CHAPTER 3
Domain-Driven Design
We don't write code; we solve business problems.
Introducing Domain-Driven Design
How do you measure the success of a software project? Do you rely solely on deploying the solution on schedule? Does the quantity and quality of design documents, such as a vision and scope document, package diagrams, component diagrams, key feature class diagrams, and other various Unified Modeling Language (UML) diagrams provide an indicator of a project’s success or failure? Have you seen the documentation created in a waterfall design–based software development project? I think trying to keep all of these documents in sync with ...
Get Pro XAML with C#: Application Development Strategies now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
