Archives: Templates

Templates and model types in the QualiWare platform.

Assignment ArchiMate

The assignment relationship expresses the allocation of responsibility, performance of behavior, or execution.
The assignment relationship links active structure elements with units of behavior that are performed by them, business actors with business roles that are fulfilled by them, and nodes with technology objects. It can, for example, relate an internal active structure element with an internal behavior element, an interface with a service, or a node with a technology object.


The usual interpretation of an assignment relationship is that the whole or part of the source element is assigned the whole of the target element. This means that if, for example, two active structure elements are assigned to the same behavior element, either of them can perform the complete behavior. If both active structure elements are needed to perform the behavior, the grouping element or a junction can be used, and if the combination of these elements has a more substantive and independent character, a collaboration would be the right way to express this.

 

Properties

The Assignment tab

Property Metamodel name Description
Display name DisplayName Initial value is off.
Short description ShortDescription  
Implements Implements Links to: All templates.
BreaksDownTo BreaksDownTo Links to: All templates.

Asset Group

The Asset Group template enables you to create groupings of assets. It is useful to have group categories for your assets to easily create overviews of the specific asset groups.

 

Properties

The AssetGroup tab

Property Metamodel name Description
Group category GroupCategory  
Short description ShortDescription  

 

Asset

The Asset template is used for Asset Management. In it you can gather all data relevant for the maintenance and documentation of your assets. You can then create checklists for maintenance of each asset, which can then be filled out via QualiWare’s webplatform. This enables you to keep track of your assets, their status and maintenance procedures.

 

Properties

The Asset tab

Property Metamodel name Description
AssetOrgID AssetOrgID  
Asset Org.ID AssetID  
Category Category  
Short description ShortDescription  
Model Model  
Se-nr SEnr  
Price Price  
Currency Currency Choices are:
EUR
USD
CAD
GBP
DKK
SEK
NOK
Purchase date PurchaseDate  
Product Product  
Vendor Vendor Links to: BusinessConnection, ExternalEntity.
Rental period RentalPeriod  

The Responsible tab

Property Metamodel name Description
Responsible HasResponsible Links to: Person, Position, OrganizationUnit, Role.
Registered by RegisteredBy Links to: Person.
Allowed to register checks AllowedToRegisterChecks Links to: Person, Position, OrganizationUnit, Role.

The Organization tab

Property Metamodel name Description
Organization unit(s) BelongsToOrganizationUnit Links to: OrganizationUnit.
Team(s) BelongsToTeams Links to: InterestGroup.

The Data tab

Property Metamodel name Description
SOP SOP Links to: BusinessProcessDiagram, Document, ExternalDocument, StandardOperatingProcedure, WorkFlowDiagram.
Technical data TechnicalData  
Manual Manual Links to: ExternalDocument, Document.
Service Partner ServicePartner Links to: BusinessConnection, ExternalEntity, OrganizationUnit, Position.
Validation report ValidationReport Links to: ValidationReport.

The IT tab

Property Metamodel name Description
Software Software Links to: InformationSystem, Software.

The Check list tab

Property Metamodel name Description
Check lists CheckLists Links to: CheckList.
Manual log ManualLog Links to: ManualLog.

The Relation tab

Property Metamodel name Description
Groups Groups Links to: label=AssetGroup.
Breaks down to BreaksDownTo Links to: Asset.

The Archive tab

Property Metamodel name Description
ArchivedObjId ArchivedObjId  

Assessment ArchiMate

In ArchiMate, an Assessment is a Motivation element.

An assessment represents the result of an analysis of the state of affairs of the enterprise with respect to some driver.

An assessment may reveal strengths, weaknesses, opportunities, or threats for some area of interest. These need to be addressed by adjusting existing goals or setting new ones, which may trigger changes to the Enterprise Architecture.

Strengths and weaknesses are internal to the organization. Opportunities and threats are external to the organization. Weaknesses and threats can be considered as problems that need to be addressed by goals that “negate” the weaknesses and threats. Strengths and opportunities may be translated directly into goals. For example, the weakness “Customers complain about the helpdesk” can be addressed by defining the goal “Improve helpdesk”. Or, the opportunity “Customers favor insurances that can be managed online” can be addressed by the goal “Introduce online portfolio management”. The name of an assessment should preferably be a noun or a (very) short sentence.

Properties:

