• Business Locations Model

• IT Architecture Delivery  >  Review the Architecture  >  Review Business Perspective  >  Business Location
• IT Architecture Delivery  >  Business Perspective Delivery  >  Business Perspective Iteration [n]  >  Business Location
• IT Architecture Delivery  >  Architectural Decision Delivery  >  Business Location
• IT Architecture Delivery  >  Business Perspective Delivery  >  Business Location
• IT Architecture Delivery  >  Logical Perspective Delivery  >  Logical Perspective Iteration [n]  >  Business Location
• IT Architecture Delivery  >  Maintain Architecture  >  Deliver Updated Business Perspective  >  Business Location
• IT Architecture Processes  >  Define Business Perspective  >  Business Location
• IT Architecture Processes  >  Review an Architecture  >  Business Location
• IT Architecture Processes  >  Manage Architectural Decisions  >  Business Location
• IT Architecture Processes  >  Develop a Migration Plan  >  Business Location
• IT Architecture Processes  >  Analyze Models  >  Business Location
• IT Architecture Processes  >  Develop Training  >  Business Location
• IT Architecture Processes  >  Consult with Stakeholders  >  Business Location
• IT Architecture Processes  >  Define Solution and Impacts  >  Business Location
• IT Architecture Processes  >  Business Location
• IT Architecture Processes  >  Define Logical Perspective  >  Business Location
• IT Architecture Processes  >  Update Business Perspective  >  Business Location
• IT Architecture Processes  >  Update Logical Perspective  >  Business Location
• IT Architecture Processes  >  Update Technical Perspective  >  Business Location

Business Locations are identified early in the process of modeling a business. It is not a simple analysis in the first instance; locations are generalized in order to simplify the model and in turn simplify implementation. Analysis of locations must be done in order to categorize them and ultimately define generalizations.

A Business Location is the generic or conceptual level locations at which the system (business) under study has a presence. Each location is defined in terms of the Business Activities present and provided at the location along with the types of communications required and provided between these locations.

UML Representation: «stereotype» BPL_Location

Extends: «metaclass» Node

It has the following properties:

• id: string - This attribute is used to uniquely identify elements.
• name: string - A descriptive name for the location.
• activities: Activities[0..*] - A list of the business activities provides at the location, which relates directly to the Business Process Model and how the business (or system under study) wants to deliver its products and services.
• nonFunctional: string - Defines things such as business importance, survivability, and availability requirements of the location.
• description: string - A description of the location in terms of building, address or other distinguishing characteristics.

Constraints

• Shall not have any owned operations;
• Shall not have any owned behaviors;
• May have relationships with only Business Domains, Business Roles or with other Business Entities;
• May communicate with other Locations via Business Communications;
• All owned properties shall be public.
  

• Location Aspect

• Business Location
• Domains and Zones

• BPL Summary