Software development failures : (Record no. 72913)

000 -LEADER
fixed length control field 03776nam a2200541 i 4500
001 - CONTROL NUMBER
control field 6267255
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20220712204611.0
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 151223s2003 mau ob 001 eng d
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
ISBN 9780262256087
-- ebook
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
-- electronic
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
-- electronic
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
-- electronic
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
-- print
082 0# - CLASSIFICATION NUMBER
Call Number 005.1
082 04 - CLASSIFICATION NUMBER
Call Number 005.1
100 1# - AUTHOR NAME
Author Ewusi-Mensah, Kweku,
245 10 - TITLE STATEMENT
Title Software development failures :
Sub Title anatomy of abandoned projects /
300 ## - PHYSICAL DESCRIPTION
Number of Pages 1 PDF (xiv, 276 pages).
520 ## - SUMMARY, ETC.
Summary, etc Failed 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.
650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1
General subdivision Development.
856 42 - ELECTRONIC LOCATION AND ACCESS
Uniform Resource Identifier https://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=6267255
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Koha item type eBooks
264 #1 -
-- Cambridge, Massachusetts :
-- MIT Press,
-- c2003
264 #2 -
-- [Piscataqay, New Jersey] :
-- IEEE Xplore,
-- [2003]
336 ## -
-- text
-- rdacontent
337 ## -
-- electronic
-- isbdmedia
338 ## -
-- online resource
-- rdacarrier
588 ## -
-- Title from title screen.
588 ## -
-- Description based on PDF viewed 12/23/2015.
650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1
-- Computer software
650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1
-- Software failures.
650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1
-- Risk management.

No items available.