Changes between Version 3 and Version 4 of Nov08Notes
- 11/08/11 22:21:19 (4 years ago)
v3 v4 15 15 16 16 '''What went right and what went wrong? Did you achieve the goals you had set out? What can you do to avoid similar problems in the future?''' 17 We started on most of our goals but did not complete several of them. For example, we started implement saving and loading functions but did not complete them. In addition, the event popups appear at the appropriate times but do not have any economic effect, yet. 17 We started on most of our goals but did not complete 18 18 19 19 '''How good were your predictions on how long the goals would take to achieve? ''' 20 20 Our predicted times were underestimates this week. This is due to the fact that saving and loading turned out more complicated than we expected it to. In addition to creating the AI framework, we also made the art for the AI events so this also took longer than expected. 21 21 22 22 == Goal Plan for Prototype == 23 23 24 25 26 24 27 25 28 == Goal Plan and Time estimates for all Deliverables == 29 30 26 31 27 32 See [https://www.cs.hmc.edu/trac/cs121fa2011_3/wiki Main Page] for the goal stack. … … 33 38 '''This week's analysis:''' 34 39 35 Observing people play our game, we think that the highest risks are related to how fun the game is. 40 . 36 41 37 * '''''Students may not read text in the information panel. '''''Currently, the text that appears in our info box is too long-winded and advanced for many middle school students. As a result, many students may not read any of it, which makes it hard to achieve the learning objectives. This week, we need to make the text as concise as possible while using simple language. As Greg Orr said during the customer elicitation, teaching the students what a tariff is will be beneficial even if they do not know more than that. 38 39 * '''''Students may lose interest in the game. ''''' We will limit the amount of text in the game and continue to make the graphics more interesting. 42 In addition, this week we will release the beta. This puts us at risk with a time constraint. Hopefully organizing the tasks and splitting up the work will put us on track for the release.