Skip to main content
Jump to: navigation, search

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

Line 24: Line 24:
 
The latest source of the architecture specification draft is available in the MDM@WEB [http://git.eclipse.org/c/mdmweb/org.eclipse.mdmweb.architecture.git architecture git repository] along with a proof of concept implementation.
 
The latest source of the architecture specification draft is available in the MDM@WEB [http://git.eclipse.org/c/mdmweb/org.eclipse.mdmweb.architecture.git architecture git repository] along with a proof of concept implementation.
  
The latest compiled version is available [[:File:Architecture-specification.zip|here]].
+
The latest compiled version is available [[Media:Architecture-specification.zip|here]].
  
 
== Technology Proposal Template ==
 
== Technology Proposal Template ==

Revision as of 13:52, 5 October 2015

Members

Speaker of the Architecture Committee: Andreas Benzing

Organization

The architecture committee has a regular conference call every three weeks. The minutes are public, but participation is limited to members of the WG and invited guests. Feel free to contact the speaker of the committee to request the discussion of architecture related topics.

Next Conference Call

The next regular call will be held on Oct 09, 2015, 11:00 CEST.

Topics:

  • Discuss requirements/template for technology proposals
  • Discuss technology proposal by Gigatronik

Documents

Architecture Specification

The latest source of the architecture specification draft is available in the MDM@WEB architecture git repository along with a proof of concept implementation.

The latest compiled version is available here.

Technology Proposal Template

Each technology proposal handed to the AC for review should contain at least the following information:

  • Proposal: The description of the proposed technology itself
  • Priotity: The priority should be specified in the according Jira ticket to allow the AC to sort upcoming decisions.
  • Lock-In/Long-Term Availability: The proposal should must a description of long-term availability of the technology including possible vendor lock-in scenarios and community changes.
  • Operations: The impact on operations must be evaluated. The information gathered from the openMDM members should be taken into account, especially the enterprise environments.
  • Driving Requiremens: The driving requirements for the proposal must be stated. If the requirements are related to the openMDM architecture, they must be illustrated using a corresponding diagram. For other requirements, an explicit description of the relation to openMDM is required.
  • Possible Alternatives: Suitable alternatives to the proposed technology must be named. An evaluation matrix of all alternatives must be provided. If no alternatives are available, the reasons for the lack of alternatives must be described, referencing previous decisions where applicable.

Presentations

Meeting Minutes

Back to the top