Week 9

Continuing on from last week, the team focused on researching methods for measuring emotion, in which Nick suggested on several points to focus on, which I agreed as Milestone Manager. I started on testing out an analysis procedure on the SAM test, in which I used a formula of Standard Deviation on some simulated data, just to see how it worked out. I also investigated the use of a program called SPSS, which is used for data analysis, among other things, but after discussing the program with the team, decided that it wasn’t worth using, and to use MS Excel. This was because all team members are familiar with it, and all have access to it.

I also created a basic draft on the SAM test, which was similar to many of the journals researched used. In addition to this, Matt went through my 8.1 Procedure, and changed it as it had to be altered due to the changes in the method of testing. The remainder of the week was just spent finalising the design document, to be in line with what was mentioned for milestone one, and then we began preparing the presentation, in which myself and James will be presenting for this milestone.

Week 8

The first few days of this week were mainly focused on finishing the tasks assigned, and then I helped proof read everyone’s work with Nick to make sure every section in the design document flowed from one to the other. This continued until Thursday, where we had to change our testing method slightly. After doing some research on testing methods, I eventually found:

http://web.media.mit.edu/~seongju/IBS.pdf

Kim, J.Y Lee, H.S (2003) A Development of an Emotion-Color Responsive Adaptation for VR Interactive Model, Journal of Asian architecture and engineering building Vol. 2, No. 2. pp 61-68

In which figure 1 shows various human senses, which signal of emotion they relate to and what can be used to measure the emotion. After discussing the meeting with Dr. Charlton, the team and I agreed that some sections had to be rewrote to reflect the changes in the design document. Consequently, the sections I wrote in the design document changed slightly, which was original part of the control measures has been moved to section 8.2, although it was decided that 6.1 did not need to be moved.

Week 7

After investigating the project management systems, it was eventually decided that I will be in charge of monitoring, and adjusting the Gantt chart for the first milestone, and that each team member will take turns being in control of the Gantt chart, with one other person taking over a second time eventually. The week was spent mainly preparing the design document and creating the Gantt chart that will be used to monitor the project. It was also decided that Matt and James will do a film analysis of two different films, while Nick and myself would being to start on the design document.

After the supervisory meeting, where Nick talked about our idea of having a project manger and that I would be taking on responsibility for the first milestone, where-after I began to create the Gantt chart and set out what tasks to do over the weekend, after discussing said tasks with the team. It was decided that we would each take parts of the design document, and start fleshing them out. The actual tasks were then to be colour coded into the Gantt chart, to show who was doing what tasks and when the date for them to be completed on.

Week 6

This week was spent mainly going over the deliverables, discussing any points then making changes to them. During the suporvisory meeting we talked, n addition to the deliverables, a project management system called Scrum, which is a way of monitoring projects, and being able to tell whether they will be on time or overrun. Several points on this video I noticed on what Scrum was were:

· Completion of a fixed set of backlog items in a series of short iterations or sprints;
· A brief daily meeting or scrum, at which progress is explained, upcoming work is described and impediments are raised.
· A brief sprint planning session in which the backlog items for the sprint will be defined.
· A brief sprint retrospective, at which all team members reflect about the past sprint.

With a more detail description at:http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf


From these you can produce a graph, showing time against the sprint day. After several parts of the list have been finished, it will be possible to predict when the project will be completed, and adjust it if necessary. In addition to this, I also made a Google-Mail account for use with the Google Docs which were mentioned in the meeting on Thursday.