Syllabus

CS 105: Logical Basis of Computing

Winter 2012

Meeting Times

Lect: 2:00 - 2:50 M&W, HB 116

Labs: 2:00 - 2:50 Tu&Th, HB 203, HB 209

Instructor

Dr. Razvan Andonie, HB 219-B, Office hours

TA

HB 203: Kyle Kinkade, kinkadek@cwu.edu

HB 209: Zachary Haberman, habermanz@cwu.edu

Text

Visual Basic 2010 - How To Program, Deitel & Deitel, Prentice Hall, 2011.

 

Grading

Class Participation

30%

Labs 0 & 1

0% each

Labs 2, 3, 4, & 5 (individual)

10% each

Final Project (team of two)

20%

Test (open book, open notes)

10%

 

Grading Scale

95 - 100

A

90 - 94

A -

87 - 89

B +

83 - 86

B

80 - 82

B -

77 - 79

C +

73 - 76

C

70 - 72

C -

67 - 69

D+

63 - 66

D

60 - 62

D -

0 - 59

F

Objectives: The basic objective of this course is to assist non-computer science majors in understanding problem solving in the context of computer applications. This will include basic problem solving and algorithm development and an introduction to Visual Basic as the vehicle to demonstrate problem solutions including the areas of: the representation of algorithms as computer programs; data; decision and control; and inherent sources of error.

Upon completion of this course, students will demonstrate the ability to:

Software: We use Microsoft’s free Visual Basic 2010 Express Edition. The Visual Studio Editions are included on the DVD bundled with the textbook and can also be downloaded from www.microsoft.com/express/.

Resources: VB Helper Website

 

Important: Late submission of assignments is generally not accepted. No partial credit for late assignments will be offered.

Schedule

Date

Topics

Readings – Items due

Jan 4

Introduction

Syllabus

Jan 5

Introduction to Labs: Lab 0

Jan 9

VB 2010 Express: Using Visual Programming to create a simple program that displays text and an image

Ch. 2

Jan 10

Introduction to Labs: Lab 0

Lab 0 due today, at the end of the class

Jan 11

Introduction to VB Programming:  Programmatically Displaying Text in a Label

Sect 3.1 – 3.2

Jan 12

Introduction to Labs: Lab 1

Jan 16

No School, M. L. King

Jan 16

Jan 17

Introduction to Labs: Lab 1

Lab 1 due today, at the end of the class

Jan 18

Introduction to VB Programming: The Addition Program

Sect 3.3 – 3.4

Jan 19

Problem Solving: Lab 2 and Lab 2 Rubric

Case Study: Simple Tuition Calculator

Watch: http://www.youtube.com/watch?v=CHGqJOoILVA&noredirect=1

Jan 23

Introduction to VB Programming: Memory Concepts, Arithmetic, Decision Making

Sect 3.5 – 3.7

Jan 24

Problem Solving: Lab 2 and Lab 2 Rubric

Lab 2 due today, at the end of the class

Jan 25

Solve a Problem: Exercises 3.7 & 3.8

Jan 26

Problem Solving: Lab 3 and Lab 3 Rubric

Jan 30

Solve a Problem: Exercises 3.9 & 3.17

Jan 31

Problem Solving: Lab 3 and Lab 3 Rubric

Lab 3 due today, at the end of the class

Feb 1

Introduction to Problem Solving and Control Statements: Control Structures

Sect 4.1 – 4.7

Feb 2

Problem Solving: Lab 4 and Lab 4 Rubric

Case Study: Example IF statement

Feb 6

Introduction to Problem Solving and Control Statements: Repetition Statements, Compound Assignment Operators, The Class Average Problem

Sect 4.8 – 4.10

Feb 7

Problem Solving: Lab 4 and Lab 4 Rubric

Feb 8

Introduction to Problem Solving and Control Statements: Nested Control Statements, Examination-Result Problem

Sect 4.11 (you may skip Sect. 4.12)

Feb 9

Problem Solving: Lab 4 and Lab 4 Rubric

Lab 4 due today, at the end of the class

Feb 13

Introduction to Problem Solving and Control Statements Part II: For …Next Repetition, Interest Calculator Application

Sect 5.1 – 5. 4

Feb 14

Problem Solving: Lab 5 and Lab 5 Rubric

Case Study: Example DO WHILE statement,
Case Study: Example ComboBox, FormLoad statement

Feb 15

Introduction to Problem Solving and Control Statements Part II: Nested Repetition, Select…Case

Sect. 5.5 – 5.6

Feb 16

Problem Solving: Lab 5 and Lab 5 Rubric

Case Study: Example CheckBox, RadioButton, global variables statement,
Case Study: Example File I/O, Arrays

Feb 20

No School, Presidents Day

Feb 21

Problem Solving

Lab 5 due today, at the end of  the class

Feb 22

Introduction to Problem Solving and Control Statements Part II: Do…Loop While, Do…Loop Until, Exit, Continue, Logical Operators

Sect. 5.7 – 5.10

Feb 23

Final Project

Final Project Prospectus

Feb 27

Introduction to Problem Solving and Control Statements Part II: Dental Payment Calculator, Exercise 5.7

Sect.5.11

Feb 28

Final Project

Final Project

Feb 29

Methods: Subroutines, Functions

Sect 6.1 – 6.4 (you may skip Sect. 6.5 & 6.6)

Mar 1

Final Project

Final Project

Mar 5

Methods: Passing Arguments, Scope

Sect 6.7 – 6.8

Mar 6

Final Project

Final Project due today, at the end of the class

Mar 7

Review

Mar 8

Final Discussion on Projects

Mar 16

Test (open book): noon – 1:00

 

Honor Code: All work turned in for credit, including exams and all components of the project, are to be the work of the student whose name is on the exam or project. For all project components, the student can receive assistance from individuals other than the instructor only to ascertain the cause of errors. Thus you can get help if you need it to figure out why something doesn't work. You just can't get help from anyone, other than the instructor or TA, to figure out how to make something work. All solutions turned in for credit are to be your individual work and should demonstrate your problem solving skills, not someone else's. The following text should appear on all assignments: “I pledge that I have neither given nor received help from anyone other than the instructor for all program components included here.

Help each other understand and debug the programming assignments. However, you should write the code for your programs yourself. Writing it yourself is the only way you will learn. Do not work together to solve the programming assignments to the extent that two programs are essentially the same solution. All program solutions turned in for credit are to be your individual work and should demonstrate your problem solving skills, not someone else's. Since everyone is writing their own code, no two programs should be the same or so similar that I could convert one to the other by a simple mechanical transformation (e.g. changing variable names and comments). I consider this plagiarism and a violation of academic code.

First violation: Students must meet with the instructor. In most cases, the grade will be split between the authors of the copied programs. Second violation: Students will receive no credit for the assignment. An incident letter will be placed on file in the Computer Science Department and the matter referred to the Computer Science Department Chair.

Class Attendance: Class attendance is expected and recorded.

ADA Statement: Students with disabilities who wish to set up academic adjustment in this class should give me a copy of their "Confirmation of Eligibility for Academic Adjustment" from the Disability Support Services Office as soon as possible so we can discuss how the approved adjustment will be implemented in this class. Students without this form should contact the Disability Support Services Office, Buillon 205 or dssrecept@cwu.edu or 963-2171.

Caveat: The schedule and procedures for this course are subject to change. It is the student's responsibility to learn of and adjust to changes.