The team has decided to meet Monday afternoons from 1130 to 1230, staying later as needed. The team will also be able to meet briefly after class on Tuesdays and Thursdays as needed to discuss issues that need to be resolved prior to the next regularly scheduled meeting.

Of the proposals, the team liked Scott Fadicks proposal best -“Monkey Wrench”. The proposal was approved unanimously. We are now Team Monkey Wrench.

Some concepts and ideas were discussed regarding drawing a logo, or having somebody draw a logo for the team. A proposal was put forth to find suitable clipart on the internet, and the team made a collective search. A suitable clipart monkey was found, and after discussion was approved by all of the team members. Some photo shop work will be required to adjust the image to our needs.

The team approved of putting the site up on Scott Fadick’s server. Mr. Fadick has already established space for the site as well as made plans to make accessible to the team members via the World Wide Web. It is planned that the capability to adjust and upload files will be added shortly, so that all of the team members will have access to all sections of the project. A system to save copies of changes to each file was discussed, and needs more investigation before it can be implemented.

A discussion was held to determine the best mode to display the minutes on the site, balanced with the ease of use by the team members. A rough template was sketched out, and deemed satisfactory by all team members with the understanding that it can be changed as needed to suit our needs in the future

The criterion with which each team member would best be evaluated by was discussed and prepared.

A rough draft was composed on paper by the team members. Mr. Johnson will do a more formal draft on paper for team evaluation before it is to be implemented.

Mr. Fadick will continue to set up the server for use; its immediate purpose will be to handle the prototype and meeting minutes which he will post. He will implement the prototype once Mr. Johnson completes the formal draft and it is approved.
Mr. Johnson and Mr. Fadick will implement the rapid prototype and its associated pages based upon the sketches, outline, and question pool that the team assembled during the meeting.
Mr. Trussell will work on the monkey clipart for the logo and assemble the minutes.

Organization for the rapid prototype, as well as the project itself, were discussed at length. A concern involving the use of drop down boxes versus text boxes was disussed. It was decided to hold this issue over until the next meeting as it was felt that the rapid prototype was simply to display the planned features and implementation, thus the text boxes will be fine for the interim.
A topic of concern was found in whether the Admin user (the scheduler) should be able to add their own and/or delete existing questions. The ability to change the survey questions, or add specific questions in the future that may become more pertininent, would be a powerful tool, however the implementation would be lengthy. Dr. Ouyang will be able to answer this question for us in the next class.

Mr. Fadick briefed the team on how to transfer files to and from the server. An issue involving the extension name being changed by Internet Exploer during the download was discussed. The resolution to this problem will be that the files will be htm files, thus insuring less concern for error during the transfer. Also, the backup system is in place, and in the event a file is corrupted, all changes will be reflected in the backups. A problem was found in uploading files from the University. An issue with the school's firewall is suspected.

The first version (if there is to be more than one) of the rapid prototype is complete, no project items are due. The team concluded the meeting and returned to working on individual midterm assignments.

All file up and downloads appear to be working without error.

Per Dr. Ouyang, it is a nice feature but in no way required. Given time and requirements of the project we may be unaware of, the decision to add it to the implementation will be held off.

Went over project work allocation for the upcoming week. Each member is handling a portion of the workload so that no one member is unfairly burdened.

Reviewed and improved the Use Case Specification for the Add-A-Question assignment to the project.

Went over the Use Case Specification, picked out the nouns, and broke the components down into classes. A Class Diagram was then drawn up using the components.

Went over work allocation assignments for the coming week. Additional, for team member evaluations, Scott will evaluate Pat, Pat will evaluate Ray, Ray will evaluate Scott.

Group meeting to develop sequence diagram for the Add-A-Question assignment on Wednesday.

Discussed, drew up, and printed the class diagram for the Add A Question feature.

Ray is to evaluate Scott, Scott is to evaluate Pat, and Pat is to evaluate Ray.

Reviewed the notebook and discussed improvements.

Discussed how to make the PHP server scripts into something that more appropriately reflects modularity.

Sketched out the sequence diagram for the Add-A-Question use case. It will be completed during Thursdays class since there is no lecture.

Members assigned tasks for the upcoming week.

Reviewed the database tables and module parameters, and the resulting documents, that are neccesary for this project.

As a group, developed and prepared the Sequence Diagram that lists interaction among the classes and shows calling relationships.

Reviewed and discussed the final drafts of the documents due to be put into the notebook.

Discussed peer performance issues and improvements relating to how well we are working with each other and as a whole. This was directly related to the peer evaluations we have done.

Members assigned tasks for the completion of the assignment due tomorrow and for the coming week.

Reviewed the notebook and scores from the last assignment. Disscused the need to double check the task allocation list when performing tasks so that efforts are not duplicated or missed entirely. Communication is the key to success!

Went over the upcoming assignment. Discussed modularity in PHP and various methods and techniques of testing modules and writing stubs.

Reviewed and discussed acceptance and module tests, and as a group outlined several tests for each one.

Discussed peer performance issues and improvements relating to how well we are working with each other and as a whole. This was directly related to the peer evaluations we have done.

Scott will work on the implementation of the verify-a-question in PHP. Pat will work on the module testing, Ray the acceptance testing. We all need to do evaluations on ourselves and BOTH team members.

Went over module tests and acceptance tests. Reccomendations were proposed in the tests, and several test cases will be rewritten.

Examined the PHP serverscript. Scott Fadick talked about some of the pitfalls of implementaiton with PHP, and the methods he uses to deal with databases using PHP.

Discussed peer evaluation sheets for each member, and made assignments for printing the various components for the notebook.

Examined the implementation of the project thus far, assesed the overall flow and evaluated some minor points to be modified. Scott Fadick and his PHP capable server reflect the design of the project very well, and all parties are pleased with the implementation to date.

The team did some trouble shooting on the project, and discussed methods of resolution for two items.

Examined the documentaiton regarding acceptance testing, and the documentation that we need to perform as a whole.

We each need to evaluate ourselves and the team members again. Pat will be handling the disk on CDrom instead of zip, we all need to get our files to him. Ray will be doing the User Manual. Scott will be fine tuning the PHP script.

Reviewed, tested, and made some final adjustments to the project site. It appeard to be in an excellent state of health, and the database of questions and the ability to add and delete items therein has no known anomalies.

Went over the progress to date, and what remains for the notebook that is to be turned in.

Pat Johnson presented the layout he had proposed earlier, with the files included to date. Several files need to be forwarded to him, including the completed acceptance tests.

The team went over several options for presentation, but assuming we will only be demonstrating functionality of our project, the specifics of implementation in PHP will be left out. We will simply give access to the project site without showing the source code.