Draft of interim report

Toolkit Developers Team

Programming

Brian Perry

Joel Salazar

Shane Michael Layne

Kezlon Sutherland

Design

Himraj Bir

Kezlon Sutherland

Use case diagrams

Kezlon Sutherland

Documentation

Manuel Browne

Consulting

Dane Nurse

Executive Summary

This report will summarize actions taken over the past month and few weeks on the game 6 strike, summaries of the actions and accomplishments made on a weekly basis along with constraints and measures we have had to reconsider in order for the game to be developed and presented.

                                                                                           

Week 1

We began experimenting with the Unity engine along with writing designs on how the game will run gameplay wise, along with writing use-case diagrams on the scope of the project and the stages it will go through. We also began to assign roles towards individuals and set them out into groups. Kezlon, being the use case diagram designer, along with making contributions towards programming and design, Brian Perry, Joel Salazar and Shane Layne on programming, , whilst Himraj manages the design of the game and the surface on which it is to be used on, and Manuel on documentation on our work.  The first week proved to be relatively productive with no constraints to be found.

Week 2

 The first week proved to be relatively productive, and the 2^nd week proved to be as significant as we managed to have our platform and level design done by Himraj, and had a partially functioning .apk that has proven to be functional on most devices without any compatibility issues with the app launching successfully, along with a new reworked logo, from the original we had last year. However, this week proved to have constraints that prevented us from advancing, as issues such as bugs in gameplay and issues with collision.

Week 3

In this week, we found more snags that made game development difficult. We had issues with map functionality, as the ball kept flying off the map

Week 4

Problem constraints

As we enjoyed developing this app, we were faced with many problems in the programming field.

·        Problem: Programming errors with C# coding by allowing the ball to go completely off the playing field.

·        Solution measure: Change C# script by rewriting code after researching collider issues with surfaces and changing the values in unity.

·        Problem: Physical ball not reacting to scoring areas

·        Solution measure:  Revise C# code to ensure values/objects  are functional

·        Problem: