Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies
Capers JonesBooks.org participates in affiliate programs including Bookshop.org and the Amazon Services LLC Associates Program. We may earn a commission from qualifying purchases made through links on this page, at no additional cost to you.
Overview
Proven techniques for software engineering success
This in-depth volume examines software engineering topics that are not covered elsewhere: 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.
- Manage Agile, hierarchical, matrix, and virtual software development teams
- Optimize software quality using JAD, OFD, TSP, static analysis, inspections, and other methods with proven success records
- Use high-speed functional metrics to assess productivity and quality levels
- Plan optimal organization, from small teams through more than 1,000 personnel
Synopsis
Proven techniques for software engineering success
This in-depth volume examines software engineering topics that are not covered elsewhere: 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.
- Manage Agile, hierarchical, matrix, and virtual software development teams
- Optimize software quality using JAD, OFD, TSP, static analysis, inspections, and other methods with proven success records
- Use high-speed functional metrics to assess productivity and quality levels
- Plan optimal organization, from small teams through more than 1,000 personnel