Showing posts with label Curricula. Show all posts
Showing posts with label Curricula. Show all posts

Wednesday, February 1, 2017

Cybersecurity Degree Guidelines

The Association for Computing Machinery (ACM) have released a draft "Cybersecurity Curricula 2017: Curriculum Guidelines for Undergraduate Degree Programs in Cybersecurity" for comment by 14 February 2017. The security areas focused on are: Data, Software, System, Human, Organizational and Societal. Discipline areas ares: Computer Science (CS); Computer Engineering (CE); Software Engineering (SE); Information Technology (IT); Information Systems (IS); and Mixed Disciplinary majors (MD). This draft has not got to the point of setting hours for knowledge areas, but is a good start.

I have submitted this comment:
"The Cybersecurity Curricula is well thought out. The only surprise for me was section 5.1 "The Academic Myth" (p. 33). This polemic against the value of baccalaureate degrees and assessment standards is not appropriate. If the authors believe that a first degree does not provide the skills required for Cybersecurity, then they should be preparing a curriculum which includes a mandatory graduate component. If the authors truly believe that "... having a degree is not sufficient to secure employment.", then they should set down the curriculum for the additional non-degree training and education required.

Setting out to specify a baccalaureate curricula which does not meet the required need seems a pointless activity. In my view a baccalaureate degree is a vocationally useful qualification. However, no single qualification will provide everything everyone needs. The authors of the Cybersecurity Curricula should not set themselves an impossible task. Such a curricula will be useful when designing educational programs, at the sub-degree, degree and also graduate levels. I suggest deleting section  5.1."

Thursday, November 19, 2015

SBS Learn Website for Schools

The SBS Learn website was launched last night at the Australian Centre for Photography (ACP) in Sydney. SBS provides teachers guides and materials for students to accompany their documentaries. These are now being collected at SBS Learn for ease of access by schools.  ACP is currently showing photos from school students as part of their "School Selfie" project on photography. For the students there is "How to sharpen your selfie skills" and for teachers a 30 pages "Teacher notes: School Selfie".

Also available are Go Back To Where You Came FromThe BoatFirst ContactWhat's the Catch, and  Once Upon A Time In Cabramatta.

This is a useful initiative, but SBS needs to provide an index to the materials, based on the Australian curriculum topics and student levels. Also it would be useful to have the materials available in low resolution versions for regional students on low bandwidth Internet connections and with the website formatted to be more mobile-friendly.

Sunday, September 20, 2015

Technologies Curriculum for Australian Schools Endorsed by Education Ministers

The "Foundation to Year 10 Australian Curriculum: Technologies" was endorsed on Friday 18 September 2015 by all Australian State and Territory Ministers for Education for use in schools. The ministers met as the "Education Council" and appropriately the meeting was held by video conference. Unfortunately the Federal Government is providing a minimal $3.5M over four years to support teaching coding in schools. It also appears that state governments are unlikely to make the coordinated investment needed to introduce the new curriculum (training teachers, providing on-line materials and support). As a result schools will have to rely on voluntary work by groups such as Information Technology Educators ACT who recently held an excellent workshop in Canberra. Despite this volunteer work, it is likely Australia will slip further behind in its supply of STEM qualified workforce. This will result in a drop in exports in five to ten years time, when the qualified people needed to create new hi-tech companies and products will not be available. In addition Australia will have to pay to import technology curriculum materials.

Friday, September 11, 2015

Techniques for Teaching the Technologies Curriculum in Australian Schools

The Technologies Curriculum for Foundation to Year 10 in Australian Schools is expected to be formally approved on 18 September 2015. On Thursday I attended the Information Technology Educators ACT (InTEACT) workshop on how to teach the new curriculum. I attended presentations by CISCO and Intel and then hands-on exercise with Grok Learning's programming teaching materials.

CISCO emphasized that the courses at their "CISCO Networking Academy" were not just for training network engineers. As an example they have a course on "Entrepreneurship". What was not clear was how applicable these courses are to the new Technologies Curriculum, given it is for younger students. Also it was not clear if these were aligned with Australian educational requirements.

The Intel presentation did not start well with some claims in the corporate slides at the start lacking credibility. As an example a claim that less than 10% of the world's population had Internet access (the Intel figure I think was 2%) did not seem to match estimates of 40%.

Also a description of the Arduino compatible  Intel Galileo single board computer was a little confusing. Also what was not clear was that a Teacher’s guide to  the Intel Galileo was developed with Macquarie University (and so should me more than just a sales brochure). The guide is designed for the Australian Curriculum, with projects which also suit other Arduino compatible hardware. Unfortunately the PDF version of the guide is 15 Mbytes (a bit big). What was good was that there were several Intel education kits to try out.

