2. The Team Team consisted of 5 members. Max Annear – Henderson Conrad Orange Mike Debney Anton Slooten Luke Stanford

3. Life cycle Agile Variation of XP Working code > extensive documentation Iterative Approach Milestones

4. Milestone 1 Components working together Milestone 2 Simple map and basic movement Milestone 3 Playable game (with bugs) Milestone 4 Final product

5. XP Practises followed Test driven development Continuous integration Program for today Small releases Simple design Pair programming

6. Planning + Issue Tracking Google Codes issue tracking provided efficient + effective project management Bug and defect reports Project planning Task assignment Clear communication

7. Authentication OpenID provides a safe + easy way to sign in Users can select which information to provide Familiar sign in page Services are customisable Google Yahoo

8. Client Technologies Widely used and well documented technologies + APIs for easy maintenance HTML5 CSS3 JavaScript Jquery 1.6 JSON Google Maps 3.6 Google Directions

9. Compatibility Consistent user experience across wide range of different browsers + platforms Chrome 14 Firefox 7 Internet Explorer 9 Safari 5 Opera 11

10. User Interface Controls are simple + easy to learn Important elements are large Mice + touch devices Simple interface for less scrolling + zooming Effective use of space Map fills most of screen Less important elements are hidden

11. Promotes planning + strategy Clear symbols indicating transport options Clear station numbers promote teamwork Station Markers 42

12. User Experience Google Chat for fast communication and enhanced teamwork Before and during gameplay Text + voice Integrated + intuitive help system Available at any stage of gameplay Downloadable user guide

13. Server Java JSP Servlets

14. Game Logic Well defined structure Modular design Documented Tested

15. Reliability Thoroughly tested client + server Qunit client testing allows testing in the actual deployment environment. Junit for game logic - Good test coverage Beta testing, allowed us to reduce bugs and optimize the UI. Risk of failure is minimised Client only provides a stateless interface to server Game logic only on server

16. Scalability Java Servlets provide a scalable platform Game supports multiple players + games Java base runs on wide range of operating systems + hardware