Describing a Functionality Map
A functionality map is a set of functionalities with their dependencies that, jointly, define the scope of a hardware or software architecture.The properties of a functionality map
The characteristics 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:
1. From the Capabilities navigation menu, expand Functionality Maps.
2. Click New > Functionality Map.
Creating a functionality component in a functionality map diagram
The components represented in a functionality map are Functionality components.
To add a functionality component in the functionality map diagram:
In the object inserting bar, click Functionality component 
.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. 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 to perform a 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.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.
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.
• The Capability Usage page,
• The Owner section provides access to the skill maps that use the skill described.
For more details on relationships between functionalities, see Creating a functionality component in a functionality map diagram.Creating a Functionality Diagram
To create a functionality diagram:
1. Open the Diagram property page of the functionality of your choice and click Create a diagram.
2. Select Functionality Structure and click Create a diagram in graphical mode.
The diagram opens in the edit area. The frame of the functionality described appears in the diagram.
To create a functionality from a functionality diagram, see Creating a functionality component in a functionality map diagram.
To define the dependencies of sub-functionalities, see Defining Functionality dependencies.