Template Type: Diagrams

Data Modelling Structure

The DataModellingStructure diagram is used to create model of datastructures.

The diagram is used to assemble the subject areas of your datamodel and it will keep track of all level of abstractions from highest level concept models, all the way through the physical representation of a database.

The diagram can be used to reverse and forward engineer databases.

The diagram consist of one or multiple SubjectArea that can be broken down to logical level using DataModelDiagram and physical level using RelationalDiagram.

First time you create a SubjectArea you are asked to create the logical model (this can be added later).

From the SubjectArea there are links to (Breaks Down To) the available models on the different abstraction levels:

 

On the Physical Implementation tab, you can link to DataConversionTemplate and add a DataSourceConnection.

When you double click on the SubjectArea you can select to open the dialog, or go to the available models directly:

 

Video

The Data Modelling Structure can together with the DataSourceConnection be used to reverse engineering of databases.

Reverse engineering of SQL Server database

EnterpriseBlueprint:EDGY

Purpose: The purpose the Enterprise Blueprint is to make a blueprint of the enterprise by collecting the most relevant elements from the enterprise point of view.

Core concerns: The Blueprint enables you to collect objects of the different facets in the EDGY language in one diagram.

CustomerJourneyMap:EDGY

The Customer Journey Map in used to create a visual representation of the end-to-end journey that a customer experiences when interacting with a product(s) or service(s) of an enterprise. It
outlines the customer’s interactions across various touchpoints, channels, and stages, capturing their emotions, pain points, and expectations at each step.

IntroductoryViewpoint:ArchiMate

The Introductory Viewpoint is a legacy viewpoint from ArchiMate 2.0.

The Introductory Viewpoint in ArchiMate is designed to provide a simplified overview of an architecture, typically used at the beginning of a design process. This viewpoint uses a subset of the full ArchiMate language with a simplified notation, making it easier to understand and communicate the initial ideas without overwhelming stakeholders with too much detail.

LandscapeMapViewpoint-ArchiMate

The Landscape Map Viewpoint is a legacy viewpoint introduced in ArchiMate 2.0.

This viewpoint helps in visualizing the relationships and dependencies between different architectural elements across various layers, providing a comprehensive overview of the architecture landscape.

Value Stream Model

Purpose: The purpose of a Value Stream Model is to model a value stream end-to-end from the perspective of one stakeholder and one value proposition.

Core concerns: The Value Stream Model template enables you to model the value stream stages, triggering stakeholder, and the value proposition. The value stream represents a formal description of how stakeholder value is delivered.

Value Stream Viewpoint : Archimate

Purpose:
The primary purpose of the ValueStreamViewpoint is to present a coherent visual representation that focuses on how value is created, progressed, and delivered in the context of the enterprise’s strategy. It provides insights into the motivations behind strategic decisions and reveals the capabilities that underpin these value creation activities.

Core Concerns:

Stakeholder Alignment: How do the strategic efforts of the organization align with the needs, desires, and expectations of its key stakeholders? What outcomes are stakeholders expecting, and how does the value stream aim to deliver on these expectations?

Strategic Capabilities: What are the foundational abilities or capacities of the organization that enable the value creation process? How do these capabilities support or interact with the various stages of the value stream?

Value Creation and Flow: How is value produced, enhanced, and delivered across the enterprise? This concerns the sequence of activities that cumulatively produce the desired outcomes for stakeholders.

Organizational Context: Given the composite elements, this viewpoint may also touch upon how the value streams and capabilities are grouped, categorized, or located within the broader organizational context.

 

Example:

the example above shows a ValueStreamViewpoint for an insurance company, where each stage in the value stream is served by a number of capabilities. Between these stages, we see the ValueFlows with associated BusinessObjects & Values, and at the end the Outcome that this value stream realizes for a particular stakeholder.

In summary, the ValueStreamViewpoint provides a strategic lens, offering stakeholders a visual narrative of how value is created, based on the enterprise’s capabilities, and how this creation aligns with the motivations and desired outcomes of its stakeholders. It gives an abstracted yet holistic view, allowing for strategic decisions, analysis, and alignment checks. The composite elements further provide a way to understand the enterprise’s structuring or geographical distribution of these strategic components.

Value Chain Model

Purpose: The purpose of a Value Chain Model is to model a value chain and show relationships to essential elements of an organization, such as capabilities, policies, regulations, information concepts and systems.

Core concerns: The Value Chain Model template enables you to model Business Processes, Capabilities, Information Concepts, Information Systems, Organizations Units, Goals, KeyPerformanceIndicators, Policies, Regulations, Risks and Opportunities.

 

