|
Collect information about the business locations
Business Processes may provide useful input for the identifications of business locations. Other sources are as-is
documentation of the enterprise or relevant business domains or systems, as the case may be for the scope in question.
|
Define the business locations
When you feel you have collected enough background information, it is time to describe the locations in detail.
Start by arranging the locations it in some sort of conceptual framework. For example, for a Bank that provides ATM
services, one conceptual location would be "ATM" ... define one for each type of location not one for each
physical instantiation. Examine the need for security domains, which may be viewed as "locations", for example a
business's Internet presence may be viewed as a conceptual location accessible to all (including employees), whereas
the businesses Intranet will only be accessible by employees.
|
Define the location relationships
Using the Business Process Model, or other sources of information, determine the services and facilities required at
and between the locations. These are business level services or facilities, such as "access to products and services"
or infrastructure services such as "email" and "telephone". The objective is to understand what services are provided
at and between locations, which will influence design choices later on.
|
Evaluate your results
| A Business Locations Model is complete only when it describes every location that the "system" has a presence at
(within the given scope). Before you finish, make sure the locations model exhibits the characteristic properties of a good
locations model, see: Guideline: Business Locations Model. |
|