CS 135: Computer Science I
http://www.cse.unr.edu/
cs135
CS 135, Computer Science I
Lecture+Lab: (3+1)
Credit(s): 3
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. (Formerly CS 201; implemented Spring 2005.)
Prereq(s): MATH 128 or satisfactory score on readiness exam.
This course introduces students to computer science. The course
provides students with the skills necessary for programming and
problem solving using a computer. We will use the C/C++ programming
language and cover the following topics.
- Program organization
- Expressions
- Assignment, selection, and iteration
- Functions and parameter passing
- One and Two Dimensional Arrays
The course has two components: Lecture and Laboratory. Both lecture
and lab components are mandatory. Note specifically that the
laboratory component is mandatory. All assignments, homework, quizzes,
and exams are required.
- Required: C++ for Engineers and Scientists
by Gary J. Bronson. Publisher: Thomson Course Technology
- Exam 1: Week of March 3, 2008
- Exam 2: Week of April 7, 2008
- Final Exam: Saturday May 10, 2008 from 9:45 - 11:45 in WRB 2030
There are two types of assignments: programming assignments and
exercises. Exercises consist of practice questions intended to assist
students in mastering 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.
Programming assignments require writing C/C++ programs to solve
problems. You will be using windows and linux boxes in the Engineering
Computing Center (www.ecc.unr.edu) in SEM 231. Each programming
assignment will come with submission instructions.
We tentatively plan for the first set of assignments to culminate in a
very simple computer game. Near the end of the semester you
will (probably) build another game.
- Late programming assignments or exercises will not be accepted
- Exams are individual efforts. A severe penalty will be given for
collusion or other form of academic dishonesty. The usual penalty for
academic dishonesty on assignments or an exam is failure in the
course.
- Carefully read the section on Academic Dishonesty found in the
UNR Student Handbook (copies of this section are on-line at
http://www.unr.edu/stsv/acdispol.html ) Your continued enrollment in
this course implies that you have read it, and that you subscribe to
the principles stated therein.
- The first set of about five (5) assignments are individual efforts. The
rest can be done in groups of two (pairs). The rules for pairing up and
working on assignments will be posted on the class website.
- For individual assignments, do not show, exchange, or copy code.
Using another person's code or having another person "ghost write" a
lab will be considered academic dishonesty. For pair group
assignments, if you are in a pair group do not show, exchange, or
copy code outside your group.
- All lab assignments should be considered "open-book, take-home
tests." If you need assistance with an assignment, you may consult
your professor, a CS TA designated to help CS 135, your textbook, or
any other textbook. Any assistance you do receive from other sources
is to be documented in the comment section of your code.
- Students will be assigned letter grades. Your grade will be one of A, B, C, D, or F. We will use the +/- grading system.
- A:
90%; 80%
B
90%; 70%
C
80; 60%
D
70%; F: below 60%
- There will be a number of programming assignments. No late
assignments will be accepted.
- There will be two midterm exams and a final exam. Midterms take place
in your regular classroom.
- The Final Exam is Saturday May 10, 9:45 - 11:45 a.m. in WRB2030.
- There will be announced and unannounced quizzes.
- Note: Failure in either the programming (assignments and
final project) component or the lecture component (exercises, quizzes,
and exams) will result in failure in the course.
Your final grade will be based on:
| |
|
| Item |
Final Grade Percentage |
| |
|
| Midterm exams (15% each) |
 |
| Assignments |
 |
| Final Project |
 |
| Quizzes and Exercises |
 |
| Final Exam |
 |
This outline is not in order. For example, we will start covering functions on the first day.
| |
|
|
| Topic |
Chapter |
Lectures (based on 50 minute classes) |
| |
|
|
| Introduction |
1 |
5 |
| Program Organization |
2 |
2 |
| Data types and Expressions |
2 |
3 |
| Selection: if-else, switch |
4 |
3 |
| Interactive input and output |
3 |
1 |
| Design |
... |
5 |
| Loops: for, while, do-while |
5 |
6 |
| Reading and Writing files |
3 |
3 |
| Functions |
6,7 |
6 |
| Arrays |
9 |
6 |
- 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 programming 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:
- (c) An ability to design a system, component, or process to meet desired needs.
- (e) An ability to identify, formulate, and solve engineering problems.
- Program Objectives covered:
- (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
- Project design documents
- 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.
- Program Objectives covered:
- (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 programming assignments and projects
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.
If we need to communicate with the class as group we will post a
message on our class web page. You are required to check the class web page
and your email every day.
CS 135: Computer Science I
This document was generated using the
LaTeX2HTML translator Version 2002-2-1 (1.71)
Copyright © 1993, 1994, 1995, 1996,
Nikos Drakos,
Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999,
Ross Moore,
Mathematics Department, Macquarie University, Sydney.
The command line arguments were:
latex2html -split 1 syl
The translation was initiated by CS 135 Class Account on 2008-01-21
CS 135 Class Account
2008-01-21