Bedrijfsproces: verschil tussen versies
k (Tekst vervangen - "{{Elementtype-eigenschappen " door "{{#elementtypeproperties: ") |
Geen bewerkingssamenvatting |
||
| Regel 15: | Regel 15: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Bestaat uit | |Elementrelatie=Bestaat uit | ||
| Regel 20: | Regel 22: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Realiseert | |Elementrelatie=Realiseert | ||
| Regel 25: | Regel 29: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Leidt tot | |Elementrelatie=Leidt tot | ||
| Regel 30: | Regel 36: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Groepeert | |Elementrelatie=Groepeert | ||
| Regel 35: | Regel 43: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Is gerelateerd aan | |Elementrelatie=Is gerelateerd aan | ||
| Regel 40: | Regel 50: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Gebruikt | |Elementrelatie=Gebruikt | ||
| Regel 45: | Regel 57: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Wordt gebruikt door | |Elementrelatie=Wordt gebruikt door | ||
| Regel 55: | Regel 69: | ||
There is a potential many-to-many relation between business processes and business functions. Informally speaking, processes describe some kind of “flow” of activities, whereas functions group activities according to required skills, knowledge, resources, etc. | There is a potential many-to-many relation between business processes and business functions. Informally speaking, processes describe some kind of “flow” of activities, whereas functions group activities according to required skills, knowledge, resources, etc. | ||
A business process may be triggered by, or trigger, any other business behavior element (e.g., business event, business process, business function, or business interaction). A business process may access business objects. A business process may realize one or more business services and may use (internal) business services or application services. A business role or an application component may be assigned to a business process to perform this process manually or automated, respectively. The name of a business process should preferably be a verb in the simple present tense; e.g., “handle claim”.<!-- Page revision date: | A business process may be triggered by, or trigger, any other business behavior element (e.g., business event, business process, business function, or business interaction). A business process may access business objects. A business process may realize one or more business services and may use (internal) business services or application services. A business role or an application component may be assigned to a business process to perform this process manually or automated, respectively. The name of a business process should preferably be a verb in the simple present tense; e.g., “handle claim”. | ||
<!-- Page revision date: 1523984512 --> | |||
Versie van 18 apr 2018 02:01
Toegestane eigenschappen
Toegestane relaties
A business process describes the internal behavior performed by a business role that is required to produce a set of products and services. For a consumer the products and services are relevant and the required behavior is merely a black box, hence the designation “internal”.
In comparison to a business interaction, in which more than two business roles are (interactively) involved, only one business role is involved with a business process. However, a (complex) business process may consist of sub-processes assigned to different business roles.
There is a potential many-to-many relation between business processes and business functions. Informally speaking, processes describe some kind of “flow” of activities, whereas functions group activities according to required skills, knowledge, resources, etc.
A business process may be triggered by, or trigger, any other business behavior element (e.g., business event, business process, business function, or business interaction). A business process may access business objects. A business process may realize one or more business services and may use (internal) business services or application services. A business role or an application component may be assigned to a business process to perform this process manually or automated, respectively. The name of a business process should preferably be a verb in the simple present tense; e.g., “handle claim”.