Model Rationale
The Constructive Rapid Application Development model has its roots in the results of a 1997 CSE Focused Workshop on Rapid Application Development. RAD refers to an application of any of a number of techniques or strategies to reduce software development cycle time. The six classes of strategies whose degree of implementation can be used to parameterize a schedule estimate given an effort estimate produced by COCOMO II.2000 are the following: Development Process Re-engineering (DPRS), Rapid Prototyping (RPRO), Collaboration efficiency (CLAB), Architecture and risk resolution (RESL), Pre-Positioning of assets (PPOS), RAD Capability of Personnel (RCAP). RESL corresponds to the COCOMO II scale driver; the other five are new. All have their effects reflected as multipliers on effort, schedule, number of personnel. In some cases, the person-months of effort can actually be increased because certain pro-active strategies, like pre-positioning of assets, are only possible with extra effort.
The intent of the Constructive Application Develpment Model is to calculate/predict the schedule (months, M), personnel (P), and adjusted effort (person-months, PM) based on the distribution of effort and schedule to the various stages, and impacts of the selected schedule driver ratings on the M, P, and PM of each stage.
Model Description
The Constructive Application Develpment Model model utilizes a new COCOMO II extension that allocates effort and schedule to the stages, which are anchored at points in a development life cycle. The anchor points are Life Cycle Objectives(LCO), Life Cycle Architecture(LCA), and Initial Operational Capability(IOC).
Click image to enlarge chart.
A phased schedule and effort distribution is needed because the effects of the RAD strategies identified above are different for the different stages. Also, a new mathematical function is used to calculate (predict) the calendar months for a given amount of effort: the function is only radically different in low (under 16) person-month's efforts where it seems more normal have an equal number of people and months to accomplish the task. At the higher (greater than 120) person-month's efforts, the traditional COCOMO II.2000 function is used which is based on the traditional cube-root-like function of effort. A smooth curve is fit within these ranges.
CORADMO also allows the specification of the number of work hours per person-month.
Papers, Reports, and Presentations
Papers:
- "Software Cost Estimation with Cocomo II" - Chapter 5
- Authors: Barry W. Boehm, Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J. Reifer, Bert Steece
- Englewood Cliffs, NJ:Prentice-Hall, 2000
Reports:
- "CORADMO Summary"
- Author: A. Winsor Brown
- 1998
- PDF format
- "CORADMO and COSSEMO Driver Determination Worksheet"
- Author: A. Winsor Brown
- 1998
- PDF format
Presentations:
- ISPA 2002, May 2002 - "USC CORADMO.2001: A Software Cost Model Implementation for RAD"
- Authors: Cyrus Fakharzadeh, Barry Boehm, A. Winsor Brown
- PDF format
- 2001 International Forum on COCOMO and Software Cost Modeling 16 - "CORADMO in 2001: A RAD Odyssey"
- Author: Cyrus Fakharzadeh
- PDF format
- ISPA/SCEA 2001 - "CORADMO: A Software Cost Estimation Model for RAD Projects"
- Authors: Cyrus Fakharzadeh, Barry Boehm
- PDF format
- 2001 USC-CSE Annual Research Review - "CORADMO Update"
- Author: Cyrus Fakharzadeh
- PDF format
- 2000 COCOMO and Software Cost Modeling International Forum 15 - "CORADMO Update"
- Author: Cyrus Fakharzadeh
- PDF format
- 1999 USC-CSE Annual Research Review - "CORADMO - Constructive Rapid Application Development Model"
- Author: Cyrus Fakharzadeh
- PDF format
- 1998 COCOMO and Software Cost Modeling International Forum 13 - "CORADMO"
- Author: A. Winsor Brown
- PDF format
Model Status
Currently, a Microsoft Excel implementation of CORADMO has been developed that includes a zip file with brief instuctions on use.
Please email A. Winsor Brown for the newest version of CORADMO.
Data Collection Program
The key factor is continuing to improve the predictive accuracy of CORADMO is good data. To that end, we are asking for the help of the software industry in collecting data. If you or the organization you work for has the ability to supply software development project data, we would like to hear from you. The benefit to you for participating in data collection will be the availability of a more accurate predictive model for estimating your software project costs. Additionally, you will have the opportunity to participate in the CORADMO oriented workshops being planned at USC, and to receive calibrated versions of the implemented model before the general public.
For your convenience, we are providing below the standard data nondisclosure agreement USC-CSSE enters into with most of our data suppliers.
For further information or to discuss participation in the CORADMO data collection program, please contact us.
Data Collection Documents:
- CORADMO Data Gathering Questionnaire
- PDF format
- CORADMO Delphi Exercise
- PDF format
- USC-CSSE Data Nondisclosure Agreement
- HTML format
- PDF format
Research Group
- Dr. Barry W. Boehm
- Mr. A. Winsor Brown
Research Sponsors
Primary funding and technical support of the development of CORADMO has been provided by the USC-CSSE Affiliates. We would like to take this opportunity to acknowledge their generous assistance, without whose help the development of CORADMO would have been impossible.
Cost Estimation Bibliography
For an extensive bibliography of software cost estimation related papers and books go here.
For Further Information Please Contact:
Copyright 1995-2009 The University of Southern California
The written material, text, graphics, and software available on this page and all related pages may be copied, used, and distributed freely as long as the University of Southern California as the source of the material, text, graphics or software is always clearly indicated and such acknowledgement always accompanies any reuse or redistribution of the material, text, graphics or software; also permission to use the material,text, graphics or software on these pages does not include the right to repackage the material, text, graphics or software in any form or manner and then claim exclusive proprietary ownership of it as part of a commercial offering of services or as part of a commercially offered product.
