Presentation Definition

The Presentation Definition is used in the PowerPoint Generator. It defines which diagram templates the presentation styling applies to, where the diagram data comes from, the optional master slide styling, and the optional AI description settings.

Short description: (Optional) Fill in Short description with a short internal note on what this Presentation Definition is for.

Relevant for template: the template(s) this Presentation Definition applies to (for example, BusinessProcessDiagram). This determines which diagram types the styling and AI settings are offered for.

Data Source: GenericQuery that is suitable for the diagram template entered in Relevant for template. This query supplies the data the presentation is built from.

Master slide file: (Optional) Fill in a Master slide file with an ExternalDocument that contains a PowerPoint file with a master slide. Only slide 1 of this PowerPoint file is used for the presentation’s visual styling — any other slides in the file are ignored.

AI settings (optional)

Complete this section only if diagrams generated from this Presentation Definition should be able to include AI-written descriptions.
Use AI to explain model: Yes/No

Context templates:

Knowledge structure: choose or create an OntologyDiagram that defines which object and symbol attributes are allowed to be sent to the AI. Only attributes covered by this ontology are available to the AI when it writes a description.

Root definition: Set Root definition to the root object of the ontology selected in the previous step (for example, BusinessProcessDiagram).

Configure Prompting (Required for AI)

Complete this section together with AI settings if you want to control how the AI writes its descriptions.

Additional knowledge characteristics: Fill in an explanation, in plain text, of how you want the AI to write the information — for example the tone, audience, and format (such as instructing it to write in bullet points for a management audience).

Set Randomness (Temperature) to a value between 0 (predictable, repeatable wording) and 1 (more varied wording).

Publish the Presentation Definition

You need to publish the HTMLPublisher on the PresentationDefinition object. Publishing makes the Presentation Definition available for selection as a styling template by web users.

DataConversionTemplate

The DataConversionTemplate specifies a Interface and the settings for conversions.

It can be used to do reverse engineering of databases, linked by a SubjectArea (on the Physical Implementation tab) from a DataModellingStructure.

The DataConversionTemplate specifies an Interface and the settings for conversions.

– Select the Interface and create the default values.

Right click the Settings areas a select Default to add the Default Content.

The settings can also be added manually.

Hint: New option fields are read-only by default. Move the horizontal cursor to the left and select the Option will enable 4 options:

  • 0 => Read only
  • 1 => Editable as string
  • 2=> By choice e.g. True or False (Add choices in ‘Choice’ column, before selecting default value in ‘Value’ column )
  • 3=> Object selection filtered by template

Name Convention

Right click the Settings areas a select Default to add the Default Content.

Internal Messages

Right click the Settings areas a select Default to add the Default Content.

Video

The DataConversionTemplate can be used to reverse engineering of databases (together with Data Modelling Structure and a DataSourceConnection)

Reverse engineering of SQL Server database

Data Modelling Structure

The DataModellingStructure diagram is used to create model of datastructures.

The diagram is used to assemble the subject areas of your datamodel and it will keep track of all level of abstractions from highest level concept models, all the way through the physical representation of a database.

The diagram can be used to reverse and forward engineer databases.

The diagram consist of one or multiple SubjectArea that can be broken down to logical level using DataModelDiagram and physical level using RelationalDiagram.

First time you create a SubjectArea you are asked to create the logical model (this can be added later).

From the SubjectArea there are links to (Breaks Down To) the available models on the different abstraction levels:

 

On the Physical Implementation tab, you can link to DataConversionTemplate and add a DataSourceConnection.

When you double click on the SubjectArea you can select to open the dialog, or go to the available models directly:

 

Video

The Data Modelling Structure can together with the DataSourceConnection be used to reverse engineering of databases.

Reverse engineering of SQL Server database

BusinessImpactAnalysisElement

The BusinessImpactAnalysisElement is a central template in the Business Continuity Management solution in QualiWare, first introduced in QualiWare 10.3.

The BIA-element handles the “What can go wrong”-view and is split into three focus areas supporting the strategic view, the process view and the technology view. In addition legal elements and afffected ressources can be mapped to the element.

Workaround can be described in the element, and furthermore the resilience, recovery and contigency can be managed and linked through the dedicated templates:

EnterpriseBlueprint:EDGY

Purpose: The purpose the Enterprise Blueprint is to make a blueprint of the enterprise by collecting the most relevant elements from the enterprise point of view.

Core concerns: The Blueprint enables you to collect objects of the different facets in the EDGY language in one diagram.

TechnicalDebt

The TechnicalDept template is used to document technical dept related to e.g. software development and IT-systems.

Technical debt refers to the long-term cost or extra work incurred when software development shortcuts are taken, prioritizing speed over code quality or maintainability.

Technical Dept is a part of the Application Management Desktop as part of the “Evaluate application portfolio”.

CustomerJourneyMap:EDGY

The Customer Journey Map in used to create a visual representation of the end-to-end journey that a customer experiences when interacting with a product(s) or service(s) of an enterprise. It
outlines the customer’s interactions across various touchpoints, channels, and stages, capturing their emotions, pain points, and expectations at each step.