Value Stream

A ValueStream is a step in a ValueStreamModel, representing a step in a stream.

A ValueStream has inherited a set of the properties from the BusinessProcess, enabling to describe it:

  • from a RASCI  (Responsible, Accountable, Support, Consulted, Informed) point of view
  • Capability view
  • IGOE (Input, Guide, Output, Enbler) point of view
  • Economic point of view

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 : Archimate

A sequence of activities that create an overall result for a customer, stakeholder, or end user.

A value stream describes how an enterprise organizes its activities to create value. A key principle of value streams is that value is always defined from the perspective of the stakeholder – the customer, end user, or recipient of the product, service, or deliverable produced by the work.

Value streams are typically realized by business processes and possibly other core behavior elements. The stages in a value stream provide a framework for organizing and defining business processes, but different parts of the organization may have their own implementations of business processes that realize the same value stream stage. Conversely, one business process may realize multiple stages in a value stream.

It is recommended that the name of a value stream be expressed using a verb-noun construct in the active tense; e.g., “Acquire Insurance Product”.

Stakeholder : Archimate

The role of an individual, team, or organization (or classes thereof) that represents their interests in the effects of the architecture. In order to direct efforts to their interests and concerns, stakeholders change, set, and emphasize goals. Stakeholders may also influence each other. Examples of stakeholders are executives and key managers in an organization, the board of directors, shareholders, customers, business and application architects, and external partners and regulators. The name of a stakeholder should preferably be a noun.

Constraint : Archimate

A limitation on aspects of the architecture, its implementation, or its
realization. In contrast to a requirement, a constraint does not prescribe some intended functionality of the system to be realized, but imposes a restriction on the way it operates or may be realized. This may be a restriction on the implementation of the system (e.g., specific technology that is to be used), a restriction on the implementation process (e.g., time or budget constraints), or a restriction on the functioning of the system (e.g., legal constraints). The name of a constraint should be easily understood and is often a short sentence.

Application Event : Archimate

An application state change. Application functions and other application behavior may be triggered or interrupted by an application event. Also, application behavior may raise
events that trigger other application behavior. Unlike processes, functions, and interactions, an event is instantaneous; it does not have duration. Events may originate from the environment of the organization (e.g., from an external application), but also internal events may occur generated by, for example, other applications within the organization. The name of an application event should preferably be a verb in the perfect tense; e.g., “claim received”


Introduction to KnowledgeScope

The KnowledgeScope template is an innovative QualiWare Lifecycle Manager (QLM) tool designed to configure the Generative QualiAI. It is structured to streamline the process of creating intelligent and context-aware response diagrams. By leveraging the KnowledgeScope, businesses can harness the power of AI to generate diagrams that are not only accurate but also tailored to the specific nuances of their operations.

Key Features:

  • Configurable Sections: The KnowledgeScope has configurable sections, such as AIKnowledgeScope, Context, Prompting, and Response, which allow you to determine the content of the diagrams created with the AI.
  • AI-Driven Diagram Generation: Leverages QualiWare’s AI capabilities to produce diagrams informed by the context and prompting provided.

Section Details


This primary section offers a succinct overview of the template’s purpose, along with a business definition and a selection of example diagrams for reference.

  • Short Description: Concisely articulates the purpose of the KnowledgeScope.
  • Business Definition: Provides a broad context of the business or a specific business space, if detailed in the definition.
  • Example Diagram List: A curated list (recommended to be 1 or 2) of diagrams from your repository which exemplify the desired outcome, aiding the AI in context understanding.


The Context section is the backbone of the template, influencing the AI’s understanding and generation process.

  • Context Dropdown Menu: Offers four methods to establish context for content generation:
    • Current Selected Object: Targets the object currently selected in the web-modeler.
    • Current Diagram: Utilizes the open diagram in the current tab.
    • Select from List: Employs the selected context from the “Link Context” function.
    • Context Undefined: Provides flexibility for open context definition via text input or object selection.
  • Context Templates Text Field: Lists available templates serving as potential context sources for the KnowledgeScope.
  • Knowledge Structure: Comprises two subfields—Ontology and Root Definition
    • Ontology: This field is dedicated to defining the ontology that governs the data to be accessed from the Context Templates. Users should link to a pre-defined ontology, using the template “OntologyDiagram:owl” in QualiWare. This format helps the AI understand what data is relevant and should be considered during the generation process. For example, if using the BusinessProcess template, the Ontology field should point to an ontology diagram that outlines the necessary data to be accessed from the BusinessProcess context.
    • Ontology Example: ‘BusinessProcess’ The accompanying image illustrates an ontology with ‘BusinessProcess’ as the root. Use this as a guide to link your context templates to your ontology. Proper linkage ensures that AI-generated content aligns with your business framework.
    • Root Definition: Root definition is crucial as it marks the starting point for the AI’s data extraction from the ontology. When multiple context templates are used, there must be a corresponding root for each, and all roots should be contained within the same diagram. This ensures that the AI has a clear entry point to begin its contextual data interpretation for each template. The roots collectively form a map of data points that the AI uses to extract information relevant to the generation of the new content.


This section allows users to input additional knowledge characteristics and set the randomness level of AI responses.

  • Additional Knowledge Characteristics: This section directs the AI in creating diagrams that align with specific organizational standards. For clarity and precision, input concise directives. For example:
    • Diagram Initiation: “Begin and end WorkFlowDiagrams with a Business Event.”
    • Naming Conventions: “Use concise, descriptive naming for all symbols.”

    These instructions shape the AI’s output, ensuring it meets your defined criteria and maintains consistency with your organization’s practices.

  • Randomness (Temperature): A dropdown to adjust the AI’s creativity level, with a recommended default of 0.3 for diagram creation.
  • Knowledge Prompts: A collection of pre-defined AI query templates, that you have created, used to standardize rules or commands across various KnowledgeScopes.

Template Naming Conventions

Proper naming of templates is critical for ensuring seamless functionality within the KnowledgeScope. Adhering to QualiWare’s naming conventions allows the AI to accurately recognize and apply the correct templates during diagram generation. Here’s what to keep in mind:

  • Exact Match Requirement: Name all templates precisely as they appear in QualiWare, with correct capitalization and spacing. For example, use “WorkFlowDiagram,” not “workflow diagram” or “Work Flow Diagram.”
  • Consistency Is Key: Uniform naming across all sections of KnowledgeScope ensures that the AI correctly interprets and utilizes the templates.
  • Verification: Double-check template names for typos or discrepancies before finalizing the KnowledgeScope configuration.

Accurate template naming enables the AI to understand and execute your instructions effectively, ensuring the generated diagrams meet your exact specifications.


The final section defines the desired outcome from the AI’s generation process.

  • Response Type: Specifies the format of the AI’s output, e.g., “Diagram with objects.”
  • Response Diagram Type: Indicates the template to be used for the response diagram, e.g., “WorkFlowDiagram,” with strict adherence to QualiWare naming conventions.
  • Response Symbols & Connection Types: Defines the elements to be used within the generated diagram.
  • Response Diagram Layout: Determines the presentation style of the generated diagram.
  • Response Template Descriptions: Provides a detailed description of the diagram and its components, with more emphasis on lesser-known templates.
  • Response Ontology: An ontology that guides the appearance and structure of the response diagram.

Utilization Guide

This template is structured for ease of use, guiding users through a step-by-step configuration for the Generative QualiAI. For precise diagram generation, it is recommended to provide detailed and accurate information in each section, aligning closely with your business’s operational context and requirements.

Association : ArchiMate

Represents an unspecified relationship, or one that is not represented by another ArchiMate relationship.

An association relationship is always allowed between two elements, or between a relationship and an element.

Value Stream Viewpoint : Archimate

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.



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.


Container serves as an essential structure, encapsulating and categorizing various elements. Think of it as a grouping tool, collecting related entities to bring clarity and structure to the broader design landscape.

Function: The Container operates much like a folder or bin, collecting and segmenting different elements, thus simplifying the overall structure and making it more navigable.


  • Organizational Clarity: By bundling related entities, it aids in understanding and visualizing relationships within the enterprise.
  • Efficient Navigation: With elements neatly grouped, users can swiftly pinpoint and access what they need.
  • Enhanced Management: Grouping similar elements under the Container umbrella streamlines management tasks.

In a nutshell, the Container is the backbone of organization in EDGY modeling, ensuring elements are systematically categorized, easy to access, and managed efficiently.