This week is going to be a long one. The levels are scheduled to be completed by the end of this week ready for testing for the next two weeks to follow.
This should be achieved but will mean a lot of late nights just to make sure we manage to meet the deadline. We have a Project Milestone on Thursday (31/03/2011) which should go over our Game and testing methods.
Realistically, the game will need next week for tweaks on both the game and the testing method we are going to be using, which is why 2 weeks for testing was planned in case we needed the extra time for polish.
Work on the documentation is going at a steady pace, though I think my work will be focused on helping the others with making sure the levels and testing method are working correctly for our test.
Monday, 28 March 2011
Thursday, 17 March 2011
Week 6 - Sememster 2
Lectures were here this week to check the progress made for the group report. Feedback was positive to my surprise. I was expecting to re-write large sections, but I was happy to receive positive comments about the structure and information given in the document.
This week will be making the changes to the document based on the feedback, while adding more to the overall report. Work towards the individual report is needed this week, so work towards that is needed as well.
This week will be making the changes to the document based on the feedback, while adding more to the overall report. Work towards the individual report is needed this week, so work towards that is needed as well.
Thursday, 10 March 2011
Week 5 - Semester 2
Since last week I have been working on the Group Report for the project. I have made a start creating a first draft, which I wanted feedback on but the lectures were away this week so I couldn't get the feedback I would like.
I was thinking about sending an e-mail with the content I had written, but I saw this as an opportunity to add more to the report this week and have even more feedback next week instead.
Work on the Design Document has been gradual process. At this stage it will be updated if needed now. It will need to be complete for the next milestone (24th March 2011), but my focus will be on making sure this Group Report is complete. Since others are focused on finishing the Levels, I feel it is important someone has made progress on the report. Once the testing is complete, the write up will be about the testing itself, which is fresh in our memories than trying to look back at early work and writing about that instead.
So the next few weeks will be Document writing and help for the others if they need it for other areas such as Level Design and Test Creation.
I was thinking about sending an e-mail with the content I had written, but I saw this as an opportunity to add more to the report this week and have even more feedback next week instead.
Work on the Design Document has been gradual process. At this stage it will be updated if needed now. It will need to be complete for the next milestone (24th March 2011), but my focus will be on making sure this Group Report is complete. Since others are focused on finishing the Levels, I feel it is important someone has made progress on the report. Once the testing is complete, the write up will be about the testing itself, which is fresh in our memories than trying to look back at early work and writing about that instead.
So the next few weeks will be Document writing and help for the others if they need it for other areas such as Level Design and Test Creation.
Thursday, 3 March 2011
Week 4 - Semeseter 2
Recent work for me has been are finishing up on the Design Document. It has more detailed information for the team to follow, though there are still some areas where I need some feedback from them in order for it to be complete.
This information has been slow in coming, but the team are working on the AI for the project, so I guess it can be understandable.
Our 3rd Milestone presentation went rather smoothly, though feedback was clear that our project need more misdirection techniques. I'm finding it hard to come up with misdirection techniques as I seem to keep coming back to the idea of change blindness.
Personally I think Change Blindness would be easier to test and gather results, but the fact there isn't much information around the idea of misdirection and video games makes the project worth fighting through.
Once the Design Document is finished this week, which I'm confident it will be complete, Work on Group/Individual reports will be my next task. I would like to get a rough draft for lectures to read for next week to see whether or not my write style is correct for report writing. Also work towards how to test our project is needed, so I would like to look more into this area this weekend.
This information has been slow in coming, but the team are working on the AI for the project, so I guess it can be understandable.
Our 3rd Milestone presentation went rather smoothly, though feedback was clear that our project need more misdirection techniques. I'm finding it hard to come up with misdirection techniques as I seem to keep coming back to the idea of change blindness.
Personally I think Change Blindness would be easier to test and gather results, but the fact there isn't much information around the idea of misdirection and video games makes the project worth fighting through.
Once the Design Document is finished this week, which I'm confident it will be complete, Work on Group/Individual reports will be my next task. I would like to get a rough draft for lectures to read for next week to see whether or not my write style is correct for report writing. Also work towards how to test our project is needed, so I would like to look more into this area this weekend.
Subscribe to:
Posts (Atom)