Design Decisions

In the creation and design of Beep Beep, there were certain decisions that had to be made. The following are some key decisions and our team's reasoning behind it.

Decision on usage of C# and Unity

In the initial design of Beep Beep, there were certain requirements we had when picking the initial language/framework to use. We needed:

• Cross platform compatibility
• Graphical support
• Heavy Documentation and online support

When researching, we narrowed our search to Java and C# with Unity. The decision to stick with Unity was that porting to mobile platforms would only require a couple sprints worth of work as opposed to an entire semesters worth. Much of the input handling and graphic rendering needed to be built on Java already existed as API calls in Unity. The downsides we found to using Unity have been the difficulty in separating test code from production code. As a result, the team voted to choose Unity as our platform.

Build View, Sim View, and Compiler

We had decided to modularize the project into three portions as it gave us the following benefits.

• Allowed parallelization of development time
• Creates a smaller load for the CPU to handle when simulating
• Makes porting the watered-down mobile version of the application much easier