A spiral model of software development and enhancement
ACM SIGSOFT Software Engineering Notes
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Using Little-JIL to Coordinate Agents in Software Engineering
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
A survey of data provenance in e-science
ACM SIGMOD Record
Provenance in collection-oriented scientific workflows
Concurrency and Computation: Practice & Experience - The First Provenance Challenge
Data Lineage Model for Taverna Workflows with Lightweight Annotation Requirements
Provenance and Annotation of Data and Processes
Using Provenance to Improve Workflow Design
Provenance and Annotation of Data and Processes
Exploiting Provenance to Make Sense of Automated Decisions in Scientific Workflows
Provenance and Annotation of Data and Processes
ESCIENCE '08 Proceedings of the 2008 Fourth IEEE International Conference on eScience
A Pattern for Modeling Rework in Software Development Processes
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
New processes for new horizons: the incremental commitment model
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Supporting undo and redo in scientific data analysis
TaPP'13 Proceedings of the 5th USENIX conference on Theory and Practice of Provenance
Supporting undo and redo in scientific data analysis
Proceedings of the 5th USENIX Workshop on the Theory and Practice of Provenance
Hi-index | 0.00 |
Rework occurs commonly in software development. This paper describes a simple rework example, namely the code refactoring process. We show that contextual information is central to supporting such rework, and we present an artifact provenance support approach that can help developers keep track of previous decisions to improve their effectiveness in rework.