Templates | QualiWare Center of Excellence

Role

The Role object can be used to represent the different parts of an organization that are involved in a specific process or workflow. For example, in a customer journey map, a role might represent the customer service team, while in a work flow diagram, a role might represent a marketing team.

By defining roles in a diagram, organizations can ensure that everyone has a clear understanding of their responsibilities and that the right individuals or teams are involved in the right activities at the right time. This can help to improve the overall efficiency and effectiveness of the organization and to ensure that everyone is working towards the same goals.

Overall, roles play a critical role in helping organizations to align their goals, improve their processes, and ensure that everyone is working together towards a common vision.

Sequence Flow

A Sequence Flow is used to show the order that activities will be performed in a Process. Each Flow has only one source and only one target. The source and target must be from the set of the following Flow Objects: Events (Start, Intermediate, and End), Activities (Task and Sub-Process), and Gateways. During performance (or simulation) of the process, a Token will leave the source Flow Object, traverse down the Sequence Flow, and enter the target Flow Object.

QualiWare will automatically name the Sequence Flow object with an abbreviated name of the From and To objects.

QualiWare permits the User to provide a Short Description for the Sequence Flow (See the Short Description field on the Sequence Flow tab of the QualiWare Object Editor ).

A Sequence Flow is a line with a solid arrowhead that MUST be drawn with a solid single line.
BPMN does not use the term Control Flow when referring to the lines represented by Sequence Flow or Message Flow. The start of an activity is controlled not only by Sequence Flow (the order of activities), but also by Message Flow (a message arriving), as well as other process factors, such as scheduled resources. Artifacts can be Associated with activities to show some of these other factors. Thus, BPMN uses a more specific term, Sequence Flow, since these lines mainly illustrate the sequence that activities will be performed. A Sequence Flow MAY have a conditional expression attribute, depending on its source object. This means that the condition expression must be evaluated before a Token can be generated and then leave the source object to traverse the Flow. The conditions are usually associated with Decision Gateways, but can also be used with activities. If the source of the Sequence Flow is an activity, rather than Gateway, then a Conditional Marker, shaped as a mini-diamond, MUST be used at the beginning of the Sequence Flow. The diamond shape is used to relate the behavior to a Gateway (also a diamond) that controls the flow within a Process.
A Sequence Flow that has an Exclusive Data-Based Gateway or an activity as its source can also be defined with a condition expression of Default. Such Sequence Flow will have a marker to show that it is a Default flow. The Default Marker MUST be a backslash near the beginning of the line.
By default, the ConditionType of a Sequence Flow is None. This means that there is no evaluation at runtime to determine whether or not the Sequence Flow will be used. (See the Condition Type field on the SequenceFlow tab of the QualiWare Object Editor for the applicable values of None, Expression, and Default).

Once a Token is ready to traverse the Sequence Flow (i.e., the Source is an activity that has completed), then the Token will do so. The normal, uncontrolled use of Sequence Flow, in a sequence of activities, will have a None ConditionType. A None ConditionType MUST NOT be used if the Source of the Sequence Flow is an Exclusive Data-Based or Inclusive Gateway. The ConditionType attribute MAY be set to Expression if the Source of the Sequence Flow is a Task, a Sub-Process, or a Gateway of type Exclusive-Data- Based or Inclusive. If the ConditionType attribute is set to Expression, then a condition marker SHALL be added to the line if the Sequence Flow is outgoing from an activity. However, a condition indicator MUST NOT be added to the line if the Sequence Flow is outgoing from a Gateway. An Expression ConditionType MUST NOT be used if the Source of the Sequence Flow is an Event-Based Exclusive Gateway, a Complex Gateway, a Parallel Gateway, a Start Event, or an Intermediate Event. In addition, an Expression ConditionType MUST NOT be used if the Sequence Flow is associated with the Default Gate of a Gateway. The ConditionType attribute MAY be set to Default only if the Source of the Sequence Flow is an activity or an Exclusive Data-Based Gateway. If the ConditionType is Default, then the Default marker SHALL be displayed.
If the ConditionType attribute is set to Expression, then the ConditionExpression attribute MUST be defined as a valid expression. The expression will be evaluated at runtime. If the result of the evaluation is TRUE, then a Token will be generated and will traverse the Sequence–Subject to any constraints imposed by a Source that is a Gateway. (See the Expression field on the SequenceFlow tab of the QualiWare Object Editor where the user must provide a valid Expression for the applicable SequenceFlow, typically done in an If, Then, Else type of statement.)

