Freshman Clinic I
Frames (Back to main page with navigation bar)
Meeting Times and
Place:
|
|
Day/s |
Time |
Room |
|
Lectures (Section 6) |
Monday |
|
Rowan Hall Room 239 |
|
Laboratory (Section 6) |
Wednesday |
|
Windows Lab: 204/206 Unix Lab: 221 Other: TBA |
Synopsis
ENGR 01101.................... 2 semester hours
Introduction to the practice of engineering through application problems drawn from engineering disciplines chosen to amplify work drawn from supporting courses. Survey of technical communication formats, analytic tools, computer-based tools, and other topics. Introduction to design; engineering ethics; teamwork.
Texts
Introduction to Engineering Design and Problem Solving, 2nd Edition.
By Eide,
Freshman Engineering Clinic I and II, McGraw-Hill/Primis, ISBN 0-390-58690-0
Schedule and Course Materials
September 5: Slides, Assignment
September 11, 13
September 18: Harriet Hartman survey in
Auditorium, September 20:
September 25, 27: Project
October 2, 4: Project
October 9, 11: Project
October 16, 18: Segway video
October 23, 25: Midterm
October 30, November 1: Project
November 6, 8:
Project
November 13, 15:
Normal for Us
video
November 20, 22: Project
November 27, 29:
Project
December 4, 6: Project
December 11, 13:
Monday Lab, Wednesday Final Presentations
December 18: Final Presentations
|
End
of Semester Schedule |
|
|
||||
|
Week |
Monday |
Wednesday |
|
|||
|
4-Dec-06 |
Lab |
Lab |
|
|||
|
11-Dec-06 |
Lab |
Presentations |
|
|||
|
18-Dec-06 |
Presentations |
|
|
|||
|
|
|
|
|
|||
|
|
|
|
|
|||
|
Team
Deliverables |
|
|
||||
|
13-Dec-06 |
Final Report |
|
|
|||
|
13-Dec-06 |
Final Presentation
file |
|
||||
|
|
|
|
|
|||
|
|
|
|
|
|||
|
Individual
Deliverable |
|
|
||||
|
13-Dec-06 |
Individual Report (see
below) |
|
||||
|
|
|
|
|
|||
|
|
|
|
|
|||
|
Presentation
Schedule |
|
|
||||
|
13-Dec-06 |
8:00 AM |
8:30 AM |
Preparations |
|||
|
13-Dec-06 |
8:30 AM |
9:30 AM |
Jet |
|||
|
13-Dec-06 |
9:30 AM |
10:30 AM |
PVC Surprise |
|||
|
18-Dec-06 |
10:15 AM |
11:15 AM |
Pooky |
|||
|
18-Dec-06 |
11:15 AM |
12:15 PM |
Ultima Cannon |
|||
|
|
|
|
|
|||
|
|
|
|
|
|||
|
Individual
Report |
|
|
|
|||
|
Format: |
Same as other reports |
|
||||
|
Topic: |
Your contribution to
the Project |
|
||||
|
Additional: |
Team Assessment |
|
||||
|
|
|
|
|
|||
|
|
|
|
|
|||
|
The
Team Assessment |
|
|
||||
|
Purpose |
Planning composition
of teams for FC II |
|||||
|
IMPORTANT |
Make a separate page;
will be shredded |
|||||
|
Format: |
Click
here for the form |
|||||
|
Address: |
Contribution, issues,
kudos |
|
||||
|
Conclusion |
Want as teammate
again: Yes/No |
|
||||
Format of Reports
The reports must have a minimum of four elements:
Cover Sheet
Executive Summary
Body
Results and Conclusions
If you need data for completeness that is not appropriate
for the body of the report, such as measurements used in a curve that is a
figure in the body, you must add an Appendix to your report. Any data in the Appendix must be referred to in
the Executive Summary, Body, or Results and Conclusions section. An appropriate place for this reference is
the paragraph that refers to the figure with the plot, or the caption of the
figure.
The format and content of each of these items is summarized below.
Cover Sheet
The Cover Sheet must include these items:
Project title .
Course.
Instructor.
Team Members.
Date Due and, if different, the date turned in.
If the report is written by a single team member, the author must be identified. Other information, such as the team name, team logo, Rowan logo, etc. may also be on the title sheet if appropriate.
Executive Summary
The Executive Summary must include these elements:
Background & Overview
Description
Status and Conclusions
These elements are in thumbnail form. In an Abstract, they must usually be very brief to meet a word count goal or restriction, usually 50 or 100 words. In an Executive Summary, a page or more is normal, but remember that this is a terse summary of the entire report and brevity, accuracy, and ease of overall understanding is paramount. Write this section last.
One thing that you must do in the Executive Summary is make it a terse summary of the entire report. Don't just make it an introduction with no Conclusions. Put the Introduction in the Body. Make sure that you have Requirements, Description, and Conclusions in the Executive Summary. Figures and references are OK for an Executive Summary but not for an Abstract; here we want an Executive Summary.
Project Description
This is the body of your report. It may contain more than one element, such as Introduction, Project Description, Project Schedule, etc. Some elements, such as Project Schedule, may be a Gantt chart with a paragraph or two and be included without a separate major section heading for the report.
The body of the report must contain these elements.
Requirements or Objective tells the reader what
the project is intended to accomplish.
Restrictions or Limitations tells the reader
what bounds the effort of accomplishing the project, such as the number of
Joules stored in the cannon when ready to fire, the deadline for completion,
resources available in terms of people and materiel, etc.,
Risk and Contingences tells the reader what the
uncertainties in the project are.
Normally you will list the top three issues. The contingencies are what you will do if one
of the problems stops you from completing the project within the restrictions
and constraints.
Equipment and Parts tells the reader what
material is needed to complete the project.
Include information on what is borrowed, donated, purchased, provided by
the lab, etc. and give appropriate credit for loaned or donated materiel or
equipment.
Resources and People tells
the reader who did what, what the materiel cost, etc.
Approach and Theory tells the reader why you
think that the project will work, and why it will meet the project requirements
or goals and objectives.
Procedure, Plan, Schedule (Gantt chart) tells
the reader how you plan to execute the project.
Results
The Results and Conclusions section tells the reader what
the project accomplished, what you learned, and what these lessons will help
you do better in the future. Spend
little or no time with negativity because the reader doesn't want to see that,
and you are writing this to a reader who wants to know what are the
requirements, limitations, equipment and other resources, schedule, risk and contingencies,
and results with lessons-learned. If you
didn't finish or your project didn't meet requirements or expectations, tell
what you learned from this and what you would do different if you know then
what you know now. This section must
include
Drawings of your project. These are the drawings that you built to.
Summary of Analysis. This is the result of the analysis you
reported in the Body.
Results and Conclusions. This tells the reader what your project
did. Include the lessons-learned here.
Appendix
If you have data or information that supports your project,
such as specifications of Schedule 40 PVC Pipe, but isn't appropriate for the
body of the report, you include it in an Appendix. This element is optional, and is included
when appropriate. Any items in the
Appendix must be referred to in the Executive Summary, Body, or Results of the
report. If you don't refer to a table or
other Appendix item, then you should consider deleting that item from the
Appendix. Items that may appear in an
Appendix include:
Tables that support graphs or figures in text.
Excel printouts.
Program listings.
Hand drawings.
Drawings from the project that were superseded
by later drawings as the project evolved.
Detailed derivations or other long explanations that
would amount to a digression in the body of the report.
Data sheets of items in your materiel list that are not readily available, such as for a recently
released plastic or electronic component.
The Final Deliverables
The Final Report
Your Final Report should be written by the entire team. Different parts may be written by different team members, or you may write it together as a team. A primary author may or may not be noted on the cover sheet. When you describe Resources, tell what each team member contributed to the project.
The Individual Report
Your individual report focuses on your individual contributions to the project. The team members are on the cover sheet, but you clearly identify yourself on the cover sheet as the author. Focus on what you did. Confine your remarks about teammates to the Team Assessment. The Individual Report should be only a few pages. You may refer to the main report to include information there without repeating it in your Individual Report.
The Final Presentation
A very good way to put together your Final Presentation is to write your Final Report, and model the flow of your Final Presentation after your Executive Summary. It must have all the elements of the Final Report but it does not have to have the detail of the Report. You may refer to the Report for things like design evolution as the project proceeded or Appendix material. Remember, you have only about 50 minutes, and there will be questions and discussion in the last 10 minutes. With the common rule-of-thumb of three minutes per slide, this is about 18 slides. If your Final Presentation is much shorter or longer than that, you need to look at it. Rehearsals of your presentation are encouraged.
Each member of the team should present the slides on their contributions to the project. Every team member must present at least one slide.
Don't forget these critical slides:
Your last drawing, the one that you built your
project to.
The schedule, in the form of a Gantt chart.
A Results and Conclusions chart.