• Applications without owners: displays a list of applications to which you can connect responsible users.
• Applications not linked to a portfolio: displays a list of applications to which you can connect portfolios.
• Applications without exposed exchanges: applications that neither receive nor send flows.
• Applications included in a transformation project: these are the applications that are part of the deliverables of a transformation project.
• Applications not mapped to business capabilities: displays the list of applications which don't cover any business capability.
To request application owners to connect applications to business capabilities, select the applications and click
Request Application Update. A notification is sent to owners.
• Critical applications: all applications that cover a strategic business capability, in other words, whose Business Value is "Significant”.
• Applications with an obsolescence risk: applications whose risk of obsolescence is between “Medium” and “Very high”.
The risk of application obsolescence corresponds to the highest risk of the technologies linked to it. See the obsolescence risk in the
Overview of a technology.
• Applications with sensitive data: applications linked to data stores containing data (classes, MD entities, data views) or Concepts in the "Sensitive data" category.
• Technologies soon obsolete
• Technologies without lifecycle
• Applications
• On-premises Applications
• Cloud Applications
• Technologies
• Microservices
A microservice is a software component that can be deployed autonomously, but which does not directly provide an end user service. It can interact with other application services, applications or application systems.
The Dashboard navigation menu gives access to two dashboards dedicated to enterprise architecture:
The Applications menu displays:
• All the applications of the repository
• Application portfolios
The Data menu allows you to make an inventory of the conceptual and logical data exchanged within the application assets.
You must have
Hopex Data Architecture to view the
Data navigation menu.
The Tools menu gives access to the following tools:
• Business Information Realization (Matrices and Realization Reports)
• Assessment and data call.
• Technopedia (BDNA technology types, BDNA vendors, BDNA software technologies)
The Reports menu provides a search tool for all report templates and saved reports.
For more information on data reports, see:
The Inventories menu gives access to the following subjects, divided into several themes.
• Business Architecture theme, giving access to the following elements:
• Environments (enterprises)
• 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.
• 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.
• Capabilities theme, giving access to the following elements:
• Functionalities
• Technology Capabilities
• Hardware capabilities
• Software theme, giving access to the following elements:
• IT Services
An IT service is a software component of an application, that can't be deployed alone and that realizes a sub-set of the functionalities of this application either for end users of this application or inside the application (or another application). This includes batch programs.
• Microservices
A microservice is a software component that can be deployed autonomously, but which does not directly provide an end user service. It can interact with other application services, applications or application systems.
• System Processes
A system process is the executable representation of a process. the events of the workflow, the tasks to be carried out during the processing, the algorithmic elements used to specify the way in which the tasks follow each other, the information flows exchanged with the participants.
• Application Hierarchy, to view applications associated with the following object types: business line, process category, business capability, etc.
• Logical software architecture, to describe the elements contained in the information system logical architecture.
• Communication systems
A communication system is an integration system responsible for implementing and processing flows. It may be a custom-built flow management system, an Enterprise Service Bus (ESB), or similar.
• Technologies theme, giving access to the following elements:
• Technologies Hierarchy, to view technologies associated with the following object types: technology capability, technology type, vendor, etc.
• Technology Stacks, which are groups of technologies.
• Vendors
• Services Catalogs theme, giving access to the following elements:
• Cloud services
• Business Services, to list the business services covered by applications.
• Technical Services, to list the technical services covered by applications.
• Hardware Service Catalogs
• Infrastructure theme, giving access to the following:
• IT Infrastructures
• Resource Architectures
• Resource Configuration
• All Sketches, to access all the skectches of your repository.
A sketching diagram is a drawing that enables you to exchange with your coworkers without an issue of methodology or formalism.
In the Governance menu you can define the regulations to which application architecture objects are subject.
In the properties of an application, the
Governance page defines the constraints to which the application is subject. By default, this page is hidden, you can display it using the
Show/Hide button of the application properties.
The Environment menu gives access to the following themes:
• Containers, to access the features of library and environment management.
• Organization
• Business lines
A business line is a high level classification of main enterprise activities. It corresponds for example to major product segments or to distribution channels. It enables classification of enterprise processes, organizational units or applications that serve a specific product and/or specific market.
• Process categories
A process category defines a group of processes. It is linked to a Process Map or higher level Process Category. It regroups several processes and/or other categorized elements (e.g. Value Streams, Applications). It serves as an intermediate categorization level in the process hierarchy, so as to provide a guided and progressive access to finer grained processes.
• Processes
A process is a set of operations performed by org-units within a company or organization, to produce a result. It is depicted as a sequence of operations, controlled by events and conditions. In the BPMN notation, the process represents a sub-process from the organizational point of view.
• Org-Units
An org-unit represents a person or a group of persons that intervenes in the enterprise business processes or information system. An org-unit can be internal or external to the enterprise. An internal org-unit is an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external org-unit is an external entity that exchanges flows with the enterprise. Example: customer, supplier, government office.
• Sites
A site is a geographical location of an enterprise. Examples: Boston subsidiary, Seattle plant, and more generally the headquarters, subsidiaries, plants, warehouses, etc.
• Common
• Report DataSets
A Report DataSet is a set of data extracted from the Hopex repository and used as a data source in reports.
For more information, see Platform - Common Features > Documentation > Generating Documentation > Managing Report DataSets.
• Tags
A tag is a classifying description used to characterize objects.
For more details on the use of tags, see Platform - Common Features > Collaboration Tools > Communicating in HOPEX.
