{"text_format":"2","workbook":"xls","n_sheets":1,"sheets":["report2"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":1,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"report2","index":0,"n_rows":23,"n_cols":5,"rows_kept":23,"cut":false,"hidden":false,"merged":[[0,2,0,3],[0,4,0,5],[1,2,1,3],[1,4,1,5],[2,2,2,3],[4,2,4,3],[5,2,5,3],[6,2,6,3],[7,2,7,3],[8,2,8,3],[10,2,10,3],[11,2,11,3],[14,2,14,3]],"flags":["formulas_cached_only"]}
[null,"1.","Record Nr.",null,"UNISA996500064403316"]
[null,null,"Titolo",null,"Product-focused software process improvement : 23rd international conference, PROFES 2022, Jyväskylä, Finland, November 21-23, 2022, proceedings / / edited by Davide Taibi [and four others]"]
[null,null,"Pubbl/distr/stampa",null,"Cham, Switzerland : , : Springer, , [2022]"]
[{"$nulls":4},"©2022"]
[null,null,"ISBN",null,"3-031-21388-2"]
[null,null,"Descrizione fisica",null,"1 online resource (682 pages)"]
[null,null,"Collana",null,"Lecture Notes in Computer Science ; ; v.13709"]
[null,null,"Disciplina",null,"005.1"]
[null,null,"Soggetti",null,"Computer software - Development"]
[{"$nulls":4},"Software engineering"]
[null,null,"Lingua di pubblicazione",null,"Inglese"]
[null,null,"Formato",null,"Materiale a stampa"]
[null,null,null,"Livello bibliografico","Monografia"]
[null,null,null,"Nota di bibliografia","Includes bibliographical references and index."]
[null,null,"Nota di contenuto",null,"Intro -- Preface -- Organization -- Contents -- Keynote -- The End-Users of Software Systems Deserve Better -- 1 Introduction -- 2 The Paradox -- 3 The Easy Things: What We are Good at -- 4 The Hard Things: What We Should and Can Do Better -- 4.1 Defining the Need and Requirements -- 4.2 Design and Implementation -- 4.3 Validation and Verification -- 4.4 Performance, Reliability and Security -- 4.5 Collaboration and Customer Care -- 5 Possible Reasons Behind the Difficulties -- 5.1 Primary Reason 1: Software Industry is Young -- 5.2 Primary Reason 2: Software is Complex -- 5.3 Primary Reason 3: We Are Optimists -- 5.4 Primary Reason 4: The Wrong People are Doing This -- 5.5 Primary Reason 5: We Do Not Understand the External Factors -- 5.6 Primary Reason 6: Lack of User Input -- 5.7 Primary Reason 7: Customers Cannot Tell Us What They Need -- 6 Servitization as a Solution -- 6.1 Enabling Agility -- 6.2 Enabling Acceleration -- 6.3 Enabling Prioritization -- 6.4 Enabling Testability -- 6.5 Making Availability Concrete -- 6.6 Uncovering Security -- 6.7 Enabling Continuous Delivery -- 6.8 Enabling Customer Care -- 6.9 Enabling Continuous Improvement and Learning -- 6.10 Enabling Trust -- 7 Conclusions -- References -- Cloud and AI -- Managing the Root Causes of ``Internal API Hell'': An Experience Report -- 1 Introduction -- 2 Background and Related Work -- 3 The ALeRCE Project -- 4 ALeRCE's APIs and the ``Internal API Hell'' Phenomenon -- 5 The Typical Issues and How We Address Them -- 5.1 Solution to Issue #1: "]
[{"$nulls":4},"Using a Multi-view Catalog to Help Discover Suitable APIs -- 5.2 Solution to Issue #2: Using a Publish-Subscribe Channel to Assist API Versioning Management and Negotiation -- 5.3 Solution to Issue #3: Using Example-Driven Delivery to Improve the Quality of API Adoption."]
[{"$nulls":4},"5.4 Solution to Issue #4: Using Operation Serialisation to Facilitate API Deployment Debugging and Migration -- 5.5 Solution to Issue #5: Using a Graphical User Interface to Facilitate Path and Parameter Assembly for API Instantiation -- 6 Threats to Validity -- 7 Conclusions and Future Work -- References -- Requirements for Anomaly Detection Techniques for Microservices -- 1 Introduction -- 1.1 Related Work -- 2 Methodology -- 2.1 Methods -- 2.2 Selected Anomaly Detection Techniques -- 3 Experienced Anomalies in a Software Company -- 3.1 Anomalies in Software Company -- 4 Collect Monitoring Data with Benchmark System -- 4.1 Anomalies Extracted from Benchmark System -- 5 Requirements for Anomaly Detection Techniques -- 6 Evaluation of Anomaly Detection Techniques -- 7 Threats to Validity -- 8 Conclusion -- References -- Towards a DSL for AI Engineering Process Modeling -- 1 Introduction -- 2 Background -- 3 DSL Design -- 3.1 Activity Core Elements -- 3.2 Data Activity -- 3.3 AI Modeling Activity -- 3.4 AI Model Deployment Activity -- 4 Tool Support -- 5 Related Work -- 6 Conclusions and Future Work -- References -- Classification of Changes Based on API -- 1 Introduction -- 2 Preliminaries -- 2.1 Catalog of API Changes -- 2.2 APIDiff -- 3 Proposed Technique -- 3.1 Detection API Refactorings -- 3.2 Detecting and Classifying API Changes -- 4 Experiment -- 4.1 Target Projects -- 4.2 The Number of Detected API Changes -- 4.3 The Precision of Classifying API Changes -- 4.4 Execution Time -- 5 Discussion -- 6 Threats to Validity -- 7 Related Works -- 8 Conclusions and Future Work -- References -- Empirical Studies -- Defining Requirements Strategies in Agile: A Design Science Research Study -- 1 Introduction -- 2 Related Work -- 3 Design Science Research Method -- 4 Findings -- 4.1 RQ1: Which Challenges Arise from an Undefined Requirements strategy?."]
[{"$nulls":4},"4.2 RQ2: How Do Companies Aim to Address These Challenges? -- 4.3 RQ3: Which Potential Building Blocks Should Be Considered for Defining a Requirements Strategy? -- 5 Artifact: Guidelines for Defining a Requirements Strategy -- 6 Discussion and Conclusion -- References -- Analysing the Relationship Between Dependency Definition and Updating Practice When Using Third-Party Libraries -- 1 Introduction -- 2 Related Work -- 2.1 Analysis of Dependency Updates -- 2.2 Vulnerable Library Dependencies -- 2.3 Library Version Requirements -- 3 Background -- 3.1 Dataset -- 3.2 Package Managers -- 3.3 Dependency Version Requirement Types -- 3.4 Dependency Updating Lag -- 4 Method -- 4.1 Research Questions -- 4.2 RQ1: Dependency Updating Lag -- 4.3 RQ2: Version Requirement vs Dependency Updating Lag -- 4.4 RQ3: Version Resolution Effect on Version Updating -- 4.5 RQ4: Dependency Updating Lag Effect on Vulnerability -- 5 Results and Discussion -- 5.1 RQ1: Dependency Updating Lag -- 5.2 RQ2: Version Requirement vs Dependency Updating Lag -- 5.3 RQ3: Version Resolution Effect on Version Updating -- 5.4 RQ4: Dependency Updating Lag Effect on Vulnerability -- 6 Threats to Validity -- 7 Conclusion -- References -- On the Limitations of Combining Sentiment Analysis Tools in a Cross-Platform Setting -- 1 Introduction -- 2 Background and Related Work -- 2.1 Sentiment Analysis -- 2.2 Voting Classifier -- 2.3 SE Data Sets for Sentiment Analysis -- 3 Study Design -- 3.1 Research Questions -- 3.2 Selection of Sentiment Analysis Tools -- 3.3 Data Sets -- 3.4 Training -- 3.5 Evaluation Metrics -- 3.6 Interrater Agreement -- 3.7 Combination of the Tools -- 4 Results -- 4.1 Within-Domain Classification -- 4.2 "]
[{"$nulls":4},"Cross-Platform Domains -- 4.3 Comparison of Results from RQ1 and RQ2 -- 5 Discussion -- 5.1 Answering the Research Questions -- 5.2 Interpretation -- 5.3 Threats to Validity."]
[{"$nulls":4},"5.4 Future Work -- 6 Conclusion -- References -- Marine Data Sharing: Challenges, Technology Drivers and Quality Attributes -- 1 Introduction -- 2 Related Work -- 3 Research Methodology -- 4 Results -- 4.1 RQ1: Challenges in Marine Data Sharing -- 4.2 RQ2: Implications of Adopting Data Ecosystems -- 4.3 RQ3: Factors for Marine Data Ecosystem Adoption -- 5 Discussion -- 6 Conclusion and Future Work -- References -- The Viability of Continuous Experimentation in Early-Stage Software Startups -- 1 Introduction -- 2 Background -- 2.1 Scientific and Online Controlled Experiments -- 2.2 Implementing Continuous Experimentation -- 2.3 Software Startups and Experimentation -- 3 Research Method -- 3.1 Case Companies -- 3.2 Data Collection -- 3.3 Data Analysis -- 4 Results -- 4.1 Case Company Descriptions -- 4.2 Cross-Case Analysis -- 5 Discussion -- 5.1 CE and Software Development Methods (RQ1) -- 5.2 Use of Data (RQ2) -- 5.3 The Appeal of Continuous Experimentation (RQ3) -- 5.4 Implications for Practice -- 5.5 Limitations -- 6 Conclusions -- References -- Data-Driven Improvement of Static Application Security Testing Service: An Experience Report in Visma -- 1 Introduction -- 2 Background -- 3 DMAIC: Data-Driven Improvement Process in Security -- 3.1 Defining the DMAIC Plan -- 3.2 Measuring the Existing Service -- 3.3 Analyzing the Data -- 4 Improving the SAST Service in Visma -- 4.1 Improving the SAST Service -- 4.2 Control -- 5 Discussion and Conclusions -- References -- Near Failure Analysis Using Dynamic Behavioural Data -- 1 Introduction -- 2 Near Failure Analysis -- 2.1 Data Preprocessing -- 2.2 Prediction Model -- 3 Early Experimental Result -- 4 Related Work -- 5 Conclusion -- References -- Process Management -- A Process Model of Product Strategy Development: A Case of a B2B SaaS Product -- 1 Introduction -- 2 Background -- 3 Methodology."]
[{"$nulls":4},"4 Process Model of Product Strategy Development -- 4.1 Case Description -- 4.2 Model Requirements -- 4.3 Model Structure -- 4.4 Model Implementation -- 4.5 Model Evaluation -- 5 Discussion -- 5.1 What Process Could be Followed to Develop an Initial Product Strategy for a Newly Productized SaaS Solution? -- 5.2 How do the B2B and SaaS Contexts Affect the Product Strategy Development Process at the Case Company? -- 6 Conclusions -- References -- Communication Skills Requirements of Junior Software Engineers - Analysis of Job Ads -- 1 Introduction -- 2 Related Work -- 2.1 SE Professional Communication Skills -- 2.2 Skill Identification in Job Ads -- 3 Methodology -- 3.1 Goals and Research Questions -- 3.2 Data Collection -- 3.3 Data Analysis -- 4 Research Results -- 4.1 Language Skills -- 4.2 Intercultural Skills -- 4.3 Communication Skills -- 5 Discussion -- 5.1 RQ1: What Language, Intercultural, and Communication Skills are Required from a Junior Software Engineer? -- 5.2 RQ2: How is the Communicative Working Environment Characterized? -- 6 Validity Discussion -- 7 Conclusions and Future Research Work -- References -- Benefit Considerations in Project Decisions -- 1 Introduction -- 2 Background and Previous Work -- 3 Research Questions -- 4 Research Method -- 4.1 Survey Questions -- 4.2 Analysis -- 5 Results -- 6 Discussion -- 7 Limitations -- 8 Conclusion and Further Research -- References -- Towards Situational Process Management for Professional Education Programmes -- 1 Introduction -- 2 Related Work -- 3 The 3Ps of Professional Education Programmes -- 4 Situational Process Management for Professional Education Programmes -- 4.1 Solution Overview -- 4.2 Status of Development -- "]
[{"$nulls":4},"5 Conclusion and Future Work -- References -- Change Management in Cloud-Based Offshore Software Development: A Researchers Perspective -- 1 Introduction."]
[{"$nulls":4},"2 Research Methodology."]