Document Desktop

Purpose: The purpose of the Document Desktop is to show the internal and external documents currently in use.

Core concerns: The Document Desktop template enables you to model Document Structures, Document Fragments, Documents, External Documents and Configuration Diagrams.

Below, you can see an example of a Document Desktop, where an organizations templates and forms are gathered in the form of external documents:

In the next example, you can see two collections of Reports, which set the structure for the reports available to print from the collaboration platform:

The Document Desktop template can also be used to gather collections of reports, which you can see examples of below:

QualiWare Diagram Template Reports:

Reports:

 

Relation to other templates: To document a well-defined combination of documents and files, a Configuration Diagram should be used. Other templates related to the configuration of Reports are: Browser Diagram, Document Structure, and Document Header.

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

  • A description of the desktop
  • 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 Document Desktop, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Document Header

Purpose: The purpose of the Document Header template is to enable the design of headers and footers for Documents and Reports.

Core Concerns: The Document Header template enables you to design your own headers and footers for reports and documents using General Concepts and User Labels.

The Document Header is when completed connected to the relevant Document Fragment. Below, you can see an example of a Header for a report:

Relation to other templates: Other templates related to the configuration of Reports and documents are: Browser Diagram, Document Structure, and Document Desktop.

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

  • A description of the Document Header
  • 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 Document Header where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Document Structure

Purpose: The Purpose of the Document Structure template is to provide a description of components in a document extracted from the repository.

Core concerns: The Document Structure template enables you to model Document Structures and their related Document Fragments and connecting them.

Below you can see two examples of Document Structures:

Relation to other templates: Other templates related to the configuration of Reports and documents are: Browser Diagram, Document Header, and Document Desktop.

Properties and metadata: The Document Structure template can for example retain the following metadata:

  • A description of the Document Structure
  • Definition of Initial and Final commands
  • Link to External document
  • Definition of PrePrintAction and PostPrintAction
  • 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 Document Structure template where you can view and edit the templates properties in QualiWare Lifecycle Manager.

HTML Explorer Layout

Purpose: The purpose of the HTML Explorer Layout is to contain information of the HTML explorer and its behavior. A new template for this purpose has been created. Please see HTML Mega Menu for information on how to change the setup of your web platform menu layout. To change the setup of the tiles in the menu, you should use the HTML Publisher.

HTML Slide Menu

Purpose: The purpose of A HTML Slide Menu is to contain information of the menu in the web platform and the behavior of the menu. A new template for this purpose has been created. Please see HTML Mega Menu for information on how to change the setup of your web platform menu layout.

HTML Popup Menu Layout

Purpose: A HTML Popup Menu Layout contains information of the popup menu and the behavior of the menu on the web. A new template for this purpose has been created. Please see HTML Mega Menu for information on how to change the setup of your web portals menu layout.

HTML Menu Layout

Purpose: The purpose of the HTML Menu Layout is to contain information of the menu and the behavior of the menu on the web. A new template for this purpose has been created. Please see HTML Mega Menu for information on how to change the setup of your web platform menu layout.

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

Control Coverage Map

Purpose: The purpose of the Control Coverage Map is to provide an overview of uncovered risks, residual risks and potential cost of the risk occurring.

Core concerns: The Control Coverage Map concerns itself with Financial Risk Management and is created using the Actions tabs in QLM. It can be created based on the information in a Risk Heatmap or by using information from a diagram which contains risks that also have control actions.

Below, you can see an example of a Control Coverage map for four risks related to a Bellhouse, a Pump, a Suction pipe and using Check lists:

ControlCoverageMap

The Blue column represents the likelihood of the risk before the control action, the green column represents the likelihood of the risk after the implementation of a control action. The red columns represent the estimated cost if the risk is realized.

Relation to other templates: The Control Coverage Map presents graphical views of information from other diagrams the same as the Heatmap, Business Charts and the Graphical Matrix. It can be used by any diagram containing Activities with attached risks that have control activities.

Properties and metadata: The Control Coverage Map ­­­­can for example retain the following information:

  • A description
  • Link to the owner
  • Link to the one responsible
  • Graphical specification for the headers of the X-axis and Y-axis
  • 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 Control Coverage Map

The above picture shows the properties dialogue window for the Control Coverage Map template where you can view and edit the template’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.