Diagrams | QualiWare Center of Excellence

Business Canvas

Purpose: The Business Canvas, is a strategic management and entrepreneurial template. It allows you to describe, design, challenge, invent, and pivot your business model.

Core Concerns: The core elements of the business canvas are framework cells that define a strategic or organizational entities and, if needed, connections between them. The Business Model can be structured any way you wish. The most well know structure of a business model is Alexander Osterwalder’s Business Model Canvas.

The above picture shows a blank Business Model Canvas where each area is represented by a framework cell.

The strategic or organizational entities can then be enriched with an extended portfolio of strategic symbols such as vision, mission, goals, stakeholders, information systems and business processes.

Full content list of the extended portfolio:

Vision
Mission
Business Object
Market
Competitive Advantage
Technology
Competence
Capability
Performance Indicator

Business Function
Business Process
Organization Unit
Stakeholder
Information System
External Entity
Location
Channel
Goal

Opportunity
Threat
Trend
Material Asset
Intellectual Capital Asset
Business Rule
Key Performance Indicator

The picture below shows a Business Model Canvas that is filled out with symbols from the extended portfolio.

Relation to other templates: The Business Canvas can link to multiple related templates detailing the businesses capabilities, business processes, strategy and more.

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

A description of the diagram
Link to the owner of the application architecture
Link to the one responsible for the application architecture
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

Browser Diagram

Purpose: The purpose of the Browser Diagram template is to build a structure for reports in QualiWare.

Core concerns: The Browser Diagram template allows you to build a graphical representation of a reports structure, from which it will then generate a code for the system to execute. The symbols available in the Browser Diagram template are: Browser Filter, Browser Action, Browser All and Browser Source. They can be connected by Browser Relation, Browser Back Relations and Browser Graphic Relations.

Several Browser Diagrams are included in the installation of QualiWare. Below, you can see an example of a Browser Diagram for a Business Process Network:

The Following is a Browser Diagram for Audit Planning:

Relation to other templates: The Browser Diagram template is used for QualiWare platform customization and is as such related to templates such as the Generic Query, Query Design.

Properties and metadata: The Browser 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 of the diagram

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

Balanced Scorecard Diagram

Purpose: The purpose of the Balanced Scorecard Diagram is to model Balanced Scorecards, as described by Robert Kaplan and David Norton in 1992.

Core concern: Usually, a Balanced Scorecard Diagram template measures the state of the enterprise via Key Performance Indicators that are categorized into four different perspectives using Business Scopes. Aside from this, the template enables you to model general concepts and cause/effect.

Below, you can see an example of a Balanced Scorecard Diagram:

Relation to other templates: The Balanced Scorecard Diagram can be used to create a Performance Evaluation Model or a Strategic Management Diagram the Key Performance Indicators it contains can be broken down into Performance Diagrams offering a detailed view of how the organization performs. If CXO dashboards are to be created, the Strategy Model should be used instead.

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

Architecture Framework

Purpose: The purpose of the Architecture Framework template, is to provide an overview of the enterprise, and the context for a diagram, showing where in the architecture and repository it belongs. An Architecture Framework shows the overall structure of the architecture and the structure with which it is represented in the repository.

Core concerns: The Architecture Framework template consists of FrameWorkCells, FrameWorkColumns, FrameWorkRows and LineOfBusinesses. You can choose to model the framework to fit the one your organization is using – QualiWare supports a wide range of architecture frameworks out of the box such as Zachman, TOGAF , OIOEA, EA3 Cube, EDGY, QualiWare EA Framework, and many more.

Below, you can see an example of the QualiWare EA Framework:

Below, you can see an example of a TOGAF framework:

Relation to other templates: The Architecture Framework template is used to represent the repository’s architecture in the form of a specific framework. If CXO dashboards are to be created, the Strategy Model should be used instead.

An ArchitectureFramework can be modeled using FrameWorkRows, FrameWorkColumns, and FrameWorkCells

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

A description of the diagram
Link to Architecture principles and project models
Link to the owner of the framework
Link to the one responsible for the framework
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 Architecture Framework where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Application Usage Viewpoint : Archimate

Purpose: Designing, deciding

Concerns: Consistency and completeness, reduction of complexity

Scope: Multiple layer/Multiple aspect

The application usage viewpoint describes how applications are used to support one or more business processes, and how they are used by other applications. It can be used in designing an application by identifying the services needed by business processes and other applications, or in designing business processes by describing the services that are available. Furthermore, since it identifies the dependencies of business processes upon applications, it may be useful to operational managers responsible for these processes.

Abstraction Level
Coherence

Layer
Business and application layers

Aspects
Behavior, active structure, passive structure

Application Functionality Context

Purpose: The purpose of the Application Functionality Context template is to document the in which Activities and/or Business Processes a given Application Functionality is used.

Core concerns: The Application Functionality Context template can be used to create graphical views showing where Application Functionalities are used. The template enables you to model Application Functionalities, Activities and Business Processes. The Business Processes and Activities are connected to Application Functionalities using Functionality Usage.

Below, you can see an example of an Application functionality contest diagram, where the context for the DocCom – Create and Store Document functionality is shown:

The diagram shows which Business Processes use the Application Functionality as well as which Information System delivers it.

Relation to other templates: To map applications hardware, the Application Architecture Diagram or Infrastructure Diagram template should be used. The Application Functionality Context template graphically connects functionalities of Information Systems to the Processes and Activities in which they are used. It offers an additional view to Application Architecture Diagrams, Workflow Diagrams, Business Process Diagrams and Business Process Networks.

Properties and metadata: The Application Functionality Context 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 diagram

The above picture shows the properties dialogue window for the Application Functionality Context template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Strategy Viewpoint : Archimate

Concerns: Strategy development
Purpose: Designing, deciding
Scope: Strategy

The strategy viewpoint allows the business architect to model a high-level, strategic overview of the strategies (courses of action) of the enterprise, the capabilities and resources supporting those, and the envisaged outcomes.

Capability Map Viewpoint : Archimate

Concerns: Architecture strategy and tactics, motivation
Purpose: Designing, deciding
Scope: Strategy

The capability map viewpoint allows the business architect to create a structured overview of the capabilities of the enterprise. A capability map typically shows two or three levels of capabilities across the entire enterprise. It can, for example, be used as a heat map to identify areas of investment. In some cases, a capability map may also show specific outcomes delivered by these capabilities.

Organization Viewpoint : Archimate

Concerns: Identification of competencies, authority, and responsibilities
Purpose: Designing, deciding, informing
Scope: Single layer/Single aspect

The organization viewpoint focuses on the (internal) organization of a company, department, network of companies, or of another organizational entity. It is possible to present models in this viewpoint as nested block diagrams, but also in a more traditional way, such as organizational charts. The organization viewpoint is very useful in identifying competencies, authority, and responsibilities in an organization.

Outcome Realization Viewpoint : Archimate

Concerns: Business-oriented results
Purpose: Designing, deciding
Scope: Strategy

The outcome realization viewpoint is used to show how the highest-level, business-oriented results are produced by the capabilities and underlying core elements.