Lastly I took part in a workshop run with Australian company, Grok Learning. We ran through two of their one hour coding exercises on "Frozen Fractals" (Python Turtle and Blockly Turtle). These are designed for an iPad, although I used them on a laptop. The exercise was to use "turtle graphics" to draw a snowflake, to learn about geometry and iteration. The two versions of the exercise used a visual programming language (Blockly) and one using Python.

The programming environment used will be familiar to those who have done one of the newer introduction to programming exercises at a university, based on the "Snap!" programming environment and UC Berkeley's "Beauty and Joy of Computing" (Harvey, 2012). The use of turtle graphics for teaching extends much further back, at least to the mid 1970s (Solomon & Papert, 1976). It is interesting to see that it has taken more than 40 years for the hardware to catch up with teaching ideas.

Grok's lesson screen shows a progress bar along the top, with circles representing information for the students and diamonds for tasks. About half the screen is devoted to lesson content, the other half has a window for entering code at the top and a window for results below. When I started the lesson the code window was only large enough for one line, but I found I could drag to make it larger.

Tasks in the progress bar are gray at the start, then turn amber when attempted and green when completed successfully. One minor problem is that it would be difficult to distinguish green and amber if the user can't distinguish color (or has a monochrome screen). However, it would not be difficult for Grok to provide a non-color indicator, to meet accessibility requirements.

To see how they went, a student first runs their code and then submits it for marking. The system shows the required behavior of the turtle and then overlays what the student's code does. One problem is, as with any automated test, the student's result must be identical to the expected result, even for irrelevant details. As an example, when asked to draw a square I left the turtle pointing a different direction to the model answer and so this was not marked as correct by the system. Also there were no helpful hints as what to do next, if your result was not correct.

Grok's implementation is only a few weeks old and they were still making some improvements. Overall the exercises worked well for teaching programming fundamentals. However, these exercises would only really be useful where the student was able to obtain help from a human tutor, such as in a classroom. On its own, for a distance education student, the exercises would be very frustrating. Even a certified computer professional, such as myself, would find it difficult. ;-)

The workshop was held in the Inspire Centre at the University of Canberra. This building was purpose built to teach teachers how technology can be incorporated into education and is the best expression of the hight tech classroom I have seen, anywhere in the world. The event started with seating arranged in theater mode (rows of chairs facing the front). I went out for a coffee in the foyer and by the time I came back the room had been rearranged: a folding wall had divided the room in two and one half was changed to group work around tables.

The Inspire Centre illustrates the sort of investment which needs to be made by Australian governments (and the non-government schools sector) to implement the Technologies Curriculum in Australian schools. While InTEACT's initiative in holding this workshop (and the contribution by companies involved) is to be commended, an investment of many hundreds of millions of dollars is needed for teacher training, equipment and curriculum development. That may sound a lot of money, but is minor compared to that spent on the previous "Building the Education Revolution" and laptops for schools programs. Unfortunately while it is relatively easy to get money for tangible hardware and buildings, it is more difficult to resources the more useful teacher training and course content which is needed for a real education revolution.

References


Harvey, B. (2012). The Beauty and Joy of Computing: Computer Science for Everyone. Proceedings of Constructionism 2012, 33-39. http://ftp.cs.berkeley.edu/~bh/BJC.pdf
Solomon, C. J., & Papert, S. (1976, June). A case study of a young child doing Turtle Graphics in LOGO. In Proceedings of the June 7-10, 1976, national computer conference and exposition (pp. 1049-1056). ACM. http://dx.doi.org/10.1145/1499799.1499945

Wednesday, September 9, 2015

Technologies Curriculum for Australian Schools Next Week

At the ACS Canberra Conference, Julie King, Curriculum Lead, Technology at ACRA, said she was expecting approval of the "Foundation to Year 10 Australian Curriculum: Technologies" by Australian education ministers on 18 September 2015. This is significant as these are the school years when students decide what they will do after school. I suggest that by directly supporting the implementation of the Technologies Curriculum, professional bodies, VET and university sectors can best encourage students to go on to ICT study and careers. One way to do that is for professions and HE to create on-line course content for use by schools. These materials would be best created in a way they can be used by teachers in the classroom, as well as being packaged for direct study by the students.

Tuesday, December 2, 2014

Canberra Computing Education Conventicle

