Channels ▼

Jonathan Erickson

Dr. Dobb's Bloggers

Parallel Programming and Computer Science 101

December 27, 2008

It's been said more than once that parallel programming is hard, which suggests that the sooner you get a jump on concurrency, the better off you'll be. So when and how should programmers be introduced to parallalism?According to the folks who teach computer science at the University of Wisconsin-Eau Claire, the answer is right off the bat by integrating parallel programming into all aspects of a student's coursework, rather than treating it as a separate topic. And this means starting in CS1.

To date, three core classes -- CS1, CS2, and Algorithms -- have integrated parallelization. For instance, one of the first topics computer-science students traditionally tackle is algorithm design. At UWEC, students start off with the basics but move into identifying parallelism in programs that involve, say, image convultion, before breaking down parallelization into tasks. They then begin assigning tasks to individual threads. Because these classes are currently taught in Java, the instructors use Java threads and synchronization primitives. But since similar constructs exist in other languages, the examples are easily adapted.

Daniel Ernst and Daniel Stevenson sum up their goals in Concurrent CS: Preparing Students for a Multicore World:

The goal of our curriculum changes is to provide our students with the skills they will need to succeed as we enter the multicore era. By giving our students a clear process for exploiting parallelism and practice at implementing it, they have gained confidence in taking advantage of new hardware. The integration of these topics into standard CS course topics has also caused our students to start thinking about concurrency in all of their programs, not just those given with an explicit directive to parallelize. In a world where every machine is a multiprocessor, we consider it a good trait for our students to be always thinking about ways to take advantage of concurrency.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.