(Created page with " == Abstract == International audience; Incident reporting is a very well-known technique in application domains such as air traffic management and health, where specialized...") |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
== Abstract == | == Abstract == | ||
− | International audience; Incident reporting is a very well-known technique in application domains such as air traffic management and health, where specialized users are trained to provide detailed information about problems. Incident reporting systems are indeed complex systems that include many actors including the users reporting incidents, | + | International audience; Incident reporting is a very well-known technique in application domains such as air traffic management and health, where specialized users are trained to provide detailed information about problems. Incident reporting systems are indeed complex systems that include many actors including the users reporting incidents, user’s colleagues and neighbors, stakeholders, policymakers, systems integrations. Incident report systems might change (positively or negatively) the users’ environment in many ways. In recent years, this kind of technique has been also been used in crisis management such as the hurricane Katrina. However, despite the fact that incident reporting systems using mobile technology are becoming more common, little is known about its actual use by the general population and which factors affect the user experience when using such system. In this paper we discuss the use of incident reporting system in critical context of use. In this paper we discuss the use of incident reporting system in several application domains. In particular we report findings in terms of dimensions that are aimed to identify social and technical aspects that can affect the design, development and use of incident reporting systems. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
Line 13: | Line 8: | ||
The different versions of the original document can be found in: | The different versions of the original document can be found in: | ||
− | |||
− | |||
* [https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf] | * [https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf] | ||
+ | |||
+ | * [https://oatao.univ-toulouse.fr/12487 https://oatao.univ-toulouse.fr/12487] | ||
+ | |||
+ | * [http://link.springer.com/content/pdf/10.1007/978-3-642-39232-0_56 http://link.springer.com/content/pdf/10.1007/978-3-642-39232-0_56], | ||
+ | : [http://dx.doi.org/10.1007/978-3-642-39232-0_56 http://dx.doi.org/10.1007/978-3-642-39232-0_56] under the license http://www.springer.com/tdm | ||
+ | |||
+ | * [https://hal.archives-ouvertes.fr/hal-01239732 https://hal.archives-ouvertes.fr/hal-01239732], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-01239732/document https://hal.archives-ouvertes.fr/hal-01239732/document], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf https://hal.archives-ouvertes.fr/hal-01239732/file/winckler_12487.pdf] | ||
+ | |||
+ | * [https://oatao.univ-toulouse.fr/12487 https://oatao.univ-toulouse.fr/12487], | ||
+ | : [https://link.springer.com/chapter/10.1007/978-3-642-39232-0_56 https://link.springer.com/chapter/10.1007/978-3-642-39232-0_56], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-01239732 https://hal.archives-ouvertes.fr/hal-01239732], | ||
+ | : [https://www.scipedia.com/public/Winckler_et_al_2013a https://www.scipedia.com/public/Winckler_et_al_2013a], | ||
+ | : [https://dblp.uni-trier.de/db/conf/hci/hci2013-1.html#WincklerBB13 https://dblp.uni-trier.de/db/conf/hci/hci2013-1.html#WincklerBB13], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-01239732/document https://hal.archives-ouvertes.fr/hal-01239732/document], | ||
+ | : [https://research.tue.nl/en/publications/characterizing-incidents-reporting-systems-across-applications-do https://research.tue.nl/en/publications/characterizing-incidents-reporting-systems-across-applications-do], | ||
+ | : [https://tue-staging.elsevierpure.com/en/publications/characterizing-incidents-reporting-systems-across-applications-do https://tue-staging.elsevierpure.com/en/publications/characterizing-incidents-reporting-systems-across-applications-do], | ||
+ | : [https://academic.microsoft.com/#/detail/2131918679 https://academic.microsoft.com/#/detail/2131918679] |
International audience; Incident reporting is a very well-known technique in application domains such as air traffic management and health, where specialized users are trained to provide detailed information about problems. Incident reporting systems are indeed complex systems that include many actors including the users reporting incidents, user’s colleagues and neighbors, stakeholders, policymakers, systems integrations. Incident report systems might change (positively or negatively) the users’ environment in many ways. In recent years, this kind of technique has been also been used in crisis management such as the hurricane Katrina. However, despite the fact that incident reporting systems using mobile technology are becoming more common, little is known about its actual use by the general population and which factors affect the user experience when using such system. In this paper we discuss the use of incident reporting system in critical context of use. In this paper we discuss the use of incident reporting system in several application domains. In particular we report findings in terms of dimensions that are aimed to identify social and technical aspects that can affect the design, development and use of incident reporting systems.
The different versions of the original document can be found in:
Published on 01/01/2013
Volume 2013, 2013
DOI: 10.1007/978-3-642-39232-0_56
Licence: CC BY-NC-SA license
Are you one of the authors of this document?