How to Succeed in CSS343
-
In CSS342, it was understood that students were arriving with a wide
range of backgrounds, and some allowance was made for that (modulo
CSS341). This is not the case for CSS343: everyone is assumed
to have full mastery of all prerequisite material. The gloves are off,
and the onus is on you to seek out any help you might need.
-
Read (and follow the instructions and guidelines in)
the syllabus! Your grade counts on it.
There are no excuses for not adhering to the instructions in
the syllabus.
-
The typical UW course is expected to demand approximately 2-3 hours per
week of your time, on average, outside of class for each credit hour.
This would translate into 10-15 hours/week for a 5-credit course. However,
programming-intensive courses always take significantly more time.
Plan to average more than 15 hours/week outside of class.
-
Learn about Unix. Use a reference book (maybe the one suggested in
the syllabus). It is possible that we will make significant use of
Unix-based software development tools for one or more assignments.
-
Get a C++ reference book. One is suggested in the syllabus.
-
If you need help with mathematics, make use of the
Quantitative
Skills Center.
-
When writing your specification, design, or other documents, you
must read and understand the handouts given you and then
write your documents in your own words.
-
Poorly written documents (and comments) reflect poorly on your
apparent understanding of the material and the importance you
place on this course. Make use of the
Writing
Center to help you write better. Bring them your documentation
before handing it in. We will deduct points for poorly written
documentation.
-
Think before designing and coding:
-
Your test plan should be your own. Don't just copy the
examples in the assignment handout.
-
Your specifications should accurately reflect the assignment
requirements.
Return to the CSS343 home page.