Course Syllabus

Course Syllabus - CS 135
Fall 2006

Catalog Description: CS 135 Computer Science I (3 credits)
- Introduction to modern problem solving and programming methods. Emphasis is placed on algorithm development. Introduction to procedural and data abstraction, emphasizing design, testing, and documentation.
Course Objectives:
- The primary objective is to provide students with the skills necessary for "programming" and "problem solving: using a computer. The programming language will be C++. Topics covered include: program organization; fundamental C++ objects, expressions, and assignment; control constructs; library and programmer-defined functions; advanced parameter passing; and arrays.
Course Outcomes:
- Students demonstrate they can define and apply the basics of a programming language.
  - Strategies and Actions:
    - Lectures, labs, and projects covering the basic concepts of a programming language, in particular C++.
  - ABET Criteria covered:
    - (a) An ability to apply knowledge of mathematics, science, and engineering.
    - (c) An ability to design a system, component, or process to meet desired needs.
    - (k) An ability to use the techniques, skills, and modern engineering tools necessary for engineering practice.
  - Program Objectives covered:
    - (2) Our graduates will have achieved a solid understanding of concepts fundamental to the discipline of Computer Science.
  - Assessment:
    - Quizzes and exams
    - Weekly lab assignments and projects
- Students demonstrate they can design small projects. Students also design a multi-part project including topic details of their own choosing.
  - Strategies and Actions:
    - Learning program design through weekly labs and projects. Many of the labs and projects describe the problem but leave the design and implementation details to the students.
    - The final project is comprehensive, implementation spans several weeks, and is loosely defined.
  - ABET Criteria covered:
    - (b) An ability to design and conduct experiments, as well as to analyze and interpret data.
    - (c) An ability to design a system, component, or process to meet desired needs.
    - (e) An ability to identify, formulate, and solve engineering problems.
    - (h) The broad education necessary to understand the impact of engineering solutions in a global and societal context.
  - Program Objectives:
    - (2) Our graduates will have achieved a solid understanding of concepts fundamental to the discipline of Computer Science.
    - (3) Our graduates will have achieved good analytic, design, and implementation skills required to formulate and solve computing problems.
  - Assessment:
    - Lab assignments pertaining to algorithm development (pseudocode)
    - Project design reports
- Students demonstrate they can solve problems by finding and then coding solutions.
  - Strategies and Actions:
    - Learning problem solving by analyzing a given problem, finding a solution, and then coding the solution.
  - ABET Criteria covered:
    - (e) An ability to identify, formulate, and solve engineering problems.
    - (i) A recognition of the need for, and an ability to engage in life-long learning.
  - Program Objectives:
    - (2) Our graduates will have achieved a solid understanding of concepts fundamental to the discipline of Computer Science.
    - (3) Our graduates will have achieved good analytic, design, and implementation skills required to formulate and solve computing problems.
  - Assessment:
    - Quizzes and exams
    - Weekly lab assignments and final project
Course Prerequisite:
- (Math 128) Precalculus and Trigonometry
Course Arrangement:
- The course is arranged on a lecture-laboratory basis. The laboratory is a mandatory part of the class. The Teaching Assistants will outline additional lab requirements. All lab assignments, homework, quizzes, and exams are required.

Course Outline:
The following is not necessarily intended as a sequential ordering.

Topic	Chapters	Lectures(based on 50 min classes)
Introduction	1	.5
Program organization	2	2
Data types & expressions	2	4
Selection: if-else, switch	4	3
Interactive input & output	3	3
Design	---	5
Loops: for,while & do-while	5	6
Reading & writing files	3	3
Functions	6,7	6
Arrays	9	6
MidTerms		2
Final Exam		1

Texts:
- Required: C++ Programming: Program Design Including Data Structures (3rd ed.)
  by D.S. Malik -- Thomson Course Technology
- Recommended: Simple Program Design A Step-by-Step Approach (4th ed.)
  by Lesley Anne Robertson -- Thomson Course Technology
Term Specific Information:
- Instructor: Judy Fredrickson
  - Office: SEM 207, 784-1414
  - email: fredrick@cse.unr.edu
  - Office Hours: MW 4:30 - 5:30 and by appointment after class
- Class Hours:
  - Sections 005, 006 -- 5:30 - 6:45 p.m., MW -- SEM 234
