Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Open-Measured-Data-Management-WG/Glossary"

(Component)
(Component)
Line 15: Line 15:
 
For every component it has to be determinable,
 
For every component it has to be determinable,
  
(/) if it complies to the openMDM(R) architecture definition
+
* if it complies to the openMDM(R) architecture definition
(/) if it complies to the openMDM(R) branding
+
* if it complies to the openMDM(R) branding
(/) if it complies to the openMDM(R) quality kit
+
* if it complies to the openMDM(R) quality kit
  
 
For every component must be documented and retrievable
 
For every component must be documented and retrievable
  
(/) which requirements are met by the component (functionality definition, see above)
+
* which requirements are met by the component (functionality definition, see above)
(/) which interfaces does the component implement
+
* which interfaces does the component implement
(/) which services does the component depend on
+
* which services does the component depend on
(/) which services does the component provide
+
* which services does the component provide
(/) which further restrictions exist (instantiate)
+
* which further restrictions exist (instantiate)
  
 
== Additional Terms ==
 
== Additional Terms ==

Revision as of 10:21, 10 December 2014

This glossary contains a list of terms commonly used to describe topics related to openMDM.

openMDM Specific Terms

This section describes terms specific to openMDM.

System

A system describes a productive openMDM environment. This environment includes, everything that is required to operate an openMDM instance.

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.

Back to the top