Software Development Patterns and Antipatterns (Record no. 2949)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 02873 a2200361 4500 |
| 001 - CONTROL NUMBER | |
| control field | 1032017228 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20250317100416.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 250312042021xx 2 eng |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9781032017228 |
| 037 ## - SOURCE OF ACQUISITION | |
| Source of stock number/acquisition | Taylor & Francis |
| Terms of availability | GBP 48.99 |
| Form of issue | BB |
| 040 ## - CATALOGING SOURCE | |
| Original cataloging agency | 01 |
| 041 ## - LANGUAGE CODE | |
| Language code of text/sound track or separate title | eng |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UY |
| Source | thema |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UMZ |
| Source | thema |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UMX |
| Source | thema |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UB |
| Source | thema |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UY |
| Source | bic |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UMZ |
| Source | bic |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UMX |
| Source | bic |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | UB |
| Source | bic |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | COM051230 |
| Source | bisac |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | COM051010 |
| Source | bisac |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | COM051430 |
| Source | bisac |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | COM032000 |
| Source | bisac |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | MAT000000 |
| Source | bisac |
| 072 7# - SUBJECT CATEGORY CODE | |
| Subject category code | 005.1 |
| Source | bisac |
| 100 1# - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Capers Jones |
| 245 10 - TITLE STATEMENT | |
| Title | Software Development Patterns and Antipatterns |
| 250 ## - EDITION STATEMENT | |
| Edition statement | 1 |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. | |
| Name of publisher, distributor, etc. | Auerbach Publications |
| Date of publication, distribution, etc. | 20210827 |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 492 p |
| 520 ## - SUMMARY, ETC. | |
| Expansion of summary note | 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. |
No items available.