Describing an Application Environment with Hopex IT Architecture
An application environment is used to represent a use context of an application. An application environment allows presenting the other application systems, applications, microservices or actors with which this application can interact.
Describing an Application Environment
An application environment is used to represent a use context of an application. An application environment allows presenting the other application systems, applications, microservices or actors with which this application can interact.
An application environment is described by several types of diagrams:
• An Application Environment diagram describes the exchanges between the subject application and its partners in a specific context.
• a scenario of application environment flows describes the flows exchanged between the described application and its partners: applications, application systems, IT services or microservices used by the described application in a specific context.
• a scenario of sequences of flows presents the agents necessary for the scenario (application, IT services, microservices, data stores) and sequence application flows exchanged.
Accessing the List of Application Environments
To access the list of application environments from the Applications navigation menu:
Open the
Environments page from the application of you interest.
The list of application environments appears in the edit area.
Creating an application environment
To create an Application environment:
1. Open the Environments page from the application of you interest.
The list of application environments appears in the edit area.
2. Click New.
The new application environment appears in the list under the name “Environment” followed by the name of the application.
Application environment properties
The Characteristics properties page of an application environment provides access to:
• its Owner, by default during creation of an application system environment, the current library.
• its Name,
• the text of its Description.
The Components property page of the application environment provides access to partners elements:
• Applications
• Microservice,
• IT Services,
• System users.
Application Environment Diagram presentation
With Hopex IT Architecture, an application environment is entirely described by a an application environment diagram that is used to describe the service interactions between the environment applications described, its users and the external applications.
An application environment diagram includes:
• applications that represent the environment described.
In the example, this concerns the applications used for buying spare parts.
An application is a software component that can be deployed and provides users with a set of functionalities.
• applications, application services or microservice partners that represent the external elements used in the described environment.
This example concerns automated Web services.
An IT service is a component of an application made available to the end user of the application in the context of his/her work.
• org-units or type positions that represent the users or the suppliers of the environment described.
This example concerns local participants.
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.
• Service interactions between components.
A Service Interaction represents an interaction for service purpose between entities in a specific context inside or outside a company. These entities can be enterprise org-units, applications, activities or processes, as well as external org-units. The content of this interaction is described in a service interface.
• request and service points
For more details on other property pages of the application environment, see Hopex IT Architecture properties pages content.