The final week of the project was most likely one of the busiest for the documents and testing team. Most of my time was spent working on the validation portion of our report. The page went through CSS validation through the W3C CSS validator Wednesday evening. One error and a few questionable browser specific issues were discovered. I reported these problems to the coding teams. As of Friday morning the validation service gave our CSS code a clean bill of health.

This week was probably the least productive period for the documents and testing team. As of now we have only a single page to work with, so adjusting the design plan is no more of a possibility than when we had the static .JPEG mockup of the site. Once the pages are all built and links ready I will be able to run them through CSS and HTML validators to make sure the coding is sound. After that I will send my audience survey out and wait for feedback on how easy or difficult it is to update the site. The next step will be to build the change document.

Due to Thanksgiving break this week was notably less productive than others during the course of this project. Due to a lack of progress of the front-end coding team we were unable to begin work on a change document or make any real adjustments to the design plan. I spent Wednesday reeducating myself on coding in HTML and CSS after being approached by one of the members of the organization team about helping the front-end team get up to speed.

This entire week has been dedicated to updating the design plan in order to meet the Wednesday deadline. My specific responsibility was the board members section. On Monday I spent most of the class period, and time that evening, working on making changes to my section of the design plan. Most of the changes made were cosmetic as no new information came out of the coding teams. After the plan was updated, I, along with the rest of the team, individually revised the entire document.

The documents and testing team spent the entirety of this week working on creation of initial design plan elements and a draft-testing plan. Personally I was in charge of working on the “board member “ audience of the website. After browsing the CFRC website I found the current board member list. This allowed me to gain a better understanding of their collective careers, as they are listed on the site. This background information, as well as some searching on some board member’s employer homepages led to the audience, context, arrangement, and strategies sections of my portion of the analysis.

http://www.concertblast.com/Show_68-John_Mayer_Concert_Review.mp3

Purpose – This podcast gives John Mayer fans and potential Mayer concertgoers a feel for the happenings of one of his concerts.

Audience – John Mayer fans are targeted by this podcast, especially those who want to attend/have attended his live show.

Context – This podcast is located on the “Concert Blast” website, a site dedicated to podcasting about live concert experiences.

Medium – This podcast is an audio.mp3 file that can be played on the internet or downloaded to your desktop.