Using TSPi and PBL to support software engineering education in an upper‐level undergraduate course

In software engineering education, large projects are widely recognized as a useful way of exposing students to the real-world difficulties of team software development. But large projects are difficult to put into practice. First, educators rarely have additional time to manage software projects. Second, classrooms have inherent limitations that threaten the realism of large projects. Third, quantitative evaluation of individuals who work in groups is notoriously difficult. As a result, many software engineering courses compromise the project experience by reducing the team sizes, project scope, and risk. In this paper, we present an approach to teaching a one-semester software engineering course in which 20 to 30 students work together to construct a moderately sized (15 KLOC) software system. The approach combines carefully coordinated lectures and homeworks, a hierarchical project management structure, modern communication technologies, and a web-based project tracking and individual assessment system. Our approach provides a more realistic project experience for the students, without incurring significant additional overhead for the instructor. We present our experiences using the approach the last 2 years for the software engineering course at The College of William and Mary. Although the approach has some weaknesses, we believe that they are strongly outweighed by the pedagogical benefits.

Many studies have reported the utilization of Problem-Based Learning (PBL) in teaching Software Engineering courses. However, these studies have different views of the effectiveness of PBL. This paper presents the design of an Advanced Software Engineering course for undergraduate Software Engineering students that uses PBL to teach them Agile software development methods- particularly Scrum. The course also aims to develop entrepreneurial skills needed for software engineering graduates to better prepare them for the software industry. The assessment process designed for this course is illustrated. The paper shows that Scrum practices correlate with the characteristics of the PBL approach, which has resulted in a successful experience of PBL as reported by students in an end of a semester survey.

The goals of computer science department and software engineering courses are not always clear as they could be, and exactly how much of a computer science curriculum should be spent on software engineering topics at the expense of topics with more immediate relevance to computer science majors is far from clear. Computer science students are sometimes skeptical about the relevance of software engineering course topics, particularly those who have had some experience in industry. They report that the techniques and procedures covered in standard software engineering texts are seldom used in industry. There is not enough communication between Industry and Academia, and graduates often must be re-trained for their new jobs. This is a proposal for a modification in the approach to software engineering education for computer science majors, and for clarification of the goals of computer science programs, and calls for procedures to increase the relevancy of computer science and software engineering courses to meet the needs of industry.

It is a common belief that good software tools are necessary to support both research and education in software engineering. The authors document their experience, in support of this belief, with two data flow testing tools named ASSET and ATAC and one mutation testing tool named MOTHRA. These tools have been in use at Purdue University in research projects related to software testing and reliability. The tools have also been used in both undergraduate and graduate courses in software engineering. >

This study presents a case study of the integration of usability evaluation into the development of task based information system prototypes in undergraduate software engineering course projects within a problem-based learning (PBL) approach. As part of the course, usability evaluation was integrated into the software development process, and the usability evaluation performance (UEP) of the projects was assessed in terms of the following criteria: effectiveness, efficiency and problem validity. It also analyzed the problem solution rate of the projects and their correlation between UEP criteria. Additionally, the study in-depth analyzed the students' final conclusions regarding the design process. The relationship between UEP criteria and the problem solving rate was examined using Spearman correlation analysis. In addition, final conclusions and problem solving behaviors were analyzed through document and thematic analysis techniques. The results supported that there is a significant correlation between usability evaluation criteria and problem solving rate. The main themes that emerged regarding usability problem solving behaviors were navigation design, error handling, database connection, algorithm design, search matching, system-user communication design and others. Final conclusions showed that project teams gained valuable insights into user-centered design, solved critical usability problems and improved their prototype design. It can be concluded that the integration of usability into software engineering education using the above approach contributes to students' understanding of user-centered interaction design.

In teaching software engineering, it is a major challenge to integrate applied methodology and theory into the practice of software development. Today teaching a course in software engineering involves a theoretical approach with white board and doing a project at the end of the course. Teaching Software engineering as a course involves many disciplines and requires delivering lectures accompanied by lecture demos and hands on lab sessions to accompany individual constituent topics or areas that form the bricks and mortar of this course. Only when the bricks and mortar of software engineering have delivered a solid foundation, is it then the software engineering as a course will be delivered in a true and meaningful sense. This paper presents a method to teach Software Engineering using the applied approach that the author designed and successfully used.

