Experience and experiments in CS1

Authors:
Adrienne Critcher;Krishna Agarwal;John Sigle
Affiliations:
Louisiana State University in Shreveport, Shreveport, LA;Louisiana State University in Shreveport, Shreveport, LA;Louisiana State University in Shreveport, Shreveport, LA
Venue:
Journal of Computing Sciences in Colleges
Year:
2000

Citing 9
Cited 0

Computing as a discipline

Communications of the ACM
Computing curricula 1991: Report of the ACM/IEEE-CS Joint Curriculum Task Force

Computing curricula 1991: Report of the ACM/IEEE-CS Joint Curriculum Task Force
Gateway laboratories: integrated, interactive learning modules

SIGCSE '93 Proceedings of the twenty-fourth SIGCSE technical symposium on Computer science education
Concepts in the classroom, programming in the lab

SIGCSE '94 Proceedings of the twenty-fifth SIGCSE symposium on Computer science education
Programming and problem solving with C++

Programming and problem solving with C++
A Laboratory Course in C++

A Laboratory Course in C++
Computer science degree programs: what do they look like? A report on the annual survey of accredited programs

SIGCSE '98 Proceedings of the twenty-ninth SIGCSE technical symposium on Computer science education
Large introductory computer science classes: strategies for effective course management

SIGCSE '98 Proceedings of the twenty-ninth SIGCSE technical symposium on Computer science education
Programming in C++

Programming in C++

Quantified Score

Hi-index	0.00

Visualization

Abstract

In the Fall semester of 1998, our Computer Science Department instituted some major changes in CS1. We wanted our students to become more active participants in the learning process, hence we decided that we must include some kind of closed lab component in CS1. Because of various constraints, we knew we would have to incorporate that lab component into our regular course. In addition to completely changing our teaching methodology for CS1, we also decided to change the programming language from Turbo Pascal to C++. Now a year later, we think we know what we did right, what did not work like we thought it would, and what to do to make CS1 more effective this year and in the future.