 Architecture Questions and answers are stored in server Tablet requests for questions and answers whenever necessary All questions and answers are stored within the tablet Tablet only uses web service to save progress AB

  We chose to adopt A instead of B  Scalability and versioning issues  Expecting updates on a daily basis  Expecting database to have thousands of questions per level  Limitation: Highly dependent on Internet connection  Focusing on the robustness of the system  Reduce crashes e.g. notifying the user that his response has been recorded etc. Justification

  Android Application  Eclipse  Java  Google GSON  SQLite  MySQL (Web-service)  Web Application  jQuery  PHP  MySQL Technologies Employed

  No prior Android Development experience  Ensuring that parents and teachers have all the required data to monitor a child  Requires a very huge database  Queries are long and complex  Streaming YouTube videos in our application.  SQLite Database Technical Complexity

  Use of SVN to minimize conflicts  Best practices are observed (meaningful method names, commenting of codes, etc.)  Test cases are drawn up for every iteration  Integration is done at the end of every iteration, on an average of once ever 10 days.  Regression testing is conducted after each integration. Code Quality