Workshop EduRex 2012 – Author Index |
Contents -
Abstracts -
Authors
|
Bogicevic, Ivan |
![]() Jochen Ludewig and Ivan Bogicevic (University of Stuttgart, Germany) The software engineering curriculum offered by the University of Stuttgart emphasizes project work from the first to the last semester. While some of the projects are similar to those in other programs, others are less common. In this paper, we describe an introductory course called “Program Understanding”, and the so called “Consulting Task”. We also give a short description of what we call the First Software Project and the Large Software Project. In the Program Understanding course, new students learn to understand a fairly large, complex program in order to implement some modifications. In the Large Software Project, some ten people work on a serious software development for one year. In the Consulting Task, a group of three students analyses a problem, usually one given by an industrial partner. The students investigate possible solutions, and finally deliver a recommendation. Both our experience and feedback from students, including feedback from alumni, prove that these projects are very successful and highly esteemed. ![]() |
|
Borici, Arber |
![]() Daniela Damian and Arber Borici (University of Victoria, Canada) Teaching real-world software engineering (SE) skills requires innovative methods to facilitate students' learning technical as well as communication, teamwork, and analysis of ill-structured problems. In this paper we describe our experiences in designing and teaching these skills in our SE courses at the University of Victoria in the last 10 years. We describe the learning outcomes and instructional design in our courses, as well as the challenges we face. ![]() |
|
Brügge, Bernd |
![]() Bernd Brügge and Michaela Gluchow (TU Munich, Germany) ![]() |
|
Burns, Richard |
![]() Richard Burns, Terry Harvey, and Lori Pollock (University of Delaware, USA) This paper reports our experience developing a product for a real-world client using a software engineering process across multiple semesters with different students each semester. New student teams test, debug, deploy, and critique previous semesters' software and then continue its development. Students are motivated to think critically about and experience real-world software engineering practice. We describe how students in one semester collectively identified the software engineering problems that could be resolved in the current semester, how the students proceeded to tackle those problems, and the impacts of their actions for future semesters. ![]() |
|
Damian, Daniela |
![]() Daniela Damian and Arber Borici (University of Victoria, Canada) Teaching real-world software engineering (SE) skills requires innovative methods to facilitate students' learning technical as well as communication, teamwork, and analysis of ill-structured problems. In this paper we describe our experiences in designing and teaching these skills in our SE courses at the University of Victoria in the last 10 years. We describe the learning outcomes and instructional design in our courses, as well as the challenges we face. ![]() |
|
Eldh, Sigrid |
![]() Sigrid Eldh and Sasikumar Punnekkat (Ericsson, Sweden; Karlstad University, Sweden; Mälardalen University, Sweden) The ubiquity of software is making every industry increasingly dependent on it for achieving their core products' functionality. The complexity in a telecom network requires not only thorough understanding of telecommunication per se, but software becomes equally interesting. This is the case with many industries, which rely more and more on software as their key enabler. Industry definitely needs a large number of software engineers with potential to be productive from day one. They are feeling impatient at the academic community for not being pragmatic. At the same time Academic community faces many challenges, which often make them thread a traditional path thus ignoring the industrial needs. We present some of these challenges from both the industrial and academic perspectives. We also present how we established a Master level advanced course on software verification and validation through mutual support and collaboration which became highly successful. ![]() |
|
Gabrysiak, Gregor |
![]() Gregor Gabrysiak, Markus Guentert, Regina Hebig, and Holger Giese (HPI, Germany) Enabling students to experience authentic stakeholder meetings as part of their requirements engineering education is a challenging task. To be authentic, involved stakeholders need to be affected by what students deliver. However, this is usually not the case. Trying to provide students authentic stakeholder interactions, we already specified two distinct settings suitable for recruiting real stakeholders by providing a benefit for them in return. However, scalability issues of these settings remained. In this paper, we present two ideas to overcome this issue. By cooperating with software companies which are building a product line, we gain access to many diverse stakeholders. Further, we propose to rely on course alumni to supervise stakeholder interactions to increase the scalability by reducing the lecturers’ supervision effort. These ideas are explained using a currently running course setting in collaboration with a software start-up which builds a product line of sports club management applications. ![]() |
|
Giese, Holger |
![]() Gregor Gabrysiak, Markus Guentert, Regina Hebig, and Holger Giese (HPI, Germany) Enabling students to experience authentic stakeholder meetings as part of their requirements engineering education is a challenging task. To be authentic, involved stakeholders need to be affected by what students deliver. However, this is usually not the case. Trying to provide students authentic stakeholder interactions, we already specified two distinct settings suitable for recruiting real stakeholders by providing a benefit for them in return. However, scalability issues of these settings remained. In this paper, we present two ideas to overcome this issue. By cooperating with software companies which are building a product line, we gain access to many diverse stakeholders. Further, we propose to rely on course alumni to supervise stakeholder interactions to increase the scalability by reducing the lecturers’ supervision effort. These ideas are explained using a currently running course setting in collaboration with a software start-up which builds a product line of sports club management applications. ![]() |
|
Gluchow, Michaela |
![]() Bernd Brügge and Michaela Gluchow (TU Munich, Germany) ![]() |
|
Gokhale, Swapna S. |
![]() Swapna S. Gokhale, Thérèse Smith, and Robert McCartney (University of Connecticut, USA) Software Engineering (SE) projects that emphasize maintenance and evolution can emulate industrial challenges and prepare students for careers in the software industry. Designing maintenance-centric SE projects, however, is difficult because software code upon which these projects must be based is not readily available. Open Source Software (OSS) can alleviate this issue by offering a rich and varied volume of code. This rich diversity of OSS projects, however, presents the greatest hurdle in seamlessly selecting suitable projects for integration. To better understand the scope of this diversity, initially, we propose to manually select uniformly difficult projects of appropriate complexity. Ultimately, based on the experiences and insights acquired through the manual selection, we envision the development of a systematic methodology based on software metrics to ease the project selection process. Such a systematic methodology will pave the way for the adoption of the OSS-based approach at peer institutions, bringing us a step closer to injecting realism into SE projects. ![]() |
|
Guentert, Markus |
![]() Gregor Gabrysiak, Markus Guentert, Regina Hebig, and Holger Giese (HPI, Germany) Enabling students to experience authentic stakeholder meetings as part of their requirements engineering education is a challenging task. To be authentic, involved stakeholders need to be affected by what students deliver. However, this is usually not the case. Trying to provide students authentic stakeholder interactions, we already specified two distinct settings suitable for recruiting real stakeholders by providing a benefit for them in return. However, scalability issues of these settings remained. In this paper, we present two ideas to overcome this issue. By cooperating with software companies which are building a product line, we gain access to many diverse stakeholders. Further, we propose to rely on course alumni to supervise stakeholder interactions to increase the scalability by reducing the lecturers’ supervision effort. These ideas are explained using a currently running course setting in collaboration with a software start-up which builds a product line of sports club management applications. ![]() |
|
Harvey, Terry |
![]() Richard Burns, Terry Harvey, and Lori Pollock (University of Delaware, USA) This paper reports our experience developing a product for a real-world client using a software engineering process across multiple semesters with different students each semester. New student teams test, debug, deploy, and critique previous semesters' software and then continue its development. Students are motivated to think critically about and experience real-world software engineering practice. We describe how students in one semester collectively identified the software engineering problems that could be resolved in the current semester, how the students proceeded to tackle those problems, and the impacts of their actions for future semesters. ![]() |
|
Hebig, Regina |
![]() Gregor Gabrysiak, Markus Guentert, Regina Hebig, and Holger Giese (HPI, Germany) Enabling students to experience authentic stakeholder meetings as part of their requirements engineering education is a challenging task. To be authentic, involved stakeholders need to be affected by what students deliver. However, this is usually not the case. Trying to provide students authentic stakeholder interactions, we already specified two distinct settings suitable for recruiting real stakeholders by providing a benefit for them in return. However, scalability issues of these settings remained. In this paper, we present two ideas to overcome this issue. By cooperating with software companies which are building a product line, we gain access to many diverse stakeholders. Further, we propose to rely on course alumni to supervise stakeholder interactions to increase the scalability by reducing the lecturers’ supervision effort. These ideas are explained using a currently running course setting in collaboration with a software start-up which builds a product line of sports club management applications. ![]() |
|
Kopczyńska, Sylwia |
![]() Sylwia Kopczyńska, Jerzy Nawrocki, and Mirosław Ochodek (Poznan University of Technology, Poland) ![]() |
|
Lassenius, Casper |
![]() Jari Vanhanen, Timo O. A. Lehtinen, and Casper Lassenius (Aalto University, Finland) Abstract—In this paper, we describe how we teach real-world software engineering to students using a project course simulating in-vivo software development projects. The course gives the students an opportunity to try out in practice the skills gained on other computer science and software engineering courses. The students execute projects in teams consisting of seven to ten students, developing software for a real customer. Students spend more than 150 hours each on the project. The main stakeholders of the projects are the project team, customer, and mentor. The mentor represents the course personnel and provides practical guidance for the project team during the project. During the course, the students are supported by mentoring and experience exchange sessions. While laborious, the course is consistently ranked in the top three in the CS curriculum by the students. ![]() |
|
Lehtinen, Timo O. A. |
![]() Jari Vanhanen, Timo O. A. Lehtinen, and Casper Lassenius (Aalto University, Finland) Abstract—In this paper, we describe how we teach real-world software engineering to students using a project course simulating in-vivo software development projects. The course gives the students an opportunity to try out in practice the skills gained on other computer science and software engineering courses. The students execute projects in teams consisting of seven to ten students, developing software for a real customer. Students spend more than 150 hours each on the project. The main stakeholders of the projects are the project team, customer, and mentor. The mentor represents the course personnel and provides practical guidance for the project team during the project. During the course, the students are supported by mentoring and experience exchange sessions. While laborious, the course is consistently ranked in the top three in the CS curriculum by the students. ![]() |
|
Ludewig, Jochen |
![]() Jochen Ludewig and Ivan Bogicevic (University of Stuttgart, Germany) The software engineering curriculum offered by the University of Stuttgart emphasizes project work from the first to the last semester. While some of the projects are similar to those in other programs, others are less common. In this paper, we describe an introductory course called “Program Understanding”, and the so called “Consulting Task”. We also give a short description of what we call the First Software Project and the Large Software Project. In the Program Understanding course, new students learn to understand a fairly large, complex program in order to implement some modifications. In the Large Software Project, some ten people work on a serious software development for one year. In the Consulting Task, a group of three students analyses a problem, usually one given by an industrial partner. The students investigate possible solutions, and finally deliver a recommendation. Both our experience and feedback from students, including feedback from alumni, prove that these projects are very successful and highly esteemed. ![]() |
|
McCartney, Robert |
![]() Swapna S. Gokhale, Thérèse Smith, and Robert McCartney (University of Connecticut, USA) Software Engineering (SE) projects that emphasize maintenance and evolution can emulate industrial challenges and prepare students for careers in the software industry. Designing maintenance-centric SE projects, however, is difficult because software code upon which these projects must be based is not readily available. Open Source Software (OSS) can alleviate this issue by offering a rich and varied volume of code. This rich diversity of OSS projects, however, presents the greatest hurdle in seamlessly selecting suitable projects for integration. To better understand the scope of this diversity, initially, we propose to manually select uniformly difficult projects of appropriate complexity. Ultimately, based on the experiences and insights acquired through the manual selection, we envision the development of a systematic methodology based on software metrics to ease the project selection process. Such a systematic methodology will pave the way for the adoption of the OSS-based approach at peer institutions, bringing us a step closer to injecting realism into SE projects. ![]() |
|
Nawrocki, Jerzy |
![]() Sylwia Kopczyńska, Jerzy Nawrocki, and Mirosław Ochodek (Poznan University of Technology, Poland) ![]() |
|
Ochodek, Mirosław |
![]() Sylwia Kopczyńska, Jerzy Nawrocki, and Mirosław Ochodek (Poznan University of Technology, Poland) ![]() |
|
Pollock, Lori |
![]() Richard Burns, Terry Harvey, and Lori Pollock (University of Delaware, USA) This paper reports our experience developing a product for a real-world client using a software engineering process across multiple semesters with different students each semester. New student teams test, debug, deploy, and critique previous semesters' software and then continue its development. Students are motivated to think critically about and experience real-world software engineering practice. We describe how students in one semester collectively identified the software engineering problems that could be resolved in the current semester, how the students proceeded to tackle those problems, and the impacts of their actions for future semesters. ![]() |
|
Punnekkat, Sasikumar |
![]() Sigrid Eldh and Sasikumar Punnekkat (Ericsson, Sweden; Karlstad University, Sweden; Mälardalen University, Sweden) The ubiquity of software is making every industry increasingly dependent on it for achieving their core products' functionality. The complexity in a telecom network requires not only thorough understanding of telecommunication per se, but software becomes equally interesting. This is the case with many industries, which rely more and more on software as their key enabler. Industry definitely needs a large number of software engineers with potential to be productive from day one. They are feeling impatient at the academic community for not being pragmatic. At the same time Academic community faces many challenges, which often make them thread a traditional path thus ignoring the industrial needs. We present some of these challenges from both the industrial and academic perspectives. We also present how we established a Master level advanced course on software verification and validation through mutual support and collaboration which became highly successful. ![]() |
|
Shida, Takahiro |
![]() Shigetoshi Yokoyama, Nobukazu Yoshioka, and Takahiro Shida (National Institute of Informatics, Japan; NTT DATA Intellilink, Japan) Education of cloud engineers will be crucial for the continued development of cloud technologies. We have developed an open-source software platform called edubase Cloud for education. The platform has multi-cloud architecture. In this paper, we discuss how edubase Cloud provides an alterable cloud platform and how effective it is for educating cloud engineers. ![]() |
|
Smith, Thérèse |
![]() Swapna S. Gokhale, Thérèse Smith, and Robert McCartney (University of Connecticut, USA) Software Engineering (SE) projects that emphasize maintenance and evolution can emulate industrial challenges and prepare students for careers in the software industry. Designing maintenance-centric SE projects, however, is difficult because software code upon which these projects must be based is not readily available. Open Source Software (OSS) can alleviate this issue by offering a rich and varied volume of code. This rich diversity of OSS projects, however, presents the greatest hurdle in seamlessly selecting suitable projects for integration. To better understand the scope of this diversity, initially, we propose to manually select uniformly difficult projects of appropriate complexity. Ultimately, based on the experiences and insights acquired through the manual selection, we envision the development of a systematic methodology based on software metrics to ease the project selection process. Such a systematic methodology will pave the way for the adoption of the OSS-based approach at peer institutions, bringing us a step closer to injecting realism into SE projects. ![]() |
|
Vanhanen, Jari |
![]() Jari Vanhanen, Timo O. A. Lehtinen, and Casper Lassenius (Aalto University, Finland) Abstract—In this paper, we describe how we teach real-world software engineering to students using a project course simulating in-vivo software development projects. The course gives the students an opportunity to try out in practice the skills gained on other computer science and software engineering courses. The students execute projects in teams consisting of seven to ten students, developing software for a real customer. Students spend more than 150 hours each on the project. The main stakeholders of the projects are the project team, customer, and mentor. The mentor represents the course personnel and provides practical guidance for the project team during the project. During the course, the students are supported by mentoring and experience exchange sessions. While laborious, the course is consistently ranked in the top three in the CS curriculum by the students. ![]() |
|
Yokoyama, Shigetoshi |
![]() Shigetoshi Yokoyama, Nobukazu Yoshioka, and Takahiro Shida (National Institute of Informatics, Japan; NTT DATA Intellilink, Japan) Education of cloud engineers will be crucial for the continued development of cloud technologies. We have developed an open-source software platform called edubase Cloud for education. The platform has multi-cloud architecture. In this paper, we discuss how edubase Cloud provides an alterable cloud platform and how effective it is for educating cloud engineers. ![]() |
|
Yoshioka, Nobukazu |
![]() Shigetoshi Yokoyama, Nobukazu Yoshioka, and Takahiro Shida (National Institute of Informatics, Japan; NTT DATA Intellilink, Japan) Education of cloud engineers will be crucial for the continued development of cloud technologies. We have developed an open-source software platform called edubase Cloud for education. The platform has multi-cloud architecture. In this paper, we discuss how edubase Cloud provides an alterable cloud platform and how effective it is for educating cloud engineers. ![]() |
27 authors
proc time: 0.03