Hopex Aquila EN

Describing an IT Service

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.

IT Service diagrams

An IT Service is described by several types of diagrams:

• an IT Service structure diagram is used to represent the service interactions between the IT Service components under the form of service interfaces.

For more details, see Using IT Service Structure Diagram.

• a scenario of IT Service Flows presents the application flows exchanged between the described IT services or microservices used by this IT Service. A scenario can represent a particular use case of the IT service or more globally all the flows exchanged within this IT service.

For more details, see Using a Scenario of Application Flows Diagram.

Accessing the list of IT services

IT Service properties

The complete description of an IT Service is accessed from its properties pages.

The Characteristics properties page for an IT Service provides access to:

• its Owner, by default during creation of the IT service, the current library.

• its Name,

• the Type,

• the Visibility,

• the Review Status,

• the text of its Description

• The Functional scope section is used to describe:

• The business capabilities covered by the IT Service,

A business capability represents a specific ability that an organization possesses or needs to develop to deliver a particular business outcome.

For more details on business capabilities, see Describing Business Capabilities with Hopex IT Architecture.

• The Implemented Functionalities that are fulfilled by the IT service.

A functionality is a service required to perform a 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.

For more details on fulfillments, see Using fulfillment mechanisms.

• the Use Cases section, see Creating an Application Use Case Diagram.

• The Responsibility section relates the person(s) responsible for the IT service

• Software Designer

• Local Application Owner

For more details on these roles, see Business Roles of Hopex IT Architecture.

• the Technologies section provides access to the list of Software Technologies used by the IT Service.

A technology is a definition or format that has been approved by a standards organization, or is accepted as a standard by the industry.

For more details on software technologies, see Describing a Software Technology.

• the Risks section presents the risks associated with the application, see Describing an Application Environment with Hopex IT Architecture.

With Hopex IT Architecture an IT service is described by other property pages, see Hopex IT Architecture properties pages content

Using IT Service Structure Diagram

For more details on use of a structure diagram, see Application Structure Diagram

With Hopex IT Architecture, the components of an IT Service can be described by an IT Service structure diagram.

An IT Service Structure Diagram includes:

• IT services,

• Microservices

• Physical data stores; see Managing Data.

• access, request and service points; Creating a Service Point or a Request Point.

• 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.