Template Type: Non-Graphical

Business Entity

The Business Entity is part of the DORA reporting (see DORA Desktop) used to manage the different business entities part of the reporting.

Questionnaire

Questionnaires are used in Survey to design the questionnaire.

On the first tab, you can choose between different design, grouping and styling.

On the Questions tab you can set up the questionnaire via questiongroups and their linked questions.

Read more about survey here.

Question

Questions are used in a survey.

It it possible to create text answers or answers with options, where the respondent choice among predefined options.

Questions are collected in Questiongroup as part of a questionnaire.

Read more about surveys here.

Survey

The survey template is used to collect all relevant elements related to manage a survey, from designing the questionnaire, simulating it, inviting participants, and analyse the results.

An essential part of the survey is the questionnaire that is linked to the survey.

The questionnaire can contain one or more questionsgroups and each questiongroup can contain one or more questions.

Read more about survey here.

Ontology:OWL

The ontology Annotations

Annotations are used to associate information with ontologies. These provide meaningful definitions to the ontology.

An ontology is defined and described with:

  • A Name (here “foaf”)
  • A Title
  • An IRI (Internationalized Resource Indicator) which points to its documentation on the web
  • A Short description
  • A Version number and its pointer to the file describing it (Version IRI)
  • Some History dates (first issued, and last modified)
  • Creators (names of its creator(s))
  • A License reference and its Publisher
  • Its Source (the target to its definition)
  • A Prefix

A Namespace definition

The “Prefix” is used as the reference to the described ontology, when its defined classes are referenced from another ontology. In the referring ontology the referenced classes appear as prefixed with this term. Supposing an ontology referencing “Person” (as defined in FOAF), this class will be prefixed as “foaf:Person” explicating that in the context of this ontology, “Person” must be understood as defined in FOAF.

 

An ontology refers

An ontology refers:

  • Possibly an external document (See also)
  • Referred ontologies (used for defining the prefixes used to refer to these ontologies)

 

Diagrams (one or more diagrams presenting graphically the ontology)

Diagrams are based on the OntologyDiagram:owl template (see below in the “OntologyDiagram” paragraph).

 

An ontology is described with content

An ontology contains (is described with) :

  • Classes (these are the Class:owl instances which appear in the Ontology Diagram)

Object Properties (these are the ObjectProperty:owl instances which appear in the Ontology Diagram)

These two fields are automatically filled at close of the Ontology Diagram which is referred to by the Ontology.

 

The ontology detailed Description

An ontology has a detailed description

 

Note

These Annotation fields described above are edited by the ontology engineer when creating his/her ontology.

The ontology example (FOAF) we use to show these Annotations populated with content is an “up level” ontology and is published on the web.

Loading automatically these published ontologies makes sense. We used a semi-automatic way to load it.

 

Currently there is no fully automated load of ontology source document. We are working on it and will deliver this automatic load soon.

News Item

The News Item template is used to post and share News on the collaboration platform.

When you create a NewsItem you can add a short description, a full description as well as information about when it should be released and archived.

The relevant news will be shown as standard on the News Tile on the Desktop.

A list of available News items can be found in the leftmenu.

Interface

This template is part of the UML. Interfaces declare coherent services that are implemented by BehavioredClassifiers, such as a Class, that implement the Interfaces via Interface Realization.

 

For more information about the UML, you can find the current specifications here.

 

Properties

The Interface tab

Property Metamodel name Description
Short Description ShortDescription
Property Property Choices are:
Root
Leaf
Abstract
Visibility Visibility Choices are:
Protected
Public
Private
Package
Operations HasOperations Links to: Operation.

The Extensions tab

Property Metamodel name Description
Stereotype Stereotype Links to: Stereotype.
Constraints HasConstraints A reference to a named rule that extends the semantics of the component.
Links to: Constraint.
Tagged values HasTaggedValues The set of tagged values that extends the properties of this component.
Links to: Tag Definition.

 

Incident

The Incident is used to register some kind of event that needs to be handled, e.g to document a DataBreach.

The incident can also be used in a more broader sence to capture “any kind of event”. This way a user can register an incident, and then an “investigator” can transfer the incident to another flow, e.g. to the Accident flow.

There is a standard governance workflow for incidents which enables you to progress the incident through the stages.

The governance workflow control the incident. Once it is created by a user, it is send to investigation by the responsible. The indicent can:

  • “stay” in its own flow and progress through the stages “Handling”, “Finished” and finally “Closed”
  • or the incident can be transferred to a complaint, non-conformance, change request or accident. This way the end user just have to register an incident and then the “investigator” has the possibility to “re-categorize” it to a more destinct flow. When an incident is transferred, the Incident is closed and a link is created to the tranferred object in the relevant flow.

There is a standard Tile for Incident Management of the Compliance Desktop.

Department

Description of this template will be available soon.