Application posture

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Tom.Reding (talk | contribs) at 20:22, 1 December 2017 (Fix Category:CS1 maint: Uses authors parameter & ref cleanup; WP:GenFixes on; using AWB). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The term application posture characterizes the nature of a software application's interaction with its user.[1]

The term was coined by Alan Cooper, who characterized four 'postures' for applications: sovereign, transient, daemonic and parasitic.[2][3]

  • A sovereign application is a program that monopolizes the user's attention for long periods of time.
  • Cooper defined transient applications thus: 'A transient posture program comes and goes, presenting a single, high-relief function with a tightly restricted set of accompanying controls. The program is called when needed, it appears and performs its job, then it quickly leaves, letting the user continue her more normal activity, usually a sovereign application.'
  • Daemonic applications are background processes that require no direct user interaction.
  • Parasitic or Auxiliary applications are similar to transient applications in providing a limited, focused set of functionality and occupy a small space, but they are shown persistently and can be used for a long period of time.

See also

Bibliography

  • About Face by Cooper, Alan, Reimann, Robert & Cronin, David ISBN 978-0-470-08411-3, 2007
  • Ernest Kinsolving; Jörg Beringer. "The Posture of Portals". sapdesignguild.org. {{cite web}}: Unknown parameter |last-author-amp= ignored (|name-list-style= suggested) (help)
  • O Moravcik; D Petrik; T Skripcak; P Schreiber. "Elements of the Modern Application Software Development" (PDF). {{cite journal}}: Cite journal requires |journal= (help)

References

External links