2. What have we been up to? Dean Leeks –Project Management –Helping Ryan with Artwork Roger Creyke –Building game engine –Prototyping game features Ryan Avent –Creating Characters –Helping Dean with Design Documents George Daters –Learning PAlib –Creating menu system Dean

3. How much progress have we made? Dean

4. Programming : Tech Design Doc Write in summary of tech doc here Roger

5. Programming : Resources Enter Table of Resources here Roger

6. Team Skill Profile Enter table of team skills here. Pics of us? Roger

7. Design : Character Development Penguin - Small, fast and the player primary character. Polar Bear - Large, slow and the players secondary character, used to bypass obstacles. Arctic Shark - Large, fast and means loss of life to the player. Ryan

8. Design : Levels Ryan & George Level obstacles - Artic shark - Moving platforms - Collapsing ice

9. Design : Level Art Water Shader demo in here please Roger Insert Dean’s animation sketches Ryan

10. Design : User Interface Dean

11. Design: Logic George Main level loop: Starts from level selection screen Defines main level scenarios Handles collision checks between character and scene End with cut-scene and returns to world selection

12. Design: Logic Slingshot Data Flow

13. Design: Logic Character Selection Data Flow

14. Design: Logic World Selection Data Flow

15. Project : General Risks George RiskDescription Likelihood Damage Demo misses deadline A playable level is aimed to be completed before the team take their Christmas holidays. Meeting this goal would ensure that the game can be playtested much earlier and would improve the overall position of the project. AbsencesA team member becomes absent from the project for a considerable amount of time. Each team member has many tasks and responsibilities which will need to be completed. Data Loss / Corruption The project data or documentation is lost or corrupted. Dissertation Presentations During the first two weeks of Decembers, all team members must make presentations for their dissertations. During this time, it is possible the team will be under pressure and have little time to work on the project. Wiki UnavailableThe team’s wiki is the main communication and sharing tool for the team. If the wiki is unavailable due to server errors for example, the project will be disrupted. Hardware FailureA team member’s personal computer fails. This may result in the team member unable to complete certain tasks on time. HighLowMedium

16. Project : Technical Risks RiskDescriptionLikelihoodDamage NDS file over 4MbThe game and all of its assets must be compiled into a single NDS file. The file size is capped at 4Mb and will not operate over that limit. PALib Forums DownThe PA Library is the programmers main development tool. Help with the library is often required because the programmers have little experience using it and there is little documentation available. The PALib forums have previously been a key area of support. It is possible that the programmers may not resolve issues because less support is available. Obscure Run-time error Programmers only have the ability to debug compile-time errors. If the game experiences a run-time error, there is usually no information provided. Programmers currently have no tools to assist the programmers debugging run-time errors. Design not feasibleDuring implementation of the game, it is discovered that one of more parts of the design are not feasible because of technical restraints. LowMedium George

17. Project : Risk Mitigation RiskMitigationContingency Plan Demo misses deadline Adjust demo scope to be more realisticPlaytests are conducted are soon as possible after the semester break. Disruption from Absences Add slack time to tasksReassign absentees tasks Project Scope Reduced Data Loss / Corruption Project data kept on web. Data backed up securely Project files are retrieved from backup versions. Wiki UnavailableNoneSetup alternative temporary wiki Emergency team meetings

18. Project : Risk Mitigation RiskMitigationContingency Plan Hardware FailureNone required due to availability of university resources. None NDS file over 4MbLow resolution images. Shared palettes. Reduce audio sample rate Reduce Project Scope PALib Forums DownOther support methods researched Greater communication of problems None Obscure Run-time error Frequent and thorough testing on the DS Extensive Source documentation Unit tests in other platforms Purchase available debugger. Revert to a previous version. Design not feasibleProgrammers refine and optimise code Graphical effects are simplified. Alternative designs are considered.

19. Programming : Menus George Design Goals: Attractive Graphics Accessible Score System Loading Saved Games Character Selection World (Level) Selection

20. Programming : Gameplay Tech Demos Roger Insert Video of Tech Demos here

21. Project : Playtesting How do we plan to carry out our playtesting? a.Third Year Designers/Programmers during spare moments b.From now on Proper Organised tests with feedbacks forms c.Testing with Second Year Games Designers d.Then move to First Year Games Designers e.Then All UCS Students and Lecturers f.Go out to local Schools to playtest g.Finally Everyone – Our game is designed to be enjoyed by all Dean

22. What next? Maintain our constant communication between group members so we all know we’re working in the right areas. This will mean we continue to stay on track deadline wise. Keep our wiki up-to-date To stick to and keep project plan up-to-date. Have even more group meetings in the bar. Alcohol induced ideas really do rock! Get game mechanics sorted and finish a tech demo asap to make sure game idea has good potential. Then playtest demo. Have one playable level in complete form by the 2nd February. Make the game fun at all costs Dean

23. Thanks for listening …any questions? Dean