1. APRIL 10, 2015

2. Meeting Agenda  Prototype 2 Goals  Robust Connections Demo  System Diagnostics Tool Demo  Final Prototype Risk Mitigation  Final Presentation  Questions & Answers

3. Prototype 2

4. Goals  Complete Data Aggregation  Synthesize different types of inputs into one or more different types of outputs  Increase the amount of data flow  Robust Connections  Demonstrate transmission failure and unintentional disconnection recovery  Network components directly related can detect device disconnects  System Diagnostics  Expand status logging of components, graphical network topology tool, and diagnostics tool

5. Progress  Complete Data Aggregation  Extended Prototype 1 structure to add automatically generated data in order to demonstrate scalability  Robust Connections  Reconnection after network failure between connected components  System Diagnostics  Parse network logs to display topology graphically  Log aggregation and filtering

6. Robust Connections TEAM LEAD – LUKE WANG

7. System Diagnostics TEAM LEAD – MAX PAYTON

8. Challenges  Complete Data Aggregation  Bottlenecks in Azure Database queries  Moving to Worker Roles from VMs more difficult than expected  System Diagnostics  Azure database connection problems prevented integration with Application

9. Final Prototype

10. Mitigation Plan

11. Final Presentation

12. Date & Location  Date: April 27th  Time: 4 PM  Location: McMurtry Auditorium

13. Format  Introduction of the Problem  Overview of the Framework Design  Demo an Application built on the Framework  Reflect on what we learned  The COMP 410 experience

14. Final Prototype  Efficiency  Recovery  Security  Extensibility  Testability

15. Final Prototype 1.High Volumes of Heterogeneous Data 2.Disconnections 3.Different Kinds of Devices 4.Human Interaction

16. Deliverables  Framework User Manual  Framework Code  Framework API Documentation  Example Application Project  Expect by May 6th