Software Failure: Management Failure (Wiley Series in Software Engineering Practice) [Paperback]

Stephen Flowers (Author)

Available from these sellers.

Trade In this Item for up to �7.60

Get an extra �5 when you trade in books worth �10 or more until June 30, 2012. Trade in Software Failure: Management Failure (Wiley Series in Software Engineering Practice) for an Amazon.co.uk gift card of up to �7.60, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.

› See more product promotions

Product details

Paperback: 210 pages
Publisher: John Wiley & Sons (29 Oct 1996)
Language English
ISBN-10: 0471951137
ISBN-13: 978-0471951131
Product Dimensions: 23.4 x 18.7 x 1.6 cm
Amazon Bestsellers Rank: 986,396 in Books (See Top 100 in Books)

Would you like to update product info or give feedback on images?

See Complete Table of Contents

More About the Author

Discover books, learn about writers, and more.

› Visit Amazon's Stephen Flowers Page

Inside This Book (Learn More)

First Sentence
Computerized information systems are at the heart of all modern organizations. Read the first page

Explore More
Concordance

Tag this product

(What's this?)

Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items.

Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more

Customer Reviews

There are no customer reviews yet on Amazon.co.uk.

5 star

4 star

3 star

2 star

1 star

Write a customer review

Most Helpful Customer Reviews on Amazon.com ^(beta)

Amazon.com: 1 review

12 of 14 people found the following review helpful

Software management cannot replace business management 25 May 1998

By Johnny Getha - Published on Amazon.com

Format:Paperback

The gist of this fascinating book is that so-called software failures are really failures of the business environment, not the coders. In not one of the case studies are the software developers to blame. The culprit is always bigger-picture management, who are often trying to use a computer system to fix a broken business practice. So far I haven't read the entire book, but the author does not seem to think practices such as CMM or Software Process Improvement will really help. The entire system, not just the computer components, must be evaluated holistically. Software must be used only where it will really help. Trying to automate a broken business practice will only result in a broken automated system.

› Go to Amazon.com to see the review

Was this review helpful? Let us know

.jsOffDisplayBlock { display: block; } .jsOffDisplayInline { display: inline; } .jsOffVisibility { visibility: visible; } .jsOnDisplayBlock { display: none; } .jsOnDisplayNoneBlock { display: block; } .jsOnDisplayNoneInline { display: inline; } .jsOnDisplayInline { display: none; } .jsOnVisibility { visibility: hidden; } .jqOnDisplayBlock { display: none; } .jqOnDisplayInline { display: none; } .jqOnVisibility { visibility: hidden; } .jqOnDisplayNoneBlock { display: block; } .jqOnDisplayNoneInline { display: inline; }