• Complain

Capers Jones - Software Development Patterns and Antipatterns

Here you can read online Capers Jones - Software Development Patterns and Antipatterns full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2021, publisher: Auerbach Publications, genre: Business. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

No cover
  • Book:
    Software Development Patterns and Antipatterns
  • Author:
  • Publisher:
    Auerbach Publications
  • Genre:
  • Year:
    2021
  • Rating:
    4 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 80
    • 1
    • 2
    • 3
    • 4
    • 5

Software Development Patterns and Antipatterns: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Software Development Patterns and Antipatterns" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Software development has been a troubling since it first started. There are seven chronic problems that have plagued it from the beginning:


  1. Incomplete and ambiguous user requirements that grow by >2% per month.

  2. Major cost and schedule overruns for large applications > 35% higher than planned.

  3. Low defect removal efficiency (DRE) < 85% on large systems.

  4. Cancelled projects that are not completed: > 30% above 10,000 function points.

  5. Poor quality and low reliability after the software is delivered: > 5 bugs per FP.

  6. Breach of contract litigation against software outsource vendors.

  7. 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 sections 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.

Capers Jones: author's other books


Who wrote Software Development Patterns and Antipatterns? Find out the surname, the name of the author of the book and a list of all author's works by series.

Software Development Patterns and Antipatterns — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Software Development Patterns and Antipatterns" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make

This is my 22nd book. As always thanks to my wife Eileen for supporting my book writing over many years.

This book is dedicated to Watts Humphrey who was a pioneer in software quality control and effective development patterns. Watts worked at IBM and then helped create the software assessment program and the capability maturity model (CMMI) for the Software Engineering Institute (SEI). Watts was an industry leader in moving organizations from harmful patterns to effective patterns.

Thanks also to the faculty of the University of Florida and to my colleagues at IBM.

Chapter 1 Challenges of Software Project Management Project management in - photo 1
Chapter 1
Challenges of Software Project Management

Project management in every industry is a challenging occupation. But the challenges and hazards of software project management are greater than those of most other industries. This fact is proven by the large number of software project cancellations and the high frequency of software project cost and schedule overruns. Software projects run late and exceed their budgets more than any other modern industry except for defense projects.

Academic training for software project managers is still not very good even today. Some technology companies have recognized the challenges of software project management and created effective in-house training for new software project managers. These companies with effective software project management training include IBM and a number of telecom companies such as AT&T, ITT, Motorola, Siemens, and GTE. Some other technology companies such as Google, Microsoft, and Apple also have effective software project management training. Many of the companies with good software management training build complex physical devices run by software. Most are also more than 75 years old and have had software measurement programs for more than 50 years.

A few companies even offer market effective software project management training. One of these is a subsidiary of Computer Aid Inc. called the Information Technology Metrics and Productivity Institute (ITMPI). The non-profit Project Management Institute (PMI) also offers effective training for software project managers.

Several years ago, a survey of engineering technology company CEOs (computers, Telecom, electronics, medical devices, autos, and aircraft) found that they regarded their software organizations as the least professional of any of the corporate engineering organizations. This was due to the fact that software projects had higher cancellation rates, longer schedule delays, and higher cost overruns than any of the other engineering organizations.

Lyman Hamilton, a former Chairman of the ITT Corporation, gave an internal speech to ITT executives in which he mentioned that newly hired software engineers just out of college needed about 3 years of internal training before being entrusted with critical projects. Other kinds of engineers such as mechanical and electrical engineers only needed about 12 months of internal training.

Hamilton was troubled by several major software failures of projects that were terminated without being completed. He was also troubled by the dissatisfaction expressed by customers in the quality of the software the corporation produced. He was further dissatisfied by the inability of internal software executives to explain why the problems occurred and what might be done to eliminate them.

It is interesting that the failing projects were all large systems in the 10,000 function point size range. Failures in this range are common, and managerial problems are usually a key factor.

Problems, failures, and litigation are directly proportional to the overall size of software applications measured using function point metrics. shows the approximate distribution of software project results circa 2020.

Table 1.1 Normal Software Results Based on Application Size Circa 2020
Size in Function PointsNote: Costs Are Based on $10,000 per Month
Schedule in Calendar MonthsTotal StaffingProductivity in Function Points per Staff MonthCost in U.S. DollarsOdds of Project FailureOdds of Outsource Litigation
10.02150.00$2000.10%0.00%
100.40125.00$4,0001.00%0.01%
1003.50214.29$70,0002.50%0.25%
1,00015.00611.11$900,00011.00%1.20%
10,00035.00505.71$17,500,00031.00%7.50%
100,00060.005752.90$345,000,00047.50%23.00%

As can be seen from , large software projects are distressingly troublesome and have frequent total failures, also a high risk of litigation. Poor project management is a key contributing factor.

Some leading companies have recognized the difficulty of successful software project management and taken active steps to improve the situation. Some of these companies include IBM, AT&T, ITT, Motorola, GTE, and Siemens. Google, Apple, and Microsoft have also attempted to improve software management although Microsoft has perhaps been too rigid in some management topics such as employee appraisals.

The companies that are most proactive in software project management tend to build complex engineered products such as computers, medical devices, aircraft controls, and switching systems that depend upon software to operate. The companies also tend to be mature companies founded over 75 years ago and having effective software measurement programs that are more than 40 years old. Most were early adapters of function point metrics and also early adapters of parametric software estimation tools.

The software benchmarks studies carried out by Namcook Analytics LLC often show a significant number of serious software project management problems and issues. summarizes 41 problems noted in a benchmark study for a Fortune 500 technology corporation.

Table 1.2 Corporate Software Risk Factors Found by a Corporate Benchmark Study
1Project management: no formal training for new managers
2Project management: no annual benchmark studies
3Project management: no annual training in state of the art methods
4Project management: no training in software cost estimating
5Project management: no training in software quality estimating
6Project management: no training in software risk analysis
7Project management: no training in cyber-attack deterrence
8Project management: no training in function point metrics
9Project management: no training in schedule planning
10Project management: lack of accurate productivity measurements
11Project management: lack of accurate quality metrics
12Project management: incomplete milestone and progress tracking
13Project management: historical data leaks by over 50%
14Project management: managers continue to use inaccurate manual estimates
15Project management: no widespread use of accurate parametric estimation
16Quality control: no use of requirements models or QFD
17Quality control: no use of automated proofs for critical features
Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Software Development Patterns and Antipatterns»

Look at similar books to Software Development Patterns and Antipatterns. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Software Development Patterns and Antipatterns»

Discussion, reviews of the book Software Development Patterns and Antipatterns and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.