A cross-collegiate analysis of software development course content

Understanding the processes in education, such as the student learning behavior within a specific course, is a key to continuous course improvement. In online learning systems, students’ learning can be tracked and examined based on data collected by the systems themselves. However, it is non-trivial to decide how to extract the desired students’ behavior from the limited data in traditional classroom courses. Software development courses are a domain where student behavior analysis would be especially useful, as continuous teaching improvement in this fast progressing domain is necessary. In this paper, we propose to use process mining for improvement-motivated process analysis of a software development course (web development in particular). To this end, we analyze Git logs of students’ projects to understand their development processes. Process mining has been chosen as it can help us to find a descriptive model of this process. The main contribution of this paper is the detailed methodology of process mining usage for students’ project development analysis, considering various commit characteristics, which are crucial in understanding student coding-behavior patterns. The process mining analysis proved to be very useful, indicating multiple directions for the course improvement, which we also include in this work as a secondary contribution. The third contribution of this work is the summary and discussion of the process mining advantages and current gaps in process mining research for this task. The data we used are made publicly available to other researchers.

This paper describes our experience integrating an authentic learning project into a junior-level software development course. During the course, students applied full software development life cycle processes to meet a campus need -- providing classroom clicker support without purchasing additional hardware. The paper provides the motivation for this approach, summarizes relevant developments in classroom response systems, details the design of the class project, and shares our results. Finally, we offer reflections describing both intended and unintended outcomes of this experiment.

It is often lamented that computer science graduates lack the skills needed to work on large, real-world projects. This paper describes an undergraduate course in software development recently offe...

This Innovative Practice Full Paper presents an approach of using software\ndevelopment artifacts to gauge student behavior and the effectiveness of\nchanges to curriculum design. There is an ongoing need to adapt university\ncourses to changing requirements and shifts in industry. As an educator it is\ntherefore vital to have access to methods, with which to ascertain the effects\nof curriculum design changes. In this paper, we present our approach of\nanalyzing software repositories in order to gauge student behavior during\nproject work. We evaluate this approach in a case study of a university\nundergraduate software development course teaching agile development\nmethodologies. Surveys revealed positive attitudes towards the course and the\nchange of employed development methodology from Scrum to Kanban. However,\nsurveys were not usable to ascertain the degree to which students had adapted\ntheir workflows and whether they had done so in accordance with course goals.\nTherefore, we analyzed students' software repository data, which represents\ninformation that can be collected by educators to reveal insights into learning\nsuccesses and detailed student behavior. We analyze the software repositories\ncreated during the last five courses, and evaluate differences in workflows\nbetween Kanban and Scrum usage.\n

Project-based learning (PBL) has gained traction in higher education as an effective pedagogical approach that promotes active learning, critical thinking, and the practical application of knowledge. Unlike traditional lecture-based methods, PBL engages students in collaborative projects that simulate real-world challenges, thereby enhancing their problem-solving skills. However, a notable gap exists in understanding how these theoretical benefits translate into actual student experiences. Therefore, this study aims to investigate undergraduate students’ perspectives and experiences in project-based learning. By understanding students’ perspectives and experiences, this research highlights the benefits, challenges, and overall effectiveness of PBL. A qualitative research design was employed, involving in-depth, semi-structured interviews with 30 undergraduate students. The students were exposed to project-based learning in research methodology and software development courses. The interviews were conducted in person and via video conferencing, ensuring a comfortable environment for participants to share their insights. The data collected from the interviews were transcribed verbatim and analyzed using thematic analysis to identify recurring themes and patterns. The thematic analysis revealed several key themes: the importance of consistent attendance due to the tailored and sequential nature of PBL; the facilitation of deeper understanding and the practical application of theoretical concepts; difficulties in adapting to PBL, especially when transitioning from traditional teaching methods; benefits and logistical challenges of collaboration; the crucial role of the iterative process of assessment and feedback in mastering concepts; and the fostering of autonomy and the development of essential skills such as time management and problem-solving.

Serious games provide a method for teaching students in an engaging, non-threatening way. To be useful educational tools, these games need to be designed with the lesson objectives in mind. This paper uses the Game Design Matrix to design a game from learning objectives. The lesson objectives focus on software development, security and operations (DevSecOps). DevSecOps requires judging the cost and risk trade offs between secure and unsecured software aspects including code, data and usability; devising a strategy to produce a system under threat; comprehending that partial security may equate to no security; and identifying examples of insecure code and methods of mitigating it. These lesson objectives combined with the teaching environment drive design decisions that produce a game that fits well into a graduate level course in secure software design and development. We evaluate the game in a graduate course on secure software design and development. Learner surveys confirm that DevSecOps conveys the learning objectives in an engaging way.

Mobile computing is popular when wireless network has been deployed almost everywhere. Smartphones have been the important tools in our society for the abundant functions including communication, entertainment and online office etc as the pivotal devices of mobile computing. Smartphone software development has also become more important than before. Android is one of the emerging leading operating systems for smartphones as an open source system platform. Many smartphones have adopted this platform and more smartphones will do so in the future. It is also an emerging problem on how to develop software for smartphones based on Android and those platforms like it. We propose smartphone software development course design based on Android in this paper. What this course focuses is how to teach the development technology to Students. The course design has two parts including the syllabus design and hands-on lab design. At the same time, the innovations are also described in detail and these innovations play a key role in the teaching.

