Work Product Descriptor (Artifact): Business Locations Model

The Business Location Model defines the high-level business locations where the system has a presence, as defined by the scope of the modeling effort.

Purpose

The Business Location Model defines the high-level business locations where the system has a presence, as defined by the scope of the modeling effort. The objective is to clearly define the business locations involved, and the sorts of services provided within and between them. This information is important in deciding on the architecture for applications and services, so that they operate effectively over a slow speed WAN for example. Security implications are also eventually derived from this model for example.

It is important to clearly define the business locations and the relationships between them in terms of the services (activities/workflows) provided and facilities provided (data/voice, etc.)

Relationships

Container Artifact	Business Perspective
Contained Artifacts	Business Communications Business Domain Business Location Business Zone
Roles	Responsible:	Modified By: Enterprise Architect
Input To	Mandatory: Assess the Architecture	Optional: Define Business Locations Model	External: None
Output From	Define Business Locations Model

Properties

Optional
Planned

Illustrations

Templates	Business Perspective Document Template
Reports	Business Locations Model Report Business Locations Report

Tailoring

Impact of not having

Failure to produce this model means you run the risk that architects and designers will give only superficial attention to the way the business operates. They will do what they know best, which is to design and build systems in the absence of proper business knowledge. The result often is that the constructed systems do not support the needs of the business.

Representation Options

UML Representation: Package stereotyped as «BPL_BLM» containing deployment diagrams.

A Business Locations Model may have the following properties:

Introduction: A textual description that serves as a brief introduction to the model.
Packages: The packages in the model (contained within the Logical Perspective package), representing a hierarchy stereotyped as «BPL_Location» or «BPL_Domain» or «BPL_Zone».
Nodes: The nodes in the model, owned by the packages stereotyped as «BPL_Location», «BPL_Domain», «BPL_Zone», or «BPL_Comms».
Relationships: The relationships in the model, owned by the packages stereotyped as «BPL_Comms».
Diagrams: The diagrams in the model, owned by the packages.

A Business Locations Model is created to illustrate the conceptual location at which the "system" has a presence. Most things defined at this stage will go on to be described in detail in the Logical Perspective and Technical Perspective.

The Business Locations Model is a way of expressing the business conducted at and between locations where it operates. Locations are conceptual at the highest level, and include "locations" based upon security concepts, see: Whitepaper: A Reference Model for Enterprise Security. The types of locations and interactions between them are what are modeled. The business activities supported or provided at each conceptual location are also described.

More Information

Checklists	Business Perspective
Concepts	Complex IT Architectures UAM Perspectives Contexts
Guidelines	Business Location Business Locations Model Business Perspective Business Perspective Views Communications Domains and Zones Modeling Basics Plan the Business Perspective Activity
Supporting Materials	BPL Summary