/16 Final Project Report By Facializer Team Final Project Report Eagle, Leo, Bessie, Five, Evan Dan, Kyle, Ben, Caleb

/16 Review & Overview Review & Overview Final Project Report 2 Android Take photos Upload to server Choose file within the phone Until the interim report, we have done: Server Photo training Facial recognition Database to store user info Totally speaking, we have designed a simple scenario and implemented some key features. After that, we focus on a more complex scenario and make some extensions and optimizations in both Android side and Server side, which make our application more powerful and practical.

/16 Scenario – A Game to Know Others Final Project Report 3 1. Before the game, all users register into the server and get his or her photo trained 2. Organizer applies a game space in the server and get a game id, and then tells it to the attenders 3. Attenders join the game with the specific game id and then get a task to find a person in this meeting 4. He or she gets to meet and takes a photo with the person, then uploads the photo to the server 5. Server recognizes the two person in the photo uploaded and return a successful or failing response and maybe another task 6.The fastest one who completes specific number of tasks will be the winner of this game, and be awarded

/16Requirements Final Project Report 4 Of course, the requirements should be changed and we can extract some key points from the previous slide. Android Add pages for new features like Join and Task info Design a proper jump orders between those pages Maintain the user identifiers in the mobile for the communication with server Server Implement a complex game logic for users joining a game Add a interface for organizer to apply a new game space in server Optimize responses to Android in JSON

/16Architecture Final Project Report 5 Server Android Database Face.com u Take a photo u Choose a file in SD u Upload user information and photos u Display response u Maintain user info u Join with a game id u Parse the response and complete the game u Associate Identifier with user information u Train the system u Recognize an individual in a photo u Provide interface for android part u Call the service of Face.com u Read and write information to DB u Implement game logic u Provide interface to apply a game interface

/16 Android - Modules Final Project Report 6 Android Photo taking Component Interaction Component Interaction Component File Locating Component Register Component Register Component Train Component Train Component Join Component Join Component Game Component Game Component old Latest for the game

/16 Android – Interaction Module Final Project Report 7 Interaction Component Interaction Component Register Component Register Component Train Component Train Component Join Component Join Component Game Component Game Component Server When we work on the left four modules, we don’t care about the server, and just invoke the interface provided by Interaction Module

/16 Android UI Page Jump Final Project Report 8 Main(Join Page) Train Page Register Page Not have registered Game Page Registered but not trained Registered and trained

/16 Android Part Implementation Coding: Environments: Android ADT 2.2 Eclipse 3.6 As showed in previous slides, OO principles are adopted: we set different structure layers and define the interface between modules clearly and reasonably. Testing: o Unit testing o Integration testing o Black box testing Final Project Report 9

/16 Server Breakdown Basic Information o Django framework (Python) o Hosted on an Amazon server Component Breakdown o Android Communication o Game Logic o Facial Detection o Database Interaction o Game Management Final Project Report 10

/16 Android Communication Must be able to receive and send information to phones. o Received data: player registration, game joining, in-game-pictures o Sent data: game notifications, in-game-picture responces o Right now data is sent via HTTP requests o Changed to JSON format Final Project Report 11

/16 Facial Detection Right now we use face.com service o Send URL of photo location (on our database) for face.com to use o Use the face.com API to train players face for games, and to identify them for in-game use o Use data retrieved from face.com for game logic Final Project Report 12

/16 Database Must store information about users o ID: how they are recognized as a player in the system (player name) o Phone ID: what phone they are using, so that the system gets called from a phone, we know which player it is o Face.com ID: to connect the player to their face.com account in our namespace o Game ID: store game sessions so we track who is playing in what game Final Project Report 13

/16 Game Logic Server runs game sessions that users play o Keeps track of who all is playing in the session. o Keeps a record of each players completed objective list names of people they have found o Updates the player with a current objective Gives the player one person at a time to go find so the logic of the game progress is on the server o Updates players when game is over Final Project Report 14

/16 Game Management We began work on a web based interface for creating games, and looking at game history. o Unfortunately we ran out of time. Right now there is a very basic architecture set up, but it is not functional.

/16 What we have learned 1. The first and foremost thing we’ve learned is some ways to share ideas with people who speak a different language and is very far away. We talk, type, and even draw diagrams to communicate. At first we were slow at understanding each other. But now I guess we progress a lot. 2. An iterative development would really help in programming. 3. We also learned how to develop on Android platform Final Project Report 16

/16 Thank you! Final Project Report 17