Mon premier blog

.NET Domain-Driven Design with C#: Problem - Design - Solution Tim McCarthy
Publisher: Wrox

During the initial phase you don't even think about architecture or programming. It could be fractured and this creates serious problems to your project. A blog about .NET and software development in general by Andriy Buday. Eric Evans' Domain-Driven Design: Tackling Complexity in the Heart of Software was one of those. You would probably say that Car is on the Right, and you are correct. Your prime goal is to understand the business, all terms that customer uses and how he models the domain. That's the wrong approach (which there of course are solutions for, but that's out of the scope of this article). What is the difference between them? The solution is to see the external subsystem as a provider of services. The customer is in fact the architect. Domain driven design is all about understanding the problem that the customer is trying to solve. Lets start with the following question: Where is a car on the left or on the right?