1 / 23

Can We Talk Now? Technology Selection for an Intelligent Status Tracking System

Can We Talk Now? Technology Selection for an Intelligent Status Tracking System. 5 th June 2009 Sidney Shek (41419979) sidney.shek@students.mq.edu.au Supervisor: Dr Rolf Schwitter. Agenda. Project Introduction Related Work Requirements and System Analysis Rule Engine Evaluation

keran
Download Presentation

Can We Talk Now? Technology Selection for an Intelligent Status Tracking System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Can We Talk Now?Technology Selection for an Intelligent Status Tracking System 5th June 2009 Sidney Shek (41419979) sidney.shek@students.mq.edu.au Supervisor: Dr Rolf Schwitter

  2. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • 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 principles • 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: • Rule engine • Client-server communications • Server platform • Prototype system development

  6. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • Future Work • Conclusion

  7. Related Work • Many public and private Social Networking Services (SNS) store status information • Not automatically populated • No logic rules applied to extract information • Dinoff et al. 2007 reports a similar system to CWTN for service providers or carriers (Intuitive Network Applications) • CWTN is low-cost ‘add-on’ system for individual enterprises

  8. Learnings from other SNSs • Need for flexibility in data and functionality • Need to integrate with SNS as mini-application rather than reinventing wheel • Need to address enterprise deployment issues: • Security • Cultural hindrance • Privacy • Scale and critical mass

  9. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • Future Work • Conclusion

  10. Application Data Structures

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

  12. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • Future Work • Conclusion

  13. Rule Engine Evaluation • Evaluated rule engines: SWI-Prolog, Prova, Drools, JESS • Criteria included: • Support for application logic • Integration with Java (for server platform) • Enterprise based criteria (robustness, development environment, support, licence fees) • Future proofing (RuleML, Semantic Web support)

  14. Comparison of Rule Engines

  15. Rule Engine Evaluation Results • No rule engine ideally suited • Backward chaining like Prolog or Prova good for problem, but lacked in other areas • Drools has good support, but is forward chaining • Use Drools for now, with architecture to support simple replacement

  16. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • Future Work • Conclusion

  17. Client-Server communications • Mobile device restrictions: • Limited battery • Limited CPU • Limited libraries • Use REST (RESTlet framework) • Fits into SOA • Easier to process than Web Services • Use JSON instead of XML • Lightweight and less bandwidth

  18. Server platform • Mobile devices need Internet-facing server • Difficult to get for a prototype system! • Deploy prototype to Google App Engine • Internet accessible and free JEE server • Consider integration with enterprise later • Enterprise hosted server • Trusted connection to Google App Engine cloud

  19. Agenda • Project Introduction • Related Work • Requirements and System Analysis • Rule Engine Evaluation • Technologies for client and server parts • Future Work • Conclusion

  20. Future Work – Next Phase

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

  22. Conclusion • Aim of project is to develop a low-cost intelligent status tracking system • Initial feasibility study and technology selection completed • Rule engine, server platform, client-server communications • Development iterations scoped • Next steps – Design and develop prototype

  23. Thank you • Questions?

More Related