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.
IoT/M2MIWG/M2M meta-model
< IoT
Revision as of 11:59, 20 February 2012 by Unnamed Poltroon (Talk) (New page: {{:DocumentationGuidelines/DraftHeader}} = Functional requirements = * The M2M application meta-model MUST allow the description of the different parts an M2M application is made of. **...)
Contents
Functional requirements
- The M2M application meta-model MUST allow the description of the different parts an M2M application is made of.
- It MUST allow the description of the data that can be exchanged between a device and a server.
- It MUST allow to declare the components that an application provides.
- It MUST allow to declare the components that an application requires.
- It SHOULD allow to indicate the binary files the application is made of.
- The M2M application meta-model
Device Management
- The M2M application meta-model MUST allow the description of the Device Management operations supported by a given system.
Data
- The M2M application meta-model SHOULD allow to structure data elements hierarchically.
- The M2M application meta-model MUST allow to associate a type to data elements.
- The M2M application meta-model MUST support the following primitive types: string, integer, double, date, boolean, byte array.
- The M2M application meta-model SHOULD allow to define constraints for the data, such as: range, max length, ...
- The M2M application meta-model SHOULD allow to indicate the protocol to use when exchanging a given data element
Binary packages
Non-functional requirements
- It SHOULD be possible to split an M2M model instance into several pieces to ease maintenance, re-use...