Repository navigation
First Client Meeting
Meeting Date: 26.04.17 Author: Inbal Zukerman
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
As we all remember from the agile development manifesto, changes in the requirements are welcome. Our project's goals have been modifies, and now we are working on infrastructure of a smarthouse, therefore changes are expected.
In the same manner the logging in Java works, we would like our system to be able to mimic the data flow and dispatching process and therefore, some changes in the current networking and messages-sending process between the sensors, the application and our system should be done.
The main idea which was presented and discussed was re-defining the structure of a message which is to be sent from the sensors to system and from our system will be dispatched to the different applications. The suggested structure is based on the tree-hierarchy.
A very basic example of a message to demonstrate this idea is: sensor.external.billing.electricity.reading.read.12. Each part of the message is adding another layer of information and description. In this structure, an application can use pattern matching to find all relevant information relatively easily.
The main goal of this feature is to create an (even) better communication protocol.
Overview
Quick Start
Smarthouse Usage for Owners
Development Manuals
Continuous Development
Misc.