Session:Education--Positions

From WICSA Conference Wiki

Revision as of 07:30, 20 June 2007 by WikiSysop (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

moderators: Hans van Vliet and Mary Shaw

Abstract

The subject of software architecture has entered computer science and software engineering curricula. One of the first such courses was developed at CMU some 10 years ago by Mary Shaw and David Garlan. Many others have followed. In this session we will exchange experiences with teaching software architecture, and try to develop some curriculum and teaching guidelines. Topics that could be addressed include: contents of a software architecture course, course material, preferred level (undergraduate, graduate), teaching methods (e.g. does one need the architecture of a big industrial system as illustration, or will a small somewhat artificial case suffice). We are especially interested in experiences of participants in teaching such a course and in good examples of well-documented architectures that could be used as teaching aids.

Participants

Please add yourself to this list. Tell us something about your background. Add a few sentences about the working session topic such as your position, questions you would like to see discussed, etc.

  1. Hans van Vliet, Vrije University.
  2. Mary Shaw, Carnegie Mellon University.
  3. Wesley Coelho - wiki coach - University of British Columbia
  4. Joao Sousa, Carnegie Mellon University - Since I'm in the job market for junior faculty, I would love to discuss what people think are good ideas and bad ideas about teaching software architecture.
  5. Eltjo Poort, Logica CMG, Netherlands - interested in working with universities on development of "technology-independent" architects with leadership skills.
  6. Judith Stafford, Tufts University - I teach a one semester course in Software Engineering followed by a semester-long team software design project. I would like to discuss how to best introduce software architecture in such a setting. What are the right goals? How to talk to students who have never created anything bigger than a class assignment about the architecture of a software system? What examples are out there? are but a few of the questions that I ask myself each year. I'd like to be more concrete in my presentations to students yet also cover the general principles.
  7. Adilson Marques da Cunha, Brazilian Aeronautical Institute of Technology - I have been using a PBL (Problem-based Learning) strategy for teaching software engineering for undergrads and postgrads at the Brazilian Aeronautical Institute of Technology (ITA). I wonder if this is a suitable approach. This methodology was documented in the last EISTA conference (paperand presentation slides are available)
  8. Tomi Männistö, Helsinki University of Technology.
  9. Ivica Crnkovis, Malardeleu University, Sweden.
  10. Judith Stafford, Tafts University.
  11. Regis Fleurquin, Scoth Brittany University, France.
  12. Wahab Hamou-Lhaoj, University of Ottawa.
  13. Anton Jansen, University of Groningen.
  14. Art Akerman, Capital One.
  15. Jesper Andersson, Vaxjo University, Sweden.
  16. Laurens Blankers, Eindhoven University of Technology.


Pre-registration for working sessions on the wiki is now closed. If you have not done so already, please sign up for working sessions at the conference registration table on Monday or Tuesday morning. We want to keep these sessions small to foster discussion. Seating is limited in some rooms. Because of this there may be a limit on the number who can participate - if that is the case then the first to sign up will be given preference. Once you have signed up at the registration table and ensured you have a spot, you can return here and add yourself to the list and introduce yourself.

Personal tools