Greetings from the famous room N101 at the Australian National University where the "Canberra Computing Education Conventicle" just started. This is a small, informal conference (Conventicle) where new work, not ready for publication is presented. There was such an event in Melbourne last year. As this is new work I can't point to published papers on these specific topics, but will refer to previous work:
  • Chair's welcome by Chris Johnson ANU
  • Curriculum drift, Lynette Johns-Boast, ANU. Lynette suggested a mechanism for more frequent adjustment of th curriculum. One of the participants suggested assessment be at a program level, not course by course. This then lead to a discussion of external examination systems in India and in OxBridge.
  • Stumbling Around Trying to Attract the Attention of Millennials, Tim Turner, UNSW Canberra. Dr. Turner pointed out many of todays university students have never known a time without a computer. He is concerned that computers are therefore not as inherently interesting to these students and constant exposure to the Internet has reduced their attention span (I am not sure this is true). He pointed out that making video takes new skills which academics may not have (I did a course in training video production, but am an exception). In my view the idea that today's students have a shorter attention span and are not really interested in learning for its own sake is nonsense (and something which academics all the way back to Aristotle). We now have about 50 years of experience in teaching vocationally orientated students and several decades of teaching students on-line. There are techniques for designing courses which have been tested and proven to work. The solution is for academics to enroll in training courses to learn how to teach. 
  • The Three Faces of Quality, Craig Macdonald, Canberra
  • Multiple-choice vs free=text code-explaining examination questions, Simon,    Newcastle 
  • ANU Measuring Success: Varying Intention and Participation, Kim Blackmore,  ANU. Kim commented that the with Understanding India edX MOOC, the most popular topic was the role of mobile phones in story telling. The course had the same drop off in student numbers as other MOOCs, but what struck me was that about 70% of the students who were still participating at week three completed the course. This is about the same as for conventional 12 to 13 week courses, where students can drop out without penalty. Perhaps the ration of completions to the number participating one quarter of the way through the course would be a useful metric for comparison with conventional courses. One interesting result was that the Understating India course was popular with the Indian diaspora. What worries me about MOOCs is that this is a very expensive way to teach university academics how to design and deliver on-line courses. It would be much quicker, cheaper and more reliable to have academics who have to teach on-line to be formally qualified to do so (there are many good courses available to learn to teach on-line). It is not difficult to get academic to do training, if they are suitably rewarded.
     
  • Computer Science Curriculum and Schools: Opportunities and Obstacles, Bruce Fuda, Gungahlin College/InTEACT. Bruce poitned out that Canberra's school based curriculum allowed them to have already been implementing the national Digital Technologies curriculum. University can expect to see Canberra students who have undertaken the school program within two years and NSW students within four years. Bruce pointed out that there were few ICT qualified teachers in schools and so those who are teaching the digital technologies program could benefit from external assistance. Bruce pointed out the curriculum included vocational skills in multimedia (which I don't think is a bad thing, I studied that at TAFE), but revision of the curriculum could have more ICT. Given the course topic is ICT and there is a shortage of trained teachers, it occurs to me that these courses could be run on-line with remote expert tutors, to assist local teachers, as well as the students. Teaching materials could also be shared with the VET sector for the advanced courses.
  • Mobile Learning in Context, Chris Johnson ANU. Chris proposes to instrument mobile devices to see how students use them for learning. This sounds a useful idea, but it would be useful to first ask teachers and students how they use the technology. As an example, I envision that students would use a small mobile device for the discussion forums of courses I run: the posts are short enough for a small screen and can be read in small chunks. I would expect, at the other extreme, the student would need a larger device and more time, to write a 2,000 word assignment. Also I suggest the research needs to take into account that students are likely to be using multiple devices at the same time. It seems to me that school teachersare the most advanced in the use of mobile devices for learning and it would be better to look at what they are doing than school teachers.
  • Flipping introduction to Computer Systems, Eric McCreath, ANU. Eric described how he converted a conventional course into a flipped one. What was most impressive about this was that it was not done with large amounts of additional resources. Eric recoded presentations with a web-cam in their own time and a weekly quiz to get them to watch the videos. Interestingly Eric used paper based multiple choice quizzes scanned with the standard university Multi-Function Unit, rather than requiring specialized "clicker" devices, or the student's mobile devices. The flipped format receives similar student feedback to the non-flipped version of the course.
The 2015 Canberra Computing Education Conventicle will be hosted by Tim Turner, at UNSW Canberra.

Monday, October 13, 2014

