Knowledge

Transparency (human–computer interaction)

Source 📝

135: 25: 346:
and decompression of data, enabling users to store more files on a medium without any special knowledge; some file systems encrypt files transparently. This approach does not require running a compression or encryption utility manually.
396:
Access transparency – Regardless of how resource access and representation has to be performed on each individual computing entity, the users of a distributed system should always access resources in a single, uniform way. Example: SQL
306:
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
243:
as much as possible while changing its internal behavior. The purpose is to shield change from all systems (or human users) on the other end of the interface. Confusingly, the term refers to the overall
450:
The degree to which these properties can or should be achieved may vary widely. Not every system can or should hide everything from its users. For instance, due to the existence of a fixed and finite
358:
access, so that the same application will work with different databases; here, the abstraction layer allows other parts of the program to access the database transparently (see
454:
there will always be more latency on accessing resources distant from the user. If one expects real-time interaction with the distributed system, this may be very noticeable.
439:– Negotiation of cryptographically secure access of resources must require a minimum of user intervention, or users will circumvent the security in preference of productivity. 152: 46: 406:
Migration transparency – Users should not be aware of whether a resource or computing entity possesses the ability to move to a different physical or logical location.
288:, especially with regards to data structures. Because of this misleading and counter-intuitive definition, modern computer literature tends to prefer use of " 199: 97: 171: 69: 178: 76: 185: 83: 167: 65: 327:
is transparent, because it introduces the access to files stored remotely on the network in a way uniform with previous local access to a
481: 462: 476: 403:– Users of a distributed system should not have to be aware of where a resource is physically located. Example: Pages in the Web 370: 192: 90: 421:
transparency – While multiple users may compete for and share a single resource, this should not be apparent to any of them.
284:
is used in a misleading way to refer to the actual invisibility of a computing process, which is also described by the term
415:
transparency – If a resource is replicated among several locations, it should appear to the user as a single resource.
218: 116: 54: 308: 253: 302:
Also temporarily used later around 1969, in IBM and Honeywell programming manuals, the term referred to a certain
486: 430: 418: 412: 324: 280:
has a good connotation (usually associated with not hiding anything). The vast majority of the times, the term
156: 50: 335:(FTP) is considerably less transparent, because it requires each user to learn how to access files through an 433:
transparency – Whether a resource lies in volatile or permanent memory should make no difference to the user.
409:
Relocation transparency – Should a resource move while in use, this should not be noticeable to the end user.
389:
should hide its distributed nature from its users, appearing and functioning as a normal centralized system.
366: 436: 463:
https://lightcast.io/open-skills/skills/KS441HX6SDYW15ZBFJNJ/transparency-human-computer-interaction
374: 35: 257: 145: 39: 332: 400: 240: 276:(usually seen as something that the user can't see, and has no control over) while the term 424: 351: 303: 8: 386: 359: 312: 296: 343: 331:, so the user might even not notice it while using the folder hierarchy. The early 427:– Always try to hide any failure and recovery of computing entities and resources. 451: 354:, it is also considered good practice to develop or use abstraction layers for 470: 289: 328: 273: 232: 299:
that is invisible either from its upper or lower neighboring layer.
134: 24: 355: 315:
internal details, making them invisible for the main application.
264:
is widely used in computing marketing in substitution of the term
373:
that hide actual implementations done with different underlying
447:, the Open Distributed Processing Reference Model (ISO 10746). 444: 380: 443:
Formal definitions of most of these concepts can be found in
295:
The term is used particularly often with regard to an
235:system, such as a new feature or new component, is 159:. Unsourced material may be challenged and removed. 369:, transparency is facilitated through the use of 468: 342:Similarly, some file systems allow transparent 239:if the system after change adheres to previous 168:"Transparency" human–computer interaction 66:"Transparency" human–computer interaction 381:Types of transparency in distributed system 53:. Unsourced material may be challenged and 219:Learn how and when to remove this message 117:Learn how and when to remove this message 248:of the component, it does not refer to 469: 392:There are many types of transparency: 311:– putting the code into modules that 385:Transparency means that any form of 157:adding citations to reliable sources 128: 51:adding citations to reliable sources 18: 250:visibility of component's internals 13: 482:Distributed computing architecture 16:Term in human–computer interaction 14: 498: 133: 23: 144:needs additional citations for 1: 457: 7: 367:object-oriented programming 318: 10: 503: 477:Human–computer interaction 333:File Transfer Protocol 292:" over "transparent". 487:Software architecture 437:Security transparency 401:Location transparency 425:Failure transparency 352:software engineering 304:computer programming 153:improve this article 47:improve this article 325:Network File System 387:distributed system 360:Data Access Object 241:external interface 323:For example, the 297:abstraction layer 268:, since the term 229: 228: 221: 203: 127: 126: 119: 101: 494: 362:, for example). 231:Any change in a 224: 217: 213: 210: 204: 202: 161: 137: 129: 122: 115: 111: 108: 102: 100: 59: 27: 19: 502: 501: 497: 496: 495: 493: 492: 491: 467: 466: 460: 383: 321: 225: 214: 208: 205: 162: 160: 150: 138: 123: 112: 106: 103: 60: 58: 44: 28: 17: 12: 11: 5: 500: 490: 489: 484: 479: 459: 456: 452:speed of light 441: 440: 434: 428: 422: 416: 410: 407: 404: 398: 382: 379: 320: 317: 227: 226: 141: 139: 132: 125: 124: 31: 29: 22: 15: 9: 6: 4: 3: 2: 499: 488: 485: 483: 480: 478: 475: 474: 472: 465: 464: 455: 453: 448: 446: 438: 435: 432: 429: 426: 423: 420: 417: 414: 411: 408: 405: 402: 399: 395: 394: 393: 390: 388: 378: 376: 372: 368: 363: 361: 357: 353: 348: 345: 340: 338: 334: 330: 326: 316: 314: 310: 309:encapsulation 305: 300: 298: 293: 291: 287: 283: 279: 275: 271: 267: 263: 259: 255: 251: 247: 242: 238: 234: 223: 220: 212: 209:February 2019 201: 198: 194: 191: 187: 184: 180: 177: 173: 170: –  169: 165: 164:Find sources: 158: 154: 148: 147: 142:This article 140: 136: 131: 130: 121: 118: 110: 99: 96: 92: 89: 85: 82: 78: 75: 71: 68: –  67: 63: 62:Find sources: 56: 52: 48: 42: 41: 37: 32:This article 30: 26: 21: 20: 461: 449: 442: 391: 384: 364: 349: 341: 336: 322: 301: 294: 285: 281: 277: 269: 265: 261: 260:). The term 249: 246:invisibility 245: 236: 230: 215: 206: 196: 189: 182: 175: 163: 151:Please help 146:verification 143: 113: 107:October 2021 104: 94: 87: 80: 73: 61: 45:Please help 33: 431:Persistence 413:Replication 344:compression 329:file system 282:transparent 278:transparent 274:connotation 262:transparent 258:open system 237:transparent 471:Categories 458:References 419:Concurrent 371:interfaces 272:has a bad 179:newspapers 77:newspapers 270:invisible 266:invisible 254:white box 233:computing 34:does not 356:database 339:client. 319:Examples 290:agnostic 397:Queries 375:classes 252:(as in 193:scholar 91:scholar 55:removed 40:sources 445:RM-ODP 286:opaque 195:  188:  181:  174:  166:  93:  86:  79:  72:  64:  200:JSTOR 186:books 98:JSTOR 84:books 172:news 70:news 38:any 36:cite 365:In 350:In 337:ftp 313:hid 256:or 155:by 49:by 473:: 377:. 222:) 216:( 211:) 207:( 197:· 190:· 183:· 176:· 149:. 120:) 114:( 109:) 105:( 95:· 88:· 81:· 74:· 57:. 43:.

Index


cite
sources
improve this article
adding citations to reliable sources
removed
"Transparency" human–computer interaction
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message

verification
improve this article
adding citations to reliable sources
"Transparency" human–computer interaction
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
computing
external interface
white box
open system
connotation
agnostic

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.