One Function Point (125 C Statements) Project Management Tools and Software Failures and Successes

S oftware development is a troubling technology. Software is highly labor-intensive, and as a result, large software projects are among the most expensive undertakings of the 20th century. Large software systems cost far more to build and take much longer to construct than the office buildings occupied by the companies that have commissioned the software. Extremely large software systems in the 100,000 function point size range can cost more than building a domed football stadium, a 50-story skyscraper, or a 70,000-ton cruise ship. Consider what the phrase " large systems " means in the context of six different size plateaus separated by an order of magnitude for each plateau. Size is expressed in terms of function points, a widely used synthetic metric based on five external attibutes of software applications: inputs, outputs, inquiries, logical files, and interfaces. The average number of C statements found within the typical function point is provided as a point of reference. There are few software applications of this size except small enhancements to larger applications or minor personal applications. The schedules for such small programs are usually only from a day to perhaps a week. This is the typical size of end-user applications and also a tremendously frequent size plateau for enhancements to existing software. Development schedules are usually less than one month. This size is heavily populated with enhancements to existing applications. It is also the practical upper limit of end-user applications. There are few stand-alone applications of this size in 1998, but 10 years ago there were a number of DOS applications in this size range, such as early BASIC interpreters. However, there are many features of larger applications that approximate this size. Development schedules are usually less than six months. Individual programmers can handle applications of this size, although technical writers and other specialists may be involved, too. This size range exceeds the capabilities of end-user development. This is a fairly common entry-level size range for many commercial and internal Windows software applications. It is also a common size range for in-house client-server applications. Schedules for software projects of this size are usually longer than 12 months. In this size range, the volume of specifications and user documentation becomes a significant contributor to software costs. Quality control also is a major requirement at this size range. Applications of this size range require development teams of up to 10 staff members, since individual …