HOPEX IT Architecture V2 > Modeling Technical and Functional Architectures > Describing Application Flows > Describing a Scenario of Application System Environment
Describing a Scenario of Application System Environment
A scenario of application system environment represents the flows exchanged between the components of the application system environment.
*For more details on use of a scenario of flows, see Describing a scenario of flows
The elements of a scenario of application system environment are:
• the main application system principal described by the environment.
*An application system is an assembly of other application systems, applications and end users interacting with application components to implement one or several functions.
• partner application systems that represent the other application system with which the main application system described by the environment interacts.
*A partner application system is an application system external to the environment of the described application service. The partner application system can be a service supplier or a service consumer with respect to application system users.
• End User Participants that represent the categories of users of application system provided by the environment.
• The categories of users of services provided by the environment are represented either by an Org-Unit or by a Position Type.
*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.
*A position type represents a status assigned to an individual or a group of individuals with the aim of defining an organization or a hierarchy.
• interactions between components
*An interaction represents a contract established in a specific context between autonomous entities that are internal or external to an enterprise. These entities can be enterprise org-units, applications, activities or processes, as well as external org-units. The content of this contract is described by an exchange contract.