<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Usability First &#187; Software Engineering</title>
	<atom:link href="http://www.usabilityfirst.com/glossary/software-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilityfirst.com</link>
	<description></description>
	<lastBuildDate>Thu, 19 Jan 2012 21:34:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>IDE</title>
		<link>http://www.usabilityfirst.com/glossary/ide/</link>
		<comments>http://www.usabilityfirst.com/glossary/ide/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 22:52:58 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3242</guid>
		<description><![CDATA[integrated development environment; a software development tool t&#8230;]]></description>
			<content:encoded><![CDATA[<p>integrated development environment; a software development tool that integrates a wide variety of tools, such as syntax-directed editors, debuggers, and screen layout tools.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/ide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML</title>
		<link>http://www.usabilityfirst.com/glossary/html/</link>
		<comments>http://www.usabilityfirst.com/glossary/html/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 21:36:00 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Acronyms]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Website Design]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3216</guid>
		<description><![CDATA[HypertText Markup Language; a simple notation for describing the fo&#8230;]]></description>
			<content:encoded><![CDATA[<p>HypertText Markup Language; a simple notation for describing the format and content of text by adding simple annotations or &#8220;tags&#8221; to the text. HTML is the fundamental format used for presenting documents on the web.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/html/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>horizontal and vertical prototypes</title>
		<link>http://www.usabilityfirst.com/glossary/horizontal-and-vertical-prototypes/</link>
		<comments>http://www.usabilityfirst.com/glossary/horizontal-and-vertical-prototypes/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 21:16:06 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3189</guid>
		<description><![CDATA[describes what types of capabilities are implemented in a prototype&#8230;]]></description>
			<content:encoded><![CDATA[<p>describes what types of capabilities are implemented in a prototype: horizontal prototypes display a wide range of features but without fully implementing all of those features; vertical prototypes do not attempt to show all that will be in a system but instead focus on implementing a small set of features in a nearly-complete fashion.</p>
<p>Horizontal prototypes are appropriate for understanding relationships across a broad system and for showing the range of abilities of a system.</p>
<p>Vertical prototypes are most appropriate when a certain complex feature of a system is poorly-understood and needs to be explored, e.g. as a proof-of-concept.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/horizontal-and-vertical-prototypes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>high-fidelity prototype</title>
		<link>http://www.usabilityfirst.com/glossary/high-fidelity-prototype/</link>
		<comments>http://www.usabilityfirst.com/glossary/high-fidelity-prototype/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 20:58:04 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3182</guid>
		<description><![CDATA[a prototype that is quite close to the final product, with lots of deta&#8230;]]></description>
			<content:encoded><![CDATA[<p>a prototype that is quite close to the final product, with lots of detail and functionality. From a user testing point of view, a high-fidelity prototype is close enough to a final product to be able to examine usability questions in detail and make strong conclusions about how behavior will relate to use of the final product.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/high-fidelity-prototype/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>hacker ethic</title>
		<link>http://www.usabilityfirst.com/glossary/hacker-ethic/</link>
		<comments>http://www.usabilityfirst.com/glossary/hacker-ethic/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 18:21:37 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Design Principles]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3137</guid>
		<description><![CDATA[the value system espoused by an ill-defined collection of hackers, p&#8230;]]></description>
			<content:encoded><![CDATA[<p>the value system espoused by an ill-defined collection of hackers, programmers and other technologists who love working with computers. The primary value is that all information should be free, and this has been reflected in shareware and open source code movements such as the Linux platform. These principles generally oppose software copy-protection, oppose all forms of censorship, oppose burdensome software licensing agreements, and generally oppose all forms of commercialization that lead to restricted access to information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/hacker-ethic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>group-enabling technologies</title>
		<link>http://www.usabilityfirst.com/glossary/group-enabling-technologies/</link>
		<comments>http://www.usabilityfirst.com/glossary/group-enabling-technologies/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 18:25:22 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Groupware]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3068</guid>
		<description><![CDATA[systems that add group support to single-user applications, by prov&#8230;]]></description>
			<content:encoded><![CDATA[<p>systems that add group support to single-user applications, by providing, for instance, telepointers, overlays for collaborative annotations, shared windows, chat facilities, and methods for finding and connecting to other users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/group-enabling-technologies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>greeking</title>
		<link>http://www.usabilityfirst.com/glossary/greeking/</link>
		<comments>http://www.usabilityfirst.com/glossary/greeking/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 18:04:23 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=3058</guid>
		<description><![CDATA[in prototypes, the representation of text as incomprehensible word&#8230;]]></description>
			<content:encoded><![CDATA[<p>in prototypes, the representation of text as incomprehensible words, greek or latin filler words, X&#8217;s, lines, or scribbles. Also called mumble text. The idea is to give a feel for how the page will look and be organized without needing to have the final text.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/greeking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iterative design</title>
		<link>http://www.usabilityfirst.com/glossary/iterative-design/</link>
		<comments>http://www.usabilityfirst.com/glossary/iterative-design/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:56:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Business and Marketing]]></category>
		<category><![CDATA[Design Principles]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2930</guid>
		<description><![CDATA[the idea that design should be done in repeated cycles where, in each c&#8230;]]></description>
			<content:encoded><![CDATA[<p>the idea that design should be done in repeated cycles where, in each cycle, the design is elaborated, refined, and tested, and the results of testing at each cycle feed into the design focus of the next cycle.</p>
<p>This is identical in spirit to the notion of developing a software product through a series of continually-refined prototypes, and the idea of developing generations of a software product through an iterative development cycle (such as the Spiral model of development).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/iterative-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Java</title>
		<link>http://www.usabilityfirst.com/glossary/java/</link>
		<comments>http://www.usabilityfirst.com/glossary/java/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:54:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Website Design]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2927</guid>
		<description><![CDATA[a cross-platform object-oriented general-purpose programming la&#8230;]]></description>
			<content:encoded><![CDATA[<p>a cross-platform object-oriented general-purpose programming language. Java can be embedded within a web page to provide a very flexible user interface. Java is not to be confused with JavaScript, an essentially unrelated scripting language that can be used within a web page, but provides extremely limited capabilities, especially with regard to input and output.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/java/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>frankensteining</title>
		<link>http://www.usabilityfirst.com/glossary/frankensteining/</link>
		<comments>http://www.usabilityfirst.com/glossary/frankensteining/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:35:56 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2887</guid>
		<description><![CDATA[the merger of multiple designs into one despite the fact that they don&#8230;]]></description>
			<content:encoded><![CDATA[<p>the merger of multiple designs into one despite the fact that they don&#8217;t form a coherent, consistent whole. A typical situation is to present multiple design options to a client who asks for a piecemeal combination of features. While the original designs each conveyed a unified message, the combination is a monstrous hodge-podge.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/frankensteining/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>layout manager</title>
		<link>http://www.usabilityfirst.com/glossary/layout-manager/</link>
		<comments>http://www.usabilityfirst.com/glossary/layout-manager/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:24:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2870</guid>
		<description><![CDATA[a program that automatically determines the layout of graphics and u&#8230;]]></description>
			<content:encoded><![CDATA[<p>a program that automatically determines the layout of graphics and user interface elements based on relationships and restrictions specified by the designer/programmer. A layout manager is particularly useful for handling layouts when a programmer cannot be certain of what graphic elements will be present or what their dimensions will be, and helps when a different font is used or the text is translated, thus changing the size of text elements in a layout.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/layout-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>forward compatibility</title>
		<link>http://www.usabilityfirst.com/glossary/forward-compatibility/</link>
		<comments>http://www.usabilityfirst.com/glossary/forward-compatibility/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:23:25 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2860</guid>
		<description><![CDATA[designing software to work with future versions of itself, e.g. by an&#8230;]]></description>
			<content:encoded><![CDATA[<p>designing software to work with future versions of itself, e.g. by anticipating the needs of future versions and how they will impact data formats and network protocols. For instance, in web development, writing HTML so that it will work in future browsers, which requires anticipating how HTML will evolve.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/forward-compatibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>learn mode</title>
		<link>http://www.usabilityfirst.com/glossary/learn-mode/</link>
		<comments>http://www.usabilityfirst.com/glossary/learn-mode/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:22:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2868</guid>
		<description><![CDATA[a state in which the computer is &#8220;learning&#8221; by observin&#8230;]]></description>
			<content:encoded><![CDATA[<p>a state in which the computer is &#8220;learning&#8221; by observing the user&#8217;s behavior. The term is often used to refer to the period when a macro is being defined by having each action the user performs added to the macro, also called &#8220;record mode&#8221;.</p>
<p>In more powerful programming-by-demonstration systems, the user&#8217;s actions can be generalized to more complicated scripts involving loops and conditionals. The hard part in doing this is determining which user actions must be performed exactly, and which are merely meant to be instances of more general concepts: a parameter to the procedure or a conditional action that depends on the current computer state.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/learn-mode/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>forms-based programming</title>
		<link>http://www.usabilityfirst.com/glossary/forms-based-programming/</link>
		<comments>http://www.usabilityfirst.com/glossary/forms-based-programming/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 22:16:41 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2853</guid>
		<description><![CDATA[programming by filling out a set of forms that query a user about the ty&#8230;]]></description>
			<content:encoded><![CDATA[<p>programming by filling out a set of forms that query a user about the types of inputs and results they want. Forms-based approaches are useful in specialized domains which do not require the full power and generalization of a traditional programming language.</p>
<p>Forms-based programming is one type of end-user programming, allowing users to create reasonably complex programs without having studied programming.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/forms-based-programming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>low-fidelity prototype</title>
		<link>http://www.usabilityfirst.com/glossary/low-fidelity-prototype/</link>
		<comments>http://www.usabilityfirst.com/glossary/low-fidelity-prototype/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 21:37:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2793</guid>
		<description><![CDATA[a prototype that is sketchy and incomplete, that has some characteri&#8230;]]></description>
			<content:encoded><![CDATA[<p>a prototype that is sketchy and incomplete, that has some characteristics of the target product but is otherwise simple, usually in order to quickly produce the prototype and test broad concepts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/low-fidelity-prototype/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>mockup</title>
		<link>http://www.usabilityfirst.com/glossary/mockup/</link>
		<comments>http://www.usabilityfirst.com/glossary/mockup/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 18:59:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2706</guid>
		<description><![CDATA[another term for prototypes, usually referring to low-fidelity pro&#8230;]]></description>
			<content:encoded><![CDATA[<p>another term for prototypes, usually referring to low-fidelity prototypes, such as paper illustrations, screenshots, or simple configurations of screens with limited interaction.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/mockup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>model-view-controller</title>
		<link>http://www.usabilityfirst.com/glossary/model-view-controller/</link>
		<comments>http://www.usabilityfirst.com/glossary/model-view-controller/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 18:54:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Acronyms]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2700</guid>
		<description><![CDATA[(MVC) an architecture for software that separates the underlying ap&#8230;]]></description>
			<content:encoded><![CDATA[<p>(MVC) an architecture for software that separates the underlying application (model) from the user interface display (view) and input (controller).</p>
<p>MVC is generally implemented with callbacks &#8211; the underlying application registers with user interface widgets (in the view and controller) and gets called back by them when something changes in the interface that it must respond to. Complete separation of the model, view, and controller is not in principle entirely possible, since all of them must still contain code to communicate changes to each other. Similar in spirit to a later architecture known as abstraction-link-view (ALV).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/model-view-controller/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>flowchart</title>
		<link>http://www.usabilityfirst.com/glossary/flowchart/</link>
		<comments>http://www.usabilityfirst.com/glossary/flowchart/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 18:21:06 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2665</guid>
		<description><![CDATA[a visual way of representing a task or procedure, traditionally used&#8230;]]></description>
			<content:encoded><![CDATA[<p>a visual way of representing a task or procedure, traditionally used by programmers to visualize the flow within their programs. Steps of a process are represented in boxes and flow is represented by arrows connecting the boxes. Input and output are typically represented in skewed parallelograms, and decision points are usually represented with diamonds. Flowcharts generally do not scale well to extremely large processes, and they mostly fell out of use as a programming tool with the advent of structured programming techniques, which minimized the use of complicated branching structures in software.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/flowchart/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>mythical man-month</title>
		<link>http://www.usabilityfirst.com/glossary/mythical-man-month/</link>
		<comments>http://www.usabilityfirst.com/glossary/mythical-man-month/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 17:59:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Business and Marketing]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2637</guid>
		<description><![CDATA[a man-month is a way of measuring work output for production which is r&#8230;]]></description>
			<content:encoded><![CDATA[<p>a man-month is a way of measuring work output for production which is reasonably helpful in certain limited areas of industries like manufacturing. The basic idea is that if you want to produce twice as many sprockets, then you can hire twice as many people to get it done. Worker productivity is measured by how much one person can do in one month. Thus, what takes 1 person 100 months to perform should take 100 people 1 month to perform.</p>
<p>This perspective is called &#8220;mythical&#8221; because it doesn&#8217;t apply in many organizational settings, and in particular in software development environments. Doubling the people on a software development project may not merely fail to double the speed of development, it may actually slow a project down.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/mythical-man-month/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>object-oriented programming</title>
		<link>http://www.usabilityfirst.com/glossary/object-oriented-programming/</link>
		<comments>http://www.usabilityfirst.com/glossary/object-oriented-programming/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 17:06:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2588</guid>
		<description><![CDATA[(OOP) a programming technique and a characteristic of programming l&#8230;]]></description>
			<content:encoded><![CDATA[<p>(OOP) a programming technique and a characteristic of programming languages often associated with graphical user interfaces. Object-oriented programming treats data items as &#8220;objects&#8221; belonging to a category of related objects with similar functionality called a &#8220;class&#8221;. Classes are organized in a hierarchy such that classes inherit properties and functionality from their parents in the hierarchy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/object-oriented-programming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>extreme programming</title>
		<link>http://www.usabilityfirst.com/glossary/extreme-programming/</link>
		<comments>http://www.usabilityfirst.com/glossary/extreme-programming/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 00:21:00 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Business and Marketing]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2521</guid>
		<description><![CDATA[an approach to managing programming projects to maximize the qualit&#8230;]]></description>
			<content:encoded><![CDATA[<p>an approach to managing programming projects to maximize the quality output of programming teams and optimize shared knowledge and training. The technique relies on pairs of programmers sharing a single computer and collaboratively solving problems. Programming tasks are kept to under 2 weeks to effectively track progress and maximize the likelihood of success.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/extreme-programming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>paper-and-pencil prototype</title>
		<link>http://www.usabilityfirst.com/glossary/paper-and-pencil-prototype/</link>
		<comments>http://www.usabilityfirst.com/glossary/paper-and-pencil-prototype/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 00:14:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Usability Methods]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2506</guid>
		<description><![CDATA[a paper sketch of a user interface with enough detail to make design de&#8230;]]></description>
			<content:encoded><![CDATA[<p>a paper sketch of a user interface with enough detail to make design decisions and usability evaluations, whether through a usability inspection, a focus group, or a simple user test.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/paper-and-pencil-prototype/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>event handler</title>
		<link>http://www.usabilityfirst.com/glossary/event-handler/</link>
		<comments>http://www.usabilityfirst.com/glossary/event-handler/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 23:52:34 +0000</pubDate>
		<dc:creator>jls</dc:creator>
				<category><![CDATA[Design Principles]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[I/O Devices]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2457</guid>
		<description><![CDATA[a central software routine for applications in graphical user inter&#8230;]]></description>
			<content:encoded><![CDATA[<p>a central software routine for applications in graphical user interfaces that processes events as they arrive, primarily user input such as keystrokes and mouse clicks, but also system events such as time-based triggers. The events arrive in an event buffer. The events are processed in a cycle called the &#8220;event loop&#8221; where the oldest event in the buffer is interpreted and quickly processed, then the event handler is revisited for the next event.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/event-handler/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>pluggable look and feel architecture</title>
		<link>http://www.usabilityfirst.com/glossary/pluggable-look-and-feel-architecture/</link>
		<comments>http://www.usabilityfirst.com/glossary/pluggable-look-and-feel-architecture/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 23:29:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Widgets]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2420</guid>
		<description><![CDATA[an application or system architecture that allows applications to r&#8230;]]></description>
			<content:encoded><![CDATA[<p>an application or system architecture that allows applications to run with a different look and feel than that originally envisioned by the application&#8217;s designers. Any other interface specification can be substituted for the same application. While allowing general-purpose substitution of the entire interface is basically an impossibly-difficult problem, some level is possible, whether it&#8217;s just switching color and font themes, or allowing alternate interfaces for people with disabilities, such as screen readers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/pluggable-look-and-feel-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>programming by demonstration</title>
		<link>http://www.usabilityfirst.com/glossary/programming-by-demonstration/</link>
		<comments>http://www.usabilityfirst.com/glossary/programming-by-demonstration/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 23:02:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://www.usabilityfirst.com.foraker.com/?p=2382</guid>
		<description><![CDATA[systems that allow a person to construct a program simply by demonstr&#8230;]]></description>
			<content:encoded><![CDATA[<p>systems that allow a person to construct a program simply by demonstrating the actions that the program needs to perform. The system then must infer what loops and conditionals might be involved, and may allow the user to select among several candidate programs that attempt to generalize the users demonstrated task into a program. This works well for very simple tasks and may even work quite well in specialized domains where meaningful inferences can easily be made, but programming by demonstration certainly will not be replacing traditional programming for large-scale programs.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityfirst.com/glossary/programming-by-demonstration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

