Analysis

  • Michael Bronzite

Abstract

Part 1 set out to establish that most system development exercises were pretty much doomed not to meet their original objectives.

Keywords

Marketing Image Scanner 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Maintenance (see Appendix 2)Google Scholar
  2. 2.
    Parikh G, Techniques of Program and System Maintenance, QED Informational Sciences, 1988, p.13Google Scholar
  3. 3.
    Project costs: Maintenance takes a two-thirds slice, Computer Weekly, 21.3.1991, p.1Google Scholar
  4. 4.
    Peverett T, Managing the maintenance crisis, Informatics, August 1991, p.31Google Scholar
  5. 5.
    Data View: Cost of correcting software errors, Computer Weekly, 20.6.1991, p.1Google Scholar
  6. 6.
    Leung L, Prepare user specifications, Computing, 12.9.1996, p.36Google Scholar
  7. 7.
    Survey of IT users, NCC, 1994, p.14Google Scholar
  8. 8.
    Evans D, IT bosses: What we want from you, Computer Weekly, 4.7.1991, p.15Google Scholar
  9. 9.
    Boyle B, Why IT and business managers must talk, Computer Weekly, 29.6.1995, p.16Google Scholar
  10. 10.
    Kavanagh J, Blind leading the blind into IT fog, Interface, The London Times, 6.8.1997, p.10Google Scholar
  11. 11.
    Bicknell D, City IT costs out of control, says survey, Computer Weekly, 4.1.1996, p.3Google Scholar
  12. 12.
    Infomonitor, IT impact continues to defy precise measurement, Information Age, October 1997, p. 5Google Scholar
  13. 13.
    James G, IT fiascoes…and how to avoid them, Datamation, November 1997Google Scholar
  14. 14.
    Glass R, Software Runaways, p.104, (see under Bibliography) Google Scholar
  15. 15.
    Collins T, The curse of the optimistic project instigators, Computer Weekly, 19.3.1998, p.36Google Scholar
  16. 16.
    Zells L, Litigated Disaster: The anatomy of a major product failure, Application Development Trends, November 1994, p.43Google Scholar
  17. 17.
    Isham P, Promising the earth will only end in tears, Computer Weekly, 5.8.1993, p.18Google Scholar
  18. 18.
    Donnelly F, Plan for all seasons, Computing, 4.6.1992, p.32Google Scholar
  19. 19.
    Jirokta M and Goguen J (editors), Requirements Engineering: Social and Technical Issues, Academic Press, 1994Google Scholar
  20. 20.
    Webster B, Pitfalls of Object-Oriented Development, p.206, (see under Bibliography) Google Scholar

Copyright information

© Springer-Verlag London 2000

Authors and Affiliations

  • Michael Bronzite

There are no affiliations available

Personalised recommendations