Jump to content

Interface bloat

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 2001:7d0:4982:1a80:79f4:4ea:8de0:39c3 (talk) at 13:53, 2 February 2018 (computer interface is not the term used in the industry and would be easily confused with an input device or a user interface, even "software interface" is confusing.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)

This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Interface bloat" – news · newspapers · books · scholar · JSTOR (March 2009) (Learn how and when to remove this message)

This article provides insufficient context for those unfamiliar with the subject. Please help improve the article by providing more context for the reader. (April 2016) (Learn how and when to remove this message)

(Learn how and when to remove this message)

In software design, interface bloat (also called fat interfaces by Bjarne Stroustrup and Refused Bequests by Martin Fowler) is when a interface incorporates too many operations on some data into an interface, only to find that most of the objects cannot perform the given operations.

Interface bloat is an example of an anti-pattern. One might consider using visitor pattern, Adapter Pattern, or interface segregation instead.

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Interface_bloat&oldid=823638200"

Hidden categories: