Week 3

in the meeting we:

• Discussed:
  • the Wiki pages yogi requested. Decided -
    • A. coding standard - will be wrriten by Yarden
    • B. testing - will be written by Roy
    • C. install me - will be written by Ron
  • who the applications will be notified on a failure to execute an instruction on the interactive sensor side. Decided it's the responsibility of the app to keep track of the sensors data report after the instruction was sent to verify successful execution.
  • the structure and behaviour of the house android application. Decide -
    • structure: registration page, login page. No additional GUI is required since the app will act upon an event sent from the house.
    • optional: adding emergency contacts from the app.
    • registration will require some sort of 2 ways verification, to allow matching between a house and its data on the cloud.
• Approved suggestions -
  • moving to services from the old API structure
  • re-organizing the project in a maven-logical manner (Ron)
  • moving to logging with log4j
  • deleting deprecated labels
  • server on cloud (Elia, depends on research results)
  • Yarden and Roy will decide which files should be excluded from the code-coverage calculations
• Declined suggestions -
  • Turning the SystemCore into a singleton
  • Separating the SystemCore GUI and functionality (overturned a day later in the stand-up meeting)