Design Patterns discussion

["Carl G. Alphonce" <alphonce AT cse.Buffalo.EDU>]

Dear colleagues,

Do you teach objects and object-orientation?  Do you teach an
objects-first CS1, or perhaps an advanced course in OO design and
modeling?  If you're a CS educator who is interested in sharing
teaching techniques or exploring pedagogical issues in a workshop
setting, this workshop may be for you!

The "Killer Examples" workshop has been held at OOPSLA since 2002.
The goal of this workshop series has been to tap into the expertise of
the OOPSLA community to improve the teaching of object orientation.
Past workshops have focused on design patterns.  This year the
workshop theme is "process in OO pedagogy".

The full call for participation in the workshop is included below.
There are two ways to participate: you can either submit a short
paper, or you may apply to attend as a discussant.  Either way you
will have plenty of opportunity to talk about process and sound
pedagogy for teaching object orientation.

The deadline for submissions/applications is September 3, 2007, but
earlier submissions are encouraged.

If you have questions about the workshop, do not hesitate to contact us at
<alphonce AT cse.buffalo.edu>,
 with subject line "OOPSLA-2007 Workshop Query".

Carl Alphonce, University at Buffalo, USA
Jürgen Börstler, Umeå University, Sweden
Michael Caspersen, Univeristy of Aarhus, DK
Adrienne Decker, University at Buffalo, USA
Michael Kölling, University of Kent, UK


               - - - - - - - - - - - - - - - - - - - -
                                FINAL
                  Call for Papers and Participation
               - - - - - - - - - - - - - - - - - - - -

                    6th "Killer Examples" workshop
                    Theme: Process in oo Pedagogy
        http://www.cse.Buffalo.EDU/faculty/alphonce/OOPSLA2007
         A workshop at OOPSLA 2007, Montréal, Québec, Canada
                                   

               - - - - - - - - - - - - - - - - - - - -
                           Important dates
               - - - - - - - - - - - - - - - - - - - -

             September 3, 2007 - Deadline for submissions
            September 9, 2007 - Notification of acceptance
     September 11, 2007 - OOPSLA 2007 early registration deadline
              October 21, 2007 - Workshop @ OOPSLA2007!


               - - - - - - - - - - - - - - - - - - - -
                              Background
               - - - - - - - - - - - - - - - - - - - -

The Jargon File defines a killer app as an "application that actually
makes a sustaining market for a promising but under-utilized
technology."  A killer example provides clear and compelling
motivation for some concept.  The theme of this workshop is killer
examples for process in oo pedagogy.

Today's computer science students are tomorrow's software developers.
As such they will be expected to design and implement solutions to
complex problems.  Object orientation is an excellent approach to
managing the complexity of large, real-world software systems.  Many
educators have been slow to adopt, or unsuccessful at adopting, or
worse, reluctant to try adopting, an object oriented approach,
especially in CS1-CS2 courses.  We believe part of the difficulty
stems from educators lacking a sound pedagogy for teaching newcomers
to object orientation (be they beginning students or seasoned
professionals trying to move into the OO arena) how to "think in
objects".  Another part of the difficulty lies in students not being
given a clear and effective process for tackling problems in an OO
way.


               - - - - - - - - - - - - - - - - - - - -
                   Themes and Goals of the workshop
               - - - - - - - - - - - - - - - - - - - -

One of the greatest challenges in teaching students object orientation
(either introductory or later in the curriculum) is teaching the art
of programming.  This workshop is therefore soliciting submissions in
the following areas:

    * "killer" examples of teaching the process of programming

    * "killer" examples of teaching OO modeling and programming

    * analyses of the process which students use to solve problems

The goal of the workshop is to develop an understanding of the
following issues:

    * Why is it that while first-year undergraduate students often
      have prior coursework in computer programming, they appear not
      to be as well-prepared for university-level CS courses.

    * What are the mental models (of programs/programming) held
      by novices? Knowing them could improve they way we teach.

    * What is the role of early design/modelling in an objects-
      first curriculum?

    * How does the teaching process and the students'programming
      process address design/modeling?

    * What are needs of industry - what will keep students
      competitive in the workplace?


               - - - - - - - - - - - - - - - - - - - -
                        How can I participate?
               - - - - - - - - - - - - - - - - - - - -

If you are interested in participating, there are two ways to do it!
You can either contribute a short paper, or you may apply to attend
as a discussant.

If you wish to present at the workshop you must submit a short paper
(4 to 6 pages) as an e-mail attachment to 
alphonce AT cse.buffalo.edu
with subject line "OOPSLA-2007 Workshop Paper Submission".  Your
submission must clearly identify why the paper is relevant to the
workshop, as described in the "Themes and Goals" section, and why you
believe your contribution is "killer".

If you wish to attend the workshop as a discussant you must submit a
short statement of interest (a manifesto, if you will) (1 to 2 pages)
as an e-mail attachment to 
alphonce AT cse.buffalo.edu
 with subject line
"OOPSLA-2007 Workshop Discussant Submission".  Your submission must
clearly state why you are interested in attending the workshop and
what OO background you have (e.g. when did you learn OO, at what level
do you teach it).  We seek the participation of people with a broad
spectrum of backgrounds, so don't hesitate to submit an application
because you think you have too little/too much experience to
contribute.

Submissions must be made on or before the submission deadline.
Submissions may be in plain text, in Microsoft Word .doc format or in
PDF.  You must submit two versions - one anonymous and one with author
names and affiliations.  Avoid self-references, if any, in the text of
the submission.

Each submission will be anonymously reviewed by at least three members
of the organizing committee.  The decision of the organizing committee
is final.

If your submission is accepted, you (or one of your co-authors) is
required to register for the workshop and attend.