|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| David R. Lindstrom, "Five Ways to Destroy a Development Project," IEEE Software, vol. 10, no. 5, pp. 55-58, September/October, 1993. | |||
| BibTex | x | ||
| @article{ 10.1109/52.232400, author = {David R. Lindstrom}, title = {Five Ways to Destroy a Development Project}, journal ={IEEE Software}, volume = {10}, number = {5}, issn = {0740-7459}, year = {1993}, pages = {55-58}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.232400}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Five Ways to Destroy a Development Project IS - 5 SN - 0740-7459 SP55 EP58 EPD - 55-58 A1 - David R. Lindstrom, PY - 1993 KW - system engineering; front-end development; tracing; tracking; software requirements; sizing; target hardware; test methodologies; software development; metrics program; software production; project management; software engineering VL - 10 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.232400
The author discusses five problems that can contribute to a software project's failure. The five pitfalls are: inadequate system engineering during the proposal and during front-end development; inadequate tracing, tracking, and management of system and software requirements; improper sizing of the target hardware; selection of design, production, and integration and test methodologies that are inappropriate to a large software development; and failure to provide a metrics program that would let managers track the progress of software production and test.
Index Terms:
system engineering; front-end development; tracing; tracking; software requirements; sizing; target hardware; test methodologies; software development; metrics program; software production; project management; software engineering
Citation:
David R. Lindstrom, "Five Ways to Destroy a Development Project," IEEE Software, vol. 10, no. 5, pp. 55-58, Sept.-Oct. 1993, doi:10.1109/52.232400
Usage of this product signifies your acceptance of the Terms of Use.

