Do we need to handle every temporal violation in scientific workflow systems?

Liu, X; Yang, Y; Yuan, D; Chen, J

Do we need to handle every temporal violation in scientific workflow systems?

Liu, X Yang, Y Yuan, D Chen, J

Permalink

Publication Type:: Journal Article
Citation:: ACM Transactions on Software Engineering and Methodology, 2014, 23 (1)
Issue Date:: 2014-02-01

Closed Access

	Filename	Description	Size
	paper.pdf	Published Version	11.62 MB	Adobe PDF	View/Open

Copyright Clearance Process

Recently Added
In Progress
Closed Access

This item is closed access and not available.

Full metadata record

Field	Value	Language
dc.contributor.author	Liu, X	en_US
dc.contributor.author	Yang, Y	en_US
dc.contributor.author	Yuan, D	en_US
dc.contributor.author	Chen, J	en_US
dc.date.issued	2014-02-01	en_US
dc.identifier.citation	ACM Transactions on Software Engineering and Methodology, 2014, 23 (1)	en_US
dc.identifier.issn	1049-331X	en_US
dc.identifier.uri	http://hdl.handle.net/10453/34942
dc.description.abstract	Scientific processes are usually time constrained with overall deadlines and local milestones. In scientific workflow systems, due to the dynamic nature of the underlying computing infrastructures such as grid and cloud, execution delays often take place and result in a large number of temporal violations. Temporal violation handling is to execute violation handling strategies which can compensate for the occurring time deficit but would impose some additional cost. Generally speaking, the two fundamental requirements for delivering satisfactory temporal QoS in scientific workflow systems are temporal conformance and cost effectiveness. Every task for workflow temporal management incurs some cost. Take a single temporal violation handling as an example, its cost can be primarily referred to monetary costs and time overheads of violation handling strategies which are normally nontrivial in scientific workflow systems.	en_US
dc.relation.ispartof	ACM Transactions on Software Engineering and Methodology	en_US
dc.relation.isbasedon	10.1145/2559938	en_US
dc.subject.classification	Software Engineering	en_US
dc.title	Do we need to handle every temporal violation in scientific workflow systems?	en_US
dc.type	Journal Article
utslib.citation.volume	1	en_US
utslib.citation.volume	23	en_US
utslib.for	0803 Computer Software	en_US
utslib.for	0806 Information Systems	en_US
pubs.embargo.period	Not known	en_US
pubs.organisational-group	/University of Technology Sydney
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology/School of Electrical and Data Engineering
pubs.organisational-group	/University of Technology Sydney/Strength - GBDTC - Global Big Data Technologies
pubs.organisational-group	/University of Technology Sydney/Strength - INEXT - Innovation in IT Services and Applications
utslib.copyright.status	closed_access
pubs.issue	1	en_US
pubs.publication-status	Published	en_US
pubs.volume	23	en_US

Abstract:

Scientific processes are usually time constrained with overall deadlines and local milestones. In scientific workflow systems, due to the dynamic nature of the underlying computing infrastructures such as grid and cloud, execution delays often take place and result in a large number of temporal violations. Temporal violation handling is to execute violation handling strategies which can compensate for the occurring time deficit but would impose some additional cost. Generally speaking, the two fundamental requirements for delivering satisfactory temporal QoS in scientific workflow systems are temporal conformance and cost effectiveness. Every task for workflow temporal management incurs some cost. Take a single temporal violation handling as an example, its cost can be primarily referred to monetary costs and time overheads of violation handling strategies which are normally nontrivial in scientific workflow systems.

Please use this identifier to cite or link to this item:

http://hdl.handle.net/10453/34942