Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
(→openMDM Specific Terms) |
(→openMDM Toolkit) |
||
| Line 5: | Line 5: | ||
=== openMDM Toolkit === | === openMDM Toolkit === | ||
| + | |||
| + | The openMDM(R) Toolkit is the central work item of the openMDM(R) Eclipse working group. It consists in | ||
| + | |||
| + | * openMDM(R) components which can be combined and configured (without programming) within openMDM(R) applications to deliver an openMDM(R) system to the final users | ||
| + | * documentation of best practices ('''end user''' processes, '''end user''' use cases) | ||
=== System === | === System === | ||
Revision as of 10:49, 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.
openMDM Toolkit
The openMDM(R) Toolkit is the central work item of the openMDM(R) Eclipse working group. It consists in
- openMDM(R) components which can be combined and configured (without programming) within openMDM(R) applications to deliver an openMDM(R) system to the final users
- documentation of best practices (end user processes, end user use cases)
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 (multiple instances possible, possibly interdependent)
- ASAM ODS service running an instance of an openMDM(R) application model
- openMDM(R) business layer service
- 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.