Extend relationship: The use case is optional and comes after the base use case. It is represented by a dashed arrow in the direction of the base use case with the notation <<extend>>
Archives: Templates
Templates and model types in the QualiWare platform.
Expression
Description of this template will be available soon.
Expansion Region
Description of this template will be available soon.
Expansion Node
Description of this template will be available soon.
Exception Handler
Description of this template will be available soon.
Execution Environment
Description of this template will be available soon.
Equipment : ArchiMate
One or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
Equipment comprises all active processing elements that carry out physical processes in which materials (which are a special kind of technology object) are used or transformed. Equipment is a specialization of the node element from the Technology Layer. Therefore, it is possible to model nodes that are formed by a combination of IT infrastructure (devices, system software) and physical infrastructure (equipment); e.g., an MRI scanner at a hospital, a production plant with its control systems, etc. The name of a piece of equipment should preferably be a noun.
Equipment
The Equipment object can be used to describe an equipment asset. The object can be used in e.g. a ProductionSite or ProductRoadmap.
Enumeration Literal
Description of this template will be available soon.
Element Import
In a Class Diagram, the element import is a directed relationship that represents the usage of a specific element from one namespace within another namespace. Essentially, it enables you to “import” or “include” elements such as classes, interfaces, or datatypes from a different package or namespace into the current one. By using element import, you can create modular designs and promote the reusability of components in your system.
In the context of templates in a Class Diagram, element import can be useful when you want to reuse a particular datatype or template class defined in another package or namespace. For instance, suppose you have a template class or a custom datatype defined in one package, and you want to use it as a type for an attribute or operation parameter in a class within another package. In this case, you can use the element import relationship to indicate that the class in the second package is using the datatype or template class from the first package.