150 likes | 286 Vues
This document provides a comprehensive overview of the evolution of the Computer Science program at Cranbrook Schools, emphasizing key curriculum changes, course offerings, and educational philosophies from its inception to the present. It highlights the transition from traditional programming languages to object-oriented programming, the establishment of various courses, and the integration of ethical considerations into the curriculum. Invitations to collaborate with organizations like MiCSTA and MACUL are also discussed, showcasing the commitment to enhancing student learning and engagement in computer science.
E N D
Computer Science @ Cranbrook Schools Rich Lamb – Computer Dept. Rlamb@Cranbrook.edu www.RichLamb.com
I. Me • CMU (the real one, in Pittsburgh) – EE • Oops, EE = false – now what?? • Experimental Psych course – stats
1977 – Cranbrook School • FORTRAN (my native language) • and others since: assembler, BASIC, Pascal, C++, Java • Notice transition to OOP in AP: Pascal —> C++ —> Java • Initial FORTRAN class had lab once per 5-day week on a Digital Equipment Corp. PDP-11 • Semester courses in Science department
1984 – Orwell would love it • AP Computer Science exam • Full year course, by necessity • Pascal • legitimized computer science at pre-college level • Computer Department established • Amicable separation from Science Department • Cranbrook and Kingswood Schools merge to form Cranbrook Kingswood School
Requirements – or Not • Typing (a.k.a. Keyboarding) – 20 wpm • Computer Literacy • Use software, computers • Two separate requirements and classes - mid-eighties • Combine these two requirements into one, and with one class • Easier for kids to schedule • Eliminate requirements (and the class) mid-nineties • Even easier to schedule!
Today • Computer Science / Computer Science I (“JV”) • Introductory course – no prerequisites or expectations • Half- v. full-credit (4 day/wk v. 5 day/wk + homework) • Objects First Using Java • Modify code – don’t write from scratch • Less teaching, more directing • Grading
CS/CSI • Balance of test and homework • High test scorers must also do HW • Note “80” is “A-”, “70” is “B-”, etc. – scale is generous • Each student has personalized grid on her/his account • Can check grade anytime. w/o seeing instructor • Final project v. Final Exam • Ethics
CS AP (“Varsity”) • More than just “comp sci II” • Full year • Students must be independent workers • Most assignments are long-term • Sometimes “random” partners • Grade sometimes by weakest link • Same grading method • Mandatory final exam at semester, final project at end of year
CS AP (“Varsity”) • IDE is now BlueJ (from JCreator) • A v. AB • Ironically, an improvement – same time for less material
Computing ≠ Programming • Directed Study • Semester long, may be repeated • Web page design • Video • Hardware • Networking
Other Thoughts • Ethics • Computer ethics are a very important consideration • Students are/will be self-policing • Gaming • Robotics – STEM • Enrollment • You are in sales • Getting to know the kids • Be part of school life
Helpful organizations • Mi CSTA • email: bwebster [at] barrywebster [dot] com • Free • MACUL – SIG Computer Science • Macul.org – navigate to SIGs • Cheap