Final answer:
In Business Process Model and Notation (BPMN), an end event can throw a message and can be a timer event, but it cannot catch a message, and typically, it cannot be shared among different pools.
Step-by-step explanation:
The question pertains to end events within Business Process Model and Notation (BPMN), which is a part of business process management in organizational development. When it comes to end events in a BPMN diagram:
- An end event cannot catch a message. Instead, it typically signifies the end of a process path and can have different types, such as message, error, or escalation events among others, but they are events that result in an action being done, rather than catching an action.
- An end event can throw a message. This means it can signify the sending of a message as a result of the process reaching its conclusion.
- An end event can be a timer event, signifying a specific point in time or duration that ends the process.
- An end event usually cannot be shared among pools, as each pool in a BPMN diagram is considered a separate process and has its own end event.
Therefore, based on the provided options, b. An end event can throw a message, and c. An end event can be a timer event, are true.