3 ms·
For more rigorous naming, Eric Evans (in his excellent book Domain-Driven Design: Tackling Complexity in the Heart of Software) recommends documenting (and main
by cpeterso 15y ago
For more rigorous naming, Eric Evans (in his excellent book Domain-Driven Design: Tackling Complexity in the Heart of Software) recommends documenting (and maintaining) your product's "Ubiquitous Language".
When developers (and the code), product managers, domain experts, and end users all use different terminology, then cross-discipline communication difficult and imprecise. A documented Ubiquitous Language enforces shared terminology (and meaning) for all communication within the team and in the code.
http://domaindrivendesign.org/node/132 http://domaindrivendesign.org/node/132