The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domain itself the main focus of the project, and maintaining a software model that reflects a deep understanding of the domain. The vision was brought to the world by Eric Evans in his book "Domain Driven Design". Eric's work was based on 20 years of widely accepted best practices in the object community, as well as Eric's own insights.
Despite the importance of Domain Driven Design, not many people are aware of it, which is why InfoQ commissioned the writing of a 100 page mini-book: Domain Driven Design Quickly, and like all InfoQ books is available for free download as well as print-purchase. The book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' 576 page book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
Comentarios, discusiones, notas, sobre tendencias en el desarrollo de la tecnología informática, y la importancia de la calidad en la construcción de software.
lunes, diciembre 11, 2006
Texto sobre "Domain Driven Design"
En Infoq se publica un texto gratuito sobre diseño basado en el dominio (Domain Driven Design):
Suscribirse a:
Comentarios de la entrada (Atom)
No hay comentarios.:
Publicar un comentario