HOPEX IT Architecture V2 > Modeling Business Capabilities and the logical application architecture > Using Functionalities with HOPEX IT Architecture
Using Functionalities with HOPEX IT Architecture
 
Describing a Functionality Map with HOPEX IT Architecture
Accessing the list of functionality maps with HOPEX IT Architecture
The properties of a functionality map
Creating a functionality map
Describing functionalities with HOPEX IT Architecture
Creating a Functionality Diagram with HOPEX IT Architecture
Describing Implementation of a Functionality
Creating a Functionality Realization
Analyzing functionality implementation
A functionality is an aptitude expected from an equipment.
*A functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a business function or an organization. If it is a software functionality, it can be provided by an application.
A functionality map describes all the functionalities the enterprise is able to cover for its internal needs or for meeting the needs of its clients.
*A functionality map is a set of functionalities with their dependencies that, jointly, define the scope of a hardware or software architecture.
Example of a functionality map
*For more details on managing a functionality map, see "Describing the functionality map", page 49.
*