HOPEX Digital Transformation Desktop > Using solutions with HOPEX Digital Transformation Desktop > Using HOPEX Business Architecture and HOPEX IT Strategy > Describing Business Capabilities and the existing architecture with HOPEX Digital Transformation Desktop
Describing Business Capabilities and the existing architecture with HOPEX Digital Transformation Desktop
To access elements describing business capabilities and architecture:
1. Click the navigation menu, then Strategic Planning.
2. In the navigation pane, click Inventory.
 
The list of main tiles for the transformation projects management appears.
• Business Capabilities
*.A business capability is a set of features that can be made available by a system (an enterprise or an automated system).
*See "Describing a business capability", page 45 in HOPEX Business Architecture guide.
• Business capability maps,
*A business capability map is a set of business capabilities with their dependencies that, together, define a framework for an enterprise stage.
*See "Building the business capability map", page 42 in HOPEX Business Architecture guide.
• Business architecture environment,
*A business architecture environment represents the relationships of a business functional area with its partners.
*See "Managing a business architecture environment", page 49 in HOPEX Business Architecture guide.
• Business functions.
*A business function is a conceptual unit of the division of responsibilities in an enterprise. It is used to structure the management of information processing, energy, and equipment produced or used. Business functions define the skills and the functionalities necessary to the enterprise to fulfill its mission.
*See "Describing business functions", page 57 in HOPEX Business Architecture guide.
• Business partners,
*A business partner designates a third-party who is in relation with the enterprise within the framework of a given business architecture environment. Examples: private sector client, regulatory organization, supplier.
*See "Describing Business Partners", page 57 in HOPEX Business Architecture guide.
• Functionalities and Functionality Maps,
*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.
*A functionality map is a set of functionalities with their dependencies that, jointly, define the scope of a hardware or software architecture.
*See "Describing Business Partners", page 57 in HOPEX Business Architecture guide.
• Value streams,
*A value stream is an end-to-end collection of Value Stages that creates an outcome for a customer, who may be the ultimate customer or an internal end-user of the value stream.
*See "Describing value streams", page 64 in HOPEX Business Architecture guide.