HOPEX System Oriented IT Architecture : HOPEX System Oriented IT Architecture : Modeling with HOPEX System Oriented IT Architecture : Describing an Application System : Describing an Application Structure
   
Describing an Application Structure
With HOPEX System Oriented IT Architecture, an application can be described by an application structure diagram.
*An application structure diagram graphically shows first level components of an application, the access points (service point and request point) and the connections between components.
The purchase request management application, which is used only for internal purchases, is based on two specialized applications: one for office supplies and the other for equipment. Both applications use Microsoft Excel.
*The version number that appears at the bottom of the frame is a property of the application. For more details, see "Described element properties".
The diagram includes:
• application components representing the applications used
In the example, this is the office supplies purchasing application and the equipment purchasing application.
*An application service component represents the fact that the application system used plays a role in the described application.
• platform application components representing the technologies used by the platform
In the example, this is the Microsoft Excel application.
*A platform application component represents the fact that the technology used plays a role of platform in the described application. For example, Tomcat is a platform component for SageCRM.
*A technology is a definition or format that has been approved by a standards organization, or is accepted as a standard by the industry.
• application service components representing application services used
These components are not used in the example.
*An application service component represents the fact that the application system used plays a role in the described application.
*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.
• access, request and service points
*For more details, see "Describing Service and Request Points".
• 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.