Experiences in Project-Based Software Engineering

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.

A critical open question in the mechanical engineering pedagogical literature is whether Capstone senior design can be taught as effectively online as in-person with emphasis on whether group work conducted under these contrasting conditions is equally effective. The onset of COVID-19 induced a natural experiment enabling comparison of engineering student group work conducted in-person versus all-online. Group work is an essential element of mechanical engineering education codified by Student Outcome 5 of ABET Criterion 3 (Groupwork). Peer evaluation is a common engineering group work assessment, especially in Capstone design courses. In this paper, recurring peer evaluations are evaluated to quantify how well students performed in groups within a longitudinal study conducted across five semesters of a mechanical engineering Capstone senior design course. In UF’s Mechanical Engineering Capstone courses, recuring peer evaluation surveys tied to group assignment deadlines were already established prior to COVID-19. By continuing to deploy this same survey when courses transitioned online during the pandemic, three full semesters of group performance data were collected when students were forced to meet remotely. As students returned to campus, the same survey provided comparative data for two semesters when students were meeting in person. These collected data represent a quantitative tool to evaluate how online vs. in-person group meeting setting impacts the quality of teamwork. This work shows that online vs. in-person meeting environments DID NOT have statistically significant impacts on teamwork performance for mechanical engineering Capstone students in the semesters being evaluated. This result suggests that ABET Criterion 3 Student Outcome 5 can be met just as effectively in online or in-person Capstone courses. This important result debunks the misconception that the quality and fidelity of Capstone groupwork is somehow diminished when senior design is taught online to learners remote from each other over the Internet. This finding adds to the growing body of evidence supporting the viability of an all-online Bachelor of Science in mechanical engineering program capable of receiving and maintaining ABET accreditation. Moreover, a forward-looking online ME program can include an effective Capstone senior design course with rich student groupwork interactions of quality equal to those experienced by students when meeting in-person.

A senior-level, project-based Software Engineering course taught at the University of Central Arkansas serves as the capstone course for the Computer Science Program and introduces students to the theory, tools, and techniques used to build large-scale software systems in a project-driven setting. Foundational to the course is the use of a class-wide, semesterlong course project to emphasize the theoretical aspects of the software process and the system used for scoring student performance on the project. One project is selected for the entire class with students divided into teams of four to six students to support different functional requirement areas. A milestone-driven approach is used following a modified version of the Unified Process for project development. Student scores on the project are divided into a group score, assignable via a rubric-like grade sheet, and an individual score which is determined by the individual’s effort as assigned using the task-management tool, Issue-Tracker. Experiences gained and lessons learned in teaching the course are provided as a guide for those wishing to follow a similar approach to teaching Software Engineering in the future.

Capstone project-based courses offer a favorable environment for the development of student skills through an approach incorporating theoretical and practical components. However, it is often difficult to successfully coordinate between students, stakeholders, and the academic team. The absence of suitable tools for addressing this issue, along with time constraints, often prevents students from attaining the expected course outcomes. This raises the question “How can we improve project management skills in computing majors through the use of technology-enhanced learning environments?” This paper presents a Cloud-based mobile system for supporting project management under a framework of best practices in software engineering capstone courses. The Kanban approach was used as a core of the proposed system. Kanban boards are very popular in the software industry today. It has been empirically shown that they provide increased motivation and project activity control due to their inherent simplicity. This helps the students and academic team be aware of the project context as it aids in preventing ambiguities, flaws, or uncertainties in the development of software artifacts.

Software engineering (SE) educators are challenged to balance the scope and depth in their courses to train students in skills which will fulfill the ever-evolving industry needs. Capstone courses are a tool for educators to transfer hands-on experience into practical knowledge and skills of SE students. This paper describes the design of a Casptone course, at Lappeenranta University of Technology. The designed course is human-centric SE capstone, infusing design thinking methods and agile practices into the project life-cycle knowhow. The capstone was offered in spring of 2017 as a 16-week course for 29 students. Design thinking was effective to perform requirement elicitation, software design and testing. Also, the applied approach allowed students to be self-directed which increased their motivation, as a result there was zero dropout rate. Design thinking is a powerful mean of problem solving and effectively supports SE education in bringing a more hands-on and minds-on, problem-based curriculum.

Currently, many Computer Science Departments have introduced or are considering the introduction of courses in software Engineering. At the same time many departments are considering the use of a language other than Pascal either for an entire Computer Science curriculum, or at least for some advanced courses, such as Data Structures or Software Engineering. At Georgia State University, where our program is primarily based on IBM PC compatible microcomputers, both our Data Structures and Software Engineering courses are based on Ada. In this paper we will discuss the rationale behind our choice of Ada and our experience with using Ada in the Software Engineering course.

This article describes how critical service learning pedagogy is applied to a 4th year Capstone design course in electrical & computer engineering. We create a series of modules based on the Social Implications Lab toolkit developed at UBC. The modules’ goals are: to develop students’ reflective and collaborative decision-making abilities in the context of their Capstone project, and to provide instruction and assessment of the non-technical CEAB graduate attributes for the purpose of accreditation. Student data indicates that students recognize the importance of the individual reflection – team collaboration process. They describe ways that the modules have supported their solution to topics related to the non-technical CEAB graduate attributes. The student feedback identifies a number of ways that the module design could be made more effective including better connection to the Capstone course deliverables, more support in developing reflection and collaboration techniques, and more emphasis on relating projects to systemic social / environmental issues.

