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.

Stakeholder Model

Purpose: The purpose of the Stakeholder Model template is to document internal and external individuals or groups who have a stake in for example an enterprise or a project. Below, you can see an example of a Stakeholder Model of Order Management:

StakeholderModel_1

Core concerns: Stakeholders can be grouped via Business Scope. Stakeholder relations are illustrated via the Interaction connection. Beyond this, you can enrich the Stakeholder Model with Capabilities, Business Processes, Information Systems, Initiatives, and Projects. Below, you can see several groupings of stakeholders:

StakeholderModel_2

Relation to other diagrams: The Interaction connections in the Stakeholder Model can be broken down into Requirement Models. The internal structure of the organization is modelled in an Organization Diagram while the interaction between the organization and its external environment can be modelled in a Business Ecosystem.

Properties and metadata: The Stakeholder 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 Stakeholder Model’s properties dialogue window, where the properties can be viewed and edited:

Business Process Network

Purpose: The purpose of the Business Process Network is to at document a mid- to high-level view of Business Processes and their interrelationships.

Core concerns: The Business Process Network template enables the documentation of top to mid-level processes. The core objects available to model with are Business Processes, Business Events, Business Objects, Business Scope, Information Systems, and different types of connections. Below you can see two examples of a Business Process Network modelled in different styles.

High level process view without business events or connections between processes:

BusinessProcessNetwork_2

High-level process view where business events and connections indicate a flow between processes, stakeholders and customers:

BusinessProcessNetwork_1

Relation to other templates: The top-level processes would typically be broken down to one or more levels of mid-level processes. The last level of Business Process Networks can then be broken down to several Workflow Diagrams or Business Process Diagrams detailing the activities contained within the business process

Properties and metadata: The Business Process Network can for example retain the following information:

  • Description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for executing the processes in 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

In the picture below you can see the Business Process Network’s properties dialogue window, where the diagrams properties can be viewed and edited:

Business Object Model

Purpose: The purpose of the Business Object Model is to present a structured view of an organization’s products and services.

Core concerns: The focus of this template is the Business Object that can be described through Decomposition, Generalization, Association and Dependency with other Business Objects. Notes can be used to group Business Objects, for example as High-Growth Revenue Products, as seen in the below model:

BusinessObjectModel

The modelling syntax can be extended to also include strategic elements such as: Requirements, Problems, Change Requests, Goals, Performance Indicators and policies. They can be connected to the Business Objects through Strategic Alignment.

Relation to other templates: The Business Object Model belongs to the Information domain where it offers a conceptual and logical view of an organizations products and services. As such, it is related to templates such as Product Canvas, Product Roadmap and Product Variant Master

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

Business Diagram

Purpose: The purpose of a Business Diagram is to show the functional structure and relationships of the whole or part of an organization.

Core concerns: The Business Diagram template enables you to model Business Functions, Information Systems, Inventory, Business Scope, Lines of Business, Information Flow and Logistical Flow. The diagram’s syntax can be extended to also include strategic elements such as Goals, Objectives, Stakeholders and Performance Indicators.

The Business Diagram should be broken down into several levels of recurring Business Diagram templates. In the model below, you can see an example of a high-level Business Diagram showing Business Functions and their Information Flows and Logistical Flows –  describing the flow of products and services – in this case for a car rental service.

The Business Functions are placed with the operational functions in the bottom together with the Logistical Flow and with management control at the top of the Business Diagram.

On lower levels (decompositions) of Business Diagrams, Information Systems are placed close to the Business Functions that are responsible for or own the Information Systems.

Relation to other templates: The Business Diagram can be used as an addition to a Business Process Network and Strategy Models, giving a practical view of how the organizations functions fit together, illuminating interdependencies.

Properties and metadata: The Business 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
  • Indication of the diagram portrays an as-is situation or a to-be situation
  • The Perspective can be defined as either: Holistic, Sub-functional, Process, or IT Focused.
  • 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 Business Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Business Context

Purpose: The purpose of the Business Context template is to reveal what value your enterprise offers, and how your business activities contribute to its success.

Core concerns: The Business Context template enables you to model Value Propositions, Business Activities and Business Values. These elements can be related through Connections, Associations, Aggregations and Flows.

The Business Context template is about market offerings and profitability. Working closely with business stakeholders, it allows expressing in business terms the objectives behind a initiative.

Below, you can see an example of a Business Context diagram for a rental car service showing the overall Value Proposition, its Business Values broken down as well as which Business Activities deliver the Business Values:

Relation to other templates: The Architecture Overview is part of the Enterprise Design framework and is as such related to the templates: Actor Map, Brand Overview, Business Context, Business Ecosystem, Communication and Customer Journey Map.

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

For more information: To learn more about the Enterprise Design framework, please visit Enterprisedesignframework.com or view our webinars on Strategic Enterprise Design.

 

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.

BusinessCanvas_1

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.

BusinessCanvas_2

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

 

Organization Viewpoint

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.

 

Application Cooperation Viewpoint

Concerns: Relationships and dependencies between applications, orchestration/choreography of services, consistency and completeness, reduction of complexity
Purpose: Designing
Scope: Multiple layer/Multiple aspect

The application cooperation viewpoint describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization. This viewpoint is also used to express the (internal) cooperation or orchestration of services that together support the execution of a business process.

Abstraction Level
Coherence, details

Layer
Application layer

Aspects
Behavior, active structure, passive structure

ApplicationCoopViewpoint

 

Motivation Viewpoint

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

The motivation viewpoint allows the designer or analyst to model the motivation aspect, without focusing on certain elements within this aspect. For example, this viewpoint can be used to present a complete or partial overview of the motivation aspect by relating stakeholders, their primary goals, the principles that are applied, and the main requirements on services, processes, applications, and objects.