Towards Understanding Provenance in Industry
Matthias Galster, Jens Dietrich

TL;DR
This paper explores the needs and perceptions of industry professionals regarding software provenance to enhance trustworthiness, using empirical data to develop a practical influence map for managing provenance concerns.
Contribution
It introduces an empirically-grounded influence map based on industry perceptions to analyze and manage provenance in software systems.
Findings
The influence map helps decision makers address provenance concerns.
Provenance management can be guided by a practitioner-informed checklist.
The approach is bottom-up, based on industry perceptions rather than regulations.
Abstract
Context: Trustworthiness of software has become a first-class concern of users (e.g., to understand software-made decisions). Also, there is increasing demand to demonstrate regulatory compliance of software and end users want to understand how software-intensive systems make decisions that affect them. Objective: We aim to provide a step towards understanding provenance needs of the software industry to support trustworthy software. Provenance is information about entities, activities, and people involved in producing data, software, or output of software, and used to assess software quality, reliability and trustworthiness of digital products and services. Method: Based on data from in-person and questionnaire-based interviews with professionals in leadership roles we develop an ``influence map'' to analyze who drives provenance, when provenance is relevant, what is impacted by…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsScientific Computing and Data Management · Big Data and Business Intelligence
