2013
DOI: 10.1007/978-3-642-36981-0_16
|View full text |Cite
|
Sign up to set email alerts
|

User Documentation: The Cinderella of Information Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
2
2
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(6 citation statements)
references
References 9 publications
0
6
0
Order By: Relevance
“…Therefore, it does not provide users with conflicting information and instead focuses on appropriate interaction. Owner's manuals are often designed such that they do not support users by providing procedural information on how to solve a task or problem when using a technology, but rather support users by providing knowledge and skills that they have to transfer to the task later on [30]. It follows that in an owner's manual, HMI elements are presented separately without relating different operating components to graphical elements or auditory elements.…”
Section: Owner's Manual Based User Educationmentioning
confidence: 99%
See 1 more Smart Citation
“…Therefore, it does not provide users with conflicting information and instead focuses on appropriate interaction. Owner's manuals are often designed such that they do not support users by providing procedural information on how to solve a task or problem when using a technology, but rather support users by providing knowledge and skills that they have to transfer to the task later on [30]. It follows that in an owner's manual, HMI elements are presented separately without relating different operating components to graphical elements or auditory elements.…”
Section: Owner's Manual Based User Educationmentioning
confidence: 99%
“…Thus, after an interactive tutorial, all users should have the same degree of system understanding before their first encounter with the driving automation system [5]. Another characteristic of an interactive tutorial is that it is somewhat focused on specific tasks that users can subsequently face as compared with abstract system descriptions in an owner's manuals [30]. Therefore, tutorials provide a meaningful context in which a driving automation system will be used and it is not necessary to transfer knowledge from abstract descriptions to specific use cases [6].…”
Section: Tutorial Based User Educationmentioning
confidence: 99%
“…Documentation for software development needs to be considered an essential factor. In his 11 -page research, [31] argued the importance of user documentation by elaborating on a misconception. His study showed that even the most well-designed software needs documentation.…”
Section: Incomplete Documentationmentioning
confidence: 99%
“…End-user documentation for persuasive technologies. End-user documentation are often dismissed as irrelevant because of two popular clichés; a "well designed software needs no documentation" [15] and users do not read user manuals [16]. To counter these, firstly, it is important to note that bad software designs do exist in the real world and that people will refer to manuals if there is the need to [17].…”
Section: Dual Connectivity Between End-user Documentation and Persuasive Technologiesmentioning
confidence: 99%