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.
Archives: Templates
Templates and model types in the QualiWare platform.
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.
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.
Interaction Overview Diagram
Purpose: The purpose of the Interaction Overview Diagram is to visualize a sequence of activities and deconstruct a complex scenario that would otherwise require multiple ‘if-then-else paths’ to be illustrated as a single sequence diagram.
Core concerns: The Interaction Overview Diagram is a Behavioral UML model. The template enables you to model Call Behavior Actions, Decision Nodes, Merge Nodes, Initial Nodes, Activity Final Nodes, Fork Nodes, Join Nodes, Duration Constraints, and Annotations. These elements can then be connected by Control Flows.
Below, you can see an example of an Interaction Overview Diagram for a sd System Authentication:
Relation to other templates: The Interaction Overview Diagram is part of the UML templates QualiWare supports along with the Activity Diagram, Communication Diagram, Deployment Diagram, Class Diagram, Composite Structure Diagram, State Diagram, Package Diagram, Component Diagram, Sequence Diagram, Use case diagram, Timing Diagram, Composite structure Diagram
Properties and metadata: The Interaction Overview 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)
- Extensions (Stereotypes, Constraints and Tagged values)
- 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 Interaction Overview Diagram template, where you can view and edit the Diagram’s properties in QualiWare Lifecycle Manager.
For more information: about the UML, please visit the Object Management Group’s Website, where you can find the complete specification.
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.
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.