CSS 342A: Mathematical Principles of Computing
Autumn 2007 MW 330-535pm at UW1-041
Prof. Munehiro Fukuda

Professor:

Course Description:

Prerequisites:

Grading:

Course Work	Percentage	Achievements	Corresponding Numeric Grade
Midterm Exam	25%	90s	3.5 -- 4.0
Final Exam	25%	80s	2.5 -- 3.4
Prog. Assignments 1 - 7	28% (4% each)	70s	1.5 -- 2.4
Quizses 1 - 4	12% (3% each)	60s	0.7 -- 1.4
Labs 1 - 7	7% (1% each)
In-Class Exercises 1 - 4	4% (1% each)
Total	101% (including 1% bonus credit)

All homework assignments are graded in accordance with the corresponding grading guide which you can see through the class website. The key answer will be made available to you through ePost when you receive your graded work. You have a right to discuss about regrading your work, which must be however done within a week after you have received your grade. Regrading will be discussed thoroughly based on the grading guide and key answer.

Textbooks:

1. Data Structures and Problem Solving Using C++, Second Edition, Mark Allen Weiss, Addison-Wesley, 2000.
2. Discrete mathematics and Its Applications, Sixth Edition, Kenneth H. Rosen, McGraw Hill, 2007.
3. A C++ book of your choice.

Some C++ Books:

• C++ How to Program, Fourth edition, H.M. Deitel and P. J. Deitel, Additon-Wesley, 2004.
• The C++ Programming Language, Third edition, Bjarne Stroustrup, Addison-Wesley, 1997.

References:

• Effective C++: 55 Specific Ways to Improve Your Programs and Designs, 3rd edition, Scott Meyers, Addison-Wesley, 2005.
• More Effective C++ 35 New Ways to Improve Your Programs and Designs, Scott Meyers, Addison-Wesley, 1996.
• Thinking in C++, Volume 1 and 2, Bruce Eckel, Second edition, Prentice Hall, 2000 and 2003.

Data Structure Books:

• Data Structures and the Standard Template Library 1st edition, William J. Collins, McGraw-Hill, 2003.
• Applied Data Structures with C++ 1st edition, Peter Smith, Jones and Bartlett, 2004.
• Data Structures and Algorithms in C++ Michael T. Goodrich, Roberto Tamassia, and Divad M. Mount, John Wiley & Sons, 2004.

Policies:

Both hard and soft copies of assignment work are due at the beginning of class on the due date. No late submisions will be accepted. Except for special circumstances such as medical and other emergencies, in which case you must present a written proof to me. Barring emergencies, the professor must be informed before the assignment due date. Note that disk crash is not considered as an emergency.

Laboratory work and in-class exercises: This series of work will be done by a group of students. At the end of each session, each group is supposed to turn in a short report that describes an answer and lists all group members' names. If you miss a session and still hope to make it up, you need to work on its topic by yourself and turn in a report with a written proof of your emergency.

Exams and quizses: Each quiz will be given from the scope covering its previous non-turn-in writing exercise and in-class exercise. It will be given for the first 20 minutes of the class. So, don't be late. Midterm and final examinations cover weeks 1 - 5 and 6 - 10 respectively. All quizes and examinations will take place in the same classroom. Niether make-up exams nor quizzes will be given unless you inform me of your medical/family/business emergency.

Special needs: To request academic accommodations due to a disability, please contact Disabled Student Services (DSS) in Library Annex Building, Room 106, (email dss@uwb.edu, TDD: 425-352-5303, and FAX: 425-352-5444). If you have a documented disability on file with the DSS office, please have your DSS counselor contact me and we can discuss accommodations.

Course Goals:

Programs:

• Harcopy must include your program specification, explanation, program listing, execution output (and discussion/verifications/evaluations if required). Write your name on top of paper, right hand corner. Use a typewriter font (e.g. courier new) for all.

• Softcopy must be a tar-archived file that includes only your source code. Your code should compile and run properly using g++ under linux since the professor (and his grader) test them only using g++. Upload your tar-archived file through CollectIt: Don't email your softcopy to me.

Syntax errors and run-time errors without much output yield a low grade. Run-time errors (occurring after the majority of the output), or incorrect answers will result in a significant number of points being deducted from your grade. Otherwise, you will be graded on documentation (clarity and completeness), style (indentation, use of blank lines and spaces), meaningful identifier names, organization of your program (modularity, design), efficiency (no useless, unnecessary, or unnecessarily complicated code), output (clarity and format), the overall readability of your entire program, and following directions.

Read assignment.html for more details.

Sample code;

Catalyst EPost (Message Board):

Topics covered and tentative 342 winter schedule: