Artifact: Business Domain
A Business Domain is used to categorize and contain a set of business systems that represent those autonomous units of the business modeled during Business Analysis.
Domains: Business Modeling
Work Product Kinds: Model Element
To provide a logical (only) grouping of Business Systems such that they are categorized according to the competencies of the larger organization.
Main Description

A Business Domain is a tool to allow a Artifact: Business Analysis Model to group business systems, especially when a model is used to describe high-level business architecture or organization (such as that produced by Concept: Component Business Modeling). The Business Domain itself is the expression of a competency of the business whereas the contained Artifact: Business Systems are the autonomous units of the business operating within that particular domain. As described in Guideline: Business System Systems communicate using provided and required Business Services (capabilities of the system) and the introduction of Business Domains does not complicate this in any way, there is no notion of priviledged communication between Systems in the same Domain (for example).

The example below demonstrates a partial model with business domains containing business systems, we assume that the enclosed systems contain far more detail than is shown here.

 Illustration of business domains containing business systems

One key aspect of the Business Domain is that Business Systems are contained within the domain; that is a Business System may only be categorized as part of one Business Domain at any time.

Key Considerations
Business Domains are not intented to model organizational structures and should not be used to do so; they are logical containers for Business Systems only.
Impact of not having

A Artifact: Business Analysis Model which does include a number of Artifact: Business System but which does not manage them using Business Domains provides far less information in terms of the catagorization of the systems it includes. When the model is used as part of a broad business transformation effort then the use of Business Domains is critical.

Reasons for not needing

When the Artifact: Business Analysis Model represents a smaller effort and focused perhaps only upon one Business System then the additional overhead of modeling a corresponding Business Domain may be unnecessary.

Representation OptionsUML Representation: a package, stereotyped as <<Business Domain>> within the Artifact: Business Analysis Model.
More Information