Concepts managed by HOPEX IT Architecture
The sections that follow explain exactly how to use each object managed by HOPEX IT Architecture.
They highlight the various links you can use to connect different objects in diagrams.
As explained above, certain objects can be used only in one diagram type: for example, nodes can be used in a TID only.
In addition, certain objects can only be accessed in a diagram if you enable the corresponding view focusing on a software, organizational, conceptual or technical view of the information system.
HOPEX IT Architecture can manage an object hierarchy containing objects of the same type. This means it can handle the following concepts:
• Composition: an object is defined as the aggregation of several other objects of the same type but of reduced scope. For example, the “Agency Reservation” application consists of N sub-applications (x, y, z, ...).
• Specialization: a generic object can be described in more detail using other, more specialized objects of the same type (special cases or sub-types). For example, the New York travel agency is a specialization (a special case) of the Agency-type described in most of the general diagrams, and a large travel agency is a specialization (a sub-type) of the Agency-type described in most of the general diagrams.