Describing the Functionality Map
A functionality map is a set of functionalities with their dependencies that, jointly, define the scope of a hardware or software architecture.Accessing the list of functionality maps
To access the list of functionality maps from the Business Architecture navigation pane:
Click Inventories > Functionality Maps in the navigation menu.The list of functionality maps appears in the edit area.
The properties of a functionality map
The Characteristics properties page of a functionality map provides access to:
• its Owner, by default on creation of the business function, the current enterprise.
• its Name,
• the text of its Description.
With HOPEX Business Architecture a Functionality map is described by:
• the Structure page, which is used to specify a list of functional components owned and the dependencies between them.
For more information on the functionality components, see Creating a functionality component in a functionality map diagram and Defining Functionality dependencies.For more details on others property pages, see "HOPEX Business Architecture properties pages content", page 24.Creating a functionality map
To create a functionality map diagram:
Right-click the functionality map that interests you and select New > Functionality Map Diagram.The diagram opens in the edit area. The frame of the functionality map described appears in the diagram.
Creating a functionality component in a functionality map diagram
The components represented in a functionality map are Functionality components.
A functionality is a service required by an org-unit in order to perform its work. This functionality is generally necessary within an activity in order to execute a specific operation. If it is a software functionality, it can be provided by an application.To add a functionality component in the functionality map diagram:
1. In the diagram insert toolbar, click Functionality Component.
2. Click the functionality map frame.
The functionality component creation window opens.
3. Click, for example, Reusing an Existing Functionality.
4. Click Display Scope to access the list of functionalities linked to the enterprise.
5. Select the functionality that interests you.
6. Click OK.
The functionality component appears in the diagram.
Defining Functionality dependencies
A dependency link between one functionality and another is used to specify the elements on which this dependency is based.
For example, for a "Pizza delivery" functionality, there must first be a "Prepare pizzas" functionality. Note that the effect of the "Deliver pizzas" functionality is a "Pizza delivered" functionality and the effect of the "Prepare the pizzas" functionality is a "Cooked pizza".
To create dependency links between two functionalities in a functionality map diagram:
1. In the insert toolbar, click Functionality Dependency.
2. Click the functionality component, and keeping the left mouse button pressed, move the cursor to the functionality component used.
3. Release the mouse button.
The creation window for the functionality dependency opens.
4. Enter the user component result of the user functionality in the Dependent Application Effect field.
For example, "Pizza delivered".
5. Enter the content result of the functionality used in the Necessary Application Effect field.
For example, "Pizza cooked".
6. Click OK.
The link appears in the diagram.
A single sub-functionality can have more than one dependency within a single diagram.Describing functionalities
A functionality is a service required by an org-unit in order to perform its work. This functionality is generally necessary within an activity in order to execute a specific operation. If it is a software functionality, it can be provided by an application.To access the list of functionalities from the Environment navigation pane:
Click Inventories > Functionalities in the navigation menu.The list of functionalities appears in the edit area.
To create a new functionality:
1. In the Business Architecture navigation pane, select Inventories > Functionalities.
2. click New.
A Functionalities creation dialog box opens.
3. Enter the name.
4. Click OK.
The functionality created appears in the list of functionalities.
The Characteristics property page of the functionality provides access to:
• its Owner, by default during creation of the functionality, the current enterprise.
• its Name,
• the text of its Description.
• the Desired Application Effects:
For more information on the effects of expected functionalities, see Defining Functionality dependencies.With HOPEX Business Architecture, a functionality is described in the following pages:
• the Structure page is used to specify a list of functionalities owned and the dependencies between them.
For more information on the structure of functionalities, see Creating a Functionality Diagram.• the Implementation page provides access to the list of architecture elements that implement the functionality.
• In the Usage page, the Capability Component section provides access to the functionality maps that use the described functionality.
For more details on the relationship between functionalities, see Creating a functionality component in a functionality map diagram.• In the Usage page, the Business Capability section provides access to the business capabilities that require the described functionality.
For more details on the functionalities associated with business capabilities, see Defining the business skills and functionalities associated with business capabilities.• In the Usage page, the Business Function section provides access to the business functions that require the described functionality.
For more details on businesses, see Business properties.• In the Usage page, the Capability Exhibition section provides access to the exposed business capabilities that require the described functionality.
An exhibited business capability is measurable objectively within the framework of an enterprise stage, on a defined geopolitical scope (site), and focused on a given market segment (business partner).For more details on others property pages, see "HOPEX Business Architecture properties pages content", page 24.Creating a Functionality Diagram
To create a functionality diagram:
Right-click the functionality that interests you and click New > Functionality diagram.The diagram opens in the edit area. The frame of the functionality described appears in the diagram.
To create a functionality in a diagram, see Creating a functionality component in a functionality map diagram.
To define the dependencies of sub-functionalities, see Defining Functionality dependencies