Description of this template will be available soon.
Archives: Templates
Templates and model types in the QualiWare platform.
Template Tag
Description of this template will be available soon.
Technology Interaction : ArchiMate
A unit of collective technology behavior performed by (a collaboration of) two or more technology internal active structure elements.
A technology interaction describes the collective behavior that is performed by two or more technology internal active structure elements, possibly by their participation in a technology collaboration. This may, for example, include the communication pattern between these elements. A technology interaction can also specify the joint behavior needed to realize a technology service.
The name of a technology interaction should clearly identify a series of technology behaviors; e.g., “Client profile creation” or “Update customer records”.
Technology Domain
The Technology Domain template is used to describe a technology domain in an InfrastructureDiagram.
A technology domain can be linked to TechnologyCapability (delivered by).
Its lifecycle can be described in terms of when it is used in the organization.
And its product lifecycle.
Technology Configuration
The Technology Configuration object is used to describe a configuration of a set of technologies.
It is possible to associate:
- Hardware Component and Software (consist of)
- InfraStructureDiagrams (Visualized in)
From the usage tab, you can see IT-services that links to the configuration.
Technology Capability
The Technology Capability template is used to describe a technology capability in an InfrastructureDiagram.
A technology Capability can be linked to Technology Component.
Its lifecycle can be described in terms of when it is used in the organization.
And its product lifecycle.
Tag Definition
Description of this template will be available soon.
Tablespace
Description of this template will be available soon.
Table Scema
Description of this template will be available soon.
Table
A Table is a basic component in a Relational Diagram that represents a collection of related data organized in rows and columns. Tables are the fundamental building blocks of a relational database, and they provide a structured way of storing and organizing data, making it easy to access, query, and manipulate.
Tables can be related to each other through foreign key constraints, creating a relational schema that models the interrelationships between different entities in the system being represented.
Example: In a Relational Diagram for a system that manages a university, you might have a table called “Students” that stores information about all the students enrolled in the university. The table might have columns such as “id”, “name”, “major”, “email”, and “enrollment_date”, among others. Each row in the “Students” table represents a single student record, with values for each of the corresponding attributes. The “id” column serves as the primary key for the table, uniquely identifying each student record. Other tables in the database, such as “Courses” and “Enrollments”, can be related to the “Students” table through foreign key constraints, creating a relational schema that models the interrelationships between different entities in the university system.