Teaching Object-Oriented Software Engineering through Problem-Based Learning in the Context of Game Design

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.

Learning Software Engineering principles, processes, methods and tools is a prerequisite to becoming a Software Engineer. The technological advancements and revolution in this new century are probing the boundaries of education and training in software engineering. This work tries to locate the shortcomings in existing approaches to Education in Software Engineering (ESE) in respect to today's technological advancements. We hereby proposed a new model for Education in Software Engineering to bridge the industry-academia gap.

Indian software industry has set up huge growth targets for future. These targets would be heavily affected by the software engineering (SE) education scenario in the country. The purpose of this paper is to provide a holistic understanding of SE education issues and challenges specific to Indian context, from both industry and academic perspective. This study is based on our (a) interaction with industry through SE education related projects, surveys and discussions. (B) Observations as an integral part of Indian SE educators' community. There is an urgent need for addressing these deep rooted issues, as the lack of proper SE education may be the single largest factor that may negatively affect the industry. Understanding these issues will help to identify the action items that initiate software engineering educational reforms in the country. We also discuss the essential and minimal set of SE knowledge, skills and dispositions that the Indian industry expects from engineers who will be joining the industry. Indian software industry is a global leader in software application development and maintenance services, but there very few studies on the issues and effects associated with SE education in the Indian context. Though this discussion is limited to India, but we believe that it represents the existing conditions in many developing countries where IT and ITES (IT enabled services) industry is gaining importance.

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.

Contribution: Results and conclusions on the use of transactive memory system (TMS) in software engineering (SE) education in student project teams that consist of undergraduate and postgraduate students are documented. This can be valuable for the adoption of this learning approach and team formation by other universities and institutes. Background: Preparing students for the SE industry requires bringing them in close collaboration to real-world tasks. This is usually performed via students carrying out software projects, working in teams. In such environments, the knowledge sharing and the interactions within the team are worth investigating, as they can affect the outcome of the student collaboration and can provide insight on how the collaboration is valued by the team members. Research Questions: 1) What is the effect of TMS on students in SE education? 2) Do parameters, such as gender, affect TMS development? 3) Does the inclusion of a project manager with more expertise affect TMS? Methodology: Students were divided into teams working on SE projects. Teams consist of both undergraduate and postgraduate students. Data from students on TMS for consecutive academic years were gathered. Findings: TMS is present in student teams and some of its scale items are affected by parameters, such as the team composition and the project type. TMS also affects performance.

This paper proposes a framework to support the development and use of tools that support the teaching of software and Web engineering. It describes the evolution of tools to support the teaching of software engineering from simple client-side tools that support drawing DFDs and UML diagrams to Web-based repositories that support process modelling. The paper specifically introduces the concept of and describes their use within the WWW. It also describes tools that automatically create automated walkthroughs for the World Wide Web (WWW) and their evaluation within a masters-level software engineering module. Conclusions are drawn about the general applicability of the framework and proposals are made for further work in this area.

The traditional teaching-learning processes used by Chilean universities are changing. This document describes two innovative strategies applied to teach software engineering (SE) at two universities in Chile. Teaching experiences are part of our ongoing effort to improve the current teaching-learning strategies of SE in the mentioned universities. In this paper, we describe our teaching experiences using both problem-based learning (PBL) and an agile software engineering methodology, to achieve learning outcomes and to improve students' participation during classes. We present two ways to correlate the activities of a software project; these activities are tasks of a software methodology and an active learning strategy based on PBL. The strategies used to verify the accomplishment of these goals are also detailed.

In the Software Engineering Education (SEE) context, virtual worlds have been used in order to improve learning outcomes. However, there is a gap in the literature in order to characterize the use of the Metaverse for SEE. The objective of this work is to characterize the state of the art of virtual worlds in SEE and provide research opportunities and challenges to fill the limitations found. We conducted a systematic literature review, and we established 8 research questions that guided the study, as well as performed data extraction. We report on 17 primary studies that deal mostly with immersive experiences in SEE. The results show some limitations: few Software Engineering (SE) topics are covered; most applications simulate environments and do not explore new ways of viewing and interacting; there is no interoperability between virtual worlds; learning analysis techniques are not applied; and biometric data are not considered in the validations of the studies. Although there are virtual worlds for SEE, the results indicate the need to develop mechanisms in order to support the integration between virtual worlds. Therefore, based on the findings of the review, we established a set of components grouped by 5 layers to enable the Metaverse for SEE through fundamental requirements. We hope that this work can motivate promising research in order to foster immersive learning experiences in SE through the Metaverse.

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.

