Overengineering: Difference between revisions
Huw Powell (talk | contribs) |
removed nonsense Tag: section blanking |
||
| Line 9: | Line 9: | ||
=== Overcomplex === |
=== Overcomplex === |
||
Many German [[Cathode ray tube|CRT]] [[television]]s designed in the late 1990s contained features entirely alien to Japanese CRT's of the time, features that would often enough not manifest industry-wide until the mainstream shift towards [[Liquid crystal display|LCD]]/[[plasma display]] screens in the late 2000s. One such feature, observed in a [[Braun (company)|Braun]] TV of the era, was the ability to auto-detect whether the incoming signal was [[Stereophonic sound|stereophonic]] or [[monaural]], and display the signal type on the screen for a period of several seconds before disappearing. While useful in theory, when combined with a weak signal (such as from an [[indoor antenna]]) it had the periphery effect of periodically being unable to analyze the signal due to poor [[signal strength]], if only for a split second, then re-displaying the audio format once a successful analysis was achieved. This would result in the word "Stereo" being superimposed across the television in large text for a period of five seconds, approximate once every minute. This could result in extreme annoyance to the owners of the television, especially when stereo analogue television broadcasts have long been standard, and such information serves no purpose. |
|||
== Cultural references == |
== Cultural references == |
||
Revision as of 09:48, 3 July 2010
Overengineering (over-engineering) is when a product is more robust or complicated than necessary for its application, either (charitably) to ensure sufficient factor of safety, sufficient functionality, or due to design errors. Overengineering is desirable when safety or performance on a particular criterion is critical, or when broad functionality is required, but it is generally criticized from the point of view of value engineering as wasteful, and as a design philosophy, overcomplexity is the opposite of the less is more school of thought (and hence a violation of the KISS principle and parsimony).
Overengineering generally occurs in high-end products or specialized market criteria, and takes various forms. In one form, products are overbuilt, and have performance far in excess of needs (a family sedan that can drive at 300 km/h, or a home video cassette recorder with a projected lifespan of 100 years), and hence are more expensive, bulkier, and heavier than necessary. Alternatively, they may be overcomplicated – the design may be far more complicated than is necessary for its use, such as a modern text editor asking whether files should be saved in ASCII or EBCDIC format. Overcomplexity reduces usability of the product by the end user, and can decrease productivity of the design team due to the need to build and maintain all the features.
A related issue is market segmentation – making different products for different market segments. In this context, a particular product may be more or less suited for a particular market segment, and may be over- or under- engineered relative to an application.
Examples
Overbuilt
Overcomplex
Cultural references
A story about very precise engineering is given in the 1858 story The Deacon's Masterpiece or, the Wonderful "One-hoss Shay": A Logical Story by Oliver Wendell Holmes, Sr., which tells of a carriage (one-horse shay)
That was built in such a logical way
It ran a hundred years to a day,
And then,
...
went to pieces all at once, --
All at once, and nothing first, --
Just as bubbles do when they burst.
because it had been engineered so that no single piece failed first – no piece was over-engineered relative to the others, and they thus all failed at the same time.
References
- www.industriallogic.com/papers/StopOverEngineering.pdf — Stop Over-Engineering! (April 2002); a software-centric discussion from Software Development magazine.