Teaching user interface development to software engineering and computer science majors

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.

We live in exceptional times in which the entire world is witnessing the exponential spread of a pandemic, which requires to adopt new habits of mind and behaviors. In this paper, I introduce the term exponential competence, which encompasses these cognitive and social skills, and describe a course for computer science and software engineering students in which emphasis is placed on exponential competence. I argue that exponential competence is especially important for computer science and software engineering students, since many of them will, most likely, be required to deal with exponential phenomena in their future professional development.

Software testing is one of the crucial supporting processes of the software life cycle. Unfortunately for the software industry, the role is stigmatized, partly due to misperception and partly due to treatment of the role. The present study aims to analyse the situation to explore what restricts computer science and software engineering students from taking up a testing career in the software industry. To conduct this study, we surveyed 88 Pakistani students taking computer science or software engineering degrees. The results showed that the present study supports previous work into the unpopularity of testing compared to other software life cycle roles. Furthermore, the findings of our study showed that the role of tester has become a social role, with as many social connotations as technical implications.

Software testing is one of the crucial supporting processes of the software life cycle. Unfortunately for the software industry, the role is stigmatized, partly due to misperception and partly due to treatment of the role. The present study aims to analyze the situation to explore what restricts computer science and software engineering students from taking up a testing career in the software industry. To conduct this study, we surveyed 88 Pakistani students taking computer science or software engineering degrees. The results showed that the present study supports previous work into the unpopularity of testing compared to other software life cycle roles. Furthermore, the findings of our study showed that the role of tester has become a social role, with as many social connotations as technical implications.

The Software Engineering Institute (SEI) is a federally funded research and development center situated as a college‐level unit at Carnegie Mellon University with facilities in Pittsburgh, PA and Arlington, VA. The SEI was created in 1984 by the U.S. Department of Defense to mature and transition new technology to industry so that the government could acquire software‐intensive systems from a broader, more capable contractor base. The SEI works to transform software engineering from an ad‐hoc, labor‐intensive activity to a managed, technology‐supported engineering discipline. The SEI's objectives are to accelerate the introduction and widespread use of high‐payoff software engineering practices and technology by identifying, evaluating, and maturing promising or underused technology and practices; maintain a long‐term competency in software engineering and technology transition; enable government and industry organizations to make measured improvements in their software engineering practices by working with them directly; and foster the adoption and sustained use of standards of excellence for software engineering practice. The institute explores promising solutions to potentially significant problems, selects the best candidate solutions, and works on them to determine their value. In some cases, the SEI works to overcome the limitations that prevent a solution from being of general use in the software community. Finally, the SEI moves mature solutions of proven value into widespread use; examples include the Capability Maturity Model® for Software (SW‐CMM®), and a model curriculum for a master's degree program in software engineering that has been adopted by universties across the country. SEI activities are grouped into two principal areas: software engineering management practices and software engineering technical practices.

Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.

Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.

Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.

Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.

Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.

While many Software Engineering (SE) and Computer Science (CS) textbooks make use of case studies to introduce difference concepts and methods, the case studies introduced by these texts focus on a specific life-development phase or a particular topic within software engineering object-oriented design and implementation or requirements analysis and specification. Moreover, these case studies usually do not come with instructor guidelines on how to adopt the introduced material to the instructor’s teaching style or to the particular level of the class or students in the class. The DigitalHome Case Study aims at addressing these shortcomings by providing a comprehensive set of artifacts associated with the full software development life-cycle. The project provides an extensive set of case study modules with exercises for teaching different topics in software engineering and computer science, as well as guidance for instructors on how to use these case modules. In this chapter, the authors motivate the use of the case study approach in teaching SE and CS concepts. They provide a description of the DigitalHome case study and the associated artifacts and case modules. The authors also report on the use of the developed material.

This paper summarises our experience in teaching Formal Methods to Computer Science and Software Engineers students from various universities around the world, including the University of Madeira in Portugal, the Pontificia Universidad Javeriana and the University of The Andes in Colombia, Carnegie Mellon University (CMU) in the USA, and Innopolis University (INNO) in Russia. We report challenges we have faced during the past 10 to 15 years when teaching formal methods using the Event B formalism, and describe how we have evolved the structure of our courses to respond to those challenges. We strive to help students to build skills on Formal Methods that they can employ later on in their future IT jobs in software Industry. Our goal is to promote the wide use of Formal Methods by software Industry. We consider that this goal cannot be achieved without first universities transferring to Industry students with a strong background in Formal Methods and related formal tools. Formal Methods are key to software development because they are based on Discrete Mathematics which can be used to properly reason about properties that the software one develops should have. We have conducted two surveys among our students, the first one at CMU and the second one at INNO, that we use here to document and justify our decisions in terms of the course structure. The first survey is about the use of Event B as main mathematical formalism, and the second one is about the organisation of teams of students within the classroom to work on software projects that use Event B as main mathematical formalism. Our hope is that our work can be reused by other Faculty to make their own decisions on course structure and content in the teaching of their Formal Methods courses.

Software Engineering (SE) is evolving to make the best out of the constantly changing technological trends, ranging from development to deployment to management and decommissioning of software systems. In this new column Trending Topics in Software Engineering, we aim at providing insights, reports, and outlooks on how researchers and practitioners around the world are working (or planning to work) on those trends. We intend to collect the challenges they are facing or foresee, and explore them in future issues. Our ultimate ambition is to stimulate fruitful discussion in our columns to contribute to identifying the next SE trends, while illustrating them to our audience.

The personal software process (PSP) has been developed by the Software Engineering Institute (SEI) to address the improvement needs of individual software engineers. It should also be of help to small projects and modest-sized software organizations. In a one-semester graduate-level course, engineers are introduced to measurement, planning, and quality control methods. A defined sequence of programming exercises are used to illustrate these methods and the exercise data are used to provide the students with feedback on their performance. The PSP course has been taught at five universities at both the graduate and senior undergraduate level. Various PSP introduction methods have also been tried at four industrial organizations, but the course format has also been found most effective. Results to date indicate that PSP training motivates engineers to use disciplined methods and it helps them to achieve significant quality and productivity improvements. While PSP principles have been demonstrated with software engineering students, their effectiveness has not yet been measured in industrial practice. This paper describes the PSP process, the strategic approach and experience to date.

The paper describes SE master training plans and suggestions for a recent Russian startup, the ambitious Innopolis project. Building the Innovation City is a challenge due to the differences in the objectives and goals of the participating sides: governmental, industry, academic, and research organizations. The new city is being built from scratch next to Kazan', the capital of Tatarstan Republic - this is also a challenge by itself. The idea is to use the synergy of IT academicians, researchers and practitioners in a single location. The Innovation City will incorporate a kindergarten, a STEM training school, a university and an IT park. Of these, the university will act as the brain for the entire project. The primary focus of the university curricula is software engineering. Currently, Innoplois faculty training is underway at Carnegie Mellon University (CMU), the birthplace of the software engineering, and the top ranked university in the field. Research and project practice are tightly coupled within the CMU SE master's program, the CMU course sequence is well justified, while each individual course is thoroughly planned. However, direct curricula copying from CMU to Innopolis would be too obvious solution to be correct. The paper discusses ways of context-specific adjustment of the CMU MSE courses to meet the new Russian university objectives. These curricula tailoring suggestions are based on the takeaways from the author's recent CMU visiting faculty experience, the primary focus of which has been SE training to be applied at Innopolis shortly.