Business Process Modeling Notation (BPMN) Quiz

Study Notes

BPMN was developed by the Business Process Management Initiative (BPMI).
BPMN provides a standard notation for business processes.
The goal of BPMN is to support business process modeling by providing a comprehensive standard notation to business users.
BPMN is intended to easily be used by stakeholders who design, manage and realize business processes.
BPMN uses a flowchart-like notation that is independent of any particular implementation environment.
BPMN creates a standard bridge between the business process design and process implementation.

Flow Objects
- Events: Triggers that start, modify, or complete a process.
- Activities: Tasks performed by a person or system.
- Gateways: Decision points that adjust the path based on conditions or events.
Connecting Objects
- Sequence flow: Shows the order of activities to be performed.
- Message flow: Depicts messages that flow across pools or organizational boundaries.
- Association: Associates artifacts or text to events, activities, or gateways.
Swimlanes
- Pool: Represents major participants in a process.
- Lane: A subpart of a pool that shows the activities and flow for a specific role or participant.
Artifacts
- Data object: Shows necessary data for an activity.
- Group: Shows a logical grouping of activities without changing the diagram's flow.
- Annotation: Provides additional explanation to a part of the diagram.

Private BP: Internal processes to a specific organization, do not cross pools or organizational boundaries.
Abstract BP: Occurs between a private BP and an external participant or process, does not show the private BP itself.
Collaborative BP: Shows interactions between two or more business entities.

UML is a visual modeling language used to architect, design, and implement complex software systems.
UML was created by combining the Booch method, Object-Modeling Technique (OMT), and Objectory.
UML is overseen by the Object Management Group (OMG).
UML provides engineers and programmers with a single language for different purposes during all phases of the software lifecycle.

Functional: Describes system functionality from the user's perspective.
Object: Describes the structure of a system using class diagrams.
Dynamic: Describes the internal behavior of the system using interaction diagrams, state machine diagrams, and activity diagrams.

Structural UML Diagrams
- Class diagram: Describes the static structure of a system.
- Package diagram: A subset of a class diagram, used to organize elements of a system into related groups.
- Object diagram: Describes the static structure of a system at a particular time.
- Component diagram: Describes the organization of physical software components.
- Composite structure diagram: Shows the internal parts of a class.
- Deployment diagram: Depicts the physical resources in a system.
Behavioral UML Diagrams
- Activity diagram: Illustrates the dynamic nature of a system by modeling the flow of control from activity to activity.
- Communication diagram: Describes the interactions between classes in terms of an exchange of messages over time.
- Use case diagram: Models the functionalities of a system using actors and use cases.
- State machine diagram: Describes the dynamic behavior of a system in response to external stimuli.
- Sequence diagram: Models interactions between objects in sequence.
- Interaction overview diagram: Combines an activity and a sequence diagram to model a more complex interaction.
- Timing diagram: An interaction UML diagram that focuses on processes during a specific period of time.

ADLs are formal languages used to model and reason about software architectures.
ADLs provide abstractions for modeling large systems.
ADLs are suitable for users with a technical background.
Examples of ADLs include UniCon, Wright, and Acme.