Property Metamodel name Description
Short description ShortDescription
Implements Implements Links to: All templates.
BreaksDownTo BreaksDownTo Links to: All templates.

Artifact ArchiMate

The Artifact is in ArchiMate defined as a passive structure element and has been adopted from UML.

An artifact represents a piece of data that is used or produced in a software development process, or by deployment and operation of an IT system.

An artifact represents a tangible element in the IT world. Artifact is a specialization of technology object. It is typically used to model (software) products such as source files, executables, scripts, database tables, messages, documents, specifications, and model files. An instance (copy) of an artifact can be deployed on a node. An artifact could be used to represent a physical data component that realizes a data object.

An application component or system software may be realized by one or more artifacts. A data object may be realized by one or more artifacts. A node may be assigned to an artifact to model that the artifact is deployed on the node. Thus, the two typical ways to use the artifact element are as an execution component or as a data file. In fact, these could be defined as specializations of the artifact element.

The name of an artifact should preferably be the name of the file it represents; e.g., “order.jar”. An artifact may consist of sub-artifacts.

Properties:

Property Metamodel name Description
Short description ShortDescription
Implements Implements Links to: All templates.
BreaksDownTo BreaksDownTo Links to: All templates.

 

Artifact

An artifact is a classifier that represents some physical entity, a piece of information that is used or is produced by a software development process, or by deployment and operation of a system. Artifact is a source of a deployment to a node. A particular instance (or “copy”) of an artifact is deployed to a node instance.

The Artifact can be used in a component diagram or a deployment diagram and linked by an execution environment, a node or a device.

 

Properties

The Artifact tab

Property Metamodel name Description
Property Property Use this field to specify special modeling characteristics of the class.
Choices are:
Abstract
Root
Leaf
Visibility Visibility The visibility of the class for other components.
Final Specialization isFinalSpecialization Initial value is off.

The Attributes tab

Property Metamodel name Description
Attributes HasAttributes Use this field to create references to the attributes contained in this class.
Links to: Attribute, Property.

The Operations tab

Property Metamodel name Description
Operations HasOperations Use this field to make references to the Operations defined in this class.

Links to: Operation.

The Extensions tab

Property Metamodel name Description
Stereotype Stereotype Links to: Stereotype.
Constraints HasConstraints A reference to a named rule that extends the semantics of the component.
Links to: Constraint.
Tagged values HasTaggedValues The set of tagged values that extends the properties of this component.
Links to: TagDefinition.

The File Details tab

Property Metamodel name Description
File type HFileType
File name HFileName
File type FileType
File name FileName
File viewer FileViewer

For more information, you can read the UML specifications

Architecture Principle

You use the ArchitecturePrinciple template to document architecture principles – meaning rules you have defined or adopted to document a coherent enterprise architecture. You can link the ArchitecturePrinciple to the FrameWorkCells they apply to under the FrameWorkCell’s Architecture principles field under the ‘relations’ tab. You can also link the architecture principle directly to the ArchitectureFramework’s properites under its Principles-field.

Architecture Domain

The Architecture Domain template is used in FrameWorkCells that populates ArchitectureFrameworks. The Architecture Domain is linked to the FrameWorkCell in the FrameWorkCells properties and help describe what type of domain the framework cell represents – such as Technology, Application, Process and so on. You can then give the architecture domain an adequate description in its properties and link it to multiple framework cells if you create different views for the same domains. You are also able to link multiple domains to the same framework cell if domains overlap.

 

Properties

Property Metamodel name Description
Description Description Long verbal description.

Application Service : ArchiMate

An application service represents an explicitly defined exposed application behavior.

An application service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces. An application service is realized by one or more application functions that are performed by the component. It may require, use, and produce data objects.

An application service should be meaningful from the point of view of the environment; it should provide a unit of behavior that is, in itself, useful to its users. It has a purpose, which states this utility to the environment. This means, for example, that if this environment includes business processes, application services should have business relevance.

A purpose may be associated with an application service. An application service may serve business processes, business functions, business interactions, or application functions. An application function may realize an application service. An application interface may be assigned to an application service. An application service may access data objects. The name of an application service should preferably be a verb ending with “ing”; e.g., “transaction processing”. Also, a name explicitly containing the word “service” may be used.

Properties:

Property Metamodel name Description
Short description ShortDescription
Implements Implements Links to: All templates.
BreaksDownTo BreaksDownTo Links to: All templates.