Differences between revisions 1 and 3 (spanning 2 versions)

DomainDrivenDesign

the essence of DDD is profoundly simple: capture the domain model in domain terms, embed the model in the code, and protect it from corruption.

Understand the business, business logic independently of the tech used
Capture the domain model, in domain terms, through interactions with domain experts.
Embed the domain terminology in the code.
Protect the domain knowledge from corruption by other domains, technical subdomains, etc.

-  ⇤ ← Revision 1 as of 2020-03-03 12:04:49 → 
  Size: 284
  Editor: localhost
  Comment:
+   ← Revision 3 as of 2020-03-03 12:09:30 → ⇥
  Size: 588
  Editor: localhost
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 6:
+ * Understand the business, business logic independently of the tech used
 * Capture the domain model, in domain terms, through interactions with domain experts.
 * Embed the domain terminology in the code.
 * Protect the domain knowledge from corruption by other domains, technical subdomains, etc.