<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>van der Meij, Hans and Mark Gellevij</title>	<link>http://tc.eserver.org/authors/van_der_Meij,_Hans_and_Mark_Gellevij</link>
	<description>A bibliography of works by van der Meij, Hans and Mark Gellevij in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>van der Meij, Hans and Mark Gellevij</title>
		<link>http://tc.eserver.org/dir/van_der_Meij,_Hans_and_Mark_Gellevij</link>
	</image>
	<item>
		<title>Effects of Pictures, Age, and Experience on Learning to Use a Computer Program</title>
		<link>http://tc.eserver.org/14250.html</link>
		<guid>http://tc.eserver.org/14250.html</guid>
		<description>Research indicates that older people generally do not process information differently than younger people do. Instead, &apos;the main difference ... seems to be that elderly users are less capable in dealing with any shortcomings in the manuals than younger users. The impact of badly designed manuals is usually greater for elderly people,&apos; (van Hees 1996, p. 531). In line with this view, Hartley (1994) suggests that &apos;text will be easier for older people to use when their perceptual and memory processing loads are reduced&apos; (p. 171). Although the criteria for good design remain a bit unclear, we can accept the general idea that designing well will help the elderly.</description>
	</item>
	<item>
		<title>Screen Captures in Software Documentation</title>
		<link>http://tc.eserver.org/10363.html</link>
		<guid>http://tc.eserver.org/10363.html</guid>
		<description>While screen captures are the most widely used illustrations in manuals, there is almost no literature on their role and design. In this paper we draw together practice, theory and empirical research to advance a taxonomy that identifies these roles and designs. We suggest that screen captures in software documentation can help the user to switch attention, develop a mental model of the program, verify screen states, and identify and locate window elements and objects. Four important design areas (coverage, positioning, size, and cueing) are distinguished and empirical findings discussed. Research has substantiated the claim that screen captures speed up task completion, but others have yet to be proven. We believe that a more refined approach, afforded by the taxonomy, is likely to improve practice and research, and yield strong evidence supporting the use of screen captures in software documentation.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/van_der_Meij,_Hans_and_Mark_Gellevij.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>