000 03776nam a2200541 i 4500
001 6267255
003 IEEE
005 20220712204611.0
006 m o d
007 cr |n|||||||||
008 151223s2003 mau ob 001 eng d
020 _a9780262256087
_qebook
020 _z0262256088
_qelectronic
020 _z0585480834
_qelectronic
020 _z9780585480831
_qelectronic
020 _z9780262050722
_qprint
035 _a(CaBNVSL)mat06267255
035 _a(IDAMS)0b000064818b421b
040 _aCaBNVSL
_beng
_erda
_cCaBNVSL
_dCaBNVSL
050 4 _aQA76.76.D47
_bE88 2003eb
082 0 _a005.1
_221
082 0 4 _a005.1
_222
100 1 _aEwusi-Mensah, Kweku,
_eauthor.
_921782
245 1 0 _aSoftware development failures :
_banatomy of abandoned projects /
_cKweku Ewusi-Mensah.
264 1 _aCambridge, Massachusetts :
_bMIT Press,
_cc2003
264 2 _a[Piscataqay, New Jersey] :
_bIEEE Xplore,
_c[2003]
300 _a1 PDF (xiv, 276 pages).
336 _atext
_2rdacontent
337 _aelectronic
_2isbdmedia
338 _aonline resource
_2rdacarrier
504 _aIncludes bibliographical references and index.
506 1 _aRestricted to subscribers or individual electronic text purchasers.
520 _aFailed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS.It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects.Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved.
530 _aAlso available in print.
538 _aMode of access: World Wide Web
550 _aDigitized and made available by: Books 24x7.com.
588 _aTitle from title screen.
588 _aDescription based on PDF viewed 12/23/2015.
650 0 _aComputer software
_xDevelopment.
_93349
650 0 _aSoftware failures.
_921783
650 0 _aRisk management.
_94713
655 0 _aElectronic books.
_93294
710 2 _aIEEE Xplore (Online Service),
_edistributor.
_921784
710 2 _aMIT Press,
_epublisher.
_921785
776 0 8 _iPrint version
_z9780262050722
856 4 2 _3Abstract with links to resource
_uhttps://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=6267255
942 _cEBK
999 _c72913
_d72913