Skip to content

Meeting minutes November 2013

kathleen-a edited this page Nov 30, 2013 · 3 revisions

28/11/2013

Attendees: AC, HN, BT, JS, KA

Hardware update:

  • Hardware list on GitHub (here)
  • Use cases on GitHub wiki (here)
  • Attempt at using HTTP PUT/HTTP POST and OGC IoT Sample Service on GitHub (doesn't work yet)

Software update:

  • Use cases on GitHub wiki (here)
  • Class diagram
  • Working on implementing something which updates periodically (e.g. reading different colours and displaying on screen)

Tech deliverables report:

  • Persons (mainly) responsible: JS, BT, HN
  • On Google docs (check your emails)
  • Schedule --> Gantt chart will be redone
  • Discuss design aspect, e.g. design choices

Tech deliverables presentation:

  • Persons (mainly) responsible: KA, AC
  • Marked on: presenting skills, timing, visual aids and content
  • Rough outline: what our project is about, requirements of our project, what IoT is, design process, hardware deliverables, scheduling, website demo

21/11/2013

Attendees: SL, AC, HN, BT, KA, JS

Update

  • Lit review is finished
  • Decided on RPi
  • Self-facing shelves, e.g. pharmacy, cosmetics...
  • People tracking - can use a Markov chain

Discussion (sort of disorganized so I hope you all can follow)

  • iBeacon - used at Macy's
  • can use a presence sensor (e.g. washrooms...)
  • Database access -- check out the OGC IoT GitHub
  • See IoT RESTful API Interactive SDK here
  • Putting sensors, e.g. (1) set up the sensor yourself or (2) sensor registers itself
  • Currently server restarts every 10 minutes (doesn't store data...)

Things we can do

  • More detailed design (architecture, 'boxes' with input and output)
  • For libraries, want class diagrams (modules, how they interact. Can use a UML diagram.)
  • Define use cases -- search "use case templates"
  • Examples of use cases... "buying goods" or "register sensor"
  • Define input/output! Then can write test code

More miscellaneous discussion

  • Website - use jQuery
  • Front end - Bootstrap
  • Go to Code School!
  • Check out D3
  • for Javascript, use Chrome as your development environment
  • identify risks early - know how much time you have, so that you can have some buffer time
  • have a Javascript library already - go check this out

For tech deliverables

  • Can create simulated data on the RPi, sending it to the server (e.g. once every minute, one of four sensors turns on) and rendered with website
  • Use jsfiddle to show off code

ACTION ITEMS

  • code school
  • get familiar with OGC, in particular how to get data onto DB
  • make list of needed hardware (sensors, e.g. presence sensor... preferably cheap stuff!)

Clone this wiki locally