As software becomes more ubiquitous and complex, the cost of software bugs continues to grow at a staggering rate. To remedy this situation, there needs to be major improvement in the knowledge and application of software validation techniques. Although there are several software validation techniques, software testing continues to be one of the most widely used in industry. The high demand for software engineers in the next decade has resulted in more software engineering (SE) courses being offered in academic institutions. However, due to the number of topics to be covered in SE courses, little or no attention is given to software testing, resulting in students entering industry with little or no testing experience. We propose a minimally disruptive approach of integrating software testing into SE courses by providing students access to a collaborative learning environment containing learning materials on testing techniques and testing tools. In this article, we describe the learning environment and the studies conducted to measure the benefits accrued by students using the learning environment in the SE courses.

Putting Requirements and Quality at the Core of Global Service Delivery: Current Efforts and Future Plans at Pace University

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.

: This report is meant as a guide to the teacher of the introductory course in software engineering. It contains a case study of a course based on a large project. Additional materials used in teaching the course and samples of student-produced documentation are also available. Other models of course organization are also discussed. A first course in software engineering is a daunting experience for both student AND teacher. The students must work in cooperation with one another on a project that uses almost all their computer science skills and illustrates the techniques taught in the class portion of the course. Since this is often the most interesting single course they take, students tend to throw themselves into it at the expense of other courses. Even when they do not want to live solely for the course, the new experience of having to cooperate with their peers instead of competing with them uses unforeseen amounts of energy in communication and compromise. The instructor is also involved more heavily in this course than in most others he or she will teach.

The evaluation of an advanced software engineering (SE) course is a challenging task that should be addressed as part of the course design. In this paper, we describe an implementation of the reflective practitioner perspective as part of an advanced SE course and introduce its use for feedback purposes. Reflective feedback goes beyond merely using feedback questionnaires. Furthermore, we show, using both qualitative and quantitative empirical data, that the course on which the perspective was applied meets its objectives and fosters students' awareness to the multidimensional nature of SE.

One of the main concerns in the software industry continues to be the development of high quality software. This concern will be exacerbated as software systems become more complex. The training of software developers continues to grow in academia since more institutions are offering software engineering (SE) courses. However, the list of topics that are expected to be covered in this course leaves little or no time for topics that focus on developing quality software, such as software testing and the use of testing tools.In this paper we describe an approach that non-intrusively integrates the use of software testing tools in SE courses. The cornerstone of our approach is the interaction students have with a Web-Based Repository of Software Testing Tools (WReSTT) that contains tutorials on testing concepts and testing tools. WReSTT employs both collaborative learning and social networking features that are attractive to students. We present the results of preliminary study performed in two SE courses that show how using the resources in WReSTT can potentially impact the students' understanding of software testing and the use of testing tools.

The Covid-19 pandemic forced many academic institutions around the world to switch to online teaching. This shift occurred suddenly and with little preparation and this method of instruction was named “emergency remote teaching”. This paper will describe the effects of emergency remote teaching on teaching a software engineering course at a Japanese university, showing how the online environment was used as an alternative to cancelling classes. Strategies for implementing active learning and for engaging students during this software engineering course will be highlighted. Based on the results and observations gathered during the teaching of this course, important conclusions will be drawn. They will constitute a starting point for planning and implementing future software engineering courses and for making sure that active learning continues to remain an essential part of the instruction process.KeywordsEmergency remote teachingActive learningSoftware engineering

본 논문은 공학교육과정에서 사용되는 캡스톤디자인 교과목에 대한 평가체계의 개발 사례를 소개한다. 캡스톤디자인은 대학 과정에서 배운 전문지식을 종합적으로 활용하여, 산업현장의 문제를 분석하고 해결책을 설계하는 교과목이다. 본 논문에서는 캡스톤디자인 교과목과 관련된 기존의 평가 요소, 평가 방법 및 절차를 설명한다. 이를 기반으로 개발된 캡스톤디자인 평가체계를 소개한다. 본 논문에서 제시한 캡스톤디자인 교과목의 학습성과 평가체계는 타대학의 캡스톤디자인 교과목 운영 시 일부 참고될 수 있으며, 산학이 연계된 교육 및 인턴 프로그램 개발 시 평가체계 설계를 위해서도 사용될 수 있다. This paper introduces a case study on the development of the evaluation system for capstone design course which is usually provided at engineering education program. A capstone design is an engineering education course which aims to improve the students' ability on analysis and design of practical industrial problems by use of overall engineering knowledge which has been learned in undergraduate program. Firstly, this paper provides a literature review on evaluation indices and methods related with a capstone design course. Secondly, the evaluation system for learning outcomes of capstone design course is described. The evaluation system for learning outcomes of capstone design course provided in this paper could be referred by other universities opening a capstone design course, and used to design an evaluation system for internship program or education course which is provided as an industry-academic connection program.