1. Team Portrayals Documentation Team Oct. 23th 2002

2. Our Team Coach: Astrid Stangler (stangler@in.tum.de) Members: Anis Trimeche (trimecha@in.tum.de) Banko Banov (banov@in.tum.de) Evelyn Koska (e.koska@web.de) Thorsten Schöckel (schoecke@in.tum.de)

3. Our Goals Page 12: Infinite Loop...see Loop, Infinite Page 21: Loop, Infinite...see Infinite Loop

4. Our Real Goal Create the documentation for the client and the programmers Keep to Software Engineering Standards

5. Procedure Construct documentation overview Provide templates and styleguides Evaluate tools and integrate them Observe timestamps and history

6. Cross-functional team who negotiates and implements changes in the FRAG Framework Responsible for finding common solutions that should be added to the Framework The Framework Team

7. What we‘ll be responsible for

8. The Framework Layer I/O component: provides an interface for merging and distributing events of multiple devices (mouse, keyboard, special input devices) Game component: manages all game data, provides access for addressing multiple FRAG objects, controls and updates the mission state Peer-to-peer component: responsible for the P2P game setup - dynamical peer discovery and connection establishment

9. Infrastructure for tournaments in mobile environments Manages peer-to-peer communication Distributed object synchronization and state replication between peers Message transport for object-based 2D or 3D game worlds... and how it is thought to be utilized Supposed to be modified and extended according to our own needs What is provided by the FRAG Framework...

10. Please post your suggestions and demands concerning the FRAG Framework on our BBoard Thanx for the attention! Your Framework Team And finally… Presentation by Profy

11. Team Portrayal Film Team

12. Team Members Atoudem Kana Michelatoudemk@in.tum.de Chris Austaust@in.tum.de Christopher Rölleroelle@in.tum.de Joerg Königkoenigj@in.tum.de Tobias Klüpfel (Coach)kluepfel@in.tum.de Vadim Alyokhinalyokhin@in.tum.de

13. Goals Customer presentation Multimedia review documentation

14. Customer presentation Product commercial Presentation of the different teams And their work Glorify our hard work

15. Review documentation Recording all reviews on video Conduct the technical part of the reviews

16. Motivation Visualize the workflow and process of the whole project Do some marketing Provide presentable material to the customer, he can use himself

17. We need YOUR help Good looking stuff like –Graphics –Screenshots –Diagramms Review organizing –Presentations –Scripts –As much information as your can give to support us

18. ARENA Build Team Overview

19. Services provided by the Build Team Build System Configuration Management Continuous Integration Automated Integration Testing

20. Build System Provides means to simplify the system building process Every user should be able to build the system from scratch Possible build systems: –Jakarta Ant –Gnu make IDEs: ProjectBuilder, JBuilder, Eclipse, Together, emacs, vi

21. Configuration Management System Manages changes in all source files of the system Available CMS: –CVS (Concurrent Version System) –Subversion (still in development) CVSweb

22. Continuous Integration Automated daily builds Benefit: find problems between modules faster Pre-requisite: well-tested units, interfaces conform to specification Suggestion: CVS Check-in only possible if unit tests pass

23. Integration Testing Test for problems Module testing is done by the development teams (JUnit) Integration Testing is done by the build team Integration builds: builds that have passed the integration test Build status should be available on web server