What do you think?
Rate this book
Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies
Publisher's Products purchased from Third Party sellers are not guaranteed by the publisher for quality, authenticity, or access to any online entitlements included with the product.
Proven techniques for software engineering success This in-depth volume examines software engineering topics that are not covered the question of why software engineering has developed more than 2,500 programming languages; problems with traditional definitions of software quality; and problems with common metrics, "lines of code," and "cost per defect" that violate standard economic assumptions. The book notes that a majority of "new" projects are actually replacements for legacy applications, illustrating that data mining for lost requirements should be a standard practice. Difficult social engineering issues are also covered, such as how to minimize harm from layoffs and downsizing. Software Engineering Best Practices explains how to effectively plan, size, schedule, and manage software projects of all types, using solid engineering procedures. It details proven methods, from initial requirements through 20 years of maintenance. Portions of the book have been extensively reviewed by key engineers from top companies, including IBM, Microsoft, Unisys, and Sony.
Proven techniques for software engineering success This in-depth volume examines software engineering topics that are not covered the question of why software engineering has developed more than 2,500 programming languages; problems with traditional definitions of software quality; and problems with common metrics, "lines of code," and "cost per defect" that violate standard economic assumptions. The book notes that a majority of "new" projects are actually replacements for legacy applications, illustrating that data mining for lost requirements should be a standard practice. Difficult social engineering issues are also covered, such as how to minimize harm from layoffs and downsizing. Software Engineering Best Practices explains how to effectively plan, size, schedule, and manage software projects of all types, using solid engineering procedures. It details proven methods, from initial requirements through 20 years of maintenance. Portions of the book have been extensively reviewed by key engineers from top companies, including IBM, Microsoft, Unisys, and Sony.
688 pages, Hardcover
First published January 1, 2009
5 people are currently reading
55 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
April 13, 2013
If software engineering has to be recognized as a true profession like other conventional engineering fields it has to inculcate the discipline of better measurements, better benchmarks, better quality control, and better security during the process of software development. Thus opines Caper Jones, the author of this book who is a well-respected authority in this field.
He also says that majority of the best-practice claims in software engineering fields are not based on solid measurements using valid metrics. In this book he attempts to remedy the situation by describing the best practices where the available quantitative data proves their effectiveness at least to some extent.
This book is a result of extensive research by Caper Jones and provides lots of data and information. However there are several instances of repetitive information (for e.g. project taxonomy description) in this book, which could have been avoided. Also I felt that Chapter 3 (A Preview of Software Development and Maintenance in 2049) was rather unnecessary. These have increased the bulk (and the price??) of the book .
The book serves more as a pointer to best practices rather than providing in-depth understanding and know-how of implementing them. I was expecting more case studies in the book of this type. Besides I came across very few best practices which I was not earlier aware of.
On the whole a good reference book, especially if you need to do some research or need some facts and figures for arguing the case for a best practice. But I don’t otherwise consider it as a MUST Read book.
For summary of each chapter in the book, go to
He also says that majority of the best-practice claims in software engineering fields are not based on solid measurements using valid metrics. In this book he attempts to remedy the situation by describing the best practices where the available quantitative data proves their effectiveness at least to some extent.
This book is a result of extensive research by Caper Jones and provides lots of data and information. However there are several instances of repetitive information (for e.g. project taxonomy description) in this book, which could have been avoided. Also I felt that Chapter 3 (A Preview of Software Development and Maintenance in 2049) was rather unnecessary. These have increased the bulk (and the price??) of the book .
The book serves more as a pointer to best practices rather than providing in-depth understanding and know-how of implementing them. I was expecting more case studies in the book of this type. Besides I came across very few best practices which I was not earlier aware of.
On the whole a good reference book, especially if you need to do some research or need some facts and figures for arguing the case for a best practice. But I don’t otherwise consider it as a MUST Read book.
For summary of each chapter in the book, go to
Read
November 21, 2011it's great!
Displaying 1 - 2 of 2 reviews
Can't find what you're looking for?
Get help and learn more about the design.