Referentiecomponent: verschil tussen versies
k (Tekst vervangen - "{{Elementtyperelatie " door "{{#elementtyperelation: ") |
Geen bewerkingssamenvatting |
||
| Regel 14: | Regel 14: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Bestaat uit | |Elementrelatie=Bestaat uit | ||
| Regel 19: | Regel 21: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Realiseert | |Elementrelatie=Realiseert | ||
| Regel 24: | Regel 28: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Is toegewezen aan | |Elementrelatie=Is toegewezen aan | ||
| Regel 29: | Regel 35: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Is gerelateerd aan | |Elementrelatie=Is gerelateerd aan | ||
| Regel 34: | Regel 42: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Wordt gebruikt door | |Elementrelatie=Wordt gebruikt door | ||
| Regel 39: | Regel 49: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Realiseert relevante standaard | |Elementrelatie=Realiseert relevante standaard | ||
| Regel 44: | Regel 56: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Realiseert verplichte standaard | |Elementrelatie=Realiseert verplichte standaard | ||
| Regel 49: | Regel 63: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Realiseert buitengemeentelijk koppelvlak | |Elementrelatie=Realiseert buitengemeentelijk koppelvlak | ||
| Regel 54: | Regel 70: | ||
}} | }} | ||
{{#elementtyperelation: | {{#elementtyperelation: | ||
|Kennismodel=Kennismodel GEMMA 2.0 | |Kennismodel=Kennismodel GEMMA 2.0 | ||
|Elementrelatie=Groepeert | |Elementrelatie=Groepeert | ||
| Regel 62: | Regel 80: | ||
An application component is a self-contained unit of functionality. As such, it is independently deployable, re-usable, and replaceable. An application component performs one or more application functions. It encapsulates its contents: its functionality is only accessible through a set of application interfaces. Co-operating application components are connected via application collaborations. | An application component is a self-contained unit of functionality. As such, it is independently deployable, re-usable, and replaceable. An application component performs one or more application functions. It encapsulates its contents: its functionality is only accessible through a set of application interfaces. Co-operating application components are connected via application collaborations. | ||
An application component may be assigned to one or more application functions, business processes, or business functions. An application component has (is composed of) one or more application interfaces, which exposes its functionality. Application interfaces of other application components may be used by an application component. The name of an application component should preferably be a noun.<!-- Page revision date: | An application component may be assigned to one or more application functions, business processes, or business functions. An application component has (is composed of) one or more application interfaces, which exposes its functionality. Application interfaces of other application components may be used by an application component. The name of an application component should preferably be a noun. | ||
<!-- Page revision date: 1523984513 --> | |||
Versie van 18 apr 2018 02:01
Definitie
:
Een modulair, zelfstandig inzetbaar en vervangbaar deel van een systeem, dat zijn functionaliteit aanbiedt via goed gedefinieerde interfaces. Applicatiecomponenten stellen functionaliteit beschikbaar, die gebruikt wordt om de applicatiediensten mee te leveren. Een voorbeeld van een referentiecomponent is een gegevensmagazijn.
Toelichting op formulier
:
Overige categorieën
:
Bron
:
KING
Verwijzing
:
Eigenschap voor begrippenlijst
:
Automatische paginanamen
:
Toegestane eigenschappen
Eigenschappen
:
Beschrijving, Toelichting, Versie, ARISID, ImportID, ARISMap, ARISImportDatum, View, ImportJobID, Semantictitle, ImportParent, Occurs in models, GEMMA positie, Eigenaar, Beleidsthema, ImportSymbolGUIDLabel, GUID Realiseert verplichte standaard, GUID Realiseert relevante standaard, GUID Realiseert buitengemeentelijk koppelvlak
Toegestane relaties
An application component is defined as a modular, deployable, and replaceable part of a system that encapsulates its contents and exposes its functionality through a set of interfaces.
An application component is a self-contained unit of functionality. As such, it is independently deployable, re-usable, and replaceable. An application component performs one or more application functions. It encapsulates its contents: its functionality is only accessible through a set of application interfaces. Co-operating application components are connected via application collaborations.
An application component may be assigned to one or more application functions, business processes, or business functions. An application component has (is composed of) one or more application interfaces, which exposes its functionality. Application interfaces of other application components may be used by an application component. The name of an application component should preferably be a noun.
Deze pagina is het laatst bewerkt op 18 apr 2018 om 02:01.