y may be off from reality by a wide margin. (Source: Agere Systems) 4. Two classic textbooks on the subject are Software Engineering Economics by Barry W. Boehm, (Upper Saddle River, New Jersey: Prentice-Hall, 1982) and Software Cost Estimation with COCOMO II by Barry W. Boehm et. al. (Upper Saddle River, Jersey: Prentice-Hall, 2000). Software engineers for 20+ years have been using the COCOMO model to make financial decisions, set project budgets and schedules, negotiate tradeoffs, plan to maintain or upgrade legacy products, and decide where to imple- ment process improvement. The model accepts estimates of either logical lines of code or function points as the primary input parameter. One can also find in this source an implementation of the COCOMO model as well as coverage of emerging extensions such as object point data, application point data, the phase schedule and effort model (COPSEMO), dynamic COCOMO, the schedule estimation model (CORADMO), the commercial-off-the-shelfintegration model (COCOTS), the quality estimation model (COQUALMO), and the productivity estimation model (COPROMO). 5. Modeling results and methodology were discussed in depth between the originators of this work and the author over a series of documented private communications in November 2002. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website. SYSTEMS ENGINEERING ISSUES NETWORK PROCESSORS (a) Lifetime development cost in $ million (40x reduction) (b) Development interval in months (3x improvement) (c) Data-plane SW-related field-defect liability in $ million Coding done in FPL (24x improvement) Coding based on traditional C and micro-coding FIGURE 16.2 IP/MPLS router-based NPU software development cost comparison when coding in descriptive lan- guages such as Agere's FPL, ASL, and classical procedural coding in C (Source: Agere Systems) Figure 16.2 illustrates some 