The requirements of using provenance in e-Science experiments
From Tetherless World Wiki
\begin{bibtex}
@article{ miles2006requirements, title = {The Requirements of Using Provenance in e-Science Experiments}, author = {Simon Miles and Paul Groth and Miguel Branco and Luc Moreau}, publisher = {Springer}, year = {2006}, journal = {Journal of Grid Computing}, volume= {5}, number ={1}, pages={1--25}, keywords = {provenance e-Science requirements use cases}, url = {http://eprints.ecs.soton.ac.uk/12566/}, abstract = {In e-Science experiments, it is vital to record the experimental process for later use such as in interpreting results, verifying that the correct process took place or tracing where data came from. The process that led to some data is called the provenance of that data, and a provenance architecture is the software architecture for a system that will provide the necessary functionality to record, store and use process documentation to determine the provenance of data items. However, there has been little principled analysis of what is actually required of a provenance architecture, so it is impossible to determine the functionality they would ideally support. In this paper, we present use cases for a provenance architecture from current experiments in biology, chemistry, physics and computer science, and analyse the use cases to determine the technical requirements of a generic, technology and applicationindependent architecture. We propose an architecture that meets these requirements, analyse its features compared with other approaches and evaluate a preliminary implementation by attempting to realise two of the use cases.}, topic ={provenance, use case}, rank = {4/5}, }
\end{bibtex}
Enumerate many use cases and requirements. The requirements can be combined into more precise features.
- annotation (data, action, etc.): data equality, version
- dataflow log (data dependency)
- workflow log (step dependency): reuse workflow
- checking : consistency, correctness
