Templates | QualiWare Center of Excellence

Firewall

Purpose: The purpose of the Firewall template is to document network zones designated by firewalls.

Core concerns: The Firewall template enables you to model Zones, Computers, Networks and Firewall Policies to create a model of a firewall. A firewall is used to control the communication between different networks, typically for security reasons.

Graphical representation of objects:

A Firewall diagram will typically show the Zones of the firewall and the communication policies/rules (Firewall Policies) that exist between the zones. Below, you can see an example of a Firewall diagram containing Zones and Servers (represented by the Computer object):

Relation to other templates: The Firewall template is a technology template and related to the Infrastructure Diagram.

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

A description of the diagram
Link to Vendor and Hardware
Link to servers
Contract information
Details about resources, costs and benefits
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 Firewall template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Environmental Impact Diagram

Purpose: The purpose of the Environmental Impact Diagram template is to document the environmental aspects and impacts for an Activity or Business Process.

Core concerns: The Environmental Impact Diagram enables you to model Business Functions, Activities, Business Objects, Environmental Aspects (Environmental Aspect, Environmental Impact, Health and safety impact) and Business Scopes. These elements can then be connected by Impact Quantities.

Below, you can see an example of an Environmental Impact Diagram, detailing the Environmental aspects and Health and safety impact:

The diagram shows all identified aspects and modes of impact for one or more specific processes.

Relation to other templates: The Environmental Impact Diagram is related to the Lifecycle Assessment diagram as well as templates containing Activities, Business Functions, Lines of Business, and Logistical Flows. As such, it is related to, for example, Business Process Diagrams, Workflow Diagrams, Business Diagrams, and Strategy Models.

Properties and metadata: The Environmental Impact Diagram 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 diagram

The above picture shows the properties dialogue window for the Environmental Impact Diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Enterprise Investment Portfolio

Purpose: The purpose of the Enterprise Investment Portfolio template is to model enterprise goals and investments.

Core concerns: The Enterprise Investment Portfolio template enables you to model Goals, Projects, and Initiatives. The projects and initiatives can be connected to enterprise goals them through Project Contributions, that show the viable minimum and optimistic maximum of the value contribution. Below, you can see an example of an Enterprise Investment Portfolio, where the way goals are realized is visualized:

Other Functionalities: By using the Enterprise Investment Actions tab, you can create, for example, a Portfolio Value matrix, which offers another way to view the same data:

Relation to other templates: The Enterprise Investment Portfolio is a strategic template and is as such related to the enterprise’s Strategy Model, Strategic Roadmap, Business Canvas and Innovation Canvas. The projects contained in the initiatives can also be further described in the Work Model template.

Properties and metadata: The Enterprise Investment Portfolio 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 Enterprise Investment Portfolio template, where you can view and edit the diagram’s Properties in QualiWare Lifecycle Manager.

For more information: This model type is used in the Enterprise Investment Methodology developed by Chris Potts and QualiWare. To learn more about Enterprise Investment, you can about it here:Enterprise Investment.

Deployment Diagram

Purpose: The purpose of the Deployment Diagram is to document the configuration of run-time processing nodes and the components they contain.

Core concerns: The Deployment Diagram template is structural UML diagram that enables you to model Packages, Components, Artifacts, Instance Specifications, Properties, Nodes, Devices, Execution Environments, Deployment Specifications, Objects, Classes, Interfaces, and Annotations. They can then be connected through Association, Dependency, Generalization, Deployment or Manifestation.

The Deployment Diagram models how the different hardware component and software components are connected. Below you can see an example of a Deployment Diagram for a booking service:

In the next example, you can see how Packages and Components would be included in a Deployment Diagram:

Relation to other templates: The Deployment Diagram is, as a component model, part of the application domain on the operational level. As such, it offers a complimentary view to those of the Application Architecture Diagram, Class Diagram, Component Diagram, Data Flow Diagram, Data Mapping Diagram, Data Replication Diagram, Sequence Diagram, State Event Diagram, Structure Chart, and Use Case Diagram.

Properties and metadata: The Deployment 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
Links to extensions such as Stereotypes and Constraints
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 Deployment Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Decision Model

Purpose: The purpose of the Decision Model template is to document complex decisions by modelling decision trees that illustrates decision gates. Below you can see an example of a Decision Model:

Core concerns: Complex decisions can be documented as decision trees. The model illustrates the Business Decision and its underlying Rule Families. The Rule Families can contain Rule Family Tables, that precisely describe the outcome of a given set of variables. Below you can see an example of a Rule Family Table:

Relation to other templates: Where the Decision Model template illustrates the decision gates, the end to end process is described in either a Work Flow Diagram or a Business Process Diagram.

Properties and metadata: The Decision Model 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 accuracy 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
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below you can see the Decision Model’s properties dialogue window, where the information can be viewed and edited:

