Bedrijfsgebeurtenis: verschil tussen versies
k (Installed/upgraded by SmartCore) |
(SmartCore migration to v3.0.0) |
||
| Regel 1: | Regel 1: | ||
{{#Elementtype: | {{#Elementtype: | ||
|ElementtypeAutoPaginaNaam=Nee | |||
|Paginanaam=Bedrijfsgebeurtenis | |Paginanaam=Bedrijfsgebeurtenis | ||
|Kennismodel=Kennismodel ArchiMate 2.0 kern | |Kennismodel=Kennismodel ArchiMate 2.0 kern | ||
| Regel 63: | Regel 64: | ||
|Eindpunten=Belanghebbende, Drijfveer, Analyse, Doel, Eis, Principe, Beperking, Werkpakket, Resultaat, Plateau, Verschil, | |Eindpunten=Belanghebbende, Drijfveer, Analyse, Doel, Eis, Principe, Beperking, Werkpakket, Resultaat, Plateau, Verschil, | ||
}} | }} | ||
{{#elementtypefooter:}} | |||
Huidige versie van 8 okt 2020 om 22:14
Toegestane eigenschappen
Toegestane relaties
Uit ArchiMate:"Business processes and other business behavior may be triggered or interrupted by a business event. Also, business processes may raise events that trigger other business processes, functions, or interactions. A business event is most commonly used to model something that triggers behavior, but other types of events are also conceivable; e.g., an event that interrupts a process. Unlike business processes, functions, and interactions, a business event is instantaneous: it does not have duration. Events may originate from the environment of the organization (e.g., from a customer), but also internal events may occur generated by, for example, other processes within the organization.
A business event may trigger or be triggered (raised) by a business process, business function, or business interaction. A business event may access a business object and may be composed of other business events. The name of a business event should preferably be a verb in the perfect tense; e.g., 'claim received'."