Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Open-Measured-Data-Management-WG/Glossary"
(→System) |
(→System) |
||
Line 5: | Line 5: | ||
=== System === | === System === | ||
− | A system describes a productive openMDM environment. This environment includes | + | A system describes a productive openMDM(R) environment. This environment includes everything that is required to operate an openMDM instance including configuration and resources. A system consists of various deployment units and (possible external) services, for instance |
− | * openMDM(R) rich | + | * openMDM(R) applications to be rolled out on user devices |
− | * | + | ** rich clients |
− | * connected commercial | + | ** apps |
− | * ASAM ODS | + | * connected commercial applications |
− | * | + | * services |
− | **instance of the openMDM(R) business layer | + | ** ASAM ODS service running an instance of an openMDM(R) application model |
− | **openMDM(R) | + | ** openMDM(R) server, for instance running an |
− | **openMDM(R) processing | + | ** instance of the openMDM(R) business layer |
+ | ** openMDM(R) web service | ||
+ | ** openMDM(R) import service | ||
+ | ** openMDM(R) processing service | ||
+ | ** storage services | ||
+ | ** database services | ||
=== Application === | === Application === |
Revision as of 10:36, 10 December 2014
This glossary contains a list of terms commonly used to describe topics related to openMDM.
Contents
openMDM Specific Terms
This section describes terms specific to openMDM.
System
A system describes a productive openMDM(R) environment. This environment includes everything that is required to operate an openMDM instance including configuration and resources. A system consists of various deployment units and (possible external) services, for instance
- openMDM(R) applications to be rolled out on user devices
- rich clients
- apps
- connected commercial applications
- services
- ASAM ODS service running an instance of an openMDM(R) application model
- openMDM(R) server, for instance running an
- instance of the openMDM(R) business layer
- openMDM(R) web service
- openMDM(R) import service
- openMDM(R) processing service
- storage services
- database services
Application
An application is a part of a system which serves a particular purpose.
Component
A component implements certain functionality. Components can be used in multiple applications.
For every component it has to be determinable,
- if it complies to the openMDM(R) architecture definition
- if it complies to the openMDM(R) branding
- if it complies to the openMDM(R) quality kit
For every component must be documented and retrievable
- which requirements are met by the component (functionality definition, see above)
- which interfaces does the component implement
- which services does the component depend on
- which services does the component provide
- which further restrictions exist (instantiate)
Additional Terms
This section describes terms which originate from an openMDM related domain and have a special interpretation in the context of openMDM.
Product Owner
The exact role of a product owner in the context of openMDM is not yet defined.