Proposal: rename "Description" to "Purpose"

[mploed]

In recent workshops with customers I often renamed the Description field of the canvas to "Purpose" following some content seen in the DDD community like:

"A Bounded Context is a boundary for a model expressed in a consistent ubiquitous language tailored around a specific purpose"

or "A Bounded Context is a unit of Autonomy, Mastery and Purpose" (from one of Alberto's presentations)

I like making the purpose very explicit because "Description" can be interpreted as something very vague.

What do you think?

[heimeshoff]

Purpose instead of description is much more fitting, absolutely. I would stick with the first quote though, because the second one about Autonomy, Mastery, and Purpose (specifically this triad) is known to be the main motivational forces from Daniel Pinks "Drive". Besides beeing associated weirdly, I don't think that it delivers a better or more fitting definition or description of a bounded context. Master for example is not necessarily bound by the context.

[morcs]

I agree :) "Purpose" tells me much more clearly what I should be writing in that box!

[mploed]

@heimeshoff I'm aware of "Drive" and the parallel which Alberto drew... Just used it as an example that the term "purpose" appears regularly with regards to Bounded Contexts.

[NTCoding]

Hey everyone. I'm all in on "purpose". It's a much better fit. Let's do it.

[mploed]

I'd create a pull request then!

[yellowbrickc]

Thank you very much!