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

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

13th November 2009Sidney Shek (41419979)[email protected]: Dr Rolf Schwitter

AgendaAgendaProject IntroductionSystem Architecture and

ConceptsDemonstrationEvaluation of Project

PerformanceFuture WorkConclusion

2

The ProblemThe ProblemWhere is ‘John’ and how should I contact

him?

What happens if I call during a meeting with the CEO?

Project AimsProject AimsTo 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 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

AgendaAgendaProject IntroductionSystem Architecture and

ConceptsDemonstrationEvaluation of Project

PerformanceFuture WorkConclusion

6

Requirements for ITEC809 Requirements for ITEC809 workwork1. 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 onITEC808 analysis

System ArchitectureSystem Architecture

8

Application Data Application Data StructuresStructures

9

Application LogicApplication Logic1. 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 communication10

AgendaAgendaProject IntroductionSystem Architecture and

ConceptsDemonstrationEvaluation of Project

PerformanceFuture WorkConclusion

11

DemonstrationDemonstration

FlashMP4

12

AgendaAgendaProject IntroductionSystem Architecture and

ConceptsDemonstrationEvaluation of Project

PerformanceFuture WorkConclusion

13

Implementation vs Implementation vs RequirementsRequirements1. 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 Learnings from ImplementationImplementationConfirmed need for integration with

calendar system

Demonstrated importance of upfront design and use of good design patterns

15

Learnings from Learnings from Implementation – Implementation – Development methodologyDevelopment methodologyImportance 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

AgendaAgendaProject IntroductionSystem Architecture and

ConceptsDemonstrationEvaluation of Project

PerformanceFuture WorkConclusion

17

Future Work – Post-ITEC809Future Work – Post-ITEC809

18

Future Work – Post-Future Work – Post-PrototypePrototypeEnterprise deployment:

◦Implement integration with SNSs

Research testbed:◦Use of Semantic Web technology for

data storage and reasoning

19

ConclusionsConclusionsAim 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 youThank youQuestions?

21