OOA/OOD is not Domain Driven Design

Analyzing functional requirements for your application to capture what and how your application should work is not necessarily domain driven design. Yes, both techniques leverage the domain model pattern to structure responsibilities in code.

My tip is to pay close attention to who the “real” domain expert, business user or sponsor is.

Translating use-case documents into a domain model representation doesn’t imply that you’ve captured domain concepts in code. Unless the use case writer is a domain driven design enthusiast.



Comments have been disabled for this content.