Gate 4 Group 27 2012

From GICLWiki
(Difference between revisions)
Jump to: navigation, search
(Introduction)
(Cause for Corrective Action)
Line 3: Line 3:
  
 
==Cause for Corrective Action==
 
==Cause for Corrective Action==
 +
During Gate 3, the plan of action had worked out well, and the changes made after Gate 2 proved to be useful.  Consistently throughout the project, we have been using email as the main source of communication for allocating tasks, and for describing the overall plan for the project.  Email was also used to give a record of meeting times.  Texts and phone calls were used for more immediate communication, in particular with regards to meeting attendance.  As for planning the project, deadlines were set for each section ahead of the actual due date of the project, so that there would be time for revisions.  Another thing that was consistent throughout the project was that one person set up the Wiki page, complete with headlines and titles, so that the whole page would be more logically ordered and more cohesive throughout.  This also prevented redundancies, as well as out of place information.  These practices, which were done throughout the project, have proven to be very effective in creating a thorough report for the drill.
  
 
==Product Reassembly==
 
==Product Reassembly==

Revision as of 22:09, 26 November 2012

Contents

Introduction

In Gate 4, we will reassemble the drill, and discuss in detail the complexity of reassembly. We will also discuss a mechanism of the drill that is used to generate a specific motion. In addition, we will suggest 3 system changes, keeping the GSEE factors in mind when considering changes.

Cause for Corrective Action

During Gate 3, the plan of action had worked out well, and the changes made after Gate 2 proved to be useful. Consistently throughout the project, we have been using email as the main source of communication for allocating tasks, and for describing the overall plan for the project. Email was also used to give a record of meeting times. Texts and phone calls were used for more immediate communication, in particular with regards to meeting attendance. As for planning the project, deadlines were set for each section ahead of the actual due date of the project, so that there would be time for revisions. Another thing that was consistent throughout the project was that one person set up the Wiki page, complete with headlines and titles, so that the whole page would be more logically ordered and more cohesive throughout. This also prevented redundancies, as well as out of place information. These practices, which were done throughout the project, have proven to be very effective in creating a thorough report for the drill.

Product Reassembly

Mechanisms

Design Revisions

Personal tools