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.

Application Behavior Viewpoint:ArchiMate

Purpose: The Application Behavior Viewpoint in ArchiMate aims to model the behavior and interactions of applications within an enterprise, providing a high-level view of how applications support business processes and goals. This helps to identify opportunities for optimizing application behavior, improving performance, and reducing costs.

Core Concerns: The core concerns of the Application Behavior Viewpoint include modeling the behavior of applications, the services they provide, and the interactions between applications and other components within the enterprise architecture. By focusing on these core concerns, the Application Behavior Viewpoint can help identify bottlenecks and areas for improvement and provide a clear understanding of how applications contribute to the overall functioning of the enterprise.

Example:

The Application Behavior Viewpoint includes several concepts for modeling different aspects of application behavior, including:

  • Application Component: An application component represents a unit of functionality provided by an application. Application components can be modeled to show the services they provide and the interfaces through which they interact with other components.
  • Application Service: An application service is a unit of functionality provided by an application component. Application services can be modeled to show the behavior and capabilities of an application component.
  • Application Interface: An application interface represents a point of interaction between application components, or between an application component and other components within the enterprise architecture. Application interfaces can be modeled to show the data and functionality exchanged between components.
  • Application Interaction: An application interaction represents the exchange of data and functionality between application components, or between an application component and other components within the enterprise architecture. Application interactions can be modeled to show the sequence and timing of events.

Overall, the Application Behavior Viewpoint is useful for modeling the behavior and interactions of applications within an enterprise, providing a high-level view of how applications support business processes and goals. By focusing on the core concerns of application behavior, the Application Behavior Viewpoint can help identify areas for improvement and optimization and provide a clear understanding of how applications contribute to the overall functioning of the enterprise architecture.

Actor Cooperation Viewpoint:ArchiMate

Purpose: The Actor Cooperation Viewpoint in ArchiMate aims to model how actors collaborate and work together to achieve business goals and objectives, and to capture the social and organizational aspects of an enterprise. This helps to provide a clear understanding of how different actors are connected and how they contribute to the overall goals of the organization.

Core Concerns: The core concerns of the Actor Cooperation Viewpoint include modeling the roles and responsibilities of actors, their collaboration and interaction, the information and functionality exchanged between them, and the interfaces through which they interact. By focusing on these core concerns, the Actor Cooperation Viewpoint can help identify opportunities for improving efficiency, reducing costs, and creating value for the organization. It can also facilitate communication and collaboration among stakeholders, providing a common understanding of the organization’s social and organizational aspects and their interdependencies.

 

Example:

The Actor Cooperation Viewpoint is a perspective in the ArchiMate enterprise architecture modeling language that focuses on the relationships and interactions between actors (people, organizations, or systems) within an enterprise. This viewpoint is used to model how actors collaborate and work together to achieve business goals and objectives.

In the Actor Cooperation Viewpoint, actors are represented as rectangular shapes with labels that describe their roles and responsibilities. Relationships between actors are shown as lines connecting the actors, with labels that describe the nature of the interaction.

The Actor Cooperation Viewpoint includes several concepts for modeling different aspects of actor collaboration, including:

  1. Roles: A role is a specific set of responsibilities and behaviors assigned to an actor. Roles can be modeled to show how different actors collaborate and contribute to business processes.
  2. Collaboration: Collaboration is the act of two or more actors working together to achieve a common goal. Collaboration can be modeled to show the actors involved, the goals they are working towards, and the interactions between them.
  3. Interaction: An interaction is a communication or exchange of information between two or more actors. Interactions can be modeled to show the flow of information and the roles and responsibilities of each actor involved.
  4. Interfaces: An interface is a point of interaction between two actors, such as a user interface between a person and a system, or a service interface between two systems. Interfaces can be modeled to show the information or functionality exchanged between actors.

Overall, the Actor Cooperation Viewpoint is useful for modeling the social and organizational aspects of an enterprise, and for understanding how different actors collaborate and work together to achieve business objectives.

Technology Interaction : ArchiMate

A unit of collective technology behavior performed by (a collaboration of) two or more technology internal active structure elements.

A technology interaction describes the collective behavior that is performed by two or more technology internal active structure elements, possibly by their participation in a technology collaboration. This may, for example, include the communication pattern between these elements. A technology interaction can also specify the joint behavior needed to realize a technology service.

The name of a technology interaction should clearly identify a series of technology behaviors; e.g., “Client profile creation” or “Update customer records”.

Product : ArchiMate

A coherent collection of services and/or passive structure elements, accompanied by a contract, which is offered as a whole to (internal or external) customers.

This covers both intangible, services-based, or information products that are common in information-intensive organizations, as well as tangible, physical products. “Buying” a product gives the customer the right to use the associated services.

The name of a product is usually the name which is used in the communication with customers, or possibly a more generic noun (e.g., “travel insurance”).

Meaning : ArchiMate

The knowledge or expertise present in, or the interpretation given to, a concept in a particular context. A meaning represents the interpretation of a concept of the architecture. In particular, this is used to describe the meaning of passive structure elements (for example, a document or message).

A meaning can be associated with any concept.

The name of a meaning should be a noun or noun phrase.

Material : ArchiMate

Tangible physical matter or energy. Material is typically used to model raw materials and physical products, and also energy sources such as fuel and electricity. Material can be accessed by technology behavior elements to model how it is created, used, moved, transformed, or otherwise manipulated. Equipment may be assigned to material, to model where the material is stored. The name of material should be a noun.

Location : ArchiMate

A location is a place or position where structure elements can be located, or behavior can be performed.

The location element is used to model the places where (active and passive) structure elements, such as business actors, application components, and devices, are located. This is modeled by means of an aggregation relationship from a location to structure element. A location can also aggregate a behavior element, to indicate where the behavior is performed.

Junction : ArchiMate

Used in a number of situations to connect relationships of the same type. A junction is not an actual relationship in the same sense as the other relationships, but rather a relationship connector. A junction may have multiple incoming relationships and one outgoing relationship, one incoming relationship and multiple outgoing relationships, or multiple incoming and outgoing relationships (the latter can be considered a shorthand of two contiguous junctions). An “and” junction is used to explicitly express that all elements together must participate in the relationship. An “or” junction is used to express that at least one of the elements participates in the relationship. The “or” junction can be used to express both inclusive and exclusive or conditions, which could be indicated by a modeler by naming the junction to reflect its type.

Influence : ArchiMate

Represents that an element affects the implementation or achievement of some motivation element. This represents an impact dependency, denoted by a dashed line. This is used to model how motivation elements are influenced by other elements.