The Open Group OGA-031 Exam Actual Questions

According to the ArchiMate 3.2 Specification1, a driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them. Drivers that are associated with a stakeholder are often called ''concerns'' of that stakeholder. A stakeholder represents the role of an individual, team, or organization (or classes thereof) that represents their interests in the outcome of the architecture. A motivation element is an element that represents the reasons for designing and implementing an architecture, such as stakeholders, drivers, goals, principles, requirements, or value. A motivation element is denoted by a hexagonal shape.

The diagram below shows a motivation element (driver) named Market Share that influences a stakeholder named CMO. The influence relationship is denoted by a dashed line with an open arrowhead.

The influence relationship means that the driver affects the stakeholder's interests or concerns. Therefore, the best interpretation of the diagram is that the CMO is motivated by the driver Market Share.

According to the ArchiMate 3.2 Specification1, a business event is a behavior element that denotes an organizational state change. It may originate from and be resolved inside or outside the organization. A business event accesses a passive structure element that represents an entity relevant from a business perspective, such as a business object, a contract, or a product. A business passive structure element is denoted by a rectangular shape with square corners. The access relationship is denoted by a line with an open arrowhead.

The diagram below shows a business event named Order Received that accesses a business passive structure element named Order. The access relationship indicates that the event reads or writes the order.

According to the ArchiMate 3.2 Specification1, the ArchiMate core language defines a structure of generic elements and their relationships, which can be specialized in different layers. Three layers are defined within the ArchiMate core language as follows:

The Business Layer depicts business services offered to customers, which are realized in the organization by business processes performed by business actors and roles.

The Application Layer depicts application services that support the business, and the applications that realize them.

The Technology Layer comprises both information and operational technology. You can model, for example, processing, storage, and communication technology in support of the application world and Business Layers, and model operational or physical technology with facilities, physical equipment, materials, and distribution networks.

According to the ISO/IEC 42010 standard1, an architecture viewpoint is a specification of the conventions for constructing and using a view. A view is a representation of a whole system from the perspective of a related set of concerns. An architecture view on an Enterprise Architecture is a representation of a part or whole of an Enterprise Architecture from the perspective of one or more stakeholders and their concerns.

The ArchiMate language provides a flexible approach in which architects and other stakeholders can use their own views on the Enterprise Architecture. In this approach, architecture views are specified by architecture viewpoints.Architecture viewpoints define abstractions on the set of models representing the Enterprise Architecture, each aimed at a particular type of stakeholder and addressing a particular set of concerns2.

According to the ArchiMate 3.2 Specification1, a capability is an ability that an active structure element, such as an organization, person, or system, possesses. A requirement is a statement of need that must be realized by a system. Capabilities and requirements are both motivation elements that represent the reasons for designing and implementing an architecture.

The ArchiMate language defines two relationships that are permitted between capabilities and requirements:

Assigned to: This relationship links a requirement to a core element (such as a business actor, a business service, a business process, an application service, an application component, etc.) that is responsible for realizing it. The core element may be assigned to a capability that enables it to realize the requirement.

Realizes: This relationship links a capability to a requirement that is fully or partially realized by that capability.