Software Development Patterns and Antipatterns
14 days return policy
Shipping & Delivery
Product details
- ISBN 9781032017228
- Weight: 721g
- Dimensions: 156 x 234mm
- Publication Date: 27 Aug 2021
- Publisher: Taylor & Francis Ltd
- Publication City/Country: GB
- Product Form: Paperback
Secure
checkout
Fast Shipping
Easy returns
Software development has been a troubling since it first started. There are seven chronic problems that have plagued it from the beginning:
- Incomplete and ambiguous user requirements that grow by >2% per month.
- Major cost and schedule overruns for large applications > 35% higher than planned.
- Low defect removal efficiency (DRE) < 85% on large systems.
- Cancelled projects that are not completed: > 30% above 10,000 function points.
- Poor quality and low reliability after the software is delivered: > 5 bugs per FP.
- Breach of contract litigation against software outsource vendors.
- Expensive maintenance and enhancement costs after delivery.
These are endemic problems for software executives, software engineers and software customers but they are not insurmountable. In Software Development Patterns and Antipatterns, software engineering and metrics pioneer Capers Jones presents technical solutions for all seven. The solutions involve moving from harmful patterns of software development to effective patterns of software development.
The first section of the book examines common software development problems that have been observed in many companies and government agencies. The data on the problems comes from consulting studies, breach of contract lawsuits, and the literature on major software failures. This section considers the factors involved with cost overruns, schedule delays, canceled projects, poor quality, and expensive maintenance after deployment.
The second section shows patterns that lead to software success. The data comes from actual companies. The section’s first chapter on Corporate Software Risk Reduction in a Fortune 500 company was based on a major telecom company whose CEO was troubled by repeated software failures. The other chapters in this section deal with methods of achieving excellence, as well as measures that can prove excellence to C-level executives, and with continuing excellence through the maintenance cycle as well as for software development.
