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

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

Introduction

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
for
Extra
Credit
Friday, March 1 Module 3: Strings and I/O   Examples    
Monday, March 4 Characters and Strings Reading from Text
  • King: Section 7.3, Chapter 13, pages 134-141, 277-299, OR
  • Kernighan & Ritchie: 1.9, 7.8.1, 7.8.2, B.3
Characters and Strings Lab    
Tuesday, March 5 Input and Output
  • printf
Input/Output Lab    
Wednesday, March 6 More I/O
  • scanf
I/O Lab Continued    
Friday, March 8 Hour Test 2 Covers through Lab on Characters and Strings    
Monday, March 11 Project   Robot follows typed commands Tuesday, April 2  
Tuesday, March 12 Project   Robot follows typed commands Tuesday, April 2  

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

Grading

Note

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.