TY - JOUR
T1 - Prime
T2 - A methodology for developing provenance-aware applications
AU - Miles, Simon
AU - Groth, Paul
AU - Munroe, Steve
AU - Moreau, Luc
PY - 2011/8
Y1 - 2011/8
N2 - Provenance refers to the past processes that brought about a given (version of an) object, item or entity. By knowing the provenance of data, users can often better understand, trust, reproduce, and validate it. A provenance-aware application has the functionality to answer questions regarding the provenance of the data it produces, by using documentation of past processes. Prime is a software engineering technique for adapting application designs to enable them to interact with a provenance middleware layer, thereby making them provenance-aware. In this article, we specify the steps involved in applying Prime, analyze its effectiveness, and illustrate its use with two case studies, in bioinformatics and medicine.
AB - Provenance refers to the past processes that brought about a given (version of an) object, item or entity. By knowing the provenance of data, users can often better understand, trust, reproduce, and validate it. A provenance-aware application has the functionality to answer questions regarding the provenance of the data it produces, by using documentation of past processes. Prime is a software engineering technique for adapting application designs to enable them to interact with a provenance middleware layer, thereby making them provenance-aware. In this article, we specify the steps involved in applying Prime, analyze its effectiveness, and illustrate its use with two case studies, in bioinformatics and medicine.
KW - Methodology
KW - Provenance
UR - http://www.scopus.com/inward/record.url?scp=80052319925&partnerID=8YFLogxK
U2 - 10.1145/2000791.2000792
DO - 10.1145/2000791.2000792
M3 - Artículo
AN - SCOPUS:80052319925
SN - 1049-331X
VL - 20
JO - ACM Transactions on Software Engineering and Methodology
JF - ACM Transactions on Software Engineering and Methodology
IS - 3
M1 - 8
ER -