Using drivers
Accessing the list of drivers
To access the list of drivers from the Vision navigation pane:
*Click Inventories > Drivers in the navigation menu.
Three tabs are available to access the list of each type of driver.
*A business driver is an expectation expressed by a client, a partner or provider with respect to the enterprise.
*A regulatory driver is guided by a change in the regulation framework to which it makes reference.
*An architectural driver is guided by a specific characteristic or an internal architectural building block. This characteristic can represent a strength or a weakness
Creating a driver
The drivers are linked to the current enterprise.
To create a driver:
1. From the Vision navigation pane, select Inventories > Drivers.
2. Select the tab that corresponds to the driver type that you wish to create and click New.
The driver appears in the list of drivers linked to the enterprise.
3. You can modify the Name of the driver.
Driver properties
The Characteristics property page of the driver provides access to:
its Name;
the text of its Description;
the Stakeholder Owner who enables the specification of the entities concerned by the driver. The entity may be:
a person group;
a governance organization;
A person (system), for example: Mr. Dupont or the ISD.
*A person (System) represents a person in the enterprise. This person can be assigned a login and a role (or a profile depending on the connection mode). The login provides access to the HOPEX Application. The role (or the profile) defines the access to product functions and repositories. A system person, if assigned a login, has a specific desktop in each database, and can connect to this desktop from any workstation in a given environment.
With HOPEX Business Architecture, a driver is described in the following pages:
the Structure page, Driving Enterprise Model Element section is used to access the architectural building blocks concerned by the driver.
*For more details on transformation plans, see "Describing implementation of an enterprise stage", page 94.
the Structure page, Possible Sites section is used to access the sites concerned by the driver.
*A site is a geographical location of an enterprise. Examples: Boston subsidiary, Seattle plant, and more generally the headquarters, subsidiaries, plants, warehouses, etc.
the Usage page, Strategy Assessment section, provides access to the strategic assessments to which the driver is connected.
*For more details on assessing strategies, see Using strategy assessments.
the Usage page, Transformation objective section provides access to the objectives to which the driver is connected.
*For more details on enterprise goals, see Identifying enterprise goals.
*For more details on other property pages, see "HOPEX Business Architecture properties pages content", page 24.