Review of the Australian School Curriculum Misses Importance of e-Learning

The Australian Government has released the Final Report of a  "Review of the Australian Curriculum" by Professor Ken Wiltshire AO and Dr Kevin Donnelly.  Available are:
  1. Final Report of the Review of the Australian Curriculum: (PDF 3.27 MB or DOCX 11.82 MB)
  2. Initial Australian Government Response Review of the Australian Curriculum
  3. Supplementary Material for the Review of the Australian Curriculum
  4. Fact Sheet on the Review of the Australian Curriculum
  5. Frequently Asked Questions on the Review of the Australian Curriculum
One concern I have is that sufficient weight is not being given to the way the Internet is changing how education is provided. The report mentions "Internet" only twice in 294 pages (on  Page 147).

In the first reference the authors comment that just having information via the Internet is not sufficient for understanding. However this fails to mention decades of research and practical experience showing it is possible to provide quality education on-line:
"The argument that the disciplines are changing so rapidly that it is impossible to identify them with any certainty or precision and, as a result, that all students need to do is to access the internet when wanting information, is misleading. Information is not knowledge and understanding is not wisdom. Education, while dealing with information and understanding, is primarily concerned with knowledge and wisdom that while evolving and open to debate has stood the test of time."
The second mention of the Internet claims that  "many" complained about a lack of hard copy of the curriculum materials. It is not clear how these many complaints were received, given that the review used an an online submission process (those who sent a submission must have had Internet access). Also, as the authors state, not all households have Internet access, but the ABS says 83% do. There are more than one million householders without Internet access, if many of had complained (in this context "many" would be tens of thousands of people).
"The bulk of parents seem to have been unhappy about the token involvement of parents in development of the curriculum, and report frustration in being able to gain independent access to curriculum documents. Many complain about the lack of hard copy, pointing out that not all households have internet access (265); nor are all parents computer literate. As in so many other aspects of government service delivery in Australia, purely web-based delivery is not adequate."
The technologies curriculum, that is teaching ICT is better covered in the report, than the use of ICT for teaching:
"There is also strong support for its inclusion in
the Australian Curriculum – particularly from professional bodies associated with computers and technologies – and a belief that it appropriately captured the critical elements of the learning area and provided a sound curriculum foundation which could accommodate future instances of digital technology. The Australian Computer Society (ACS) says:

The ACS strongly endorses the creation of the digital technologies subject and notes the
important distinction of this subject from the role of ICT as a general capability. Both aspects
are critically important in the education of students, but the distinction between them is vital
for individual students and for Australia as a nation.
414" Page 208
Recommendation 15 of the report is likely to be most contriversial and with which I have most difficulty with:
"ACARA revise the Australian Curriculum to place more emphasis on morals, values and spirituality as outlined in the Melbourne Declaration, and to better recognise the contribution of Western civilisation, our Judeo-Christian heritage, the role of economic development and industry and the
democratic underpinning of the British system of government to Australia’s development." Page 246
It is not clear to me why the many Australian citizens who do not have a British Judeo-Christian heritage should have their taxes spent indoctoranating their children in someone else's values. Discussion of "Western civilisation" belongs in history courses, but alongside the other civilisations which have contributed to today's Australia.

An emphasis on morals and values would be appropriate for schools, along the lines of the  Primary Ethics, program developed by St James Ethics Centre for NSW primary schools. However, this should discuss Judeo-Christian concepts alongside other religions and moral systems of Australians.

Sunday, November 17, 2013

ACM/IEEE-CS Computer Science Curricula 2013

The joint ACM/IEEE-CS Computer Science
Curricula 2013 Steering Committee (CS2013), have released a Draft Final Report (October 2013). The previous versions of the ACM/IEEE-CS curricular have been used by universities around the world in designing their degree programs. There is also a core learning outcomes spreadsheet and some Course and Curriculum Exemplars.

The ACM/IEE-CS Curricula specifies the proportion of course on each topic in terms of lecture hours, for delivery in a traditional face-to-face class. This does not include self-study time, lab sessions or student work on assessments. So confusingly it is less than the usual measure used by universities of  "contact hours" (which includes tutorials and labs sessions). The Total Core Hours are: Tier1 165 Hours, Tier1 143 Hours. Programs are required to have all of Tier 1, plus at least 80% of Tier 2, making a total of at least 279.4 Hours.

