Can We Talk Now? A Prototype Intelligent Status Tracking System For Enterprises 13 th November 2009 Sidney Shek ( ) Supervisor: Dr Rolf Schwitter

Agenda Project Introduction System Architecture and Concepts Demonstration Evaluation of Project Performance Future Work Conclusion 2

The Problem Where is ‘John’ and how should I contact him? What happens if I call during a meeting with the CEO?

Project Aims To develop a low-cost prototype intelligent status tracking system (Can We Talk Now?) ◦ Based on Social Networking concept of ‘status’ ◦ Populate user’s status information based on calendar, location, etc. ◦ Use logic to determine ‘best’ means of communication between two users ◦ To integrate with mobile devices (Apple iPhone) 4

Project Phases Project split into two phases: 1.Feasibility study and technology selection  Literature review  Requirements analysis 2.Prototype system development  Develop and demonstrate core server and mobile client modules 5

Agenda Project Introduction System Architecture and Concepts Demonstration Evaluation of Project Performance Future Work Conclusion 6

Requirements for ITEC809 work 1. Implement rules for finding ‘best means of communications’ 2. Develop a mobile application client ◦ Support simple and quick status data entry ◦ Support querying of other users’ status 7 Form the foundation for a prototype based on ITEC808 analysis

System Architecture 8

Application Data Structures 9

Application Logic 1. Populating Activity facts based on: ◦ GPS, calendar information, etc. 2. Determining available means of communication based on: ◦ Matching location ◦ ‘Free to talk’ status:  Current activity (e.g. meeting versus idle)  Relative importance of people  Relative urgency of question 3. Prioritising means of communication 10

Agenda Project Introduction System Architecture and Concepts Demonstration Evaluation of Project Performance Future Work Conclusion 11

Demonstration Flash MP4 12

Agenda Project Introduction System Architecture and Concepts Demonstration Evaluation of Project Performance Future Work Conclusion 13

Implementation vs Requirements 1. Implement rules for finding ‘best means of communications’ 2. Develop a mobile application client ◦ Support simple and quick status data entry ◦ Support querying of other users’ status ◦ Integrated with server via REST 14

Learnings from Implementation Confirmed need for integration with calendar system Demonstrated importance of upfront design and use of good design patterns 15

Learnings from Implementation – Development methodology Importance of ‘proof of concept’ development Importance of unit testing Importance of iterative approach ◦ Especially for client application development Need ‘realistic’ estimates for development time ◦ Include learning and debugging time 16

Agenda Project Introduction System Architecture and Concepts Demonstration Evaluation of Project Performance Future Work Conclusion 17

Future Work – Post-ITEC809 18

Future Work – Post-Prototype Enterprise deployment: ◦ Implement integration with SNSs Research testbed: ◦ Use of Semantic Web technology for data storage and reasoning 19

Conclusions Aim of project was to develop a low-cost intelligent status tracking system Developed and demonstrated core server and mobile client application Next steps – complete prototype based on all ITEC808 requirements 20

Thank you Questions? 21