This week I created our team website in Google Sites. While doing so I integrated a Google Calendar that will reflect important project dates such as team meetings, customer meetings, deadlines, and presentation dates. The calendar is viewable by anyone and can be edited by any of the team members. The calendar is accessible here. Under the Project tab you will see a "Files" link, this page has a Google Drive folder mapped that will house any important project documents that we need to share. These files can be found here.
Week of February 6 - February 10:
This week we were given read/write access to an ssh folder than contains all of the code we need to work with. I was able to connect and view said files. It seems that we will mostly be working with one PHP file that consists of mainly MySQL calls, HTML, PHP, and some JavaScript. We met with our customer on Wednesday and nailed down the design scope and decided that by February 17th we would have some mock up designs done for the new menu bar. This coming week we plan to bring those designs to life, code them and let our customer view them before our next meeting on February 22nd.
Week of February 13 - February 17:
This week I worked on one of the two prototypes we submitted to our customer for their review. The prototype was to be a menu bar that would improve navigation on the company's existing website. We used the Cloud 9 development platform to create the menu bar so that we could work together and collaborate. We used HTML bootstrap as the backbone for this particular design. After the prototype was finished we published the it so that our customer could interact and test the menu bar to see if it will meet their needs. We have a meeting with our customer scheduled for this coming Wednesday to talk through the prototypes and decide which direction we need to go next.
Week of February 20 - February 24:
This week we met with our customer at their office on Wednesday and talked through which direction they would like to go with the two different prototypes we delivered the week before. We are now more clear on what they are wanting and plan to go to work coding this next week. Aside from customer interaction, we have scheduled our presentation meeting with Presentation U for Monday. We worked to finished the design and presentation so that we are prepared for our meeting tomorrow. There are still some finishing touches to do on our presentation that we plan to iron out after we meet with Presentation U. Our midterm presentation is scheduled for next Monday during our normal class time.
Week of February 27 - March 3:
This week we met with Presentation U and went through our midterm presentation with them. Prior to this meeting I rehearsed my part of the presentation so that I would be better prepared for our meeting. They gave us some very good tips on how to improve our presentation after seeing it. Since that I have spent time improving how I will display and present my portion of the presentation based on their recommendations. We present on Monday, March 6th during the 12pm lecture. Going forward we continue to work on integrating our menu bar design with the existing code.
Weeks of March 6 - March 17:
This week we met with our customer and will continue to work towards implementing our final prototype into the existing code. I will be out of town for Spring Break and away from my computer so I will not be able to work on our project until I return to Lexington after break. After spring break we plan to meet as a team and work towards implementing the prototype that our customer has approved before our next joint meeting with our customer.
Weeks of March 20 - March 24:
This week I have tested the usability of our site which is still under development to insure that there are no functionality problems that go unnoticed. I was out of town for a university sponsored and excused trip Thursday - Sunday where I did not have internet access, so I was unable to make much progress on the project. We did discuss our plan as a team going forward. Next week I plan to work on creating our testing document so that when it is time to begin testing we will have a plan in place and a document to record our findings as we go.
Week of March 27 - March 31:
This week we met with our customer on March 29th. We discussed how we plan to go further on the project as we near the end of the semester. This week I have taken the information on our Testing page and have begun to create a testing document where we will document each test that we run. In the document there will be columns for test descriptions, what we entered to run the test, expected outcome and actual outcome for if the test passed or failed on Google Chrome, Mozilla Firefox, Apple Safari, and Apple iPad Safari. If the test fails, we will document that and make a note when the issue has been resolved. We meet with our professor on Monday, April 3rd to discuss our testing plan.
Week of April 3 - April 7:
This week I finished our testing document that we will use during the testing phase of our project. It houses a place to mark whether the test pass or not and if the test did not pass there is a place for comments so that we can document what happened as opposed to what should have happened. I have also worked on parts of our final report. This next week I plan to begin writing the user manual for our project that will be included in the final report at the end of the semester. We met as a team on Saturday morning to get items ready for our code review on Monday morning with our professor.
Week of April 10 - April 14:
This week I have worked on testing our website and recording my findings in the testing document that will be included in our final report. Aside from that I have practiced my portion of our final presentation for our practice tomorrow morning (Monday) in the Davis Marksbury building. I will be touching on some Then vs Now Cumer Ideas and Initial Assumptions we had made about the project. I'll also speak briefly about some vital lessons we learned along the way, lessons that we can take with us into the industry after graduation. Finally, I will wrap up by hitting on some future enhancements that could be made to our project after we are finished and how the project will be maintained after our time with it has come to an end.
Week of April 17 - April 21:
This week I practiced my part of our final presentation. I also made some changes to the the slides I will be presenting to match the changes recommended by our instructor. We presented as a team to our instructor on Monday afternoon as a practice. We plan to present using Microsoft Powerpoint instead of Google Slides due to Powerpoint's presenter view feature being more stable.
Week of April 24 - April 28:
We had our final presentation this week that seemed to have gone well. Our customer was pleased and we were as well. Next week we will deliver the final project to our professor and customer.