The Assignment field in the Sequence Flow object editor allows the QualiWare user to define a set of variables that are or may be necessary for generation of BPEL (Business Process Execution Language).

Service

A Service in QualiWare typically represents a Service in the context of Service Oriented Architecture (SOA) and therefore common and reusable services that will be used in the context of Information Systems that support the processes of the business. The Service template can also be used to define Business Services; i.e., in the context of services the business either offers to its customers or clients or wishes to offer them.

On the object editor window the following properties for Service can be entered:
· Short Description – brief description of the service and its purpose.
· Operations – a listview where the user can link to Operations (i.e., The specification of a service that may be requested from objects) that are or will be used to support the Service.
· Handles Data – a listview where the user can link to multiple data related templates to show what data is handled by or required by the Service.
· On the Capability tab – the QualiWare user can link to the Capability template via the Deliver Capability listview; thus showing what Capabilities currently are or will be provided via the Service, and the Executed by Activity listview provides the ability to link the Service to one or more Activities as they may be part of one or more business processes; thus showing the linkage between Services and Business Processes.

On the Information tab – the QualiWare user can link to data related templates via the Uses Information listview and specify by clicking in the Create, Read, Update, Delete, or Source columns of the listview what action is being taken by the Service on the data item in the listview. The QualiWare user can also link to UserInterfaces that are used or will be used in the delivery or execution of the Service.

Serving : ArchiMate

The serving relationship describes how the services or interfaces offered by a behavior or active structure element serve entities in their environment. This relationship is applied for both the behavior aspect and the active structure aspect.

Compared to the earlier versions of this standard, the name of this relationship has been changed from ‘used by’ to ‘serving’, to better reflect its direction with an active verb: a service serves a user. The meaning of the relationship has not been altered. The ‘used by’ designation is still allowed but deprecated, and will be removed in a future version of the standard.

The usual interpretation of a serving relationship is that the whole of the source element serves (is used by) the target element. This means that if, for example, two services serve the same internal behavior element, both of these services are needed. If two services are alternative solutions and only one of them is needed by the internal behavior element, an or junction can be used.

Signal

Indicates that a signal is either sent or expected depending on the specification.

Software

Software is a computer program. Software can either be bound directly to a Computer or through a Software License. Using software licenses enables you to keep track of multiple licenses for each piece of software.

Software Configuration

A software configuration is way of defining standard packages of multiple programs. A configuration can contain Software objects or Software License objects which enables you to keep track of your licenses. It is also possible to make trees of configurations making administration even easier.

Software License

A software license is used to control your licenses. The license is either bound to a Computer or a Software Configuration.
Through the license you can get an overview on which computers your licenses are installed.

Specialization ArchiMate

The specialization relationship has been inspired by the generalization relationship in UML class diagrams, but is applicable to specialize a wider range of concepts. The specialization relationship can relate any instance of a concept with another instance of the same concept.
A specialization relationship is always allowed between two instances of the same element.
Alternatively, a specialization relationship can be expressed by nesting the specialized element inside the generic element.

Specialization Aspect

A selection of a property that determines which subclass a concept instance of the super class shall belong to. If it is exhaustive an instance of the superclass must always belong to at least one subclass. If it is overlapping an instance may belong to more than one subclass at a time.