Each formal report consists of two parts: A formal written report and oral presentation, all done in teams and in the spirit of collaborative learning.
These formal reports are equivalent to "Exam 3"; see also Grading.
1. Team written reports
Students collaborate in teams to learn and to produce regular reports that must be submitted before the deadlines shown in the course calendar. Late reports will receive a grade penalty: (1) 0th - 6th hour after deadline, -10%; (2) 7th - 12th hour after deadline, -20%; (3) more than 12 hours after deadline, zero report grade (reports not accepted).
Each formal written report should have the following attributes:
- Write for others not connected with your work to read and understand and for your own use / reference in the future.
- Complete and careful documentation of all details are important.
- Reports are formal, and should be written following the methods in Writing tools, pros and cons, with the grades scaled with respect to the best report(s) produced by the class; see also Grading.
- Restate the problem in plain language, and in mathematical expressions.
- Provide detailed writeup of your methods of solution.
- Describe your computer code (if applicable), i.e., how you constructed your code, what it is supposed to receive as input data, what output can one expect from it.
- List the input data for your problem (if applicable).
- Discuss the computational results that you obtained for your problem.
- In the appendix of your report, provide the listing of your code, the listing of the input data file, the listing of the output file (if applicable).
- Make sure that your teammates proofread your report contributions.
2. Team oral presentations
There will be frequent team presentations in most class meetings. One or more teams will be selected randomly to present their solutions to selected problems using the teams formal reports. See also
Policy.
Home page: Loc Vu-Quoc