Product-Focused Software Process Improvement

Name: Product-Focused Software Process Improvement | 19th International Conference, PROFES 2018, Wolfsburg, Germany, November 28-30, 2018, Proceedings
Brand: Springer
Price: 53.49 EUR
Availability: OnlineOnly

19th International Conference, PROFES 2018, Wolfsburg, Germany, November 28-30, 2018, Proceedings

Marco Kuhrmann Kurt Schneider Dietmar Pfahl Sousuke Amasaki Marcus Ciolkowski Regina Hebig Paolo Tell Jil Klünder Steffen Küpper(Editor)

Springer (Publisher)

Published on 19. November 2018

XXIV, 458 pages

E-Book

PDF with digital watermarking

System requirements

978-3-030-03673-7 (ISBN)

€53.49incl. 7% vat

System requirements

for PDF with digital watermarking

E-Book Single Licence

Available for download

Description

More details

Other editions

Content

Intro
Preface
Organization
Keynotes
The Hitchhiker's Guide to Engineering AI-Infused Applications
Architecture - Key to Digital Transformation
Contents
Processes and Methods
On the Tasks and Characteristics of Product Owners: A Case Study in the Oil and Gas Industry
1 Introduction
2 Reference Model of Tasks and Characteristics of Product Owners
2.1 Related Work: Characteristics of Product Owners
2.2 Related Work: Tasks of Product Owners
2.3 Reference Model of Tasks and Characteristics
3 Product Owner Analysis at BHGE
3.1 Data Collection
3.2 Data Analysis
4 Results
5 Conclusion and Future Work
References
Agile Manifesto and Practices Selection for Tailoring Software Development: A Systematic Literature Review
1 Introduction
2 Related Work
3 Research Methodology
3.1 Research Questions
3.2 Search Strategy
3.3 Study Selection
3.4 Data Extraction
4 Results
4.1 RQ1: How Have the Agile Manifesto and Its Influence Been Discussed in Tailored Agile Methods Adoption?
4.2 RQ2: Is the Agile Manifesto Related to Agile Practices Selection?
5 Threats to Validity
6 Discussion and Conclusion
References
Agile Meets Assessments: Case Study on How to Do Agile Process Improvement in a Very Small Enterprise
Abstract
1 Introduction
2 Background and Related Work
3 Study Design
3.1 Research Questions
3.2 Study Procedure
3.3 Company Context
4 Study Results
4.1 Pre Assessment
4.2 SPI Using Agile Practices (RQ1)
4.3 Post Assessment
4.4 Comparison of Both Assessments (RQ2)
4.5 Retrospective (RQ3)
4.6 Measurement (RQ3)
5 Threats to Validity
6 Conclusions
Acknowlegements
References
Implementation of a DevOps Pipeline for Serverless Applications
Abstract
1 Introduction
2 Background and Related Work
2.1 DevOps
2.2 Serverless Applications
2.3 DevOps for Serverless Applications
3 Research Process
3.1 Data Collection
3.2 The Case Description
4 Results
4.1 Influence of Serverless Architectures on DevOps Practices
4.2 Design and Implementation of the Pipeline
5 Discussion
5.1 Answers to Research Questions
5.2 Threats to Validity
6 Conclusions
Acknowledgements
References
Iterative Prototyping Methodology for the Development of Innovative and Dependable Complex Embedded Systems Through SPC&KPI Techniques
Abstract
1 Introduction
2 Background
2.1 New Product Development (NPD) Processes
2.2 Dependable and Safety Critical Systems' Development
2.3 Statistical Process Control (SPC) and Key Performance Indicator (KPI)
3 Related Work
4 Development Methodology
4.1 Opportunity Identification Stage
4.2 Opportunity Identification Gate
4.3 Proof-of-Concept Validation Stage
4.4 Proof-of-Concept Validation Gate
4.5 Prototype Development Stage
4.6 Prototype Development Gate
4.7 Real Field Validation Stage
4.8 Real Field Validation Gate
5 Case Study
6 Conclusions and Future Work
References
HAVOSS: A Maturity Model for Handling Vulnerabilities in Third Party OSS Components
1 Introduction
2 Related Work
3 Methodology
3.1 Research Steps
3.2 Participating Companies and Practitioners
3.3 Validity
4 Capability Areas and Practices
4.1 Product Knowledge
4.2 Identification and Monitoring of Sources
4.3 Evaluating Vulnerabilities
4.4 Remedy of Vulnerabilities
4.5 Delivering Updates
4.6 Communication
5 Maturity Levels
6 Results of Evaluations
6.1 First Evaluation Round
6.2 Second Evaluation Round
7 Conclusions
References
Towards a Digital Ecosystem for Rural Areas: Experiences from Three Years of Development
Abstract
1 Introduction
2 Related Work
3 The Project
4 Experiences
4.1 Requirements Engineering
4.2 Architecting
4.3 Design and Implementation
4.4 Testing and Evaluation
4.5 Discussion
5 Conclusion
Acknowledgments
References
Software Processes Analysis with Provenance
Abstract
1 Introduction
2 Background
3 Related Work
4 Provenance in Software Processes
4.1 PROV-SwProcess: A PROV Extension Data Model for Software Processes
4.2 Software Process Analysis Goals
5 Approach
6 Evaluation
6.1 Evaluation with Experts
6.2 Evaluation Using Real-World Data
6.3 Threats to Validity
7 Conclusions
References
The Essence Theory of Software Engineering - Large-Scale Classroom Experiences from 450+ Software Engineering BSc Students
Abstract
1 Introduction
2 The Essence Theory of Software Engineering
3 Research Design and Methodology
3.1 The Course
3.2 The Role of Essence in the Course
3.3 Data Collection and Analysis Methodology
4 Results
4.1 Theme 1: Difficult or Resource-Intensive to Learn
4.2 Theme 2: Inexperience
4.3 Theme 3: Way of Working and the Method Prison
4.4 Theme 4: Progress Control
4.5 Summary of Findings
5 Discussion
5.1 Limitations of the Study
6 Conclusions
References
Empirical Studies in Industry
An Exploratory Study on Software Products and Development Organizations in New Zealand
1 Introduction
2 Research Method
3 Results
3.1 Demographics
3.2 RQ1 - Software Products
3.3 RQ2 - Software Development Organizations
4 Discussion
4.1 Key Findings
4.2 Limitations and Threats to Validity
5 Conclusions
References
Software Professionals' Attitudes Towards Video as a Medium in Requirements Engineering
1 Introduction
2 Documentation for Communication: A Challenge of RE
3 Survey - Video as a Medium in RE
3.1 Survey Results
3.2 Threats to Validity
4 Discussion
5 Conclusion
References
Do Developers Really Worry About Refactoring Re-test? An Empirical Study of Open-Source Systems
Abstract
1 Introduction
2 vD&M's Test Taxonomy
2.1 Category Analysis
2.2 Refactoring Analysis
2.3 Evolutionary Analysis
3 Conclusions and Further Work
References
Moving Beyond the Mean: Analyzing Variance in Software Engineering Experiments
1 Introduction
2 Background
3 Research Method
4 Simulated Experiment
5 Real Experiment
5.1 Experimental Settings
5.2 Data Analysis
6 Discussion
7 Threats to Validity
8 Conclusion
References
An Activity and Metric Model for Online Controlled Experiments
Abstract
1 Introduction
2 Background and Related Work
3 Research Method
4 Findings
5 The Experimentation Process Framework
5.1 The Experimentation Activity Model
5.2 The Experiment Metric Model
6 Conclusions
Acknowledgments
References
Influential Factors of Aligning Spotify Squads in Mission-Critical and Offshore Projects - A Longitudinal Embedded Case Study
1 Introduction
2 Background
2.1 Large-Scale Agile Development
2.2 Inter-team Coordination
2.3 Spotify
3 Research Design and Methodology
3.1 Research Site
3.2 Data Collection
3.3 Data Analysis
4 Threats to the Validity
5 Findings
5.1 Strengthening Collective Code Ownership
5.2 Strengthening Decision-Making
5.3 Strengthening Inter-team Coordination
6 Discussion
7 Conclusion and Future Research
References
Testing
Test-Driving FinTech Product Development: An Experience Report
1 Introduction
2 Background and Related Work
3 Case Description and Analysis Method
3.1 Studied Artifacts
3.2 Tools
4 Results and Discussion
4.1 Size of the Code Base
4.2 Defect Prevalence
4.3 Changes to the Code Base
4.4 Guiding Principle: Test Fast, Test in Layers
5 Implications for Research and Practice
References
Does the Performance of TDD Hold Across Software Companies and Premises? A Group of Industrial Experiments on TDD
1 Introduction
2 Related Work
3 Group of Experiments
3.1 Dependent and Independent Variables
3.2 Experimental Settings
3.3 Subjects
3.4 Analysis Approach
4 Analysis
4.1 Descriptive Statistics
4.2 Individual Analyses
4.3 Joint Result and Sub-group Meta-analysis
4.4 Post-hoc Analysis: Developers' Characteristics
5 Discussion
6 Threats to Validity
7 Conclusion
References
Test Case Prioritization Using Test Similarities
1 Introduction
2 Background and Related Work
2.1 Background
2.2 Related Work
3 Research Method
3.1 Objective and Research Questions
3.2 Subjects Under Study
3.3 Study Design
3.4 Evaluation
4 Findings
4.1 RQ1: Is Prioritization by Similarity-Based TCP More Effective at Finding Defects Than Random Permutation?
4.2 RQ2: Which Similarity-Based TCP Technique Is the Most Effective and Has the Best Performance?
5 Discussion
5.1 Overview of Findings, Their Implications, and Future Works
5.2 Threats to Validity
6 Concluding Remarks
References
Measurement and Monitoring
Feature Crumbs: Adapting Usage Monitoring to Continuous Software Engineering
1 Introduction
2 Requirements
3 Feature Crumb Concept
3.1 Object Model
3.2 Implications for the Development Process
4 Reference Implementation and Initial Evaluation
5 Related Work
6 Conclusion
References
Software Process Measurement and Related Challenges in Agile Software Development: A Multiple Case Study
Abstract
1 Introduction
2 Background and Related Work
3 Research Methodology
3.1 Research Context
3.2 Data Collection
3.3 Data Analysis
4 Results
4.1 RQ1: What Metrics Are Software-Intensive Companies Interested in to Assess Their ASD Processes, and the Rationale Behind Them?
4.2 RQ2: What Are the Challenges Faced by Software-Intensive Companies in Operationalizing the Choice of Metrics to Assess Their ASD Processes?
5 Discussion
5.1 RQ1: What Are the Metrics Software-Intensive Companies Interested in to Assess Their ASD Processes, and the Rationale Behind Them?
5.2 RQ2: What Are the Challenges Faced by the Software-Intensive Companies in Operationalizing the Choice of Metrics to Assess Their ASD Processes?
6 Threats to Validity
7 Conclusion and Future Work
Acknowledgment
References
Emperor's New Clothes: Transparency Through Metrication in Customer-Supplier Relationships
1 Introduction
2 Background: Transparency and Software Metrics
3 Pre-Test Survey of Need for Metrics
4 AENEAS Project: Implementation and Field-Trial
5 Lessons for Early Metrication Programmes
6 Conclusion
References
Global Software Engineering and Scaling
Global Software Development: Practices for Cultural Differences
1 Introduction
2 Background
2.1 Global Software Development - GSD
2.2 Global Teaming Model - GTM
2.3 Cultural Differences in GSD
3 Method
3.1 Document Selection
3.2 Study Quality
3.3 Data Extraction
4 Results
4.1 Understand and Be Aware of Cultural Differences
4.2 Make Onsite Visits
4.3 Standardise Skills Required for Global Team Members
4.4 Identify and Establish the Cultural Context of Each Global Team
4.5 Provide a Cultural Training
4.6 Look Out for Cultural Misunderstanding in Requirements
4.7 Develop and Maintain a Cultural Knowledge Base
4.8 Assign a Local Manager with the Skills Needed for a Global Team
4.9 Offer English Language Training Sessions
4.10 Plan How to Mitigate Issues Caused by Cultural Misunderstanding
4.11 Prepare for Distributed Meetings
4.12 Project Managers Should Take into Account Cultural Differences During Group Exercises
5 Discussion
5.1 Limitations
6 Conclusions
References
Exploring Cross-Site Networking in Large-Scale Distributed Projects
1 Introduction
2 Related Work
2.1 Networking Needs in Large-Scale Distributed Projects
2.2 Experts in Networks
3 Methodology
3.1 Data Collection
3.2 Data Analysis
4 Results
4.1 Project Cases
4.2 Networks
4.3 Key Contacts in Networks
5 Discussion
5.1 Networking in Large-Scale Distributed Projects
5.2 Key Contacts in Network
5.3 Implications and Limitations
6 Conclusions
References
Benefits and Challenges of Adopting the Scaled Agile Framework (SAFe): Preliminary Results from a Multivocal Literature Review
1 Introduction
2 Related Work
2.1 Scaled Agile Framework (SAFe)
2.2 Secondary Studies on Large-Scale Agile
3 Research Method
3.1 Multivocal Literature Review
3.2 Study Selection
3.3 Analysis
4 Results and Discussion
4.1 Benefits of Adopting SAFe
4.2 Challenges of Adopting SAFe
5 Limitations
6 Conclusions and Future Work
References
Industry Talks
Threat Analysis in Practice - Systematically Deriving Security Requirements
1 Introduction
2 Security by Design
3 Security Practice: Threat Analysis
4 Conclusion
References
Process Evolution and Product Maturity: From Prototype to Product
1 Situation and Challenges
2 Approach
3 Appropriate Processes in a Changing Environment
3.1 Communication Structures and Tools
3.2 Focus: Just Let People Work
3.3 Allow to Produce Quality
3.4 Requirements Engineering
4 Conclusion
Workshops and Tutorial
Workshops and Tutorials
1 Workshops
2 Tutorials
Workshop: QuASD 2018
2nd QuASD Workshop: Managing Quality in Agile and Rapid Software Development Processes
Abstract
1 Introduction
2 Keynote: Data Science for Software Quality Management - Examples and Challenges
3 Industry Talk: The Q-Rapids Approach from the Bittium Perspective
4 Accepted Papers
5 Program Committee
6 Activities
Quality Improvement of Mobile Apps - Tool-Supported Lightweight Feedback Analyses
Abstract
1 Introduction
2 Background
2.1 Demand for Lightweight Analyses
2.2 Using Emojis to Analyze Textual User Feedback
3 Feedback-Driven Quality Process and Tool Chain
3.1 Process and Supporting Toolchain
3.2 Examples and Discussion
3.3 Future Work
4 Conclusion
Acknowledgments
References
Thinking Strategically About Knowledge Management in Agile Software Development
1 Introduction
2 Knowledge Management in Strategic Management Domain
3 Knowledge Management Strategies in Agile Software Development
3.1 Potential Research Opportunities
4 Conclusion
References
Modeling in Agile Software Development: Decomposing Use Cases Towards Logical Architecture Design
Abstract
1 Introduction
2 Main Concepts
2.1 RE Discipline in ASD
2.2 Lean Startup
2.3 Design Thinking
2.4 Behaviour-Driven Development (BDD)
2.5 Domain-Driven Design
3 The AMPLA Process
3.1 Requirements Elicitation and Discovery
3.2 Requirements Modeling
3.3 Software Delivery Kick-off Phase and Learning from the Models
4 Modeling Requirements Within the UH4SP Research Project
5 Conclusions and Future Work
References
Mapping Agility to Automotive Software Product Line Concerns
1 Introduction
2 Related Work
2.1 Agile Software Product Lines in Automotive
3 Research Approach
3.1 Research Design
3.2 Threats to Validity
4 Results and Analysis
4.1 Aligned Goals
4.2 Competing Goals
5 Discussion
6 Conclusion
References
Making Runtime Data Useful for Incident Diagnosis: An Experience Report
1 Introduction
2 Project Context
3 Problem: Root-Cause Analysis of Runtime Incidents
4 Providing Runtime Data
4.1 Setting up a Tool Chain for Data Collection
4.2 Providing a Simplified Access to Runtime Data
5 Discussion and Conclusions
References
Workshop: HELENA 2018
3rd Workshop on Hybrid Development Approaches in Software System Development
1 Introduction
2 The HELENA Study
3 The Workshop
4 Conclusion and Future Work
References
Possibilities of Applying Institutional Theory in the Study of Hybrid Software Development Concepts and Practices
Abstract
1 Introduction
2 Applying Institutional Theory in Software Engineering
3 Proposed Conceptual Framework
3.1 The Logic of Traditional Software Engineering
3.2 The Logic of Agile Software Development
3.3 The Adoption of Hybrid Methods as a Reaction to Conflicting Logics
4 Conclusion and a Way Forward
References
Towards Understanding the Motivation of German Organizations to Apply Certain Software Development Methods
1 Introduction
2 Related Work
3 Data Analysis
4 Preliminary Results
5 Discussion
6 Conclusion
References
Author Index

System requirements

Save as PDF Copy link into clipboard

Schweitzer Fachinformationen

Product-Focused Software Process Improvement

Description

More details

Other editions

Additional editions

Content

System requirements