The growing enactment of Global Software Engineering in industry has triggered educational institutions to perceive the importance of preparing students for distributed software development. During the last twelve years we have disclosed advantages and pitfalls of GSE to our students through our Distributed Software Development course. After running the projects according to the iterative process model for eleven years, we decided to shift to an agile development model, SCRUM. This decision was due to the growing industrial adoption of agile methods, but more importantly to increase proactiveness, sense of responsibility, and to balance the workload among the project team members. In this paper we describe the process and outcomes of our first attempt at introducing SCRUM in our distributed course.

The increasing needs of information and communication technology affects the emerge of information and communication technology projects. One type of its project is software application development project, which this kind of project often totally or partially fails. Indonesia, as one of developing country requires various software types for their business environment in all aspects such as government, private sector or also personal use. The high use of information technology was not followed by awareness and financial ability to use proprietary technology, which is costly and monopolized by some certain vendor. The needs of uncostly and monopolized software was responsed by a software development community and some software vendor which later produced some softwares that are free to use and developed. These kind of softwares are called free and open source software (FOSS). Open source technology that emerged and boomed since few years lately still have various weakness and need to be accomodated by software developers and consumers. Differ from proprietary software, product support from vendor or community isn’t always available. This research’s aim is to identify, structuring and also analyze risk factors of open source-based software development.First stage of this research is to identify risk factors based on Carr et al, (1993) an approach named taxonomy-based risk identification. Combinined with risk identification by Peer, (2006) and FFIEC, (2004), it resulted new factor atribute. Second stage of research is risk assessment of identified risk factors. Most of risk assessment influenced by perception from expert, therefore, the assessment methods is needed to accomodated expert perception. This research used two perception-based methods, qualitative assessment by AS/NZS 4360, (1999) and Analytical Hierarchy Process proposed by Saaty, (1996). Both of this methods was assumed able to map expert’s perception and yield classification and priorities of risk factors.As a conclusion, risk factors identification by Carr et al, (1993) need to be enhanced by new atribute, which is the license options. This atribute becomes an important matter in course of software development because it can influence project succes and software legal attitude. AS/NZS 4360 Qualitative risk assessment classifies risk factors into three classification: extreme, high and moderate (while the low classification isn’t present). AHP risk assesment yields risk factors priority and classification by converting risk weight into four classification : extreme, high, moderate and low. Keywords : Risk Assessment, Taxonomy Software Development, Qualitative Analysis, Pairwise Comparison, analytical Hierarchy Process.

In this paper we describe our initiative to incorporate research, professional practice and methodologies into two undergraduate software engineering courses. As part of the Undergraduate Research Experience (URE) initiative on our campus, we modified two of our core software engineering courses. In our Software Development II (junior level) and Software Development Project (senior level) courses we integrated research projects, corporate visits and research talks to develop a deeper understanding of software engineering research and practice amongst our students.

Traditionally, computer software development courses have produced projects with small numbers of homogeneous users requiring limited maintenance and which run on a single platform as opposed to products which are distributed to large numbers of diverse users, run on multiple platforms, and which are upgraded and re-released many times. The NSF/ILI-IG grant with the university match provided funding to establish a software product development laboratory in an effort to provide students with the product development experience that many will need upon graduation.This paper discusses the concept for, the goals and subgoals of, and the first year's evaluation of the Product Development Laboratory.

Modern softwares are very large and complex. As the size and complexity of software increases, software developers feel an urgent need for a better management of different activities during the course of software development. In this paper, we present an approach of use case scenario prioritization suitable for project planning at an early phase of the software development. We consider only use case model in our work. For prioritization, we focus on how critical a scenario path is, which essentially depends on density of overlapping of sub path of a scenario path with other scenario path(s) of a use case. Our proposed approach provides an analytical solution on use case scenario prioritization and is very much effective in project management related activities as substantiated by our experimental results.

Within a year of its launch, the University of Moratuwa's open learning platform (open.uom.lk) has over 180,000 registered participants, providing free and open access to a series of asynchronous online courses in software development. Nearly 17,000 people have completed the two foundation courses: Python for Beginners and Web Development for Beginners. Considering the low overall completion rate compared to the total number of registered users, it is important to study the factors contributing to successful completion while promoting meaningful learning. To support the learning process, there are multiple activities like lecture videos, lecture notes, coding playgrounds, lecture slides, assessments, and discussion forums. Thus, this study investigates student behaviour to understand activities that are high in cognitive load and promote active engagement. The study is carried out using learning management system (LMS) user logs and feedback from completed and ongoing students. The elaborative logs with user activities and time stamps help identify the pace of completion by students with different capabilities and learning patterns. The study's findings will be useful to educators because they will be able to design similar LMS platforms that optimise student performance and promote effective learning outcomes. Furthermore, it would be useful to evaluate how students would manage the load in asynchronous online learning programs. Understanding how the learning and assessment activities are related to the completion of the course would enable predicting completion rates and times to properly plan for the employment opportunities for the successful learners.

Teaching group based Agile software development project courses is difficult. There are many aspects that need to be considered for a project to be successful such as a well defined scope, students working effectively together, and engaging with the customer. In this paper we present an experience report at teaching an Agile software development project course that involved teams developing web applications. The resources developed for the course and discussion about our experience will help inform others who also wish to teach group based software development courses.

Human Computer Systems (HCS) consist of machinery, software and people. However, all too many introductory software development courses concentrate unduly on the nature of programming and ignore the needs of the user. In this paper we will implicitly critique most existing introductory software development units, from an analysis of their supporting texts. We will suggest a checklist that could be applied to a unit or to a text to ensure that they include usability considerations. We will also critique many existing HCI units and courses that do not pay adequate attention to integrative exercises. We will conclude by suggesting ways in which these problems can start to be solved.