As such it can influence the services provided by that bounded context.” Customer/Supplier Teams/Development): “One bounded context uses the services of another and is a stakeholder (customer) of that other bounded context. Published Language (PL): “The interacting bounded contexts agree on a common language (for example a bunch of XML schemas over an enterprise service bus) by which they can interact with each other.”.This protocol exposes the Published Language.” Open Host Service (OHS): “A bounded context specifies a protocol by which any other bounded context can use its services (for instance, a RESTful HTTP service or a SOAP Web service).Shared Kernel: “Two bounded contexts use a common kernel of code (for example a library) as a common lingua-franca, but otherwise do their other stuff in their own specific way.”.In “An Introduction to Domain Driven Design”, Dan Haywood summarizes the original six patterns as this: The original DDD book by Eric Evans defined an initial set of relations between Bounded Contexts appearing in a Context Map, e.g., the Conformist pattern Later on, a few additional types were added. The following domain model for Strategic DDD gives an overview of the patterns in it (as well as the connection to Tactic DDD via Aggregates): Inside the boundary, all terms and phrases of the Ubiquitous Language have specific meaning, and the model reflects the language with exactness” Martin Fowler emphasizes that a Bounded Context is explicit about its interrelationships in his bliki article on Bounded Contexts. “A description of a boundary (typically a subsystem, or the work of a particular team) within which a particular model is defined and applicable” “A bounded context is an explicit boundary within which a domain model exists. The key pattern in strategic DDD is Bounded Context, an abstraction of a functional area (i.e., a set of related features targeting one or more stakeholder groups), system (from different viewpoints, for instance logical and physical), or team (or, more generally, an organizational unit): Finding out about such domain facets when coding or, even worse, during integration or interoperability testing causes extra effort and other pain strategic DDD can unveil such ambiguities early, and help manage them from then on. And legal entities/persons might have similar but not the same properties (what would the body mass index of a company be?). Differences between customers, business partners, and staff members do exist and probably matter, even if all three are human beings. For instance, different attributes and different relations between domain concepts around people may have to be analyzed, designed, and implemented.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |