It is an internationally accepted IT control framework that provides organizations with a set of “good practices” that helps in implementing an IT governance structure throughout an organization.

This is the most widely accepted set of best practices in the IT service delivery domain, which is composed of series of documents giving guidance on the provision of good IT services, including the facilities that need IT support, in a process-oriented approach.

It provides a standard repository of MDA model and defines structures that help multiple groups work with a model while having a standard view.

This provides the “way of working” for architects. It is considered as the core of TOGAF, which consists of the stepwise cycle approach for the overall enterprise development and centers requirements management.

This addresses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture within an enterprise.

– This is a blueprint of an enterprise that provides a common organizational understanding and is used to align strategic objectives and tactical demands (Lankhorst, 2017). This also provides a business-oriented abstraction of the enterprise in an ecosystem which translates strategies into actions

This includes the business requirements and business model or domain model that describes the state of the enterprise where the system will be integrated. This abstracts the automated data processing system.

This shows the interactions between two or more business entities.

It is a physical machine, tool, or instrument that can create, use, store, move, or transform materials

This occurs between a private BP and an external participant or process. This does not show the private BP itself.

This business entity is capable of performing behavior.

It is the responsibility for performing specific behavior, to which an actor can be assigned.

It is an aggregate of two (2) or more active internal business structure elements that work together to perform collective behavior

It is a point of access where a business service is made available to the environment.

It is a perceptible form of the information carried by a business object.

It is used to model an object type in which several instances may exist within an organization. It represents important information or conceptual elements within a particular business domain.

It is a precisely defined outcome of a work package

Refine an element in a model. Other than introducing new elements, refining can be done by adding specific details to existing elements.

People have the tendency to perceive incomplete objects as complete and asymmetric objects as symmetric. Symmetry and regularity increase the readability of models and reduces perceived complexity

This action involves the administration and documentation of all or some modeling actions, such as refinement and abstraction.

This involves an explicit decision of eliminating or delete a concept or relation with proper documentation, to avoid the concept of "lingering around."

This activity uses the model representation to communicate with the stakeholders and evaluate whether the model and the visualization achieved the intended outcome

the time between issuing a request and receiving the result

This is typically used at the start of a design trajectory, where not everything needs to be detailed. This viewpoint avoids the impression that the architectural design is already final

This shows the structure of the internal organization of an enterprise. This is commonly used to identify authority, competencies, and responsibilities within an organization. It can be represented by a nested block diagram

This focuses on the relationships of actors within an environment. It is useful in determining external dependencies and collaborations.

This shows the main business functions of an organization and their relationships in terms of the flow of information, value, or goods. It also provides high-level insight into the general operations of the company, which can be used to identify necessary competencies or structure an organization according to its main activities.

This depicts the value of products to the customers or other external parties involved. It actually shows the composition of one or more products in terms of the constituting services, the associated contracts and/or other agreements. It may also be used to show the channels or interfaces through which a product is offered.

This is used to show that business services are realized by the underlying business processes in an organization. This bridges the product viewpoint and the business process viewpoint.

This is used to show the detailed relationship of one (1) or more business processes with each other and/or their surroundings

This encompasses the higher-level structure and composition of one (1) or more business processes.

This shows the structure of the information used in the enterprise or a specific business process application in terms of data type or class structure

This is typically used to create an overview of the application landscape in a company. It also shows the relationships of applications in a company, including the dependencies in terms of information flow or the services a company offers.

This describes how applications are used to support one (1) or more business processes. This can be used in designing an application by identifying the services needed by the business processes and other applications.

This describes the internal behavior of an application or a component. This can be used in identifying overlaps between different applications.

This comprises the hardware and software infrastructure wherein the application layer depends. This contains the physical devices, networks, and supporting system software such as the operating system, databases, and middleware.

This shows how the software and hardware infrastructure support applications. This plays an important role in the performance analysis and scalability of the technological aspect of the enterprise.

This shows the structure of one (1) or more applications or components, including the associated data.

This shows how one (1) or more applications are deployed on the technical infrastructure. This includes the logical mapping of application and components onto the technological layer of the enterprise architecture.

This contains equipment such as the physical machine, tools, and/or instruments that can create, use, store, move, or transform materials. Interconnectivity within and between facilities are also specified.

This focuses on the performance engineering evaluation of software applications.

It is the presentation or notation of views. This can take many forms such as standard diagrams, tables, cartoons, and dynamic visualizations.

This defines abstractions on a set of models representing the enterprise architecture, each aimed at a particular type of stakeholder and addressing a particular set of concerns. This can be used to isolate certain aspects of a model, and relating two (2) or more aspects in a model. It is typically used for communicative activities such as designing, analysis, obtaining commitment, and formal decision making, among others. It is the specification of the conventions for constructing and using views.

the transformation effort will most likely fail with severe consequences

significant failure of parts of the transformation effort resulting in certain goals not being achieved

noticeable failure of parts of the transformation effort threatening the success of certain goals

certain goals will not be wholly successful