Robot Rock

Hey guys. Check this out and edit as necessary before submission on Apr. 20 -- Travis

We were very impressed by the interactive tutorial as it clearly explained the interface's operations. The forward/reverse interface components seems to be unnecessary if this project is taking a game based approach, as it would eliminate the possibility of the user “losing”–clearly the user can “win” as indicated by the message in between stages. If you wish to keep the forward/back possibility then a time limit may prove to be an incentive to keep users engaged.

The tutorial-based beginning was useful and really helped us learn our way around your project. Games that teach their users how to play with several tutorial levels have been the norm for a while now, and you executed this portion well.

The simplicity of the user interface was very appealing as well. After playing through the tutorial level, there were very few points at which we were confused about what buttons would do. As you develop this application more, undoubtedly more complex operations and simulations will be added to it (we have suggestions for a few aspects of traffic that seemed missing in this prototype), but we would suggest you pay mind to the simplicity you had in your first model and try to integrate the new features without adding an excessive number of clicks for the user.

We understand that the simulation component of the application is critical and difficult to properly demonstrate on paper, and you did a good job at “simulating the simulation.” This project is difficult, much like our Robot Rock is, to determine its output by paper alone—we feel your pain! The lack of an accurate simulation, however, left us wondering how deterministic the outcome of a simulation would be. One concern we had was that if traffic had a random element to it, then could any given configuration pass at some times and not at others?

Another concern with the project was a lack of cost in the design. This cost could either be either monetary with respect to traffic signals, or a time cost with respect to the driver upon the road, or simply a limit to the number of traffic lights placed. We couldn't see any incentive to not simply place as many traffic lights as possible.

There were also other traffic variables that we didn't see. Speed limits were not posted nor was the option to change the speed limit—this seems like a vital component to have absent in a traffic simulation. Other, and admittedly one that adds to the complexity, is that there are two factors that undeniably contribute to traffic: time of day (rush hour) and accidents.

Good job so far and we look forward to seeing subsequent updates.

- Team Robot Rock