CSC 161 Grinnell College Spring, 2012
Imperative Problem Solving and Data Structures

CSC 161 Module 3: Working with Characters, Strings, and I/O


This module introduces CSC 161 students to writing dynamic programs that can take input and follow commands based on input, including

  1. characters
  2. strings,
  3. input and output.

Day-by-day Details

Day Topic Preparation In-class Due Date Availability
Monday, March 5 Module 3: Strings and I/O   Examples    
Tuesday, March 6 Characters and Strings Kernighan & Ritchie, 1.9, 7.8.1, 7.8.2, B.3 Characters and Strings Lab    
Wednesday, March 7 Input and Output
  • printf
Kernighan & Ritchie, 1.5, 7.1, 7.2, B.2 (reference) Input/Output Lab    
Friday, March 9 More I/O
  • scanf
Kernighan & Ritchie, 7.4
B.1.2, B.1.4 (reference)
I/O Lab Continued    
Monday, March 12 Project   Robot follows typed commands Friday, March 16  
Tuesday, March 13 supplemental problem 3   supplemental problem 3 Wednesday, March 14  
Tuesday, March 13 Project   Robot follows typed commands Friday, March 16  

Project: Robot Follows Typed Commands

Working in pairs, students should develop a program that includes these elements:

Together with the program, a student pair must write a paragraph that describes what tests are needed to demonstrate the program is working correctly. That is, what should a tester do to demonstrate the program works? Also, the student pair must present a sequence of steps that the tester should do to carry out the test plan. (E.g., what should be typed in a terminal window, including the details of the compile, link, and run steps?)

Command Requirements


This project will be worth 25 points, based on the following rubric:


This project is planned for use as the base of a later project, so you will want to document your code well now — in anticipation of later activities.