Team Portrayals Documentation Team Oct 23 th 2002

Team Portrayals Documentation Team Oct. 23 th 2002

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)

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

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

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

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

What we‘ll be responsible for

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 P 2 P game setup - dynamical peer discovery and connection establishment

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

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

Team Portrayal Film Team

Team Members • • • Atoudem Kana Michel Chris Aust Christopher Rölle Joerg König Tobias Klüpfel (Coach) Vadim Alyokhin atoudemk@in. tum. de aust@in. tum. de roelle@in. tum. de koenigj@in. tum. de kluepfel@in. tum. de alyokhin@in. tum. de

Goals • Customer presentation • Multimedia review documentation

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

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

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

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

ARENA Build Team Overview

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

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: Project. Builder, JBuilder, Eclipse, Together, emacs, vi

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

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

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