|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Michiel van Genuchten, Les Hatton, "Software: What's In It and What's It In?," IEEE Software, vol. 27, no. 1, pp. 14-16, January/February, 2010. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2010.19, author = {Michiel van Genuchten and Les Hatton}, title = {Software: What's In It and What's It In?}, journal ={IEEE Software}, volume = {27}, number = {1}, issn = {0740-7459}, year = {2010}, pages = {14-16}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.19}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Software: What's In It and What's It In? IS - 1 SN - 0740-7459 SP14 EP16 EPD - 14-16 A1 - Michiel van Genuchten, A1 - Les Hatton, PY - 2010 KW - Software business KW - empirical KW - size KW - volume KW - COTS KW - open source KW - embedded VL - 27 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2010.19
IEEE Software's new series of Impact columns intends to get a better quantitative insight into the impact of software on various businesses. This introduction describes the reasoning behind the columns. All contributors will be asked to quantify the size (in lines of code or another size measure) and volume (number of copies sold per year or another measure) of their projects. This should allow the software developers to position and compare the experiences coming out of the different industries. We hope to publish three to six columns a year and to solicit submissions as momentum grows. Both engineering managers and business managers are encouraged to submit a column. We've already lined up the first columns with submissions from the mobile phone, computer and automotive industries. Our proposal's wide scope should let us accept contributions from large or small programs, low or high volume projects, open or closed source projects, embedded or commercial-off-the-shelf software, and in-house or outsourced software development.
1. R.N. Charette, "Why Software Fails," IEEE Spectrum, vol. 42, no. 9, 2005, pp. 42–49.
2. M. Mecham, "Boeing Faces 'Pretty Tight' 787 Delivery Schedule," Aviation Week,9 Sept. 2007; www.aviationweek.com/aw/generic/story_generic.jsp?channel=awst&id=news aw091007p2.xml&headline=Boeing%20Faces%20%27%27Pretty%20Tight%27%27%20787%20Delivery%20Schedule .
3. M. van Genuchten, "The Impact of Software Growth on the Electronics Industry," Computer, vol. 40, no. 1, 2007, pp. 106–108.
4. L. Hatton, "Estimating Source Lines of Code from Object Code: Windows and Embedded Control Systems," leshatton.org, 2005; www.leshatton.org/LOC2005.html.
Index Terms:
Software business, empirical, size, volume, COTS, open source, embedded
Citation:
Michiel van Genuchten, Les Hatton, "Software: What's In It and What's It In?," IEEE Software, vol. 27, no. 1, pp. 14-16, Jan.-Feb. 2010, doi:10.1109/MS.2010.19
Usage of this product signifies your acceptance of the Terms of Use.

