PRE- REPORT AND
COMPANY-SIGNED PROBLEM STATEMENT
Each Senior Engineering Project team will prepare
and submit a "Pre-Report" to the Project Grading
Committee (PGC), per the Senior Engineering Project
schedule. The "Pre-Report" is due soon after the first
subgroup meeting when the ideas of the project are well
in mind. This report introduces the team to report
mechanics and requirements and gets much of the detail
work out of the way which will be the basis of the later
reports. Comments from the PGC are intended to
troubleshoot the problem statement, initial direction of
the project, and preliminary report mechanics. The
"Pre-Report" consists of the following items:
cover sheet (see
example)
title page (see
example)
abstract (see example)
table
of contents (see
example)
introduction (see
example)
problem statement
(see
example)
objectives (see example)
Sample of a Pre-Report (see example)
Pre-Report Outline
A
detailed outline will be prepared for the Pre-Report,
per section 8.1, and will be reviewed with your Advisor.
Again, the outline should contain the structure and
detail that will be incorporated into the
Pre-Report. |
|
Submittal of Copies
Staple the report
securely, (do not bind) and submit 3 copies to 104
TB. Office personnel will give them to your Advisor and each
member of PGC. The PGC members will provide feedback as
comments written on your Pre-Report, and on the evaluation
form (Form PR) (see Chapter 14, Grading). Arrange a
meeting with your graders if you would like feedback
clarification.
Company-Signed Problem Statement
At the time
the Pre-Report is due, the project team will submit to 104 TB
a copy of the complete problem statement, scope of work and
deliverables, signed by the company contact to verify
the problem statement and scope of work for the project. Any
changes to the problem statement, scope of work, or
deliverables later in the semester, must be approved and
signed by the company, and a copy be kept on file with the
course chairman.
DON'T
PROCRASTINATE - THERE IS NEVER ENOUGH
TIME
|
