Template Type: Web-Modeler Enabled Diagram

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.

OrganizationMap:EDGY

Purpose: The purpose of the Organization Board is to set up team structures and group people together to realize the capabilities of the enterprise. It divides and organizes our work into roles and responsibilities.

Core concerns: An organization is a complex social structure. People form organizations to collaborate and co-create outcomes they cannot achieve alone without explicit agreements about membership, responsibilities and behavioral rules. Organizations are fractal: they are made up of nested structures (e.g. business unit-department-team) that have similar attributes on each level, such as purpose, goals, capabilities and hierarchy.

The Organization Board is a part of the EDGY language created by the Intersection Group.

MilkyWayEnterpriseMap:EDGY

Purpose: The purpose of the MilkyWayEnterpriseMap diagram is to map the different elements into one diagram, creating a view of the enterprise

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

 

From the center and outwards, the milkyway shows:

  • the identity elements (Purpose and Story)
  • the Organization
  • the architecture elements (Capability and Process)
  • the Product
  • the experience elements (Task and Journey)
  • the Brand

JourneyMap:EDGY

Purpose: The purpose the Journey Board is to promote an empathetic view of the people we are designing for/with and to share insight and data about people’s lives in a narrative scenario form that co-creators can relate to.

Core concerns: A brand is a symbolic representation of our enterprise and its products. It is designed to communicate our identity (especially how we are different from others) and to invoke a set of expectations in people about our enterprise and our products, particularly in relation to people’s own needs and desires.

The Activity Board is a part of the EDGY language created by the Intersection Group.

ContentMap:EDGY

Purpose: The purpose the Content Board is to capture key messages, media and formats used to convey identity, story and purpose to audiences, while setting a consistent ton of voice across formats, media and distribution channels to best engage people.

Core concerns: Content refers to data or information that is communicated between and towards people. It requires a medium to convey the underlying message to its audiences, such as audiovisual media like text, images or video, sound recordings or accessible alternatives. In an enterprise, various forms of content are being produced and maintained, exchanged and promoted.

The Content Board is a part of the EDGY language created by the Intersection Group.

ChannelMap:EDGY

Purpose: The purpose the Channel Board is to get an overview of where and how people interact with the enterprise or each other and make them connect.

Core concerns: Channels are the means of communication between people and the enterprise. They are where moments of interaction between people and the enterprise take place.

The Channel Board is a part of the EDGY language created by the Intersection Group.

CapabilityMap:EDGY

Purpose: The purpose the Capability Board is to Clarify what needs to be done and the assets your people need to do that, while focusing your resources on the right outputs to contribute towards achieving the intended outcomes.

Core concerns: Enterprises strive to achieve their purpose by creating products that feature in people’s experiences. To do so, they must design and realise their capabilities by orchestrating meaningful combinations of people and assets. Each capability produces well-defined outputs for internal or external business use and contributes directly or indirectly to product creation.

The Capability Board is a part of the EDGY language created by the Intersection Group.

BrandMap:EDGY

Purpose: The purpose the Brand Board is to structure, plan and create brand identities, their interrelations, dependencies and expressions (e.g. physical appearance, culture, values, promises).

Core concerns: A brand is a symbolic representation of our enterprise and its products. It is designed to communicate our identity (especially how we are different from others) and to invoke a set of expectations in people about our enterprise and our products, particularly in relation to people’s own needs and desires.

 

The Brand Board is a part of the EDGY language created by the Intersection Group.