English 421: Technical Writing

 This is the final log for the Jagerbombers. It is almost time for us to disband and forth into the world with the knowledge and understanding of our project. Today in class we presented our Multimedia part of the documentation project. Cat said that we had a really good presentation. The compliment to our group was nice and appreciated. We also finished the final touches on our Mulitmedia project and submitted it via email to cat for grading. Thats all folks!!! 

~Andy... OUT 

Well, this week class was canceled on Tuesday so much did not get accomplished that day. On Thursday we were informed of new dates to turn in final drafts of our useability projects and what nots. We also worked on putting together a power point presentation for our useability project. This task took up most of the class time. Cat also proposed a meeting place for our final class get together...Scotty's I have never heard of this place but i hope that they have beer there.

~Andy 

Here is an article that i dug up on the net. Errors in documentation are always never a good idea and should always be avoided. One thing that this article mentioned is that they wondered if consumers would think of their product as of a lesser quality if its documentation contained errors. This article talks about how a company set up and ran an experiment on with unsuspecting patrons with the effectiveness of flawed documentation.

This weekend i worked on putting together a paragraph for our executive summary that we forgot to put into our white paper. I also read through the entire paper looking for errors in the paper and have made notes to correct them with the group in tuesdays class. On tuesday we went threw the paper and made the corrections to it. We also added a table of contents that was missing and fixed up a few other citation errors. On thursday made a few final touches to the white paper final draft and went on a quest to find a color printer on Purdue's campus.

During this week, our group worked together in class to on developing a persona for the next portion of the project "usability". This was interesting because we had to make up some people that would need to use our technology that we have researched. Also, we got back the answers to the questions that we sent over to the Drive Through Marketing Team. I dont think that they liked us. They pretty much said that our technology was not what they were looking for. So Cat informed us that we would just be using our imaginary friends for the rest of our project. 

I missed the group meeting on sunday because of work. My group excused me and accomodated me by sending me an email of my responsibilities for the upcoming week. Cody and I are supposed to research more on the collaborating issue and it to the introduction section that wrote up.  

~Andy 

Here is another article on how to put your white paper. I am sure that everyone is working diligently on making their white the best it can be. I liked this article because it talks about some of the marketing of the white paper and how to get it noticed. It also has some good tips on how to start off the paper as well as some things to do when you get stuck. Enjoy

~Andy 

 Here are the two memo's for our group 

This the link to the article that i found for this week. I chose this article for this week because I have been charged with the task of constructing the introduction of our white paper by my group. I figured that i should look up some things on the design of the white paper, since how i start the paper the group will have to follow suit to make it flow well. This article makes some good points that you would not often think of until you have written and read a few white papers.

This week our group was assigned on Tuesday Oct 21 the annotated bibliography section of our white paper. This segment was due on Thursday to be posted online along with a hard copy presented to Cat.