- .W. BOEHM INTRODUCED COCOMO MODEL IN HIS BOOK SOFTWARE ENGINEERING ECONOMICS IN 1981 CO VERIFICATION
- .W. BOEHM INTRODUCED COCOMO MODEL IN HIS BOOK SOFTWARE ENGINEERING ECONOMICS IN 1981 CO SOFTWARE
In addition, this issue is a core concern in the Defense Science Board (DSB), September 2007, Report of the Defense Science Board Task Force on Mission Impact of Foreign Influence on DoD Software, Washington, DC: Office of the Undersecretary of Defense for Acquisition, Technology, and Logistics, at pp. The challenges relating to assurance were highlighted by several briefers to the committee.
.W. BOEHM INTRODUCED COCOMO MODEL IN HIS BOOK SOFTWARE ENGINEERING ECONOMICS IN 1981 CO SOFTWARE
(COCOMO II, or constructive cost model II, is a software cost, effort, and schedule estimation model.) This analysis suggests that improvements are needed in up-front areas as well as in testing and supporting the importance of architecture research, especially for ultra-large systems. In Balancing Agility and Discipline (Addison-Wesley, 2004), Barry Boehm and Richard Turner provide an analysis of the COCOMO II Architecture and Risk Resolution scale factor, indicating that the increase in rework due to poor architecture and risk resolution is roughly 18 percent for typical 10-KSLOC (KSLOC stands for thousand software lines of code) projects and roughly 91 percent for typical 10,000-KSLOC projects.
![.w. boehm introduced cocomo model in his book software engineering economics in 1981 co .w. boehm introduced cocomo model in his book software engineering economics in 1981 co](https://docplayer.net/docs-images/46/21350399/images/page_2.jpg)
Clark, Ellis Horowitz, Ray Madachy, Donald Reifer, and Bert Steece indicate that the cost of test planning and running tests is typically 20 to 30 percent plus rework due to defects discovered.
![.w. boehm introduced cocomo model in his book software engineering economics in 1981 co .w. boehm introduced cocomo model in his book software engineering economics in 1981 co](https://www.coursehero.com/thumb/1b/a6/1ba664599cb185b0eed486608c2be4978ee6b2fb_180.jpg)
Winsor Brown, Sunita Chulani, Bradford K. In Software Cost Estimation with COCOMO II (Prentice Hall, 2000), Barry W.
![.w. boehm introduced cocomo model in his book software engineering economics in 1981 co .w. boehm introduced cocomo model in his book software engineering economics in 1981 co](https://www.coursehero.com/thumb/ba/7e/ba7e782a366a4a9d0e3ed7e87f74b2b891c8f946_180.jpg)
.W. BOEHM INTRODUCED COCOMO MODEL IN HIS BOOK SOFTWARE ENGINEERING ECONOMICS IN 1981 CO VERIFICATION
Santhanam say, “In a typical commercial development organization, the cost of providing this assurance via appropriate debugging, testing, and verification activities can easily range from 50 to 75 percent of the total development cost.” In Estimating Software Costs (McGraw-Hill, 1998), Capers Jones provides a table relating percentage of defects removed to percentage of development effort devoted to testing, with data points that include 90 to 39 percent, 96 to 48 percent, and 99.9 to 58 percent. In “Software Debugging, Testing, and Verification,” IBM Systems Journal (41)1, 2002, B.