Usage
A well thought-out domain model serves as a clear depiction of the conceptual fabric of the problem domain and therefore is invaluable to ensure all stakeholders agree the scope and meaning of the concepts in the problem domain. An accurate domain model can also serve as an essential input to solution implementation within a software development cycle since the model elements comprising the problem domain can serve as key inputs to code construction, whether that construction is achieved manually or through automated code generation approaches. It is important, however, not to compromise the richness and clarity of the business meaning depicted in the domain model by expressing it directly in a form influenced by design or implementation concerns.
The domain model is one of the central artifacts in the project development approach called feature-driven development (FDD).
In domain-driven design, the Domain Model (domain entities and actors) covers all layers involved in modelling a business domain, including (but not limited to) Service Layer, Business Layer, and Data Access Layer thus ensuring effective communication at all levels of engineering. It is considered an effective tool for software development, especially when domain knowledge is iteratively provided by domain experts (such as Business Analysts, Subject Matter Experts and Product Owners.)
In UML, a class diagram is used to represent the domain model.
Read more about this topic: Domain Model
Famous quotes containing the word usage:
“I am using it [the word ‘perceive’] here in such a way that to say of an object that it is perceived does not entail saying that it exists in any sense at all. And this is a perfectly correct and familiar usage of the word.”
—A.J. (Alfred Jules)
“Pythagoras, Locke, Socrates—but pages
Might be filled up, as vainly as before,
With the sad usage of all sorts of sages,
Who in his life-time, each was deemed a bore!
The loftiest minds outrun their tardy ages.”
—George Gordon Noel Byron (1788–1824)
“...Often the accurate answer to a usage question begins, “It depends.” And what it depends on most often is where you are, who you are, who your listeners or readers are, and what your purpose in speaking or writing is.”
—Kenneth G. Wilson (b. 1923)