Attached is the final documentation for Team Dragonfly.

Since the website doesn't seem to like 29 MiB attachments, the presentation can be downloaded here.

The presentation is a zip file which should be extracted prior to viewing the PowerPoint show. The source to the show -- the original PPT and the original SWF videos -- are also included. This is in case you have difficulty playing the transcoded video files, or just want to see the clearer and crisper originals.

Attached is Team Dragonfly's presentation demo. Due to technology constraints it doesn't have multimedia content yet, but there are placeholders which should clearly denote where videos are going to be included. Our final version will also include several screenshots. Any feedback on the actual content, however, is appreciated.

Attached is the final draft of my individual usability study.

This week has been a very productive one for Team Dragonfly. First of all, we received late feedback on our contact email, so we were a little delayed in getting that out. On Tuesday, we had a long discussion on AIM, and worked out most of the details of the project. I also updated the client contact email in response to feedback, and then we sent it out. On Wednesday, again several of us had a chat in AIM to discuss usability tests and the project proposal. Jeff produced the draft of the proposal, and after some minor edits, I posted it. We also completed our usability studies based on different aspects of the program. Finally, in response to peer reviews, I made some significant changes to the proposal for our final draft, and am currently waiting for other input so we can post it tonight.

Attached is Team Dragonfly's proposal draft. Any feedback is appreciated.

Attached is my individual usability study. I focused on the installation of Dragonfly, while others in the group are focusing on other aspects of the program. Any feedback and suggestions are welcome.

Attached is the draft of our client contact email. Thank you for any feedback and suggestions.

This week began with getting our team together, and figuring out a topic for our project. After exchanging introductions and ideas, we held a meeting with Kevin and four of our five team members. During this meeting, we discussed various topics and tasks (including the focus of the project itself, which is something I was confused about).

We settled on trying to introduce a content management system (CMS) to an amateur radio club at Purdue, of which one of my teammates is a member. The particular CMS we are going to use is called Dragonfly, and accordingly we chose the name Team Dragonfly for our team.

Two of our members drafted the client contact email and sent it out for review. I offered several suggested changes, and am currently waiting for the revised document to be posted on the course website. When this is done, our tasks for this week will be complete. Overall, I think we are off to a good start.

I have reviewed the changes Seth made to our instructions and am in the process of making additions. My contributions will primarily be graphics updates and additions, though I continually edit text where improvements can be made. I will get these to him tomorrow, as well as the draft of our revision memo when we have confirmed all of our changes. Since we have not received feedback from our usability test, it may be difficult for us to identify specific areas of improvement, but we will do our best. After finalizing the instructions and revision memo, we each need to finish the project-end documents, specifically the checklist and the peer evaluation.

This week, our primary objective was to complete the final usability
test and the complete instructions draft. Seth began things by merging our
individual instruction drafts and filling in the rest of the document with the
content we had previously discussed. After he had completed this, I revised the
document. I completely reformatted it, as well as made some significant changes
to the text (though in fairness, Seth did the greater share on this phase of
the project). Also, I updated our usability test; from the feedback we’d
received and from reviewing the document ourselves we only identified a couple
things which needed to change. I made these changes, and finally uploaded the
instructions draft and usability test.