Archives: Templates

Templates and model types in the QualiWare platform.

Inventory

The inventory symbol describes the holdings of a company’s raw materials, work-in-progress products, finished goods, and safety stock. The symbol represents the physical goods that the company holds in stock and is ready to sell or use in its operations.

Interface Realization

Interface Realization is a template in a Class Diagram that represents the relationship between a class (or component) and an interface, indicating that the class implements the interface. An interface is a collection of abstract operations (methods or functions) without any implementation details. A class that realizes an interface is contractually obligated to provide an implementation for all the operations defined in the interface.

Interface Realization promotes the concept of separation of concerns by defining the contract (interface) separately from the implementation (class). This allows for greater flexibility and maintainability, as multiple classes can implement the same interface while providing different implementations, and changes to the interface or implementation can be made independently.

Example: In a Class Diagram for a system that processes payments, you might define an interface called “PaymentProcessor” with operations like “authorizePayment()” and “capturePayment()”. Then, you can create different classes such as “CreditCardProcessor” and “PayPalProcessor” that realize the “PaymentProcessor” interface. Each of these classes will have to provide their own implementation of the “authorizePayment()” and “capturePayment()” operations, as defined in the interface. This allows the system to handle various payment methods while maintaining a consistent API for processing payments.

Interface

This template is part of the UML. Interfaces declare coherent services that are implemented by BehavioredClassifiers, such as a Class, that implement the Interfaces via Interface Realization.

 

For more information about the UML, you can find the current specifications here.

 

Properties

The Interface tab

Property Metamodel name Description
Short Description ShortDescription  
Property Property Choices are:
Root
Leaf
Abstract
Visibility Visibility Choices are:
Protected
Public
Private
Package
Operations HasOperations 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: Tag Definition.

 

Interest Group

InterestGroup is a template that can be used to collect a set of organizational objects into a group.

In the standard Metamodel you can include the following templates types into an interest group:

  • Person
  • OrganizationUnit
  • InterestGroup
  • Postion
  • Role

An InterestGroup can be used to in relation to other objects in the repository, in relations to GovernanceWorkFlows or AcknowledgeLists.