1. March 27, 2015

2. Meeting Agenda Framework Overview Prototype 1 Design Goals
Prototype 1 Demo
Prototype 2 Design Goals
Timeline Moving Forward
Questions & Answers
Speaker: Lauren

3. Framework Overview
Do we need this or should we go right into prototype 1? Would it make more sense to show this first?
Should be discussion formatted – maybe present our current design, start dialog about changing the design

4. Here, include the full burglar alarm graph
Talk about this representation of information flow
“And, when deploying this graph, we’ll actually deploy it as three graphs across three different devices”
Show the boundaries
There’s a hurricane
We have sensors monitoring conditions during the storm so we can get an idea of what is hit the hardest
People need water, food, and medicine
The city has shelters that people are going to for relief
How does the city use its food banks, hospitals, weather information, and relief trucks to distribute resources to those shelters?

7. Shaping the Network
Graph implementation should use the same concepts as graph design
Business logic should be decoupled from connection logic
This computational graph abstraction applies to any level of the system
New devices must be able to connect to the network at runtime
Bottom two points conflict – be sure to clarify what you mean here.

8. Quick Prototype 0 example: show the components in the Photo Collector device, the edge configuration for the application, and the resulting graph that the framework produces
Isn’t this the same as the previous photo? Don’t get the difference…

9. Components We support three types of components:
Behavior
Input channels
Output channels
We support three types of components:
Processors: an atomic unit of C# code
Subgraphs: a fully encapsulated graph, embedded as a node in a larger graph
Pools: a collection of same-type components, whose members can change at runtime
Note: Rough Diagram Sketch
Will likely have some more inputs and outputs coming in (imagine hospital and warehouse scaling diagram)
Mention:
"These are useful when, say, encapsulating a third-party sensor: when the component starts, use the proprietary sensor API to listen for events; when an event occurs, emit it on an output channel, perhaps after reformatting it in some way to be more useful to other components."

10. Processors A processor is a C# class.
For each input channel, it provides a callback function to the framework to receive incoming messages
For each output channel, it requests a callback function from the framework to send output messages
It provides start and stop methods, to manage any services it encapsulates
For example, consider the processor that encapsulates the connection with the Kinect.
On start, the processor uses the Kinect SDK to start a connection.
When it receives a photo request, the processor uses the Kinect’s Camera API to take a photo, and outputs the resulting photo.
On stop, the processor uses the Kinect SDK to stop the connection.

11. Subgraphs
So I’m still not entirely sure how to demonstrate this, but one option might be:
Show the photo collector device in its entirety
Show that the Kinect-Wunderbar-BusinessLogic section can be encapsulated as a subgraph that acts as a camera
Show the photo collector device with just this opaque camera component and its connection with the monitor

15. Pools

16. Use the CM as a pool example here plz

18. Feature Priority Dynamic Network Topology Framework Scalability
Data Aggregation from multiple sources
Historical Data Storage
Robust Connections
System Diagnostics
UX/UI
Should we include a definition of the feature being “complete?” This connects back to having a deliverable specs & reqs
Message passing and adapters – P0 features that have been completed (work into list permanently)

19. Prototype 1
Design Goals and Demo

20. Essentially a reminder graphic for the prototype
Essentially a reminder graphic for the prototype. Should give basic story (hospitals have supplies, request new supplies from warehouse, helicopter finds people and sends info to hospitals), then go to goals slide (next)

21. Goals Framework Scalability Establish Infrastructure to Aggregate Data
Interaction with Cloud Services to store and produce data
Establish Infrastructure to Aggregate Data
Multiple inputs and outputs, heterogeneous data
Dynamic Network Topology
Introduce new components without reconfiguring
Definitions:
Framework Scalability  Arbitrarily complex graph of cloud and ground based devices
The Cloud Service is Azure – store data in a cloud SQL server and produce data by spinning up component instances (or by random generation)
Multiple inputs and outputs allowed by our Framework’s BLANK component
Dynamic Network Topology – system robustness (pulling new components in if other fails, reconfiguring without taking system down, etc.)
Question: Did we achieve goals beyond these listed?

22. Prototype 1 Demo

23. Disconnected Subgraph Mobile device
This is the final demo network
Disconnected Subgraph
Mobile device

24. 10 10 5
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

25. 10 10 5
-10
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

26. 10 10 -5
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

27. 10 5 5 -5
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

28. 10 5 5 5 -5
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

29. 10 5 5
Ha - 5 Wa - 10 Hb - 10
Everyone starts connects their machine in the demo network, except Hb, Wb, and EB.
Patient walks in with QR code, requiring 10 bandages.
PM sends PatientInfo to Ha (Ha budget increases to 10)
Ha uses 5 bandages via GUI (Ha inventory decreases to 0, budget decreases to 5)
Ha sends RestockRequest to CM (requesting 5)
CM sends Deliveryorder to Wa (requesting 5) and RequestConfirm to Ha
Wa confirms delivery (Wa inventory decreases to 5)
Ha confirms receipt (Ha inventory increases to 5)

30. 10 5
Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture
-20

31. 10 5
Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture
-20

32. 5
Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture
-10

33. Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture -5

34. Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture -5

35. Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture 10 -5

36. Connect what was demoed to the piece of the Framework that was being used.
I.E. “When Hospital A was added to the network after initial configuration, X piece of the Framework allowed it to bypass reconfiguration by going through X process instead.”
Remember – purpose is connecting demo use case diagram to system use case diagram/architecture 5

37. Prototype 2
Design Goals

38. Goals Complete Data Aggregation Robust Connections System Diagnostics
Synthesize different types of inputs into one or more different types of outputs
Increase the amount of data flow
Robust Connections
Demonstrate transmission failure recovery and unintentional disconnection recovery
Network components directly related can tell when a device disconnects
System Diagnostics
Expand status logging of components, Graphical network topology tool, diagnostics tool
UX/UI
Ability to view actions while running the application
System Diagnostics – Logger already created, we just need to fine tune what is being logged and find a way to display it in the application (to show it works)

39. We will introduce a new component (because we want to introduce more types of data -- hetereogeneous) a traffic reporter. This will relay traffic/road information to the central manager who uses this new information to estimate the time it will take for a warehouse to deliver resources. This will help address the Large Scale Data Aggregation by introducing new types of data that affect the central manager's decision of which warehouse toship the resources from.
The central manager can begin to predict resource usage of each hospital, using historical usage data.
The central manager will have a user interface for resource management personnel to take manual control over the manager's decisions. (Addressing the UX/UI feature)