This document outlines a plan to develop an Android taxi calling application. The objectives are to create Android apps for users to call taxis and for drivers to respond to requests, as well as a central server to manage communication. Key resources include development computers, Android devices for testing, and a Glassfish server to be deployed on Windows Azure. A single student will implement the apps and server with supervision to ensure deadlines and architecture validation. Risks include migrating the server to Azure and achieving cross-device consistency. Proper planning will help determine timelines, costs, and optimize resource usage.

1. Android taxi call
Lucian TIMOFTE
An IV CTI

2. Objective
 Develop an Android application that allows
users to call a cab
 Develop an Android application that allows taxi
drivers to respond to user requests
 Develop a central server to manage
comunicatoin between taxi drivers and clients

3. Resources
Physical:
 1 computer for development
 10 android test devices
Logical:
 10 different android emulators for testing
 Eclipse + android sdk
 Glassfish server
 Windows Azure account

4. Team
1 student, responsible for:
 Implementing the webserver and the two
android client applications
 Testing
 Deploying server on Azure
1 supervisor, responsible for:
 Makinging sure deadlines are met
 Validate overall architecture of application

5. Task Information

6. Task overview

7. Final cost

8. Workload distribution

9. Risks
 Moving the webserver to azure (problems with
database conectivity, having to migrate from
PostgresSQL to MsSQL
 Having the same look and feel on all devices
 Possible Intensive workload on server in real-
life scenarios

10. Conclusions
 Planing help with determining the timeframe for
the project
 Aproximate costs can be determined from the
begining
 Activities can be planned so that each resource
is used at it's maximum potential