In the fall of 1999, we started, the Integrated Product Development- Collaborative Engineering ( IPD-CE) project as a first pilot. We experimented with modern communication technology in order to find useful tools for facilitating the cooperative work and the contacts of all the participants. Teams have been formed with engineering students from Lehigh University in the US, the Fontys University in Eindhoven, The Netherlands and from the Otto-von-Guericke University in Magdeburg, Germany. In the fall of 2000 we continued and also cooperated with the Finnish Oulu Polytechnic. It turned out that group cohesion stayed low (students did not meet in real life), and that Internet is not mature enough yet for desktop video conferencing. Chatting and email were in these projects by far the most important communication media. We also found out that the use of a Computer Support for Cooperative Work (CSCW) server is a possibility for information interchange. The server can also be used as an electronic project archive. Points to optimise are: 1. We didn't fully match the complete assignments of the groups; 2. We allowed the groups to divide the work in such parts that those were developed and prototyped almost locally; 3. We haven't guided the fall 2000 teams strong enough along our learning curve and experiences from previous groups. 4. We didn't stick strong enough to the, by the groups developed, protocols for email and chat sessions. 5. We should facilitate video conferencing via V-span during the project to enhance the group performance and commitment.
Author supplied: DOI : http://dx.doi.org/10.1145/2691352.2691357 Assignments and exercises are an essential part of software engineering education. It usually requires a variety of these assignments to cover a desired wide range of educational objectives as defined in the revised Bloom's taxonomy. But such a variety has inherent problems, e.g. that students might not see the connections between the assignments and find it hard to generalize the covered concepts. In this paper we present the educational design pattern Multi-Level Assignment which addresses these problems. It enables the assignment designer to incorporate a variety of educational objectives into a single assignment by including the concepts on multiple knowledge and process levels. The description as educational design pattern and the provided three implementation examples make this approach directly applicable for other software engineering educators.
LINK
The paper summarizes two models for engineering education, as discussed in earlier papers. The first model (Corporate Curriculum) aims to bring Industry into the school, while the second model (I3) intends to bring the school into Industry. The contribution of the presented models to the Bologna Declaration and to the Renaissance Engineer idea are discussed.
