This was created to establish a common, semantic, and syntactical visual modeling language for the architecture, design, and implementation of complex software systems both structurally and behaviorally (Lucid Software Inc., n.d.).

A trigger that starts, modifies, or completes a process. These types include message, timer, error, compensation, Signal, cancel, escalation, link, etc. This can be classified as either "throwing" or "catching," depending on their function.

Event

A particular task performed by a person or system. It can include sub-processes, loops, multiple loops, and compensations.

Activity

A decision point that can adjust the path based on conditions or events. This can be exclusive or inclusive, parallel, complex, or based on data or event.

Gateway

This shows the order of activities to be performed.

Sequence flow

This depicts messages that flow across pools, or organizational boundaries such as departments. It should not connect events or activities within a pool.

Message flow

This associates an artifact or text to an event, activity, or a gateway.

Association

It represents major participants in a process.

Pool

It is a sub-part of a pool. It shows the activities and flow for a certain role or participant, defining the accountability within the processes.

Lane

This shows the necessary data for an activity.

Data object

This shows a logical grouping of activities, but does not change the diagram's flow.

Group

This provides further explanation to a part of the diagram.

Annotation

This involves internal processes to a specific organization and do not cross pools or organizational boundaries.

Private BP

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

Abstract BP

This shows the interactions between two or more business entities.

Collaborative BP

Which statement is NOT TRUE about Unified Modeling Language

This is also known as Business Process Model and Notation.

This concept involves use case diagrams, which describes system functionality from the point of view of a user.

Functional

This concept describes the structure of a system in terms of objects, attributes, associations, and operations.

Object

This concept involves interaction diagrams, state machine diagrams, and activity diagrams, which are used to describe internal behavior of the system.

Dynamic

It describes the static structure of a system.

Class diagram

It is a subset of a class diagram used to organize elements of a system into related groups

Package diagram

It describes the static structure of a system at a particular time, and can be used to test class diagrams for accuracy.

Object diagram

This describes the organization of physical software components, including source codes, run-time code, and executables.

Component diagram

This diagram shows the internal parts of a class.

Composite structure diagram

This depicts the physical resources in a system, including nodes, components, and connections.

Deployment diagram

This illustrates the dynamic nature of a system by modeling the flow of control from activity to activity.

Activity diagram

This describes the interactions among classes in terms of an exchange of messages over time

Communication diagram

This models the functionalities of a system using actors and use cases, and can be considered as a simplified version of a collaboration diagram introduced in UML 2.0

Use case diagram

This describes the dynamic behavior of a system in response to external stimuli.

State machine diagram

It models the interactions between objects in sequence.

Sequence diagram

It is a combination of an activity and a sequence diagram, which models a more complex interaction.

Interaction overview diagram

It is an interaction UML diagram that focuses on processes that take place during a specific period of time, wherein time is shown to increase from left to right.

Timing diagram

Which statement is NOT TRUE about Architecture Description Language (ADL)

The Object Management Group (OMG) oversees the definition and maintenance of the UML specifications, which provides engineers and programmers the ability to use one language for different purposes during all phases of the software lifecycle, for all system sizes (Lucid Software Inc., n.d.).

Which is NOT an Artifact

Pool

Which is NOT a Structural UML Diagram?

Sequence diagram

Which is NOT a Behavioural UML Diagram

Component diagram

It is the role of an individual, team, department, or organization that represents their interest in the outcome of the architecture.

Stakeholder

It is an external or internal condition that motivates an organization to define its goals and implement the necessary change to achieve them

Driver

It is the result of an analysis of a particular business issue within the enterprise with respect to some drivers.

Assessment

It is a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.

Goal

It is a specific statement of need that architectural designers must meet.

Requirement

It is a factor that averts or hinders the realization of goals.

Constraint

It is strongly related to the organization’s goals and requirements. It is considered a qualitative statement of intent that should be met by the architecture.

Principle

It is a result that has been achieved.

Outcome

It is the relative worth, usefulness, or importance of a core element or an outcome.

Value

It is the knowledge or expertise present in a business object or its representation, given a particular context

Meaning

Which statement is NOT TRUE about Motivation Concepts

This represents what an enterprise has decided to do to realize its goals.

This business entity is capable of performing behavior.

Business Actor

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

Business Role

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

Business Collaboration

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

Business Interface

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.

Business Object

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

Representation

It is an encapsulation of an application’s functionality that is aligned to the implementation structure, which is modular and replaceable.

Application Component

It is an aggregate of two (2) or more application components working together to perform collective application behavior.

Application Collaboration

It is a point of access where an application service is made available to users to another application component or a node.

Application Interface

It is a data that is structured for automated processing.

Data Object

It is a computational or a physical resource that hosts, manipulates, or interacts with other computational or physical resources.

Node

It is an aggregate of two (2) or more nodes that work together to perform collective behavior

Technology Collaboration

It is a point of access where technological services offered by a node can be accessed.

Technology Interface

It is a physical information technology resource wherein system software and artifacts can be deployed for execution.

Device

It is a software that supports a business environment in storing, executing, and utilizing applications, including the data deployed within the environment.

System Software

It is a link between two (2) or more nodes through which the exchange of data or material happens.

Path

It is a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data or information.

Communication Network

It is a piece of data that is used and/or produced in a software development process or a system deployment and operation.

Artefact

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

Equipment

It is a physical structure or environment interconnected by distribution networks.

Facility

It is a physical network used to transport materials, data, or information.

Distribution Network

It is a tangible matter or physical element that can be accessed by equipment.

Material