Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Transparency (human–computer interaction)
open-in-new
<p>Any change in a <a href="/facts/Computing/Kghtm9fX">computing</a> system, such as a new feature or new component, is transparent if the system after change adheres to previous <a href="/facts/Interface_(computing)/zdfp8unT">external interface</a> as much as possible while changing its internal behaviour. The purpose is to shield from change all systems (or human users) on the other end of the interface. Confusingly, the term refers to overall <i>invisibility</i> of the component, it does not refer to <i>visibility of component's internals</i> (as in <a href="/facts/White_box_(software_engineering)/tFkNbWpA">white box</a> or <a href="/facts/Open_system_(computing)/tVwr9W6r">open system</a>). The term <i>transparent</i> is widely used in computing marketing in substitution of the term <i>invisible</i>, since the term <i>invisible</i> has a bad <a href="/facts/Connotation/6GMwFTn9">connotation</a> (usually seen as something that the user can't see, and has no control over) while the term <i>transparent</i> has a good connotation (usually associated with not hiding anything). The vast majority of the times, the term <i>transparent</i> is used in a misleading way to refer to the actual invisibility of a computing process, which is also described by the term <i>opaque</i>, especially with regards to data structures. Because of this misleading and counter-intuitive definition, modern computer literature tends to prefer use of "agnostic" over "transparent". </p><p>The term is used particularly often with regard to an <a href="/facts/Abstraction_layer/EV8c84SY">abstraction layer</a> that is invisible either from its upper or lower neighbouring layer. </p><p>Also temporarily used later around 1969 in IBM and Honeywell programming manuals the term referred to a certain <a href="/facts/Computer_programming/QmSsFnu0">computer programming</a> technique. An application code was transparent when it was clear of the low-level detail (such as device-specific management) and contained only the logic solving a main problem. It was achieved through <a href="/facts/Encapsulation_(computer_science)/kzDnbHPe">encapsulation</a> – putting the code into modules that <a href="/facts/Information_hiding/dnSDPMaz">hid</a> internal details, making them invisible for the main application. </p>