Data Replication Diagram

Purpose: The purpose of the Data Replication Diagram template is to map a high-level view of the movement and replication of information between data sources.

Core concerns: The Data Replication Diagram template enables you to map Data Sources, Data Files, Data Transformations and Data Warehouses. These elements can then be connected by either a Data Extract or a Data Apply.

Graphical representation of the elements:

Below, is an example of a Data Replication Diagram for a commercial Data Warehouse:

The model shows that the data is extracted from different data sources, transformed and applied to the Data Warehouse from which it is extracted, aggregated and either applied to sales, production or improvement.

Relation to other templates: The Data Replication Diagram offers a high-level data mapping. The Data Transformations contained in the Data Replication Diagram can be further decomposed into more detailed Data Mapping Diagrams.

Properties and metadata: The Data Replication 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 it

The above picture shows the properties dialogue window for the Data Replication Diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Data Model Diagram

Purpose: The Purpose of the Data Model Diagram template is to model the structure of data entities of an Information System and their relationships. Documenting the structure of information is a very important part of the preliminary analysis before implementing any Information System.

Core concerns: The Data Model Diagram template enables the user to document the structure of the information, that an Information System is supposed to store. The template allows you to model using Data Entities, Subject Area, Data Entity View, Model View and inheritance. The Connection types available are: Data Relation, Inheritance Connection, Complex Relation and Generalization. Below you can see an example of a Data Model Diagram describing the information structure related to an order:

Relation to other templates: The Data Model Diagram template should not be used to document data flows. In that case the Data Flow Diagram template should be used.

Properties and metadata: The Data Model 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 accuracy 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
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

The above picture shows the properties dialogue window for the Data Model Diagram where you can view and edit the diagram’s properties.

Data Mapping Diagram

Purpose: The purpose of the Data Mapping Diagram is to map data’s sources.

Core concerns: The Data Mapping Diagram template enables you to model Data Entities, Classes, Tables, Records and Mapping Algorithms. These are connected by Data Mappings. The Data Mapping Diagram is sometimes called Entity Mapping Diagram.

Below, you can see an example of a Data Mapping Diagram where data is moved from one table to another transforming from ‘customer data’ into ‘client data’:

The following very simple diagram illustrates the relations between Records and their elements:

Relation to other templates: The Data Mapping Diagram is, through the object Data Transformation, related to the Data Replication Diagram. Data Transformation is contained in the Data Replication Diagram and has a mapping which is described in the Data Mapping Diagram.

Properties and metadata: The Data Mapping Diagram 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 Data Mapping Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Data Flow Diagram

Purpose: The purpose of the Data Flow Diagram is to document a system’s or part of a system’s data flows; the data input the system (or a process within the system) consumes and the data output the system produces.

Core concerns: The Data Flow Diagram enables you to model Processes, Data Stores, External Entities, Control Processes and Control Stores. These elements can then be connected by either Data Flows or Control Flows.

Graphical representation of the elements:

The Data Flow Diagram can show different levels of processes within a system that exchange data, and illustrate how those exchanges occur. As such, the model can document a system’s functional hierarchies.

Below, you can see an example of a Data Flow Diagram showing the Data Flows between several Data Stores, Processes and External Entities in a Bookshop:

The next example shows the Data Flow between process, Data Stores and External Entities for a Highway Repair Service:

The final example shows the Data Flows between Processes, Datastores and External Entities in an Outlook Mailbox:

Relation to other templates: The Processes in the Data Flow Diagram can be decomposed into more detailed Data Flow Diagrams to comprise the total functional model. The top level of a Data Flow Diagram is sometimes called a Context Diagram. However, in QLM we use the Data Flow Diagram template for the higher levels as well as the more detailed ones.

The Data Flow Diagram can be a decomposition of an Information System. It can offer a more detailed view of Data Flows than, for example, the Application Architecture Diagram.

An Information System could likewise be decomposed into a Business Process Diagram which offers a complimentary view less concerned with Data Stores and Data Flow, and more concerned with Activity Flow.

Properties and metadata: The Data Flow 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 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 Data Flow Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Dashboard

Purpose: The purpose of the Dashboard template is to publish selections of Business Charts targeting different stakeholders. It should be used to gather a series of relevant or connected Business Charts to provide a dashboard-like overview.

Core concerns: The Dashboard template enables you to gather Business Charts, Key Performance Indicators, Performance Indicators and General Concepts to create stakeholder specific views of analyzed data. For example, an Enterprise Architect could find a Dashboard containing Business Charts relevant to the usage and governance of the Enterprise Architecture useful.

Below, you can see examples of different Dashboards presenting an array of Business Charts:

Relation to other templates: The Dashboard template is closely connected to the Business Chart template, as the Dashboard publishes the charts the Business Chart template generates.

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

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