Definition

stove-piped development

In engineering and information technology, stove-piped development is an approach in which improvements are considered only within the existing and technologically familiar context. The need for a change is perceived, an obvious solution is found, and improvements are made without much thought of future and larger contexts. An example is the telephone as originally developed. It operated by sending baseband audio-frequency signals over electrical wires. This system, without further refinement, had limited geographic operating range because of resistance loss in the wires. To some extent it was possible to overcome this loss by using excellent electrical conductors for the wires and by using the largest-diameter wire possible, but this was a stove-piped approach and was impractical beyond a certain point.

The telephone would never have given rise to today's communications infrastructure if an integrated approach had not been taken by theoreticians, inventors, and engineers in response to public pressure. But the telephone evolved along with other technologies such as electronic amplification, radio, and data conversion. The telephone was eventually modified to accommodate fax machines, remote-control devices, and computers. Ironically, long-distance telephone communications is now re-emerging within the Internet, which originally arose within the telephone infrastructure!

The expression was originally coined by the U.S. Army to describe any system or method developed in isolation, without considering how it might function with other existing or future technologies.

Contributor(s): Tim Stilwell
This was last updated in January 2006
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: