Templates and model types in the QualiWare platform.
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:
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.
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”.
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.
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.
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”
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.
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.
The Context section is the backbone of the template, influencing the AI’s understanding and generation process.
This section allows users to input additional knowledge characteristics and set the randomness level of AI responses.
These instructions shape the AI’s output, ensuring it meets your defined criteria and maintains consistency with your organization’s practices.
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:
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.
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.
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.
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.
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.
Applications:
In a nutshell, the Container is the backbone of organization in EDGY modeling, ensuring elements are systematically categorized, easy to access, and managed efficiently.