Value chain models can help businesses by:
  • Highlighting weak points in core functions and processes
  • Breaking down all the activities that go into producing a good or service and understanding areas of cost savings and differentiation
  • Optimizing efforts, eliminating waste, and improving profitability
  • Visualising relationships between processes and capabilities

Principles Viewpoint:ArchiMate

Purpose: The Principles Viewpoint in ArchiMate is used to define and model the principles that guide an enterprise’s decisions and actions. It enables architects to capture and communicate the fundamental values and beliefs that shape an organization’s strategy, culture, and behavior. By doing so, the Principles Viewpoint helps to ensure that all stakeholders have a common understanding of the principles and can make informed decisions based on them.

Core Concerns: The core concerns of the Principles Viewpoint include defining and documenting the principles, their relationships to other architectural elements, and their impact on the enterprise. The Principles Viewpoint helps to ensure that the principles are aligned with the enterprise’s goals and objectives, and that they are consistent with its vision, mission, and values. Additionally, it helps to ensure that the principles are integrated into the enterprise’s architecture and that they are applied consistently across all areas of the organization.

Example:

Overview: The Principles Viewpoint is a perspective in the ArchiMate enterprise architecture modeling language that focuses on the principles that guide an organization’s decisions and actions. Principles are high-level statements that capture an organization’s values, beliefs, and goals, and they provide a framework for decision-making and action. In the Principles Viewpoint, principles are represented as rectangular shapes with labels that describe their meaning and purpose. Relationships between principles are shown as lines connecting the principles, with labels that describe the nature of the relationship.

The Principles Viewpoint includes several concepts for modeling different aspects of principles, including:

  • Principles: A principle is a high-level statement that captures an organization’s values, beliefs, and goals. Principles can be modeled to show their meaning, purpose, and impact on the enterprise.
  • Relationships: Relationships between principles can be modeled to show the dependencies, conflicts, and synergies between them. This helps to ensure that the principles are consistent and aligned with the enterprise’s goals and objectives.
  • Impacts: The impact of principles on the enterprise can be modeled to show how they influence decision-making and action. This helps to ensure that the principles are integrated into the enterprise’s architecture and that they are applied consistently across all areas of the organization.

Overall, the Principles Viewpoint is useful for defining and modeling the principles that guide an enterprise’s decisions and actions. It provides a common understanding of the principles and ensures that they are aligned with the enterprise’s goals and objectives. By doing so, it helps to ensure that the enterprise operates in a consistent and coherent manner and achieves its strategic objectives.

Goal Contribution Viewpoint:ArchiMate

Purpose: The Goal Contribution Viewpoint in ArchiMate is used to model how business goals are related to each other and how they contribute to the overall business strategy of an enterprise. The purpose of this viewpoint is to provide a clear understanding of the relationships between goals and how they align with the enterprise’s overall objectives. This can help organizations prioritize their goals and ensure that they are working towards their strategic objectives.

Core Concerns: The core concerns of the Goal Contribution Viewpoint include modeling the relationships between business goals, the contributions that each goal makes towards the overall strategy, and the measures used to assess progress towards the goals. By focusing on these core concerns, the Goal Contribution Viewpoint can help organizations identify opportunities for improving their strategy and ensuring that their goals are aligned with their overall business objectives.

Example:

The Goal Contribution Viewpoint is a perspective in the ArchiMate enterprise architecture modeling language that focuses on the relationships between business goals and how they contribute to the overall strategy of an enterprise. In this viewpoint, goals are represented as ovals with labels that describe their purpose and significance. Relationships between goals are shown as lines connecting the goals, with labels that describe the nature of the relationship.

The Goal Contribution Viewpoint includes several concepts for modeling different aspects of goal contribution, including:

  • Goal Dependencies: Goal dependencies are used to show how one goal contributes to another goal. This can help organizations understand how achieving one goal may impact the achievement of another goal.
  • Goal Decomposition: Goal decomposition is used to break down high-level goals into more specific, measurable objectives. This can help organizations track progress towards their goals and assess whether they are on track to achieve their strategic objectives.
  • Goal Measures: Goal measures are used to assess progress towards goals. This can help organizations determine whether they are making progress towards their goals and whether any adjustments need to be made to their strategy.

Overall, the Goal Contribution Viewpoint is useful for modeling the relationships between business goals and ensuring that they are aligned with the overall strategy of an enterprise. By providing a clear understanding of how goals contribute to the enterprise’s strategic objectives, organizations can prioritize their goals and ensure that they are working towards their strategic objectives.