The ANU Bachelor of Information Technology
requires the completion of 144 units, with 36 compulsory computer science units, another 30 units from later years CS courses, 24 units of additional CS courses, 6 core maths courses, leaving 28 units of general electives. A typical 6 unit ANU Computer Science course has thirty one, one hour lectures and six two hour tutorials. The full time degree program is usually made up of three years of two semesters, with four courses per semester for a total of  24 courses (3 x 2 x 4). This equates to 744 hours of lectures.

While the ACM/IEE-CS have been influential with their curriculum internationally, it should be noted that this is a very US-centric document. The only mention of Australia in the document, is Judy Sheard's Human Computer Interaction (FIT3063), Monash University. The UK is represented by Paul Cairns' Human Aspects of Computer Science, University of York, Alan Blackwell's Human Computer Interaction and Software and Interface Design, University of Cambridge. Most of the other courses are from the USA, with a few from Europe and Asia.

ACM/IEEE-CS Computer Science Curricula 2013 

Table of Contents

Chapter 1: Introduction . 10

Overview of the CS2013 Process . 11
Survey Input  12
High-level Themes  13
Knowledge Areas  14
Professional Practice . 15
Exemplars of Curricula and Courses  16
Community Involvement and Website . 16
Acknowledgments  16
References . 19

Chapter 2: Principles . 20

Chapter 3: Characteristics of Graduates . 23

Chapter 4: Introduction to the Body of Knowledge 27

Knowledge Areas are Not Necessarily Courses (and Important Examples Thereof). 28
Core Tier-1, Core Tier-2, Elective: What These Terms Mean, What is Required . 29
Further Considerations in Designing a Curriculum  32
Organization of the Body of Knowledge  32
Curricular Hours . 32
Courses 33
Guidance on Learning Outcomes . 33
Overview of New Knowledge Areas  34

Chapter 5: Introductory Courses . 39

Design Dimensions . 39
Mapping to the Body of Knowledge. 45

Chapter 6: Institutional Challenges . 46

Localizing CS2013 . 46
Actively Promoting Computer Science  46
Broadening Participation  47
Computer Science Across Campus . 48
Computer Science Minors  48
Mathematics Requirements in Computer Science  49
Computing Resources . 51
Maintaining a Flexible and Healthy Faculty. 51
Teaching Faculty. 52
Undergraduate Teaching Assistants 53
Online Education  53
References . 54

Appendix A: The Body of Knowledge . 55

Algorithms and Complexity (AL). 55
Architecture and Organization (AR). 62
Computational Science (CN)  68
Discrete Structures (DS) . 76
Graphics and Visualization (GV) . 82
Human-Computer Interaction (HCI)  89
Information Assurance and Security (IAS)  97
-4-Information Management (IM) . 112
Intelligent Systems (IS)  121
Networking and Communication (NC). 131
Operating Systems (OS) . 136
Platform-Based Development (PBD) . 143
Parallel and Distributed Computing (PD) . 146
Programming Languages (PL)  156
Software Development Fundamentals (SDF) . 168
Software Engineering (SE) . 173
Systems Fundamentals (SF) 187
Social Issues and Professional Practice (SP)  193

Appendix B: Migrating to CS2013 . 205

Outcomes  205
Changes in Knowledge Area Structure . 206
Core Comparison  207
Conclusions . 211

Appendix C: Course Exemplars 228