University Extension is an educational, cultural, and scientific process that establishes the exchange between academic and popular knowledge. Project-Based Learning (PjBL) consists of allowing students to confront the issues and problems of the world through a real project. PjBL has been adopted in Software Engineering (SE) teaching to motivate and engage students in studying and applying processes and methods. In this work, the university extension was integrated with the PjBL in teaching SE in a postgraduate course to bring students closer to real practices of software development, meeting a demand from the State of notorious value for society. Interviews were conducted with stakeholders, artifacts were delivered, and students received feedback from the professor and the stakeholders. Through a questionnaire, the students provided feedback about the practical activity, the learning method, and their perceptions regarding their evolution and dedication to group work. We can highlight the following findings: (i) the use of PjBL together with extension and the development of a real project was promising for the evolution of learning; (ii) greater motivation of the students, who evaluated: (iii) the learning method as satisfactory, and (iv) the practical activity and their evolution of learning as good and excellent. Our main contribution is the lessons learned that might guide future experiences that adopt PjBL in SE teaching and extension.

Software engineering education must be guided by developments in software engineering and aim for professional and educational development of students. This position paper explores the historical and conceptual evolution of software engineering as a discipline central to modern integrated design, software systems, and process science, tracing the trajectory from early structured models, through waterfall, to Agile and AI-augmented paradigms, and looks at how changes in application mix and modes of use, technological complexity, and business and enterprise needs have shaped development methodologies. Special attention is paid to the role of generative AI on the software engineering process and the role of the software engineer, altering workflows, collaboration, and enterprise architectures, and further enabling automation, digital transformation, and autonomous systems, shifting responsibilities and skill sets upwards. The article then considers corresponding shifts in software engineering education, highlighting the need for curricula that intertwine process thinking, systems theory, and ethical engagement, integrate with generative AI technologies, and place greater emphasis on “soft skills”, in courses that combine development of professional expertise with conceptual capabilities and an enhanced capacity for life-long learning. It then presents a set of requirements, options, and guidelines for software engineering education in the era of generative AI.

Background. Programming is widely known to be a cognitively demanding field. Learning programming can be a strenuous task without the proper guidance and methodology. Students often face difficulties in understanding even the most basic and fundamental concepts of programming, leading to their confusion and disappointment. Serious games for programming have the potential to alleviate students’ difficulties with programming. Aim. This article introduces a new serious game named jAVANT-GARDE which aims to educate the player on the basic concepts of programming and object-oriented programming through Java. By design, the game is suitable for everyone, even for players with no previous knowledge of programming. This article aims to present important information regarding the design, implementation and pilot evaluation of jAVANT-GARDE. Method. The game was evaluated by 42 high school students (age 16-17) in terms of perceived player experience and short-term learning. The participants played the game for one hour in the school lab and then answered a questionnaire based on the MEEGA+ framework. Results. Students evaluated positively the game in terms of its usability, confidence in playing the game, challenge, satisfaction, fun, focused attention and relevance. Moreover, the majority of students stated that would prefer learning programming with this game to learning through other teaching methods. Conclusions. The results of the pilot study and students’ replies in the questionnaire are rather positive. This gives us the initiative to proceed with studying the effect of the game in long-term learning of programming concepts.

This chapter addresses the application of computer games and simulations in order to explore reality in many educational areas. The Games-Based Learning (GBL) can improve the teaching and learning experience by training future professionals in real life scenarios and activities that enable them to apply problem-solving strategies by putting into use the correct technique stemming from their own skills. For that reason, GBL has been used in software engineering teaching. At Pontifical Catholic University of Rio de Janeiro, the authors have developed SimulES-W (Simulation in Software Engineering), a tool for teaching software engineering. SimulES-W is a collaborative software board game that simulates a software engineering process in which the player performs different roles such as software engineer, technical coordinator, project manager, and quality controller. The players can deal with budget, software engineer employment and dismissal, and construction of different software artifacts. The objective of this chapter is to describe the approach to teaching software engineering using SimulES-W and demonstrate how pedagogical methodology is applied in this teaching approach to improve software engineering education. The teaching experience and future improvements are also discussed.

Teaching software engineering (SE) in our universities and colleges is crucial as a means to help offset the software crisis. This paper describes an evolutionary approach used at one university to address the problems of teaching software engineering. Issues of difficulty in teaching software engineering, the evolution of software engineering techniques and our specific evolutionary approaches to teaching software engineering are presented. The nature of our courses, projects and laboratories in the curriculum is examined. Suggestions are presented on enhancements to existing approaches to software engineering education techniques, with an emphasis on guidelines for projects.

Studio-based teaching is a method commonly used in arts and design that emphasizes a physical "home" for students, problem-based and peer-based learning, and mentoring by academic staff rather than formal lectures. There have been some attempts to transfer studio-based teaching to software engineering education. In many ways, this is natural as software engineering has significant practical elements. However, attempts at software studios have usually ignored experiences and theory from arts and design studio teaching. There is therefore a lack of understanding of what "studio" really means, how well the concepts transfer to software engineering, and how effective studios are in practice. Without a clear definition of "studio", software studios cannot be properly evaluated for their impact on student learning nor can best and worst practices be shared between those who run studios. In this paper, we address this problem head-on by conducting a qualitative analysis of what "studio" really means in both arts and design. We carried out 15 interviews with a range of people with studio experiences and present an analysis and model for evaluation here. Our results suggest that there are many intertwined aspects that define studio education, but it is primarily the people and the culture that make a studio. Digital technology on the other hand can have an adverse effect on studios, unless properly recognised.