Describing the Functionality Map
A technical functionality map is a set of functionalities with their dependencies that, jointly, define the scope of an architecture.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 Process Analysis a Functionality map is described by:
• the Structure page is used to specify a list of components owned by the functionality map and the dependencies between them.
For more information on the components of a functionality map, see Creating a functionality component in a functionality map diagram and Defining Functionality dependencies.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 technical functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a technical element or 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. Select the functionality that interests you.
4. 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.
5. Enter the content result of the functionality used in the Necessary Application Effect field.
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 technical functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a technical element or an application.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.
• its Desired capability effects.
• the Desired Capability Effect is an Outcome.
For example, the desired capability effect of "Displaying the status of a reservation" is a "Reservation status"
For more details on results, see Describing the outcomes.For more information on the use of expected functionality effects, see Defining Functionality dependencies.With HOPEX Business Process Analysis, 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 Fulfillments 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.Creating a Functionality Diagram
To create a functionality diagram:
1. Right-click the functionality that interests you and select New > Diagram.
The Diagram type selection dialog box opens.
2. Select Functionality Diagram.
3. (Optional) Uncheck the Diagram Initialization box.
4. Click OK.
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