Course Exemplar Template  232
CSCI 140: Algorithms, Pomona College  234
COS 226: Algorithms and Data Structures, Princeton University 237
CS 256 Algorithm Design and Analysis, Williams College . 240
CSE332: Data Abstractions, University of Washington . 243
CS/ECE 552: Introduction to Computer Architecture, University of Wisconsin . 246
CS150: Digital Components and Design, University of California, Berkeley . 249
-5-CC152: Computer Architecture and Engineering, University of California, Berkeley  251
eScience, University of North Carolina at Charlotte  253
COSC/MATH 201: Modeling and Simulation for the Sciences, Wofford College  258
MAT 267: Discrete Mathematics, Union County College . 262
CS103: Mathematical Foundations of Computer Science, Stanford University  265
CS109: Probability Theory for Computer Scientists, Stanford University  265
CS 250 - Discrete Structures I, Portland Community College . 268
CS 251 - Discrete Structures II, Portland Community College  271
CS 175 Computer Graphics, Harvard University . 274
CS371: Computer Graphics, Williams College  277
Human Aspects of Computer Science, University of York  280
FIT3063 Human Computer Interaction, Monash University 282
CO328: Human Computer Interaction, University of Kent  285
Human Computer Interaction, University of Cambridge . 287
Human-Computer Interaction, Stanford University . 289
Human Information Processing (HIP), Open University Netherlands . 291
Software and Interface Design, University of Cambridge  293
Computer Systems Security (CS-475), Lewis-Clark State College  295
CS430: Database Systems, Colorado State University. 298
Technology, Ethics, and Global Society (CSE 262), Miami University  301
CS 662; Artificial Intelligence Programming, University of San Francisco  304
Intelligenza Artificiale ( Artificial Intelligence), Politecnico di Milano  306
CMSC 471, Introduction to Artificial Intelligence, U. of Maryland, Baltimore, County  308
Introduction to Artificial Intelligence, Case Western Reserve University . 310
-6-CS188: Artificial Intelligence, University of California Berkeley . 313
Introduction to Artificial Intelligence, University of Hartford . 315
Computer Networks I, Case Western Reserve University  318
CS144: Introduction to Computer Networking, Stanford University . 320
Computer Networks, Williams College  323
CSCI 432 Operating Systems, Williams College . 327
CS 420, Operating Systems, Embry-Riddle Aeronautical University  330
CPSC 3380 Operating Systems, U. of Arkansas at Little Rock . 332
582219 Operating Systems, University of Helsinki . 334
RU STY1 Operating Systems, Reykjavik University. 336
Parallel Programming Principle and Practice, Huazhong U. of Science and Technology . 339
Introduction to Parallel Programming, Nizhni Novgorod State University . 342
CS in Parallel (course modules on parallel computing) . 344
CS453: Introduction to Compilers, Colorado State University  348
Csc 453: Translators and Systems Software, The University of Arizona  351
CSCI 434T: Compiler Design, Williams College  353
Compilers, Stanford University  356
Languages and Compilers, Utrecht University . 359
COMP 412: Topics in Compiler Construction, Rice University  361
CSC 131: Principles of Programming Languages, Pomona College 364
CSCI 1730: Introduction to Programming Languages, Brown University  367
CSC 2/454: Programming Language Design and Implementation, University of Rochester 369
CSE341: Programming Languages, University of Washington . 372
CSCI 334: Principles of Programming Languages, Williams College . 375
-7-Programming Languages and Techniques I, University of Pennsylvania  378
15-312 Principles of Programming Languages, Carnegie Mellon University 381
15-150: Functional Programming, Carnegie Mellon University  385
CIS 133J: Java Programming I, Portland Community College  389
Introduction to Computer Science, Harvey Mudd College  392
CpSc 215: Software Development Foundations, Clemson University . 395
CS1101: Introduction to Program Design, WPI . 398
Data Abstraction and Data Structures, Miami University  401
Software Engineering Practices, Embry Riddle Aeronautical University  403
CS169: Software Engineering, University of California, Berkeley 407
SE-2890 Software Engineering Practices, Milwaukee School of Engineering  410
Software Development, Quinnipiac University  412
CS2200: Introduction to Systems and Networking, Georgia Institute of Technology . 415
CS61C: Great Ideas in Computer Architecture, University of California, Berkeley 419
CSE333: Systems Programming, University of Washington . 421
Ethics in Technology (IFSM304), University of Maryland . 424
Technology Consulting in the Community, Carnegie Mellon University  427
Issues in Computing, Saint Xavier University 431
Ethics & the Information Age (CSI 194), Anne Arundel Community College . 433
Professional Development Seminar, Northwest Missouri State University . 436
The Digital Age, Grinnell College  439
COS 126: General Computer Science, Princeton University . 443
CSCI 0190: Accelerated Introduction to Computer Science, Brown University . 447
An Overview of the Two-Course Intro Sequence, Creighton University. 449
-8-CSC 221: Introduction to Programming, Creighton University . 450
CSC 222: Object-Oriented Programming, Creighton University . 452
An Overview of the Mulit-paradigm Three-course CS Introduction at Grinnell College  454
CSC 151: Functional problem solving, Grinnell College . 456
CSC 161: Imperative Problem Solving and Data Structures, Grinnell College . 458
CSC 207: Algorithms and Object-Oriented Design, Grinnell College . 460

Appendix D: Curricular Exemplars  463

Bluegrass Community and Technical College (A.S. Degree)  465
Bluegrass Community and Technical College (A.A.S. Degree)  472
Grinnell College  480
Stanford University . 492
Williams College  503 Brown University . 447
An Overview of the Two-Course Intro Sequence, Creighton University. 449
-8-CSC 221: Introduction to Programming, Creighton University . 450
CSC 222: Object-Oriented Programming, Creighton University . 452