Papers by Brigit van Loggem
Proceedings of the 20th European Conference on Pattern Languages of Programs - EuroPLoP '15, 2015
Proceedings of the 30th European Conference on Cognitive Ergonomics - ECCE '12, 2012
ABSTRACT Semi-naturalistic research designs allow for studying behaviour in a realistic setting, ... more ABSTRACT Semi-naturalistic research designs allow for studying behaviour in a realistic setting, achieving a fair degree of ecological validity without the disadvantages of purely naturalistic designs. A semi-naturalistic study sets boundaries for the behaviour under investigation, within which respondents still act freely. In order to allow for between-subjects comparisons, the raw data obtained must be structured, either through pre-structuring or through post-structuring. Motivation -- There exists little methodological guidance in the field of documentation design. Qualitative and quantitative studies alike are carried out using an amalgam of methods that were developed for other disciplines. This paper contributes to awareness of the pitfalls (but also the benefits) of doing so. Research approach -- This paper considers two semi-naturalistic studies into interaction with software and documentation from a methodological point of view. In the first, the data was collected in the respondents' workplace and then post-structured. In the second, the data was collected in a laboratory setting and pre-structured through the use of an observation tool. Findings/Design -- Both methods are described in some detail, followed by a discussion of methodological issues discovered after the design had been executed. Finally, the relative advantages and disadvantages of the two approaches are highlighted. Take-away message -- Documentation design can fruitfully combine methodological approaches originally developed for other disciplines, provided these are adapted for the purpose with care and discretion.
Proceedings of the 31st European Conference on Cognitive Ergonomics - ECCE '13, 2013
ABSTRACT An abstract model is developed of "computer-mediated activity" or CMA.... more ABSTRACT An abstract model is developed of "computer-mediated activity" or CMA. The CMA model is based on the existing literature and describes how people interact with software to fulfil an intention and how, over time, they may achieve full mastery of the software. Academic studies related to the design of user documentation for software are sparse, and no underlying reference framework is available within which design rationale could be expressed. The CMA model is intended as a first step towards the development of such a framework. Its implications for documentation design are discussed and its application is illustrated by describing a number of well-known documentation formats in terms of the model.
Proceedings of the International Conference on Information Systems and Design of Communication - ISDOC '14, 2014
ABSTRACT
Proceedings of the 29th Annual European Conference on Cognitive Ergonomics - ECCE '11, 2011
Abstract A convincing argument can be made for placing documentation at the heart of the developm... more Abstract A convincing argument can be made for placing documentation at the heart of the development cycle. Communication between stakeholders is facilitated when the system under consideration is represented in a semi-formal manner, creating common ground for discussion and decision-making. By enhancing and elaborating one and the same document, ownership of which is repeatedly passed from one stakeholder group to another, it is ensured that this common ground is maintained throughout the design and ...
Proceedings of the 29th Annual European Conference on Cognitive Ergonomics - ECCE '11, 2011
ABSTRACT Motivation -- To support documentation designers in their on-going search for documentat... more ABSTRACT Motivation -- To support documentation designers in their on-going search for documentation that genuinely supports end users. Research approach -- Existing findings from a multi-disciplinary literature are combined to arrive at a model of the cognitive involvement of users with software, and separately a model of the way people interact with documentation. A number of design patterns are proposed that target particular elements in the two models. The patterns will be field-tested for applicability by designers as well as end users. Findings/Design -- The hope is that the design patterns will prove of value to both stakeholder groups (documentation designers and end users). Research limitations/Implications -- The naturalistic nature of the theoretical framework as well as the subsequent field-testing hinders generalization of the results. Originality/Value -- The research makes a contribution to the need of documentation designers to base their work on current insights resulting from theoretical and applied research. Take away message -- Documentation is a relatively under-valued professional discipline, which needs academic input as much as any other design discipline that works to support the end user.
In this paper, we argue how a documentation-centred approach to systems design and development co... more In this paper, we argue how a documentation-centred approach to systems design and development could provide the different roles involved in this activity with a common ground. A large heterogeneous development team can be seen as a Community of Interest, consisting of individuals brought together from different Communities of Practice. Each group brings to the CoI not only their own skills and experience but also their own values, mental models, working practices, and communication styles. Re-shaping documentation into a boundary object offers a solution to the dual problems of (1) heterogeneous mental models within a software development team and (2) the user support role being peripheral to the team. Documentation that evolves dynamically, changing shape as the development process proceeds, can support communication both internally (between members of a software development team) and externally (between developers and end users).
This paper describes a desk study in which a user manual dating from 1925, describing how to oper... more This paper describes a desk study in which a user manual dating from 1925, describing how to operate a table loom, was verified for conformance to an ISO standard that lists requirements for software user documentation and was last revised in 2008. A remarkably high degree of conformance was established. It is discussed whether this is coincidental, or more fundamentally related to the way in which the documentation of software tools is regarded as quantitatively rather than qualitatively different from the documentation of physical tools. The paper concludes by making a case for academic research resulting in guidelines for software documentation that take into account the specific nature of software, and the specific problems that users encounter when working with software.
An exploratory study was conducted into the interaction with documentation displayed by users of ... more An exploratory study was conducted into the interaction with documentation displayed by users of an unknown software tool. Five adult men were observed during their work with a software simulation of a fictitious machine for the production of liquorice. Their only source of information on the machine’s functioning was its printed user manual. The log data from the observations was analyzed with a view to pinpointing interesting patterns of behaviour that deserve further, more formal, research.
Introduction. This paper describes an empirical study in which two separate groups of respondents... more Introduction. This paper describes an empirical study in which two separate groups of respondents were questioned as to their preferred sources of information when working with software.
Method. Respondents were asked to imagine working with software and to indicate how much interest they would have in accessing six distinct sources of information about its functioning. This question was asked four times, corresponding to four different situations in which information could imaginably be required.
Analysis. A relational database was created to store the data, which could then be queried in many different ways.
Results. The results imply that in general, users of software have a preference for information sources that take little effort to access. This does not, however, mean that software users 'do not read the instructions', as has been suggested in the academic and professional literatures.
Conclusions. Software users are quite willing to use documentation as and when required. It is then up to the designers of user documentation to make this worth their while.
User documentation is a structurally under-valued aspect of information systems and end user assi... more User documentation is a structurally under-valued aspect of information systems and end user assistance. Popular belief has it that documentation is required only where insufficient attention has been paid to the design of usability, user satisfaction and user experience; and that documentation is not referred to by users anyhow. Both lines of reasoning are shown to be faulty, and a case is made for an interest in user documentation from the pertinent research communities.
An abstract model is developed of “computer-mediated activity” or CMA. The CMA model is based on ... more An abstract model is developed of “computer-mediated activity” or CMA. The CMA model is based on the existing literature and describes how people interact with software to fulfil an intention and how, over time, they may achieve full mastery of the software. Academic studies related to the design of user documentation for software are sparse, and no underlying reference framework is available within which design rationale could be expressed. The CMA model is intended as a first step towards the development of such a framework. Its implications for documentation design are discussed and its application is illustrated by describing a number of well-known documentation formats in terms of the model.
Semi-naturalistic research designs allow for studying behaviour in a realistic setting, achieving... more Semi-naturalistic research designs allow for studying behaviour in a realistic setting, achieving a fair degree of ecological validity without the disadvantages of purely naturalistic designs. A semi-naturalistic study sets boundaries for the behaviour under investigation, within which respondents still act freely. In order
to allow for between-subjects comparisons, the raw data obtained must be structured, either through pre-structuring or through post-structuring.
One way to support end users of software is to provide documentation materials such as user manua... more One way to support end users of software is to provide documentation materials such as user manuals and online Help. As not all software is equally difficult to master, documentation designers need to determine the quality and quantity of the information to be included in the user documentation. A first step towards this end would be to assess the complexity of the software from the user's point of view.
Semi-naturalistic research designs allow for studying behaviour in a realistic setting, achieving... more Semi-naturalistic research designs allow for studying behaviour in a realistic setting, achieving a fair degree of ecological validity without the disadvantages of purely naturalistic designs. A semi-naturalistic study sets boundaries for the behaviour under investigation, within which respondents still act freely. In order to allow for between-subjects comparisons, the raw data obtained must be structured, either through pre-structuring or through post-structuring.
Uploads
Papers by Brigit van Loggem
Method. Respondents were asked to imagine working with software and to indicate how much interest they would have in accessing six distinct sources of information about its functioning. This question was asked four times, corresponding to four different situations in which information could imaginably be required.
Analysis. A relational database was created to store the data, which could then be queried in many different ways.
Results. The results imply that in general, users of software have a preference for information sources that take little effort to access. This does not, however, mean that software users 'do not read the instructions', as has been suggested in the academic and professional literatures.
Conclusions. Software users are quite willing to use documentation as and when required. It is then up to the designers of user documentation to make this worth their while.
to allow for between-subjects comparisons, the raw data obtained must be structured, either through pre-structuring or through post-structuring.
Method. Respondents were asked to imagine working with software and to indicate how much interest they would have in accessing six distinct sources of information about its functioning. This question was asked four times, corresponding to four different situations in which information could imaginably be required.
Analysis. A relational database was created to store the data, which could then be queried in many different ways.
Results. The results imply that in general, users of software have a preference for information sources that take little effort to access. This does not, however, mean that software users 'do not read the instructions', as has been suggested in the academic and professional literatures.
Conclusions. Software users are quite willing to use documentation as and when required. It is then up to the designers of user documentation to make this worth their while.
to allow for between-subjects comparisons, the raw data obtained must be structured, either through pre-structuring or through post-structuring.