- Hardcover: 656 pages
- Publisher: Addison Wesley; 1 edition (16 Aug 2004)
- Language English
- ISBN-10: 0321228758
- ISBN-13: 978-0321228758
- Product Dimensions: 24.1 x 17.9 x 3.5 cm
- Average Customer Review: 5.0 out of 5 stars See all reviews (1 customer review)
- Amazon Bestsellers Rank: 1,267,285 in Books (See Top 100 in Books)
- See Complete Table of Contents
| |||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details. |
Product details |
More About the Author
Product Description
Product Description
Is your organization getting the maximum value out of its precious, limitedresources (specifically, money, time, and manpower)? Most professionaldevelopers do not consider the business implications of the technical decisionsthey are making -- but they should! In order for software engineering to trulybecome an engineering discipline, software professionals need to know andunderstand the engineering economy.This new book helps software practitioners appreciate the organizationalramifications of each decision they make. It is an insight into the engineeringeconomy that more software organizations aspire to. Each chapter contains aseries of self-study questions to help the reader apply the learned techniques,and the book can also serve as a reference that software engineers can turn to,again and again.
From the Back Cover
"This pioneering book highlights critical, overlooked skills needed by true software professionals."
Steve McConnell
CEO and Chief Software Engineering
Construx Software
"It's about time someone took this stuff seriously."
Steven Mellor
Chief Scientist
Embedded Systems Division
Mentor Graphics Corporation
Co-Author of Exploring the Role of Executable UML in Model-Driven Architecture and six other books
"Despite the fact that engineering economics is considered a core area of any engineering field, virtually no books have been written in the area of software engineering economics. Steve Tockey's Return on Software nicely fills this gaps by providing a comprehensive introduction to software engineering economics accessible both to students and to new software professionals."
Donald J. Bagert, Ph.D., P.E. Director of Software Engineering and Professor of Computer Science & Software Engineering Rose-Hulman Institute of Technology
"The elements of this book are useful not only in making decisions but also in understanding why and how other people and organizations make decisions"
Shari Lawrence Pfleeger
Senior Researcher, RAND
Co-author of Security in Computing and eight other software engineering titles
"This just what the doctor ordered to help software programs solve the problem of how to introduce engineering economics and business decision-making into their curricula. The economics of software development should not only be part of any computing curriculum they are an essential element of recent accreditation and certification recommendations.
This book is an accessible and relevant text for any student of software engineering. The style is clear and straightforward and the software examples will be appealing to students and faculty alike. I can't wait to use it in class!"
Thomas B. Hilburn, Professor
Department of Computer and Software Engineering
Embry-Riddle Aeronautical University
Is your organization maximizing the return on its investments of money, time, and personnel? Probably not, because most software professionals don't know how to consider the business aspects of their software decisions. Most don't even know that it's important to do so. Business consequences should play a critical role in all software technical choices—from choosing which projects to do, selecting software development processes, choosing algorithms and data structures, all the way to determining how much testing is enough.
Return on Software: Maximizing the Return on Your Software Investment is about making choices: software technical choices in a business context. It helps software professionals appreciate the business consequences of the decisions they make. This primer will prove a valuable reference for making the important decisions the typical software organization faces both today and down the road. Inside, you'll learn how to:
Estimate how much each proposed software technical decision will cost, and how much it will return.
Weigh the time frames for a software decision's costs and benefits against each other to reveal when there might be a more important factor than schedule.
- Attach a value to quality and produce a rational answer to the question, "How much testing is enough?"
Account for risk and uncertainty in software technical decisions, such as when considering a new technology.
Communicate your decisions in a way that speaks to the all-important bottom line.
Each chapter contains a set of self-study questions designed to help you apply the featured concepts and techniques. An enhanced online index allows you to quickly and easily search the entire text for specific topics.
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
Most Helpful Customer Reviews
2 of 2 people found the following review helpful
Format:Hardcover
Software engineering is, more often than not, still taught void of economic considerations. The significance of the term engineering - that is, the use of proven methods, refined over time, to implement cost-effective solutions to over-constrained real world problems - seems, in the main, to have been lost on academic institutions and businesses alike. Software development is ultimately an irreversible capital investment, and therefore, it should be driven by business considerations that add (quantified) value to the organisation.
"Return on Software" provides the rationale and the relevant decision making tools to redress the problem. Tockey masterfully adapts existing and proven analytical techniques of managerial economics for use throughout the software development life cycle. Written for and from the point of view of software decision makers at various levels in an organisation, the topics are clearly laid out and richly annotated with cogent examples throughout. Ignoring the featured concepts is not an option for financially responsible organisations.
The book is an important contribution to the attempt to tame software development. It is pitched at the right level and covers the fundamentals as well as the advanced concepts in a practical manner.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
9 reviews
5 of 5 people found the following review helpful
Economics with a Software Spin
28 Feb 2005
Format:Hardcover
First, a confession, I know Steve Tockey. I work with Steve. That may bias my review a bit depending on how much I like Steve. One thing about Steve is that he home brews many nice beers and brings them into work where we get to share. I like Steve.
I also like his book. Now, I will admit that this is no thriller where you are excited to turn the next page (though I did get a little worked up on Analytical Hierarchical Process). It is designed to be an entry level economics text for the world of software engineering. The world of computer science and software engineering needed a book like this and didn't have one. So, Steve brewed this one up.
Part one (chapters 1-9) contain the basic economic theory you would find in most basic economic books. The topics are based around making decisions to make the most money (for profit companies) or to deliver the most benefit (non-profit). The text in these sections tends to get acronym heavy and Steve had to use the equation editor to type all the fancy mathematical formulas needed for things like interest for equal-payment-series capitol recovery. If you have had a basic economics course in college you can probably skip the first part without any pain. If you haven't or had forgotten (like me), then reading them is warranted. I found Steve's prose on this very dry subject to be reasonable.
Parts two through five carry on in the same way (chapters 10 - 20). Part two in decision making in for-profit companies and part three is advanced decision making in for-profit companies. Again, if you have concepts like Minimum Attractive Rate of Return, Cash-Flow Streams, Planning Horizons, Sunk Cost & Salvage, Inflation & Purchasing Power, Depreciation, Modified Accelerated Cost Recovery System, etc. then you can skip these sections. Same sort of story for part four, decisions in non-profit companies and part five, present economy.
BUT WAIT, there is part six! Estimation, risk, and uncertainty. Now here is a section that everybody should read, at least a couple of times. In my work and consulting, I find I am recommending to my clients that they read this section carefully. People building software seems to really miss these economic concepts. Steve does a very good job here in explaining how estimation, risk, and uncertainty work together (often against) on a work effort. He then provides several decision making strategies that work within the reality of uncertainty.
Part seven completes the teaching part with working with multiple-attribute decisions with a good discussion on number theory and how to rationally make comparisons. This is another section that I find most people don't understand too well and highly recommend that everybody reads this part.
There is a part eight but it is a summary and conclusion.
So, my bottom line is that some parts of the book are a must read. So parts are a could read. If you don't mind skimming the parts that you know or are not applicable for the current situation, this book should work out fine. It is also one of those books that you will actually pull off the shelf next time you are asked to lead the selection of a new Commercial Off The Self (COTS) system, choose between two competing project ideas, or just want to make a better personal finance decision.
I also like his book. Now, I will admit that this is no thriller where you are excited to turn the next page (though I did get a little worked up on Analytical Hierarchical Process). It is designed to be an entry level economics text for the world of software engineering. The world of computer science and software engineering needed a book like this and didn't have one. So, Steve brewed this one up.
Part one (chapters 1-9) contain the basic economic theory you would find in most basic economic books. The topics are based around making decisions to make the most money (for profit companies) or to deliver the most benefit (non-profit). The text in these sections tends to get acronym heavy and Steve had to use the equation editor to type all the fancy mathematical formulas needed for things like interest for equal-payment-series capitol recovery. If you have had a basic economics course in college you can probably skip the first part without any pain. If you haven't or had forgotten (like me), then reading them is warranted. I found Steve's prose on this very dry subject to be reasonable.
Parts two through five carry on in the same way (chapters 10 - 20). Part two in decision making in for-profit companies and part three is advanced decision making in for-profit companies. Again, if you have concepts like Minimum Attractive Rate of Return, Cash-Flow Streams, Planning Horizons, Sunk Cost & Salvage, Inflation & Purchasing Power, Depreciation, Modified Accelerated Cost Recovery System, etc. then you can skip these sections. Same sort of story for part four, decisions in non-profit companies and part five, present economy.
BUT WAIT, there is part six! Estimation, risk, and uncertainty. Now here is a section that everybody should read, at least a couple of times. In my work and consulting, I find I am recommending to my clients that they read this section carefully. People building software seems to really miss these economic concepts. Steve does a very good job here in explaining how estimation, risk, and uncertainty work together (often against) on a work effort. He then provides several decision making strategies that work within the reality of uncertainty.
Part seven completes the teaching part with working with multiple-attribute decisions with a good discussion on number theory and how to rationally make comparisons. This is another section that I find most people don't understand too well and highly recommend that everybody reads this part.
There is a part eight but it is a summary and conclusion.
So, my bottom line is that some parts of the book are a must read. So parts are a could read. If you don't mind skimming the parts that you know or are not applicable for the current situation, this book should work out fine. It is also one of those books that you will actually pull off the shelf next time you are asked to lead the selection of a new Commercial Off The Self (COTS) system, choose between two competing project ideas, or just want to make a better personal finance decision.
4 of 4 people found the following review helpful
The Latest on Software Economics
3 Dec 2004
Format:Hardcover
There are hundreds of books on topics relevant to various aspects of software engineering. However, when we analyze what went wrong with so many of our large practical software projects, one of the leading culprits is a misunderstanding of the business, economic and financial aspects of the projects. Where are the books and courses to help us with this major problem?
University engineering programs often have a course such as Fundamentals of Engineering Economy. What Steve Tockey has done with his book is to apply these general engineering economics topics specifically to the field of Software Engineering and set a standard for the subfield of Software Engineering Economics. His is not the first such book (see, e. g., Barry Boehm, Software Engineering Economics, Prentice Hall, 1981 or Leon Levy, Taming the Tiger - Software Engineering and Software Economics, Springer-Verlag, 1987) but it is the most thorough and up-to-date one that I know. It is an excellent book on a very important subject. Every professional software engineer, whether CTO, group manager or programmer in the trenches, will benefit considerably from reading this book.
Return on Software is divided into several major parts: general concepts of business decision-making, interest and the value of money, and cash flow streams; business decision-making at for-profit companies; decision-making at government and not-for-profit organizations; estimation, risk and uncertainty; and decision-making based on criteria other than money such as reliability, quality, speed, and other important features (strict economists might argue that all of these other criteria could be equivalenced to money considerations but I think considering these other criteria on their own seems more natural to me).
Judging from the topics listed above, Steve believes business decision-making to be the key ingredient of successful software engineering. I could not agree more. The crucial chapter in the book is #4: The Business Decision-Making Process. The key topics in this chapter include understanding the real problem, defining the selection criteria, identifying all reasonable technically feasible solutions, evaluating those proposals, selecting the preferred proposal, and monitoring its performance. The remainder of the book is an elucidation of those topics.
Each chapter closes with a summary and a set of self-study questions supporting the book to being used as a textbook. My university will offer a course around "Return on Software" in the spring quarter for our Master of Software Engineering students and I expect the course to be offered regularly. The last time I checked, Steve's company was not offering a short course on his book's topic but it would not surprise me to see one soon.
To prove that I am not from the publisher's marketing department, I would like to suggest that the next edition include at least two more topics: buy-or-build decision-making and outsourcing (whether offshore or not).
University engineering programs often have a course such as Fundamentals of Engineering Economy. What Steve Tockey has done with his book is to apply these general engineering economics topics specifically to the field of Software Engineering and set a standard for the subfield of Software Engineering Economics. His is not the first such book (see, e. g., Barry Boehm, Software Engineering Economics, Prentice Hall, 1981 or Leon Levy, Taming the Tiger - Software Engineering and Software Economics, Springer-Verlag, 1987) but it is the most thorough and up-to-date one that I know. It is an excellent book on a very important subject. Every professional software engineer, whether CTO, group manager or programmer in the trenches, will benefit considerably from reading this book.
Return on Software is divided into several major parts: general concepts of business decision-making, interest and the value of money, and cash flow streams; business decision-making at for-profit companies; decision-making at government and not-for-profit organizations; estimation, risk and uncertainty; and decision-making based on criteria other than money such as reliability, quality, speed, and other important features (strict economists might argue that all of these other criteria could be equivalenced to money considerations but I think considering these other criteria on their own seems more natural to me).
Judging from the topics listed above, Steve believes business decision-making to be the key ingredient of successful software engineering. I could not agree more. The crucial chapter in the book is #4: The Business Decision-Making Process. The key topics in this chapter include understanding the real problem, defining the selection criteria, identifying all reasonable technically feasible solutions, evaluating those proposals, selecting the preferred proposal, and monitoring its performance. The remainder of the book is an elucidation of those topics.
Each chapter closes with a summary and a set of self-study questions supporting the book to being used as a textbook. My university will offer a course around "Return on Software" in the spring quarter for our Master of Software Engineering students and I expect the course to be offered regularly. The last time I checked, Steve's company was not offering a short course on his book's topic but it would not surprise me to see one soon.
To prove that I am not from the publisher's marketing department, I would like to suggest that the next edition include at least two more topics: buy-or-build decision-making and outsourcing (whether offshore or not).
3 of 3 people found the following review helpful
An Excellent Resource
29 Nov 2004
Format:Hardcover
How I was introduced to this book:
About nine months before this book was published I was researching the return on investment of software projects. While doing my research, I was introduced to Steve Tockey who asked if I might be interested in reviewing his book.
My background:
For almost 10 years I've worked in the software and consulting industry. Currently, I work at one of the leading CRM software companies worldwide where I spent three years advising customers on how they can get the most out of their investment in our software. At the time of my research, it was imperative that our division understood how software investments are impacted by certain business decisions and related financial considerations. Today, I am responsible for planning, implementing, and measuring the outcomes of investments and projects within our marketing organization.
Comments on the book:
This book does an excellent job covering the financial aspects of investing in software systems (or really any investment) as well as covering decision-making and risk management techniques. If your career path includes the development of any business case for software systems, this book explains many of the concepts you will have to use. While the introductory portions of the book explain how financial principles generally apply to software, the book goes far beyond an introduction - honestly, it's depth in content will give it a home on my bookshelf as a trusted reference for years to come. Besides clear explanations and good fundamental examples, the accompanying self-study questions, website, and tools will help readers truly understand and use what is being taught.
If you are familiar with Steve McConnell's books on software, you will not be disappointed with this one (as Steve Tockey works at Construx Software).
About nine months before this book was published I was researching the return on investment of software projects. While doing my research, I was introduced to Steve Tockey who asked if I might be interested in reviewing his book.
My background:
For almost 10 years I've worked in the software and consulting industry. Currently, I work at one of the leading CRM software companies worldwide where I spent three years advising customers on how they can get the most out of their investment in our software. At the time of my research, it was imperative that our division understood how software investments are impacted by certain business decisions and related financial considerations. Today, I am responsible for planning, implementing, and measuring the outcomes of investments and projects within our marketing organization.
Comments on the book:
This book does an excellent job covering the financial aspects of investing in software systems (or really any investment) as well as covering decision-making and risk management techniques. If your career path includes the development of any business case for software systems, this book explains many of the concepts you will have to use. While the introductory portions of the book explain how financial principles generally apply to software, the book goes far beyond an introduction - honestly, it's depth in content will give it a home on my bookshelf as a trusted reference for years to come. Besides clear explanations and good fundamental examples, the accompanying self-study questions, website, and tools will help readers truly understand and use what is being taught.
If you are familiar with Steve McConnell's books on software, you will not be disappointed with this one (as Steve Tockey works at Construx Software).
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
- Books > Business, Finance & Law > Management > Management Skills > Decision Making
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Software & Graphics
- Books > Science & Nature > Engineering & Technology > Mechanical & Materials Engineering > Production Engineering
- Books > Science & Nature > Engineering & Technology > Production, Manufacturing & Operational > Productivity
- Books > Scientific, Technical & Medical
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
