10th IEEE Pacific Rim International Symposium on Dependable Computing, 2004. Proceedings.
DOI: 10.1109/prdc.2004.1276591
|View full text |Cite
|
Sign up to set email alerts
|

Representing user workarounds as a component of system dependability

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 12 publications
0
2
0
Order By: Relevance
“…Kobayashi et al, 2005), and controversial (Obradovich and "Drops hollowing the Stone". Workarounds as Resources for Better Task-Artifact Fit Woods, 1996;Martin and Koopman, 2004;Petrides, 2004;Patterson et al, 2006;Vogelsmeier et al, 2007). Ferneley and Sobreperez (2006) propose to go beyond the mere positive-negative dichotomy mentioned above: they follow the notion submitted by Kobayashi et al (2005); Petrides (2004), which relates workarounds to either an "action ensuing from resistance" for both "good" or "bad" organizational reasons , or to an engagement with the system that yet fails to conform to the prescribed "rules of engagement"; yet, they also distinguish between: "hindrance workarounds", which are undertaken to circumvent system procedures or processes that are perceived to be too time consuming ("viscous" in the sense hinted above), onerous or difficult (Prasad and Prasad, 2000); harmless workarounds, which do not significantly affect the flow of work or the quality of the involved information (Button et al, 2003;Lapointe and Rivard, 2005); and lastly, essential workarounds, that is actions that are necessary to complete a task or reach a goal (Kobayashi et al, 2005).…”
Section: Beyond Good and Evilmentioning
confidence: 99%
“…Kobayashi et al, 2005), and controversial (Obradovich and "Drops hollowing the Stone". Workarounds as Resources for Better Task-Artifact Fit Woods, 1996;Martin and Koopman, 2004;Petrides, 2004;Patterson et al, 2006;Vogelsmeier et al, 2007). Ferneley and Sobreperez (2006) propose to go beyond the mere positive-negative dichotomy mentioned above: they follow the notion submitted by Kobayashi et al (2005); Petrides (2004), which relates workarounds to either an "action ensuing from resistance" for both "good" or "bad" organizational reasons , or to an engagement with the system that yet fails to conform to the prescribed "rules of engagement"; yet, they also distinguish between: "hindrance workarounds", which are undertaken to circumvent system procedures or processes that are perceived to be too time consuming ("viscous" in the sense hinted above), onerous or difficult (Prasad and Prasad, 2000); harmless workarounds, which do not significantly affect the flow of work or the quality of the involved information (Button et al, 2003;Lapointe and Rivard, 2005); and lastly, essential workarounds, that is actions that are necessary to complete a task or reach a goal (Kobayashi et al, 2005).…”
Section: Beyond Good and Evilmentioning
confidence: 99%
“…Software dataflow and control flow automatic analysis [12,13,14,15] has become important measures to find dependability attributes。Markov Model [12,16] …”
Section: Dependability Validation and Evaluationmentioning
confidence: 99%