Making an Application Provenance-Aware through UML – A General Scheme
An application is said to be provenance-aware when it monitors and captures the information regrading the activities of each and every process in that application. The provenance of a data item includes information about the processes and source data items that lead to its creation and current representation. This type of information or the metadata about the activities of each and every object in the application is very much important for the security purpose. The provenance information ensures the integrity of the data items and the objects involved in the application. Our approach enables an application to track the activities of each and every object involved in the application and captures the state changes of the objects into a permanent store. This information can later be queried by a Data Analyst whenever an attack by an intruder occurs into the application database. Majority of the provenance systems designed are domain specific. The methods available already for capturing the provenance are highly application specific. So there is a need to have a general methodology for capturing the provenance information automatically from the application while the application is under execution. In this paper, we present a general methodology for making an application provenance-aware by using the basic UML design diagrams of the application.
KeywordsData Item Class Diagram Software Product Line Application Execution Provenance Information
Unable to display preview. Download preview PDF.
- 1.Vahdat, A., Anderson, T.: Transparent result caching. In: Proceedings of the Annual Conference on USENIX Annual Technical Conference, ATEC 1998, p. 3. USENIX Association, Berkeley (1998)Google Scholar
- 2.Zhao, J., Goble, C., Greenwood, M., Wroe, C., Stevens, R.: Annotating, linking, and browsing provenance logs for e-science. In: Proc. of the Workshop on Semantic Web Technologies for Searching and Retrieving Scientific Data, pp. 158–176 (2003)Google Scholar
- 3.Lanter, D.P.: Lineage in GIS: The Problem and a Solution. Technical paper. National Center for Geographic Information and Analysis (1990)Google Scholar
- 4.Foster, I., Vockler, J., Wilde, M., Zhao, Y.: Chimera: a virtual data system for representing, querying, and automating data derivation. In: Proceedings of the 14th International Conference on Scientific and Statistical Database Management, pp. 37–46 (2002)Google Scholar
- 6.Chiticariu, L., Tan, W.-C., Vijayvargiya, G.: DBNotes: a post-it system for relational databases based on provenance. In: Proceedings of the 2005 ACM SIGMOD International Conference on Management of Data, SIGMOD 2005, pp. 942–944. ACM, New York (2005)Google Scholar
- 7.Miles, S., Groth, P., Munroe, S., Moreau, L.: Prime: A Methodology for Developing Provenance-aware Applications. ACM Trans. Softw. Eng. Methodol. 20(3), 8:1–8:42 (2011)Google Scholar
- 8.Badharudheen, P., Chacko, A.M., Madhukumar, S.D.: A Scheme for Generating Provenance-aware Applications Through UML. International Journal of Management and Information Technology 6(3) (2013)Google Scholar
- 9.Lanceloti, L.A., Maldonado, J.C., Gimenes, I.M.S., Oliveira Jr., E.A.: Smartyparser: a xmi parser for uml-based software product line variability models. In: Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systems, VaMoS 2013, pp. 10:1–10:5. ACM, New York (2013)Google Scholar