General comments on report writing:
your write-up through the Writing Center .
should be a signed statement on the contribution of each team member.
organization could be improved: table of contents, page numbers,
should some introduction of the proposed project. Reports often assumed prior knowledge
of the design. Several reports jumped into design details without
ever introducing or discussing the project or issue at hand.
should be a table comparing the original design specifications with the
achieved performance in simulation. This would highlight the
specifications and reduce inconclusive textual discussions of performance.
proposals read more like a detailed design report than a project proposal.
The project proposal should be succinct, but contain enough relevant
information to be persuasive.
all references in the text (list references in the order cited).
all axes in plots.
when appropriate: e.g., MATLAB, ARCS.
"I", "You" (We is okay).
legend on graphs with multiple plots.
Make sure the plots can be clearly distinguished (use circle or x
overly informal style, e.g., "insane", "beefy"
etc. Too much humor is also
to Ben as "the course TA, Ben Potsaid", rather than just
creating new words such as "guesstimate".
several design alternatives and justify your choice.
analysis should consider sources and estimated amount of uncertainty in the
any patent search if appropriate.
design specification should be clearly stated.
tables for specification, simulation result comparison, etc.
and include references on control design.
simulation results in task space (e.g., actual target tracking error)
For progress report evaluation format, see the evaluation form.