Workshops and Tutorials

Workshops

Chair: Jeff Carver

The Roles of Student Projects and Work Experience in Undergraduate and Taught Postgraduate Programmes

Professor J Barrie Thompson and Professor Helen M. Edwards
School of Computing and Technology, University of Sunderland, St Peter's Campus
Sunderland, SR6 0DD, United Kingdom.

Contact: barrie.thompson@sunderland.ac.uk, tel: +44 (0)191 515 2769, Fax: +44 (0)191 515 2781
Date/Time: Wednesday, April 16 (2 afternoon sessions)

Theme
It is important when educating the Net Generation of Software Engineers that the students undertake work that relates to real world issues and this workshop’s theme addresses such by considering the roles of student projects and work experience. The workshop relates directly to particular parts within Curriculum Guideline 14 in the ACM/IEEE-CS Software Engineering 2004 curriculum.

Objectives

  • To gain information on specific instances of: Project-based classes, Capstone course(s), and Student work experience
  • To gain an understanding of: Beneficiaries and benefits, Constraints, risks and challenges, and Resources that are needed and those actually provided.
  • To consider evaluations (Pros and Cons). These should be post-event, overall evaluations of expectations against the actual experience. It should be noted that the above information is relevant not only to undergraduate programmes but also to taught postgraduate programmes.


Teaching Communication Skills in the Software Engineering Curriculum

Janet Burge, Miami University
Charles Wallace, Michigan Technological University
Contact: wallace@mtu.edu, Tel: +1 906 487 3431, Fax: +1 906 487 2283
Date/Time: Tuesday, April 15 (2 afternoon sessions)

Abstract
Communication — between humans — remains at the heart of software development. Software engineers must constantly engage with a wide range of stakeholders with very different perspectives and goals. Failure in communication between software engineers and other stakeholders is a common cause of requirements deficiencies, cost overruns, and delays. Yet software engineering students typically get little exposure to the communication challenges in the workplace. We have a vision of a new curriculum where communication is a core skill, tightly integrated with the other aspects of software engineering, rather than a stand-alone topic taught outside of software engineering. With such a curriculum, software engineering students will become not only creative designers and thoughtful analysts but also effective communicators. The proposed workshop will serve as a forum for those invested in this topic to articulate challenges and solutions, and to build links for further work. Workshop attendees will collaborate on a document that addresses particular questions concerning communication skills in software engineering education.

Each participant is encouraged (not required) to submit a one-page position paper in advance, with a brief background and a list of preferred questions to be discussed at the workshop. Participants are also encouraged to give short (5 minute) presentations on relevant course materials that they have developed.

Workshop attendees will collaborate on a document that addresses particular questions concerning communication skills in software engineering education. The consensus document will be further developed after the workshop and submitted to the next CSEET conference.


Tutorials

Chair: Joseph Chao

How Successful Open Source Projects Work, and How and Why to Bring your Students into the Open Source World

Greg DeKoenigsberg, Community Development Manager, Red Hat, Inc.
Date/Time: Wednesday, April 16, 2008 (2 afternoon sessions)

Abstract:
The goal of this tutorial is to explain why open source matters and how it works at a practical level and to solicit feedback from attendees about how it should work in a classroom environment. I've spoken at length, with lots of people -- VC folks, CEOs, leaders of huge open source projects -- about all of these topics. I'm extremely familiar with the subject matter, and expect to be able to do it justice.

  • PART ONE: Theory of open source
    1. Why bother with teaching open source to students at all?
    2. Open source and the software lifecycle
    3. Theoretical analysis of open source
  • PART TWO: Practice of Open Source
    1. Nuts and bolts: the tools
    2. Culture: "the way we do things round here"
  • PART THREE: The Classroom
    1. Open discussion about how this might work in classroom environments.
    2. Some key questions for discussion

Professionalism and the Software Engineering Code of Ethics- Software Engineering Ethics Training in Industry and Academe

Donald Gotterbarn, East Tennessee State University
Keith Miller, University of Illinois at Springfield
Date/Time: Wednesday, April 16, 2008 (2 afternoon sessions)

Abstract:
In a half-day tutorial, we will present well developed examples and modules which can be used to engage students and computing professionals. We will introduce some examples of realistic, ethically-charged decisions that computing professionals face, and then we will explore how the Code is useful in making wise and creative decisions. We will illustrate the ethical impacts of choice of software process model, architecture, and design patterns using real world examples including examples from Grady Booch. We will practice some of the ethics training techniques that have successfully been used by some corporations in the computer-related industries. We will also describe how to make useful ethics training tools relevant and accessible to software engineers.

Participants will be given complete “turnkey” training examples and they will understand how to develop new examples and course materials for use in industry and academe.