Fundamental Principles

In order to have a coherent criteria to make architectural and technological choices, it is necessary to indentify a set of fundamental principles.
These principles shall guarantee that the platform will keep the original characteristics and attributes over time and will consolidate a differentiating identity from other commercial systems in terms of effectiveness, efficiency, openness and ease of use.

Maximal innovation

Technological choices shall follow the maximal innovation principle, within the constraints of the practical accessibility. If more options are available, the most innovative shall be taken.

Comment: innovation is a winning characteristic in case of competition against legacy and incumbent solutions. Projects having innovative characteristics have more chances of success.
Accessibility and feasibility of an option will be evaluated even considering education, cooperation and partnerships

Open Source

The architecture and source code (HW platforms, common libraries, …) shall be available to the community in an Open Source manner. For this reason implementation shall use only components released with Open Source licenses or anyway compatible with such licenses.

Comment: It can be demonstrated that a good Open Source development process, coordinating orderly feedback and contributions from the community, delivers higher quality results with respect to proprietary processes. Such process has in general lower production costs with higher quality. The business model should consider the delivery of services as the main source of earning, rather than the transfer of a license of use.

Minimize new designs

This principle will favor the reuse of existing techniques, protocols and solutions before defining new proprietary solutions and design.

Comment: Following this principle will ensure more documentation and widely distributed knowledge base. The risk of following design choices with no real life, real users validation will be reduced.

Minimal HW variance

Architecture will follow the key principle of the hardware identity as much as possible. Deployed nodes will have the least variance as possible, with the exception of a Central Control node.
Identity will be limited to the central body of a node, which may interface different sets of peripherals.
For interfaces as well, variance shall be minimized and standardization must be maximized.

Comment: This principle will reduce design and production costs, allowing repeated production and economy of scale.
It will allow easier reconfiguration, reuse of nodes at lower costs.
It will also allow merging systems into one and split of one system into multiple systems at minimal cost.

Copy-left owner: Alberto Trentadue - 2016

"ClEnSensors" is Free Software Licensed GPLv3


Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License