Priority: 2

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.

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:

HTMLDialogLayout

Purpose: The purpose of the HTML Dialog Layout template is to enable the organization to tailor the objects Dialog Layout on the collaboration platform.

Core concerns: The HTML Dialog Layout template enables you to model HTML Dialog Layout, HTML Dialog Fields, HTML Dialog Groups and HTML Dialog Text. Using these elements, you can design the content of your dialogs. Below you can see an example of a Dialog Layout for a Business Process Network:

Relation to other templates: The HTML Dialog Layout template is, like the other HTML templates, a tool for creating a fully tailored collaboration platform that meet the needs of the specific organization. As such it is related to HTML Mega Menu, Generic Query and Query Design.

Properties and metadata: The HTML Dialog Layout template can for example retain the following information:

  • A description
  • Audits (auto generated information regarding its current state)
  • Access rights (such as linking to roles with read/write rights)
  • Layout (such as dialog title and colors)
  • Sub-dialogs (shown as additional tabs in the dialog)

The above picture shows the properties dialogue window for the HTML Dialog Layout template, where you can view and edit the diagram’s 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 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.

Package Diagram

Purpose: The purpose of the Package Diagram is to group elements of a large system and illustrate the dependencies between them.

Core concerns: The Package Diagram can be used to organize a system’s parts and enables you to model Packages, Profiles and Annotations. These can be connected using Dependency, Profile Application, Package Merge, Package Import and Containment.

Below, you can see an example of a Package Diagram for a booking system for a car rental service:

 

Relation to other templates: The Package diagram offers a simplified view of for example a Class Diagram, grouping classes into packages. It should be used when a class diagram becomes too large and complex to easily read.

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

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

Performance Diagram

Purpose: The purpose of the Performance Diagram is to provide a view over an organization’s performance in reaching their strategic goals.

Core concerns: The Performance Diagram enables you to model Key Performance Indicators – which can be related to strategic goals, derivative Performance Indicators and Derivation Rules. You can create a Performance Diagram as a decomposition of a Key Performance Indicator and model a hierarchy of performance diagrams. The model below shows an overview of an organizations Key Performance Indicators and their status:

In the following model the Key Performance Indicator has been enriched with derivative performance indicators explaining in more details the status of the performance and how it is measured:

The overview of the Key Performance Indicators can also be presented with a simplistic view, highlighting their status using color coded icons:

Relation to other templates: The Performance Diagram is a Strategic template and can be decomposed from Key Performance indicators contained in, for example, a Balanced Scorecard Diagram or Dashboard.

 

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

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

Production Site

Purpose: The purpose of the Production Site template is to provide a model over the content and flow of a production site.

Core Concerns: The Production Site template enables you to model Production Lines, Work Centers, Equipment, Inventory and Fixed Installations. These elements can then be connected by Logistical Flows, Wires or Transport Systems. Below, you can see an example of a ‘Job Shop’ Production Site:

The Production Site can in its property window have its production process environment classified as being either a:

  • “Job Shop” which is characterized by the organization of similar equipment by function such as drilling, welding, painting and assembly. As jobs flow from work center to work center a different type of operations is performed in each center.
  • “Continuous Flow” which is characterized by an uninterrupted flow in the production such as processing of fluids, wastes, powders and basic metals., e.g. and oil refinery.
  • “Dedicated Repetitive Flow” which is characterized by production of discrete parts in a production facility dedicated to only one product.
  • “Batch Flow” which is characterized as a flow shop design producing more than one product. Due to long setup time production is run in large batches, e.g. a brewery where production line needs to be cleaned up between each batch to avoid product contamination from previous product.
  • “Fixed Site” which is characterized by transportation of materials, tools and personnel to a fixed location where the product will be built, e.g. shipbuilding, construction and assembly of item that are difficult to move.

 

Relation to other templates: The Production Site template offers an additional perspective to the Product Architecture, Product Canvas, and Product Roadmap templates. Together, these templates illustrate the different aspects of the production process.

 

Properties and metadata: The Production Site Diagram can for example retain the following information:

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