Templates and model types in the QualiWare platform.
The GovernanceActionList or a single GovernanceActionMethod is used in relation to a GovernanceWorkflow and can be activated when doing a transition (GovernanceTransition/GovernanceConditionalMessage) either before (pre) or after (post).
It can also be activated when an event happens (GovernanceEventMessage).
A GovernanceActionList can be composed of one or more GovernanceActionMethod(s) and NoticationTemplate(s).
A high-level statement of intent, direction, or desired end state for an organization and its stakeholders. A goal can represent anything a stakeholder may desire, such as a state of affairs, or a produced value. Examples of goals are as follows: to increase profit, to reduce waiting times at the helpdesk, or to introduce online portfolio management. Goals are typically used to measure success of an organization. Goals are generally expressed using qualitative words; e.g., “increase”, “improve”, or “easier”. Goals can also be decomposed.
A goal refers to a desired end-state or outcome that a process, workflow, or journey is meant to achieve. It is the objective or purpose of a given activity or set of activities. Goals provide a clear and concise representation of what an organization is trying to achieve.
For example, in a customer journey map, goals might include improving customer satisfaction, increasing sales, or reducing churn. By representing goals in a diagram, organizations can better understand the desired outcomes of their processes, workflows, and journeys and to align their efforts and resources accordingly.
The Generic Table Interface enables import or export data to and from QualiWare.
It is possible to import data from multiple sources as instances of templates within QualiWare.
The GenericTableInterface template can import and export to Delimited text files such as a comma-separated values (CVS).
See Guide to Generic Table Interface for details.
Description of this template will be available soon.
Description of this template will be available soon.
The General Concept template can be used as a generic symbol to show an image on a diagram, and it is possible to associate macros to the object.
Generalization is a template that represents an inheritance relationship between a more general (superclass or base class) and a more specific (subclass or derived class) element. In generalization, the subclass inherits the features (attributes and operations) of the superclass, and can also extend or override them to add or modify behaviors. This template promotes reusability and modularity in the system design by allowing common features to be shared among multiple classes.
Example: In a Class Diagram for a system that manages different types of user accounts, you might have a general class called “User” with attributes like “username”, “email”, and “password”, and operations like “login()” and “logout()”. You can then create more specific classes like “Admin” and “Customer” that inherit from the “User” class through generalization. These subclasses would automatically inherit the attributes and operations of the “User” class, and could also define additional features or customize behaviors specific to their roles.
Description of this template will be available soon.
A statement of difference between two plateaus.
