Product-Focused Software Process Improvement: 22nd International Conference, PROFES 2021, Turin, Italy, November 26, 2021, Proceedings (Programming and Software Engineering)

This book constitutes the refereed proceedings of the 22nd International Conference on Product-Focused Software Process Improvement, PROFES 2021, held in Turin, Italy, in November 2021. Due to COVID-19 pandemic the conference was held as a hybrid event. The 20 revised papers, including 14 full papers, 3 short papers and 3 industry papers, presented were carefully reviewed and selected from 48 submissions. The papers cover a broad range of topics related to professional software development and process improvement driven by product and service quality needs. They are organized in the following topical sections: agile and migration, requirements, human factors, and software quality. Preface Organization Contents Agile and Migration Implications on the Migration from Ionic to Android 1 Introduction 2 Related Work 3 Overall Assessment 3.1 User Study 3.2 User Study Results 3.3 Controlled Experiment 3.4 Controlled Experiment Results 4 Overall Discussion 4.1 Implications and Future Extensions 4.2 Threats to Validity 5 Conclusion References The Migration Journey Towards Microservices 1 Introduction 2 Related Work 3 Methodology 3.1 Participants 3.2 Protocol 3.3 Analysis 4 Results 4.1 Architectural-Level Migration Journey 4.2 System-Level Migration Journey 5 Discussion 5.1 Changing Modes and the Reoccurring Phases of Migrations 5.2 Implications for Engineering Teams 5.3 Threats to Validity 6 Conclusion References Migrating from a Centralized Data Warehouse to a Decentralized Data Platform Architecture 1 Introduction 2 Background 2.1 Data Warehousing 2.2 Data Lakes 2.3 Data Platform Architecture 2.4 Service Oriented Architecture 2.5 Microservice Architecture 3 Case Context and Challenges 4 Drivers of Modernization 5 New Data Architecture 6 Experiences 7 Conclusions References How Do Agile Teams Manage Impediments? 1 Introduction 2 Related Work and Background 2.1 Related Work 2.2 Background 3 Study Design 3.1 Research Goal and Questions 3.2 Data Collection and Analysis 3.3 Survey Questionnaire 4 Study Results 4.1 Participant Demographics 4.2 RQ1: Identification 4.3 RQ2: Documentation 4.4 RQ3: Resolution 4.5 Threats to Validity 5 Conclusion and Future Work References Keeping the Momentum: Driving Continuous Improvement After the Large-Scale Agile Transformation 1 Introduction 2 Background 2.1 Scaled Agile Framework (SAFe) 2.2 Related Research 3 Research Method 3.1 Research Goals and Questions 3.2 Case Organisation 3.3 Data Collection 3.4 Data Analysis and Validation 4 Results 4.1 RQ1: How Has the LACE Changed over Time? 4.2 RQ2: How Does the LACE Work? 4.3 RQ3: How Does the LACE Influence the Organisation? 4.4 RQ4: How Can the LACE Improve to Inspire and Facilitate Change? 5 Discussion and Conclusions References Requirements How Do Practitioners Interpret Conditionals in Requirements? 1 Introduction 2 Fundamentals 3 Study Design 3.1 Survey Definition 3.2 Survey Design 3.3 Survey Implementation and Execution 3.4 Survey Analysis 4 Results 5 Threats to Validity 6 Concluding Discussion and Outlook References Situation- and Domain-Specific Composition and Enactment of Business Model Development Methods 1 Introduction 2 Background 2.1 Business Model Development 2.2 Situational Method Engineering 3 Research Approach 4 Solution Requirements 5 Solution Concept 5.1 Knowledge Provision of Methods and Models 5.2 Composition of Development Method 5.3 Enactment of Development Method 6 Solution Implementation 6.1 Architecture 6.2 Tool-Support 7 Evaluation on Local Event Platform 7.1 Evaluation Setting 7.2 Execution of the Study 7.3 Analysis of Results and Implications 8 Conclusion and Future Work References Using a Data-Driven Context Model to Support the Elicitation of Context-Aware Functionalities – A Controlled Experiment 1 Introduction 2 Background 3 Experiment Planning 3.1 Goals 3.2 Design 3.3 Participants 3.4 Participants' Task 3.5 Hypotheses and Variables 3.6 Experimental Materials 3.7 Procedure 4 Execution 4.1 Preparation 4.2 Deviations 5 Analysis 5.1 Descriptive Statistics 5.2 Data Set Preparation 5.3 Hypothesis Testing 6 Discussion 6.1 Evaluation of Results and Implications 6.2 Threats to Validity 7 Conclusion and Future Work References A Transformation Model for Excelling in Product Roadmapping in Dynamic and Uncertain Market Environments 1 Introduction 2 Background and Related Work 2.1 Background 2.2 Related Work 3 Research Approach 4 Product Roadmap Transformation Approach 4.1 Process for the Product Roadmap Transformation 4.2 Procedure for Analyzing Which Dimension Promises the Most Benefit 4.3 Mapping Tables 5 Perception of Practitioners 6 Threats to Validity 6.1 Threats to Validity of the Development of the Transformation Approach 6.2 Threats to Validity of the Interviews with Eleven Practitioners 7 Summary and Future Work Appendix A. DEEP Product Roadmap Self-assessment Tool References Introducing Traceability in GitHub for Medical Software Development 1 Introduction 2 Background and Motivation 3 Design Control in Software Intensive Medical Products 4 Proposed Approach 4.1 Traceability Information Model 4.2 Native GitHub Enablers 4.3 Prototype Implementation 5 Discussion 6 Conclusions References Human Factors A Preliminary Investigation on the Relationships Between Personality Traits and Team Climate in a Smart-Working Development Context 1 Introduction 2 Background 2.1 Big Five Model and Associated Instruments 2.2 Team Climate Research in Software Engineering 2.3 Related Work 3 Study Design and Planning 3.1 Goal 3.2 Participants 3.3 Data Collection 3.4 Data Analysis Procedure 4 Results 4.1 Descriptive Analysis 4.2 Normality Test Results 4.3 Correlation Analysis 4.4 Regression Analysis 5 Threats to Validity 6 Implications 7 Conclusion References Searching for Bellwether Developers for Cross-Personalized Defect Prediction 1 Introduction 2 Related Work 3 Methodology 3.1 Bellwethers Approach 3.2 Datasets 3.3 Prediction 3.4 Performance Evaluation 4 Results 4.1 RQ1: Is There a Bellwether Developer in a Project? 4.2 RQ2: How Are the Bellwethers Effective for Predicting Faults Made by the Other Active Developers in a Project? 4.3 RQ3: Do the Bellwether Developers Also Predict Faulty Commits of the Others Than the Bellwether Candidates? 5 Threats to Validity 6 Conclusion References Using Machine Learning to Recognise Novice and Expert Programmers 1 Introduction 2 Related Work 3 Methodology 3.1 Dataset 3.2 Features 3.3 Machine Learning Models 4 Results 4.1 Exp0: First Experiment 5 Ethical Concerns 6 Conclusion 6.1 Review of the Research Questions 6.2 Further Work References Is Knowledge the Key? An Experiment on Debiasing Architectural Decision-Making - a Pilot Study 1 Introduction 2 Related Work 3 Study Design 3.1 Bias Selection 3.2 Data Acquisition 3.3 Data Analysis 3.4 Participants 4 Results 5 Threats to Validity 6 Discussion 7 Research Outlook 8 Conclusion References Communicating Cybersecurity Vulnerability Information: A Producer-Acquirer Case Study 1 Introduction 2 Methodology 2.1 Involved Companies 2.2 Interview Questions 2.3 Validity 3 Results 3.1 Roles and Responsibilities 3.2 Communication Within and Between Producer and Acquirer 3.3 Decision and Information 3.4 Identified Challenges and Opportunities 4 Discussion and Analysis 5 Conclusion References Software Quality Analyzing SAFe Practices with Respect to Quality Requirements: Findings from a Qualitative Study 1 Introduction 2 Background and Related Works 3 Research Method 3.1 Selecting Agile Scaled Framework 3.2 Uncovering the Assumptions in SAFe About Engineering the QRs 3.3 Understanding How Real-World SAFe Projects Resolve QRs Challenges 4 Scaled Agile Framework (SAFe) 5 Results 5.1 SAFe Elements Assumed Mitigate the QRs Challenges Defined in [9] 5.2 Answers to RQ2 and RQ3 6 Discussion 7 Threats of Validity 8 Conclusion References Capitalizing on Developer-Tester Communication – A Case Study 1 Introduction 2 Background and Related Work 2.1 LDA 2.2 Related Work 3 Research Method 3.1 Research Context 3.2 Data Collection 3.3 LDA Application and Data Analysis 4 Results 4.1 Development-Related Insights from Developer-Tester Communication 5 Discussion 5.1 Development-Related Insights from Developer-Tester Communication 6 Limitations and Threats to Validity 7 Conclusion References Toward a Technical Debt Relationship with the Pivoting of Growth Phase Startups 1 Introduction 2 Background and Related Work 2.1 Growth Phase Startups' Pivoting: A Dilemma 2.2 TD and Pivoting in Growth Phase Startups: A Preliminary Analysis 3 Exploring the Practitioners' Point of View 3.1 Case Selection 3.2 Case Demographics 3.3 Interview Design and Data Collection 3.4 Data Analysis 4 The Relationship Between Technical Debt and Pivoting in Growth Phase Startups 4.1 TD Influence on Pivoting Types 4.2 TD Processes in Pivoting Scenarios 5 Discussions 5.1 TD Influence on Pivoting in Growth-Phase Startups 5.2 Benefit to Researchers and Practitioners 5.3 Threats to Validity 5.4 Hypotheses 6 Conclusions and Future Work References Towards a Common Testing Terminology for Software Engineering and Data Science Experts 1 Motivation 2 Background on Data-Driven Components 3 Related Work on Testing Terminology 4 Mapping of Software and AI Testing Terminology 4.1 Test Abstraction Levels and Objects 4.2 Getting from Test Objective to Test Cases 4.3 Test Execution and Evaluation 5 Conclusion References Towards RegOps: A DevOps Pipeline for Medical Device Software 1 Introduction 2 Background 3 DevOps and Pipelines 3.1 Building Blocks for a DevOps Pipeline 3.2 DevOps Pipeline Reference Model 4 Integration of Regulatory Requirements into the DevOps Pipeline 4.1 Requirements of the Selected Standards Aligned 4.2 Burdensome Requirements Arising from the Standards 5 RegOps Pipeline for Medical Software 5.1 Gate 1: Continuous Integration 5.2 Gate 2: Change Review and Approval 5.3 Gate 3: Deployment Pipeline 5.4 Gate 4: Integration Verification 5.5 Gate 5: Manufacturer Release Approval 6 Discussion and Conclusions References Author Index This book constitutes the refereed proceedings of the 15th International Conference on Product-Focused Software Process Improvement, PROFES 2014, held in Helsinki, Finland, in December 2014. The 18 revised full papers presented together with 14 short papers were carefully reviewed and selected from 45 initial submissions. The papers are organized in topical sections on agile development, decision-making, development practices and issues, product planning, and project management.