Linked e-resources
Details
Table of Contents
Intro
Preface
Organization
Abstract of Keynotes
Humanizing Software Architecture
Software Architectures in the Age of Cloud Computing
Software Sustainability: What it Means for Software Architects and Why Should We Care
Contents
Components, APIs and Interface Management
Avoiding Excessive Data Exposure Through Microservice APIs
1 Introduction
2 Related Work
3 Excessive Data Exposure in Microservice APIs
4 Communication Model
4.1 Formal Model Description
4.2 Source Code Mining
5 Metrics
6 Case Studies
6.1 Case Study 1: Lakeside Mutual
6.2 Case Study 2: eShopOnContainers
6.3 Summary
7 Discussion
8 Threats to Validity
9 Conclusions and Future Work
References
Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study
1 Introduction
2 Background and Related Work
2.1 DaC-Documentation-as-Code
2.2 ICD Management Approaches
3 Research Method
3.1 Problem Formulation and Research Questions
3.2 Research Method
4 Results
4.1 RQ1: What Are the Issues with ICDs Management that Cause Assumptions and Misunderstandings When Working with These Documents in SoS?
4.2 RQ2: What Are the Features Required for a DaC-Based ICD Management Approach to Address Such Issues?
4.3 RQ3: What Is the Design of an ICD Management Pipeline that Provides the Identified Features?
4.4 RQ4: To What Extent Can the Designed ICD Management Pipeline Improve the Identified ICD Management-Related Issues?
5 Discussion/Lessons Learned
6 Conclusion
References
To Deprecate or to Simply Drop Operations? An Empirical Study on the Evolution of a Large OpenAPI Collection
1 Introduction
2 Dataset Overview
3 Results
3.1 Deprecation Detection
3.2 Operation Stability over Time
3.3 Operation State Model
4 Discussion
5 Related Work
6 Conclusion
References
Architecting for Data-Driven Systems
ProML: A Decentralised Platform for Provenance Management of Machine Learning Software Systems
1 Introduction
2 Preliminary
3 ProML Platform
3.1 User-Driven Provenance Capture
3.2 Artefact-as-a-State-Machine
4 Performance and Cost Evaluation
4.1 Experimental Design
4.2 Results
5 Security Evaluation
5.1 Threat Model
6 Discussions
6.1 Usage Scenarios
6.2 Where ProML Performs unsatisfactorily
6.3 Threat to Validity
7 Related Work
8 Conclusion
References
A Systematic Survey of Architectural Approaches and Trade-Offs in Data De-identification
1 Introduction
2 Background and Motivation
2.1 Architectural Privacy Tactics and Patterns
2.2 Problem Statement and Research Questions
3 Reference Model for De-identification
4 Study Design
Preface
Organization
Abstract of Keynotes
Humanizing Software Architecture
Software Architectures in the Age of Cloud Computing
Software Sustainability: What it Means for Software Architects and Why Should We Care
Contents
Components, APIs and Interface Management
Avoiding Excessive Data Exposure Through Microservice APIs
1 Introduction
2 Related Work
3 Excessive Data Exposure in Microservice APIs
4 Communication Model
4.1 Formal Model Description
4.2 Source Code Mining
5 Metrics
6 Case Studies
6.1 Case Study 1: Lakeside Mutual
6.2 Case Study 2: eShopOnContainers
6.3 Summary
7 Discussion
8 Threats to Validity
9 Conclusions and Future Work
References
Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study
1 Introduction
2 Background and Related Work
2.1 DaC-Documentation-as-Code
2.2 ICD Management Approaches
3 Research Method
3.1 Problem Formulation and Research Questions
3.2 Research Method
4 Results
4.1 RQ1: What Are the Issues with ICDs Management that Cause Assumptions and Misunderstandings When Working with These Documents in SoS?
4.2 RQ2: What Are the Features Required for a DaC-Based ICD Management Approach to Address Such Issues?
4.3 RQ3: What Is the Design of an ICD Management Pipeline that Provides the Identified Features?
4.4 RQ4: To What Extent Can the Designed ICD Management Pipeline Improve the Identified ICD Management-Related Issues?
5 Discussion/Lessons Learned
6 Conclusion
References
To Deprecate or to Simply Drop Operations? An Empirical Study on the Evolution of a Large OpenAPI Collection
1 Introduction
2 Dataset Overview
3 Results
3.1 Deprecation Detection
3.2 Operation Stability over Time
3.3 Operation State Model
4 Discussion
5 Related Work
6 Conclusion
References
Architecting for Data-Driven Systems
ProML: A Decentralised Platform for Provenance Management of Machine Learning Software Systems
1 Introduction
2 Preliminary
3 ProML Platform
3.1 User-Driven Provenance Capture
3.2 Artefact-as-a-State-Machine
4 Performance and Cost Evaluation
4.1 Experimental Design
4.2 Results
5 Security Evaluation
5.1 Threat Model
6 Discussions
6.1 Usage Scenarios
6.2 Where ProML Performs unsatisfactorily
6.3 Threat to Validity
7 Related Work
8 Conclusion
References
A Systematic Survey of Architectural Approaches and Trade-Offs in Data De-identification
1 Introduction
2 Background and Motivation
2.1 Architectural Privacy Tactics and Patterns
2.2 Problem Statement and Research Questions
3 Reference Model for De-identification
4 Study Design