Producer: QualiWare Superusers

HTML Mega Menu

Purpose: The purpose of the HTML Mega Menu template is to enable the tailoring of the left menu on the collaboration platform.

Core concerns: The HTML Mega Menu template enables you to build the left menu using HTML Mega Menu Items, which can be layered. The example below shows how a menu looks in our modelling tool:

The screenshots below show how a menu can look on the collaboration platform and how the sub-menus are shown:

The left menu can be configured for differently for diffrent roles. The left menu can be modelled in 3 levels:

The HTMLMegaMenu is composed of HTML Mega Menu Items.

The Mega Menu is published to the Web via the HTML Publisher.

Relation to other templates: The HTML Mega Menu is related to the other HTML templates such as Generic Query, HTML Dialog Layout and Query Design.

 

Properties and metadata: The HTML Mega Menu template can for example retain the following information:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Menu settings
  • Text settings

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

Menu Layout

Purpose: The Purpose of the Menu Layout template is to provide the menu structure for the system developed in the Dialog Model.

Core concerns: The Menu Layout template enables you to model Menu Items which can be connected by containing each other – as is the case with the HTML Mega Menu template.

Relation to other templates: The Menu Layout is a QualiWare system template and is related to the Dialog Model, Dialog Layout, Report Layout and Help Model.

Properties and metadata: The Menu Layout 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 Menu Layout

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

Query Design

Purpose: The purpose of the Query Design template is to enable easy design of Generic Queries.

Core concerns: The Query Design template enables you to model Object Queries and Relation Queries into Generic Queries. When creating a Query Design, a Generic Query will be generated automatically and appear graphically on the diagram as a white triangle in a green circle – see the model below:

Relation to other templates: The Query Design template is used to generate Generic Query templates which can be used in creating Report Definitions, Spreadsheets and HTMLQueryResultViews.

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

  • A description
  • Audits (auto generated information regarding its current state and access rights)
  • Query filter (with wizard for filter options)

The above pictures show the properties dialogue window for the Query Design Template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager

You can see an example of a Query Design in the QualiTube sections, where there is a video on Composity Query Design.

Report Layout

Purpose: The purpose of the Report Layout is to provide the layout of a report for the system developed in the Dialog Model.

Core concerns: The Report Layout template enables you to model Report Pages and Report Fields which can be related by connections.

Relation to other templates: The Report Layout is a QualiWare system template and is related to the Dialog Model, Dialog Layout, Menu Layout and Help Model.

Properties and metadata: The Report Layout 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 Report Layout template

The above picture shows the properties dialogue window for the Report Layout template where you can view and edit its 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.

 

 

 

 

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 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.

 

 

Dashboard

Purpose: The purpose of the Dashboard template is to publish selections of Business Charts targeting different stakeholders. It should be used to gather a series of relevant or connected Business Charts to provide a dashboard-like overview.

Core concerns: The Dashboard template enables you to gather Business Charts, Key Performance Indicators, Performance Indicators and General Concepts to create stakeholder specific views of analyzed data. For example, an Enterprise Architect could find a Dashboard containing Business Charts relevant to the usage and governance of the Enterprise Architecture useful.

Below, you can see examples of different Dashboards presenting an array of Business Charts:

Dashboard_1

 

Dashboard_2

Relation to other templates: The Dashboard template is closely connected to the Business Chart template, as the Dashboard publishes the charts the Business Chart template generates.

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

  • A description of the Dashboard
  • Link to the owner of the Dashboard
  • Link to the one responsible for the Dashboard
  • 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 Dashboard template where you can view and edit the dashboard’s properties in QualiWare Lifecycle Manager.