Project-based learning is widely recognized as an effective pedagogical approach in software engineering education, fostering real-world problem-solving, collaboration, and the integration of theory and practice. However, its scalability is challenged by the resources demanded for individualized feedback, especially in large classes. This pilot study explored the feasibility of simulated automated formative feedback to support student teams in a project-based software engineering course. Eighty-six students participated over 4 weeks, alternating between receiving simulated automated formative feedback emulated by instructors and standard feedback. Weekly surveys assessed perceptions of usefulness and motivation. No statistically significant differences were found between feedback conditions (Cohen's d = 0.16). Students expressed positive attitudes toward the simulated automated formative feedback: 78% agreed it supported their learning goals, and 74% reported it increased motivation. These findings suggest that automated feedback tools may effectively complement instructor support, offering a scalable solution for enhancing formative feedback in project-based learning environments.

The instructors generally utilize conventional methods in teaching software engineering courses, where the students are provided theoretical knowledge based on text books or lecture notes. Usage of collaborative tools may be a solution to the problems of not practicing the depth of the components of the subject. This study proposes the usage of a collaborative tool, namely, Google Docs in a software engineering course based on predefined scenarios. The review meeting subject was selected for this purpose and students’ reactions were assessed with a survey after the completion of the experiments. The survey data were analysed using least square regression method. The results have shown that efficiency, certainty, satisfaction, advantage, complexity, learnability, and intention are indicators of the adoption of the online collaborative tool.

Software development is a fast-changing area. New methods and new technologies emerge all the time. As a result, the education of software engineering is generally considered not to be keeping pace with the development of software engineering in industry. Given the limited resources in academia, it is unrealistic to purchase all the latest software tools for classroom usage. In this chapter, the authors describe how free/open-source data and free/open-source tools are used in an upper-level software engineering class at Indiana University South Bend. Depending on different learning objectives, different free/open-source tools and free/open-source data are incorporated into different team projects. The approach has been applied for two semesters, where instructor’s experiences are assembled and analyzed. The study suggests (1) incorporating both free/open-source tools and free/open-source data in a software engineering course so that students can better understand both development methods and development processes and (2) updating software engineering course regularly in order to keep up with the advance of development tools and development methods in industry.

Within the last few years constructivism has attracted both computer science and software engineer educators, because of its potential for improving academic learning. Currently, however, the application of constructivism is limited to examples in specific contexts so that it is difficult to transfer them to other institutions or even other courses. To apply effectively constructivism to software engineering and computer science education, instructors need a generic pedagogical model for translating constructivist principles into practice. This paper reports on the application of a pedagogical model for translating constructivism into a Web-based course in object-oriented software engineering.

Most of the principles and concepts that need to be taught in Software Engineering courses are hard to share the realistic experiences because it is difficult to give the student practical exposure to the insight and processes involved. This paper presents an innovative framework tailored for the establishment of an immersive learning environment within the context of a Software Engineering Project course. The overarching objective is to effectively tackle the inherent challenges associated with teaching intricate software engineering concepts, notably Agile Scrum and Team Software Process (TSPi). Conventional pedagogical approaches often prove inadequate in providing a comprehensive and engaging learning experience for students, educators and stakeholders. In response, our study introduces a pioneering immersive learning approach, offering a robust solution to this educational gap. To gauge the framework's efficacy and pertinence, we conducted online surveys, specifically targeting third-year students enrolled in the Software Engineering Laboratory course and the project stakeholders involved. These surveys were instrumental in collecting valuable feedback on the practicality and impact of our approach in enhancing the teaching and learning processes. This study presents a thorough exposition encompassing the framework's conceptualization, implementation and iterative evolution. Our research outcomes reveal that our immersive learning approach has successfully met the predefined course objectives, effectively addressing the intrinsic challenge of imparting hands-on experiences associated with software engineering principles and concepts. As a significant contribution to the ongoing initiatives aimed at elevating software engineering education, our study underscores the importance of providing students with tangible exposure to vital concepts such as Agile Scrum and TSPi. Moreover, this paper delineates the collaborative journey involved in the creation, execution and refinement of the course framework. Ultimately, our research endeavours to evaluate the degree to which our innovative framework aligns with the objectives established by both students and stakeholders. By doing so, it underscores the transformative potential of our approach in reshaping the landscape of software engineering education, ultimately enhancing its effectiveness and relevance.

When teaching software engineering courses it is highly important to have good text books that are well-founded, up-to-date, and easily accessible to students. However, currently available text books on the market are either very broad or highly specialized, making it hard to select appropriate books for specific software engineering courses. Moreover, due to the rapidly changing subject of software engineering, books tend to become obsolete, which make students hesitate to buy books even if they are part of the listed course literature. In this paper, we briefly explain and discuss an approach of using a web-based system for creating collaborative and peer-reviewed text books that can be customized individually for specific courses. We describe and discuss the proposed system from a use case perspective.

Recent advances in AI-powered writing tools provide powerful support for students but also raise concerns about academic misconduct, especially in large-enrollment courses where monitoring is challenging. To address these concerns, this paper presents a case study on implementing video-based assignments as an alternative to traditional written assessments in an introductory BSc-level Software Engineering course. In this approach, students recorded concise video presentations responding to specific tasks and/or questions, demonstrating both conceptual understanding of course topics and analytical skills — making it more difficult to rely solely on AI-generated text. Survey data and follow-up interviews indicate that this video-based format not only curbed AI-assisted misconduct but also fostered deeper engagement, enhanced communication skills, and reinforced perceptions of fairness in evaluation. These findings underscore the potential of video assignments as a scalable method for mitigating emerging AI-related challenges while enhancing essential soft skills in software engineering education.

The software engineering education (SEED) workshop will address pedagogical issues related to software engineering education as part of computer science and engineering programs. During this workshop, we plan to share and discuss approaches -- focusing on tools and techniques - to the design and delivery of software engineering courses for effective teaching and learning.

Context: Undergraduate students often struggle with research methods and methodologies crucial for their development. Effective training is essential to bridge the gap between theory and practice. Objective: This course aimed to empower students with a solid understanding of scientific research, enhance their research planning skills and proficiency in empirical methods, and improve their scientific writing and presentation skills. Method: An in-person Empirical Software Engineering course was conducted for 17 undergraduates over 60 hours in a semester. It included theoretical classes, practical activities, seminars, evaluations of empirical articles, and peer evaluations of research projects. Results: Students reported high satisfaction with the course, particularly in topic approach, content references, and achieving objectives. Areas for improvement included clarity of course objectives and developing critical thinking skills. Most activities were found useful, though some were challenging. Conclusions: The course successfully developed research skills among students. Improving clarity of objectives and support for complex activities can further enhance the learning experience. This report provides insights into empirical research education in software engineering, highlighting successes and areas for improvement.