Brief: Buy, Don't Build - What Does That Mean for a Software Developer?
- Authors
- Todd Little (Western Atlas Software) | M. Ahsan Rahi (Western Atlas Software) | Craig Sinclair (Western Atlas Software)
- DOI
- https://doi.org/10.2118/30886-JPT
- Document ID
- SPE-30886-JPT
- Publisher
- Society of Petroleum Engineers
- Source
- Journal of Petroleum Technology
- Volume
- 47
- Issue
- 06
- Publication Date
- June 1995
- Document Type
- Journal Paper
- Pages
- 502 - 503
- Language
- English
- ISSN
- 0149-2136
- Copyright
- 1995. Society of Petroleum Engineers
- Downloads
- 1 in the last 30 days
- 48 since 2007
- Show more detail
- View rights & permissions
Summary
The buzz phrase of the 1990's for the petroleum software industry has become "buy, don't build." For an end user in an oil company, this generally means acquiring application software rather than developing it internally. The concept of buy, don't build can also apply for a software developer. Purchasing software toolkit components can expedite the development of an application as well as reduce future support requirements.
| File Size | 191 KB | Number of Pages | 2 |
