Can We Talk Now? A Prototype Intelligent Status Tracking System For Enterprises

1. Can We Talk Now?A Prototype Intelligent Status Tracking System For Enterprises 13th November 2009 Sidney Shek (41419979) sidney.shek@students.mq.edu.au Supervisor: Dr Rolf Schwitter

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

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

4. 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)

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

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

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

8. System Architecture

9. Application Data Structures

10. Application Logic • Populating Activity facts based on: • GPS, calendar information, etc. • 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 • Prioritising means of communication

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

12. Demonstration • Flash • MP4

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

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

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

16. 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

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

18. Future Work – Post-ITEC809

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

20. 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

21. Thank you • Questions?