Describing an Application with HOPEX IT Architecture V2
A project for describing the functional architecture of an information system is used to inventory the existing applications and their interactions.
An application is a software component that can be deployed and provides users with a set of functionalities.An application is described by several types of diagrams:
• An scenario of application flows describes the flows exchanged between the IT services or the micro-services used by this application. A scenarios can represent a particular application use case or more globally all the flows exchanged within this application.
For more details, see Describing a scenario of flows.• an application structure diagram is used to represent the interactions between the application components in the form of exchange contracts.
For more details, see Creating a structure diagram.• an application technical architecture used to represent the technical elements that support the application.
For more details, see Creating an Application Technical Architecture.Creating an Application with HOPEX IT Architecture V2
To create an application:
1. From the Application Architecture navigation pane, select Functional Architecture > Applications.
The list of applications appears in the edit area.
2. Select My Applications tab, for example.
3. Click New.
4. The Creation of Application dialog box appears.
5. Enter the Name of your application and click OK.
The new application appears in the list.
The properties of an application with HOPEX IT Architecture V2
The Characteristics property page of an application provides access to different sections.
• The Identification section provides access to the following information:
• the Name
• its Owner, by default during creation of the application, the current library.
• the text of its Description.
• the internal Code
• the Type of application
• if it is an Application template: to be selected if the application is used to create other applications.
• a Comment.
• the business processes that use the application.
A business process represents a system that offers products or services to an internal or external client of the company or organization. At the higher levels, a business process represents a structure and a categorization of the business. It can be broken down into other processes. The link with organizational processes will describe the real implementation of the business process in the organization. A business process can also be detailed by a functional view.• the Responsibility: it relates to the person(s) responsible for the application.
• Software Designer
• Local Application Owner
• IT Owner
For more details on these roles, see Business Roles of HOPEX IT Architecture V2..• the Technologies section provides access to the list of Technologies and the list of technology stacks used by the application.
A software technology is a basic component necessary for operation of business applications. Software technologies include all basic software such as: application server, electronic mail server, software components for presentation, data entry, storage, business information sharing, operating systems, middleware, navigators, etc.A software technology stack is a set of software technologies.For more details on software technologies, see Describing a Software Technology.• the Risks associated with the application. See Specifying the Risks Associated with an Application.
• associated Attachments.
For more details on other property pages proposed by HOPEX IT Architecture V2, see HOPEX IT Architecture V2 properties pages content.Defining Application Functional Scope
To indicate the objects that define application functional coverage:
1. Open the Characteristics property page of the application.
2. Expand the Functional Scope section.
The types of data that define functional coverage of the application are:
• The business capabilities covered by the application
.A business capability is a set of features that can be made available by a system (an enterprise or an automated system).For more details on business capabilities, see Using Business Capabilities with HOPEX IT Architecture V2.A report covers distribution of applications in business capabilities, see Business Capabilities reports .• The functionalities implemented by the application
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.For more details on functionalities, see Describing a Functionality Map with HOPEX IT Architecture V2.• The Logical realizations enable to define the logical applications and the logical application systems that the application implements.
A logical application is a set of application functionalities that is independent of a particular implementation. For example, the classification of all purchase request processing applications implemented in an enterprise.A logical application system is an assembly of other application architectures, logical applications and end users, interacting with application components to implement one or several functions.For more details on logical architectures, see Describing a Logical Application Architecture with HOPEX IT Architecture V2.Specifying the Risks Associated with an Application
HOPEX IT Architecture V2 is used to identify the risks associated with an application, and to retrieve the evaluations defined in the HOPEX Enterprise Risk Management solution. You can define a new risk using the application or connect a previously defined risk.
To connect a risk to an application:
1. Open the Characteristics property pages of the application.
2. Expand the Risk section.
3. Click Connect.
The search window appears.
4. Find and select the risk required and click OK.
For more details on risks and their evaluation, see HOPEX Enterprise Risk Management.