search

NeoWang1986614 / games-development-project

Automatically exported from code.google.com/p/games-development-project
0 stars 0 forks source link

Restructure documentation #19

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Read marking scheme document.
2. Restructure documentation to match it.

Original issue reported on code.google.com by hollgam on 8 Nov 2011 at 10:56

GoogleCodeExporter commented 8 years ago 
Group Feedback on draft report: 
• Your contents page could do with page numbers in the final version.
• The order of your sections should match those outlined in the assessment. 
See the assessment for more information. For example, research forms part of 
the requirements analysis.
• Your introduction section could include more detail regarding the game 
concept.
• Your specification section should have more depth and scope. It should 
include research conducted. For example, Which AI techniques to use when 
implementing the character control behaviour.  See lecture 3 notes for more 
information.
• The methodology section should focus on what development methodology (e.g. 
scrum) and what development methods you use. Choosing a tool and language is 
not appropriate for this section; however, it can all be included in other 
sections of the report.
• Good start to a discussion unity in the specification section. However, 
this work would go in the requirements analysis section.  Also bring in other 
game engines to your discussions. 
• There are many screenshots without captions to describe them – use the 
following notation for figure 1: Figure 1: <Figure title / description>.
• Good discussion of physics; however, it feels more like a requirements 
analysis or more likely an implementation section rather than a research 
section.
• Is the figure “Collision detection example” created by you or from a 
source? If from a source you need to use the Harvard referencing system.
• There are many sections missing and there is poor structure to other 
elements of the report, therefore I have not highlighted your grade above.
• See week 3’s lecture for more information regarding the contents of the 
report. Do not forget diagrams, such as UML and system diagrams.

Original comment by domsmit...@gmail.com on 8 Nov 2011 at 11:05

GoogleCodeExporter commented 8 years ago

Original comment by hollgam on 8 Nov 2011 at 4:07

GoogleCodeExporter commented 8 years ago 
Hi Dominic,

The structure looks very good to me. Here is a link to game documentation that 
you may find useful: 
http://www.gamasutra.com/view/feature/3384/the_anatomy_of_a_design_document_.php
.

Some content is missing / lacks depth. Keep working on this.

I hope this helps.

Best regards,

Tom..

Dr. Thomas Hartley PhD BSc PGCert
Lecturer in Computer Games Development / Computer Games Coordinator for the 
Institute of Gaming and Animation.

Original comment by domsmit...@gmail.com on 2 Dec 2011 at 11:21