The principle of good enough (sometimes abbreviated to POGE) is a rule for software and systems design. It favours quick-and-simple (but potentially extensible) designs over elaborate systems designed by committees. Once the quick-and-simple design is deployed, it can then evolve as needed, driven by user requirements. Ethernet, the Internet protocol and the World Wide Web are good examples of this kind of design.
This kind of design is not appropriate in systems where it is not possible to evolve the system over time, or where the full functionality is required from the start.
Quantitatively, some measure of "good enough" may be assessed by establishing both a metric and a metric cutoff (or tolerance) of one previous iteration of a design and the current one; when the metrics converge to or below the cutoff, then the specification has been satisfied.
See also
External links
- The Net's gettin' messy (ZDNet on POGE)
- The Good Enough Revolution: When Cheap and Simple Is Just Fine (Wired (magazine) by Robert Capps August 24, 2009)
 |
This software engineering-related article is a stub. You can help Wikipedia by expanding it. |
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
