Blogs

Kings Documentation Individual Blog 1

Last week our group met to discuss and type the proposal. We also decided on our schedule for the following weeks ahead. I provided some input on the steps for the game of Kings and I tested some of the steps during our meeting as well. For this week I will contribute to the storyboard and the overall presentation for Wednesday.

Origin 6.1- Individual Blog Week of 4/13

This week:

-presented storyboard- need to format visuals

-practiced with program

-meeting on sunday to create documentation and plan testing

Individual Blog: 4/17/09

This past week, we finished and presented our story board.  With it's completion, we now have a fairly complete set of screenshots to use in our Documentation.  We now begin the task of writing the Documentation rough draft, due next week.  Because we were so thorough on our story board, creating the draft shouldn't be too difficult.  Lastly, we have already scheduled our usability testing and reserved a room.

Starcraft Documentation Individual Blog 2

I wrote most of the text for our storyboard this week and presented it in class.  I've also begun working on the documentation paper.  I've written a few introductory paragraphs covering some basic information that will be used in the documentation. We're focusing on setting up a very defensive base to hopefully allow the users to survive rushed attacks from an AI computer opponent.  We're also only covering the initial setup and will have to convinve people to stop playing then during the usability testing.

17Apr09 Individual Contribution to DesignWorkshop Lite Group

This week the group produced a storyboard detailing how the tutorial will proceed and what the tutorial will describe.  I was responsible for producing screenshots for each slide on the storyboard presentation, and I initiated the revision process for the storyboard presentation as a whole.

Week Two: Individual Blog

This week I was able to play around with the program more in order to become more acquainted with the steps we are going to document.  Since I was very unfamiliar with the program, this was a necessary action to take.  Also, this allowed me to figure out other parts of the program that we can insert into the documentation if we need to lengthen the documentation.  I am ready to now start writing the documentation on Saturday.

Origin 6.1: Week Two

  • When you met and where:  we only needed to meet in class this week because we got all of the storyboard work done last Friday.

myPurdue Documentation Individual Blog - 3

I took the screenshots for our project last night. I edited the screenshots today to remove any of my personal information that I want to protect. I used a red box to set off the steps we need for emphasis. Usually, my mouse arrow is not too far away from the item that needs focus. I then uploaded the screens to our Google site for the project. There is an Easter Egg in the screens. I wonder if anyone will find it.

Documentation StarCraft Individual: Blog 3

This week so far I have done some editing of our storyboard ideas as well as helped put the entire storyboard together.  Also I have begun the opening and closing surveys for the usability testing and ran a trial run of our documentation to see how well it worked. 

Documentation StarCraft Group: Meeting 5

Our group met on Tuesday April 14th in the Beering building computer lab.  The members of the group present were Liz, Brett, and John and Hu was late for unknown reasons.  During this meeting we completed our storyboard and had Liz run through the instructions to test them out.  Some problems were discovered and mroe detail will be added to the rough draft of our documentation in order to cover these issues at a later date.  The goal for the next meeting will be to produce the rough draft as well as begin the usability scheduling.