Walking Through the Method Zoo: Does Higher Education Really Meet Software Industry Demands?

Software engineering educators are continually challenged by rapidly evolving concepts, technologies, and industry demands. Due to the omnipresence of software in a digitalized society, higher education institutions (HEIs) have to educate the students such that they learn how to learn, and that they are equipped with a profound basic knowledge and with latest knowledge about modern software and system development. Since industry demands change constantly, HEIs are challenged in meeting such current and future demands in a timely manner. This paper analyzes the current state of practice in software engineering education. Specifically, we want to compare contemporary education with industrial practice to understand if frameworks, methods and practices for software and system development taught at HEIs reflect industrial practice. For this, we conducted an online survey and collected information about 67 software engineering courses. Our findings show that development approaches taught at HEIs quite closely reflect industrial practice. We also found that the choice of what process to teach is sometimes driven by the wish to make a course successful. Especially when this happens for project courses, it could be beneficial to put more emphasis on building learning sequences with other courses

Catching up with Method and Process Practice: An Industry-Informed Baseline for Researchers

Software development methods are usually not applied by the book.companies are under pressure to continuously deploy software products that meet market needs and stakeholders\u27 requests. To implement efficient and effective development processes, companies utilize multiple frameworks, methods and practices, and combine these into hybrid methods. A common combination contains a rich management framework to organize and steer projects complemented with a number of smaller practices providing the development teams with tools to complete their tasks. In this paper, based on 732 data points collected through an international survey, we study the software development process use in practice. Our results show that 76.8% of the companies implement hybrid methods.company size as well as the strategy in devising and evolving hybrid methods affect the suitability of the chosen process to reach company or project goals. Our findings show that companies that combine planned improvement programs with process evolution can increase their process\u27 suitability by up to 5%

Evaluating the Impact of Critical Factors in Agile Continuous Delivery Process: A System Dynamics Approach

Continuous Delivery is aimed at the frequent delivery of good quality software in a speedy, reliable and efficient fashion – with strong emphasis on automation and team collaboration. However, even with this new paradigm, repeatability of project outcome is still not guaranteed: project performance varies due to the various interacting and inter-related factors in the Continuous Delivery 'system'. This paper presents results from the investigation of various factors, in particular agile practices, on the quality of the developed software in the Continuous Delivery process. Results show that customer involvement and the cognitive ability of the QA have the most significant individual effects on the quality of software in continuous delivery

Agile software development in a context of plan-based organizations

Agile software development has increasingly been used in the last fifteen years with the goal of improving traditionally time-consuming and rather non-user friendly process of developing software code. As implications of agile development and its impact on employees are still unclear, it is important to understand the benefits, opportunities and limitations of this development or collaboration mechanism. Thus, empirical evidence with implications for decision makers in the field of corporate policy and software development is an open research field. This master thesis analyzes the potentials of agile software development and how this approach can be used to support the development processes in companies, in terms of efficiency, shorter time-to-market as well as better customer fit of the developed products or services. By exploring some of the key features of different methods and processes, the potentials and limitations of the selected approaches are analyzed and linked to recent literature insights

DPVis: Visual Analytics with Hidden Markov Models for Disease Progression Pathways

Clinical researchers use disease progression models to understand patient status and characterize progression patterns from longitudinal health records. One approach for disease progression modeling is to describe patient status using a small number of states that represent distinctive distributions over a set of observed measures. Hidden Markov models (HMMs) and its variants are a class of models that both discover these states and make inferences of health states for patients. Despite the advantages of using the algorithms for discovering interesting patterns, it still remains challenging for medical experts to interpret model outputs, understand complex modeling parameters, and clinically make sense of the patterns. To tackle these problems, we conducted a design study with clinical scientists, statisticians, and visualization experts, with the goal to investigate disease progression pathways of chronic diseases, namely type 1 diabetes (T1D), Huntington's disease, Parkinson's disease, and chronic obstructive pulmonary disease (COPD). As a result, we introduce DPVis which seamlessly integrates model parameters and outcomes of HMMs into interpretable and interactive visualizations. In this study, we demonstrate that DPVis is successful in evaluating disease progression models, visually summarizing disease states, interactively exploring disease progression patterns, and building, analyzing, and comparing clinically relevant patient subgroups.Comment: to appear at IEEE Transactions on Visualization and Computer Graphic

A Comparison between Agile and Traditional Software Development Methodologies

Agile and Traditional software development methodologies, both are being used in different projects of software development industry. Agile software development technology is an incremental software development process. On the other hand, Traditional software development methodologies or plan-driven software can be explained as a more formal approach to software development. These methodologies come with a fully completed set of systems requirements followed by an architectural and high leveldesign development and inspiration. This research focuses on the software development life cycle, role and responsibilities of agile and traditional software development methodologies and their technical practices. It performs a comparison between both the software development methodologies. Here a questionnaire is used to collect data from the various experts of different IT related organizations of Bangladesh. In the questionnaire, there are three sections to bring out the individual knowledge from different organization, methodology knowledge of the respondents and software development experience of the respondents. The respondents are mainly software engineer, system analyst, software developer etc. A comparison is also performed between this survey result and a survey done by Ambler