writing guide - 32.5

for the member in question). In this case the ’fired’ student is responsible for finding another team that will accept (or ’hire’) them. In the event they cannot find another team to join, they will be expected to perform all of the work themself. The firing mechanism is intended to deal with individuals who ’harm’ the progress of the team, not for non-participants.

32.4 DELIVERABLES

The following items are to be submitted at various stages of the project.

32.4.1 Conceptual Design

Concepts are normally communicated with sketches that make the overall design clear. Components that would be expected for this type of design are,

-Sketches should be done using normal drafting practices. A good set of sketches will include 2-D, isometric and pictorial views.

-Calculations should be provided that support the design concept.

-Electrical schematics to describe the control system.

-Block diagram to describe the control system.

-Lists of components and budgets to indicate the major parts of the system.

-Other items, such as flowcharts, are often required to clarify the design concept.

32.4.2EGR 345/101 Contract

This project involves participants from EGR 101 and 345. Although the students are at different points in their academic careers they are all considered peers, and should have equal voices in the team. To help clarify issues of differences between the EGR 101 and 345 students, a ’contract’ will be written that formalizes the responsibilities of the students in EGR 101. As with most contracts, it outlines a process that is mutually beneficial. In this case both parties are expected to benefit in an educational sense. The contract will be written in such a manner that if all requirements are satisfied work will be marked ’as-is’. In the event of a failure, marks will be deducted to hold the responsible party(s) accountable.

writing guide - 32.7

tion.

-a table of contents

-three view drawings of each significant part

-block diagram of the control system

-block diagrams showing the system architecture

-circuit schematic

-if a motion profile will be used, it should be documented

-an assembly drawing of the mechanism, including a BOM

-a budget listing each of the parts that must be purchased/acquired. Catalog pages and quotes can be used to validate the budget. In the final report, copies of receipts, or catalog pages will be required.

-a weight inventory, itemized by each part of the design

-additional calculations for mechanical design issues, such as stress that may result in failure. Normally these result in a factor of safety.

-the equations of motion for the system

-a Scilab program that verifies the operation of the system using the equations of motion.

-a C program that implements the controller as designed.

32.4.5The Final Report

The final design will follow the same structure as the Design Proposal, with the addition of the following elements.

-test results

-the drawings, calculations, etc. should be based upon the final design. It is reasonable to write a page or less about the modifications that were required, but it is a minimal/optional part of the report.

The report should concisely and clearly describe the design, as shown in the diagrams, drawings, calculations, etc. In general the format of the report is as outlined below. Sections and subsections should be numbered.

Cover page

Executive summary - one page or less that summarizes the design and results. Table of contents

Design description - this section should describe the mechanical, electrical and software design aspects. Subsections should focus on the following elements;

Drawing summary - selected isometric and assembly drawings System block diagrams

Description of control scheme, such as the motion profile Schematics