Architecture Layer: Governance

Governance Workflow

Purpose: The purpose of the Governance Workflow template is to enable tailored governance solutions for the objects in your repository.

Core concerns: The Governance Workflow template enables you to model Governance Roles and Governance States. The Governance States are placed inside a Governance Role (just like a workflow diagram) and are connected by Governance Transitions, Governance Conditional Messages, and Governance Event Messages.

Below, you can see an example of a Governance Workflow:

The green arrows symbolize a Governance Transition towards the approval of an object while the red arrows symbolize a Governance Transition towards the development state of an object. The blue arrows are Governance Conditional Messages. While the broad, dark green arrows are the preferred Governance Transition, the lighter green colored arrows are alternate routes to the approved state.

 

Relation to other templates: The Governance Workflow template is a template that can be applied to any of the published objects or diagrams in the repository.

 

Properties and metadata: The Governance Workflow template can for example retain the following information:

  • A description of the workflow
  • Link to the owner of the Governance Master Role
  • Audits (auto generated information regarding its current state and access rights)

The above picture shows the properties dialogue window for the Governance Workflow template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Further details can be added under the different tabs such as which templates the Governance Workflow pertains to and email settings:

Repository Desktop

Purpose: The primary purpose of The Repository Desktop template is to design toolbars in QLM.

Core concerns: The Repository Desktop enables you to use Button Panels and Icons to design additional toolbars that can be added to the desired diagram template types in the actions tab in QLM. The toolbars can, when assigned to a template type, be used to analyze the data shown in diagrams.

Below, you can see some examples of different toolbars:

RepositoryDesktop_2

RepositoryDesktop_1

The repository has several toolbars available when installed that you, through the repository template can assign to the desired template types.

Other functionalities: The Repository Desktop template can also be used as an overview page that links out to other diagrams relevant for certain stakeholders. Below, you can see an example of a strategy desktop where each icon links to the model illustrated:

Relation to other templates: The Repository Desktop is, like the Matrix template, an auxiliary diagram. As such it is not directly connected to other templates but can be used to enable certain analytical functions in all types of diagrams.

Properties and metadata: The Repository Desktop template can, for example, retain the following information:

  • A description of the template
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Repository Desktop template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Matrix

Purpose: The Matrix template is used as an auxiliary diagram type for other diagrams. It can either show the properties or links of and between existing objects.

Concerns: There can be generated three types of Matrix diagrams: Link Matrices, Property Matrices and Text Matrices.

  • Link Matrices are typically used to summarize the links of two different template types. For example, a Link Matrix can be created using Business Process as the rows and Information Systems as the columns to quickly get an overview over which Information Systems are linked to which Business Processes under IT -Support.
  • Property Matrices can be used to summarize the contents of many objects, for example, of a single template type in a single diagram. For example, a Property Matrix can be created for Information Systems to obtain an overview over the details describing all the relevant Information Systems and identify any gaps in the information. You could also choose to filter the items in the template, so only the Information Systems used in a specified process are shown.
  • Text Matrices function as a regular spreadsheet. This type of matrix can for example be used to store data used for KPIs

Below is an example of a property matrix detailing the risks and control processes related to the process called ‘Inventory’:

Matrix_1

Below is an example of a link matrix detailing the relation between three identified risks and several controls (from the diagram, you can see that only two of three risks are addressed by the control processes):

Matrix_2

Relation to other templates: Where the Matrix can be used as a backend tool, Query Result Views (QRV’s) are created to give an overview of specific objects and their attributes on the collaboration platform.

 Properties and metadata: The Matrix template can for example retain the following information:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects

In the picture below you can see the Matrix template’s properties dialogue window, where the properties can be viewed and edited:

You can also edit the properties of the Matrix in the properties dialogue window by changing the Matrix behavior, Row filter or Column filter.

 

 

 

 

Hierarchy View

Purpose: The purpose of the Hierarchy View template is to show the hierarchy of objects related to a chosen root object.

Core concerns: The root object in the hierarchy View can for example be a Capability or a Business Process. The view is not modeled as a diagram, but generated based on information specified in the template’s property dialog, making the scope of the view flexible. Below, you can see an examples of a Hierarchy View for the Capability “Market Objects”:

Relation to other templates: The Hierarchy View is not directly connected to any single template but is not unlike a Context View. The Hierarchy View is, compared to a Context View, usually filtered to only show certain types of relations amongst certain types of objects and not as a default connected to diagram templates:

Properties and metadata: The Hierarchy View template can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the Hierarchy View
  • Link to the one responsible for the Hierarchy View
  • Audits (auto generated information regarding its current state and access rights)
  • Specifications (definition of root object and other inclusion criteria)
  • Adjust (specification of templates that should be removed from the view)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Hierarchy View template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

The HierachyView can be used in relation to the Standard Tree View in the HTMLPublisher, to establish a hierarchy for the network of process models in a repository.

Heatmap

Purpose: The purpose of the Heat Map template is to document a representation of values from other QualiWare templates in the form of a Heat Map.

Core concerns: The Heat Map template is created using the Risk Management and Application Portfolio Management toolbars in a diagrams action tab in QLM. It can afterwards be found under the Heat Map template in the repository explorer window.

The Heat Map template can, for example be used to document risks, identify the most pressing ones. Additionally, Heat Maps can be used to identify systems that don’t live up to business or technical criteria.

Below, you can see two examples of Heat Maps for risks. The first shows two risks and how they compare to each other with regards to significance and likelihood:

HeatMap_2

The second Heat Map shows four risks as well as their residual risks, and how they compare to each other regarding likelihood and significance:

HeatMap_1

Relation to other templates: The Heat Map can for example be generated from data gathered from a Business Process Network, Workflow Diagram, Business Process Diagram, Application Architecture Diagram or a Strategy Model.

Properties and metadata: The Heat Map template ­­­­can for example retain the following information:

  • A description of the diagram
  • Link to the owner
  • Link to the responsible
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the model

The above picture shows the properties dialogue window for the Heat Map template, where you can view and edit the template’s properties in QualiWare Lifecycle Manager.

To learn how to build Heat Maps in QualiWare click here

Graphical Matrix

Purpose: The purpose of the Graphical Matrix template is to compare the states or scores of objects, such as for example Capabilities or Information Systems.

Core concerns: The Graphical Matrix is generated based on information inserted into its property dialog where input, x-axis and y-axis are defined. Below, you can see an example of a Graphical Matrix for capabilities, scoring their quality and timeliness:

GraphicalMatrix_1

Relation to other templates: When scoring risks and visualizing residual risks, you can use a Heatmap.

Properties and metadata: The Graphical Matrix template can for example retain the following information:

  • A description
  • Link to the source of the input
  • Coordinate definitions of the Graphical Matrix
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects

The above picture shows the properties dialogue window for the Graphical Matrix, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager. Below, you can see the tab for Coordinate Definition:

Generic Query

Purpose: The Purpose of the Generic Query template is to provide datasets for QualiWare System templates.

Core concerns: The Generic Query template is an auxiliary template. The Generic Query can be created using a Query Design template which enables you to easily structure the query for creating reports. When creating a Report for a diagram, the Generic Query created using the Query Design should be used as a Data Set in the Report Definition.

A Generic Query can also be generated using its Property Dialog, where you can link to Data Source and filter the data selection using a wizard – see example of the property dialog below:

The Generic Query can, for example, take the form of data sheets:

GenericQuery_2

The Generic Query template can also execute a command using the Advanced Query tab:

Relation to other templates: Generic Queries are automatically created when creating a Query Design. Generic Queries are used in the following templates: HTML Template Definitions, HTML Embedded content, HTML Publisher, HTML Template Definition and HTML Content tab.

Properties and Metadata: The Generic Query can for example rentain the following information:

  • A description
  • Audits (auto generated information regarding its current state and access rights)
  • Query Filter, including a wizard for filter options
  • Attribute Definition
  • Advanced Query
  • Matrix Behavior

The above picture shows the properties dialogue window for the Generic Query where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

 

 

Browser Diagram

Purpose: The purpose of the Browser Diagram template is to build a structure for reports in QualiWare.

Core concerns: The Browser Diagram template allows you to build a graphical representation of a reports structure, from which it will then generate a code for the system to execute. The symbols available in the Browser Diagram template are: Browser Filter, Browser Action, Browser All and Browser Source. They can be connected by Browser Relation, Browser Back Relations and Browser Graphic Relations.

Several Browser Diagrams are included in the installation of QualiWare. Below, you can see an example of a Browser Diagram for a Business Process Network:

The Following is a Browser Diagram for Audit Planning:

BrowserDiagram_1

Relation to other templates: The Browser Diagram template is used for QualiWare platform customization and is as such related to templates such as the Generic Query, Query Design.

Properties and metadata: The Browser Diagram template ­­­­can for example retain the following information:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Browser Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.