- Lab Hours:
  - Sec 005 -- 5:00 - 5:50 p.m., R -- SEM 231C
  - Sec 006 -- 6:00 - 6:50 p.m., R -- SEM 231C
- Teaching Assistant:
  - Sections 005, 006
    - Brad Towle
    - email: towle@cse.unr.edu
    - Office: SEM 255A
    - Office Hours: TBA
- Important Dates:
  - Exam I -- Wednesday, October 4
  - Exam II -- Wednesday, November 8
  - Final Exam -- Saturday, December 16; 9:45 - 11:45 in WRB 2030
Assignments:
- There are two types of assignments: exercises and lab assignments. The exercises consist of practice questions which are intended to assist the student in mastering the course content. Some of these exercises may be collected and graded, but you will be informed in advance when an exercise is to be handed in.
- The lab assignments require the solutions to problems using the computer. We will be using the Windows boxes in the College of Engineering Computing Center (SEM 231). You will be instructed how to submit your lab assignments for grading.
- Late exercises or lab assignments will not be accepted.
All assignments (exercises, lab assignments and projects) and all exams (quizzes, midterms and the final exam) are to be treated as individual and not a collective effort except for some labs as described below**. A severe penalty will be given for any other assignment or exam which indicates collusion or other form of academic dishonesty. The usual penalty for academic dishonesty on assignments or an exam is failure in the course.
- You should carefully read the section on Academic Dishonesty found in the UNR Student Handbook (copies of this section are on-line) Your continued enrollment in this course implies that you have read it, and that you subscribe to the principles stated therein.
- ** Conditions of collaborative lab(project) work:
  - Lab assignments 0,1, 2 and 3 must be an individual effort (no collaboration).
  - If you wish to join efforts with ONE other individual on lab assignment 4 or later you must both sign up on the INTENT form your TA will have. Upon signing up to work jointly on lab assignments, you may do so for succeeding labs not yet assigned. Any currently assigned lab assignment must be finished individually.
  - If you wish to quit working jointly, both persons must notify by signing the INTENT form again. The currently assigned lab must be completed as a joint effort. In the event that your partner drops the class notify your TA and instructor immediately.
  - The names of both individuals are to be included on the lab assignment and
  - as part of the lab assignment each individual will include an independently completed, typed statement indicating what he/she contributed to the lab and how full understanding of the entire lab assignment was achieved.
  - It is each individual's responsibility to assure his/her full understanding of the material from each lab.
  - Any joint project will require additional design/coding/documentation information to clearly indicate a joint effort as will be described in the project description.
  - All other assignments and exams are to be completed on an individual effort basis.
- All lab assignments should be considered "open-book, take-home tests". If you (individual/lab team) need assistance with an assignment, you may consult your professor, a CS TA designated to help CS 135, your textbook, or any other textbook. You may not receive substantive assistance in any form from any other source (i.e., from other students, from computer center personnel, from paid or unpaid tutors, etc.). Any assistance you do receive is to be documented in the comment section of your code.
- The only help you may receive from other students is with syntax errors or with questions regarding the computer system. Do not show, exchange or copy code. Using another person's listing or having another person "ghost write" a lab will be considered academic dishonesty. Any indication of joint collaboration other than that defined above** will be considered academic dishonesty.

Assessment and Grading Scheme:

There will be 2 midterm exams and a final exam. All midterm exams will take place in the regular classroom. Note that the final exam is scheduled elsewhere. Makeup exams will only be allowed for medical emergencies.
There may be announced and unannounced quizzes. There will be no makeups for missed quizzes. Your two lowest quiz grades will be dropped in the final grade calculation.
Lab assignments will be collected at the start of the lab session in which they are due. No late labs will be accepted.

The final grade will be based on:

Section
Quizzes & Exercises	10%
Lab Assignments	20%
Final Project	20%
Midterm Exams	30% (15% each)
Final Exam	20%

Note: Final grades will be A through F, with no plus or minus:

A: 90%; B: 80%; C: 65%; D: 55%; F: below 55%

Note: Failure in either the programming (lab assignments and final project) component or the lecture component (exercises, quizzes, and exams) will result in failure in the course.

Disability Statement:
- If you have a disability for which you will need to request accommodations, please contact me or someone at the Disability Resource Center (Thompson Student Services - 107), as soon as possible.
Class Policies:
- You are responsible for all material covered in the lectures and in the labs. The scheduled laboratory time is mandatory. There may be announced and unannounced quizzes in class.