COCOMO-SCORM: Cost Estimation for SCORM Course Development

Slides:



Advertisements
Similar presentations
Software Cost Estimation
Advertisements

COST ESTIMATION TECHNIQUES AND COCOMO. Cost Estimation Techniques 1-)Algorithmic cost modelling 2-)Expert judgement 3-)Estimation by analogy 4)-Parkinsons.
SW Economics & COCOMO II November 25, 2005 Jongmoon Baik, Ph.D. School of Engineering Information and Communications University.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
March 2002 COSYSMO: COnstructive SYStems Engineering Cost MOdel Ricardo Valerdi USC Annual Research Review March 11, 2002.
CSCI COCOMO Tutorial1 CS “Tutorial” Presentation: Software Cost Estimation Tools – COCOMO II and COCOTS A Winsor Brown and Ye.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5.
University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
COCOMO II 資管研一 張永昌. Agenda Overall Model Definition COCOMO II Models for the Software Marketplace Sectors COCOMO II Model Rationale and Elaboration Development.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 Reuse and Maintenance Estimation Vu Nguyen March 17, 2009.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
©2011 Rolls-Royce plc The information in this document is the property of Rolls-Royce plc and may not be copied or communicated to a third party, or used.
April 27, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #3 Tuesday, April 27, 2004.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
Information System Economics Software Project Cost Estimation.
ESD web seminar1 ESD Web Seminar February 23, 2007 Ricardo Valerdi, Ph.D. Unification of systems and software engineering cost models.
By K Gopal Reddy.  Metrics in software are of two types.direct and indirect.  Function points as indirect metrics.  Function points are used to measure.
University of Southern California Center for Systems and Software Engineering Cost Estimation with COCOMO II Barry Boehm CS 510, Fall 2015 v3: Slide 10.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
10/27/20151Ian Sommerville.  Fundamentals of software measurement, costing and pricing  Software productivity assessment  The principles of the COCOMO.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
University of Southern California Center for Systems and Software Engineering (c) USC CSSECSCI 577a 2010 COCOMO + COCOTS Tutorial1 577a 2010.
Overview of COCOMO Reporter:Hui Zhang
University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
1 Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5 LiGuo Huang Computer Science and Engineering Southern Methodist University.
(8) Potential required for planning with management Top-Down Estimating Method: Top-down estimating method is also called Macro Model. Using it, estimation.
COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
THE FAMU-CIS ALUMNI SYSTEM
Project Cost Management
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Metrics and Terms SLOC (source lines of code)
Cost Estimation with COCOMO II
Tutorial: Software Cost Estimation Tools – COCOMO II and COCOTS
COCOMO II Overview CSCI 510 Fall 2013 (c) USC CSSE.
COCOMO II Overview Barry Boehm CSCI 510 Fall 2011 (c) USC CSSE
COCOMO II Overview Barry Boehm CSCI (c) USC CSSE 2018/9/19.
COCOMO II Overview A Winsor Brown (especially from page 50 on)
Constructive Cost Model
Pongtip Aroonvatanaporn CSCI 577b Spring 2011 March 25, 2011
COCOMO II Overview Ray Madachy CSCI 510
SLOC and Size Reporting
Cost Estimation with COCOMO II
Software Systems Cost Estimation
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
Cost Estimation with COCOMO II
COCOMO 2 COCOMO 81 was developed with the assumption that a waterfall process would be used and that all software would be developed from scratch. Since.
COCOMO II Overview LiGuo Huang Computer Science and Engineering
Chapter 23 Software Cost Estimation
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
COCOMO II: Airborne Radar System Example
COCOMO II Overview Marilee Wheaton CSCI 510.
COCOMO II: Airborne Radar System Example
Center for Software and Systems Engineering,
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Presentation transcript:

COCOMO-SCORM: Cost Estimation for SCORM Course Development Roger Smith & Kelly Ward SPARTA Inc. and Anteon Inc. rsmith@sparta.com and kward@anteon.com 07 March 2006

What is COCOMO? The Constructive Cost Model (COCOMO I) was first published in 1981 by Barry Boehm. Its ability to estimate software projects led to its almost universal adoption and continued research that led to the creation of COCOMO II in 1998. Since 1981, the COCOMO estimation method has been adapted to serve a number of different types of projects, e.g. Systems Engineering (COSYSMO) COTS Acquisition (COCOTS) Cost, Schedule, Quality Balance (COQUALMO) Rapid Application Development (CORADMO) Productivity Improvement (COPROMO) Lifecycle Costs (COPSEMO)

What is SCORM? Sharable Content Object Reference Model (SCORM) A standard for web-based E-learning. It defines how the individual instruction elements are combined on a technical level and sets conditions for the software needed for using the content. The standard uses XML and it is based on the results of work done by AICC, IMS, IEEE, and Ariadne. SCORM is a suite of technical standards that enable web-based learning systems to find, import, share, reuse, and export learning content in a standardized way. 

Project Description Create an interactive project estimation tool for ISD/SCORM content Algorithmic foundation for the tool is the COCOMO II algorithm developed for software projects by the research team at the University of Southern California and led by Barry Boehm ISD methodology estimated will be the ADDIE model developed at Florida State University and adopted by the U.S. Armed Services Resulting algorithm and tools will estimate the person-months required to create a SCORM conformant learning product Dollar costs can be derived outside of the model by applying industry standard or specific company labor rates

Current Estimation Methods Historical Bottom-up Top-down Industry standards For example, audience completes the top survey question Problems introduced: Conditions change – i.e. SCORM, new technologies

Different Approach Enumerate SCORM products and processes that contribute to the staffing and duration of a project Identify mathematic and logical relationships between these items Quantify the level of contribution of each item to project cost Define a bounded set of conditions under which the algorithm can be relied upon Validate the algorithm for various sets of data within the bounded conditions

Why Change? Consistent, objective, and reliable estimation tool for SCORM content and projects First step in formalizing an estimation method in the ADL community Create a tool that other projects can apply, modify, and mature COCOMO II has been evolving for 25 years. COCOMO-SCORM tool from this project will be the first step in the long evolution and improvement of a tool for this community

COCOMO II Tool Example User’s Perspective Quantitative Qualitative

COCOMO-SCORM Drivers (27 Input Variables) Size Source Lines of Code (SLOC) Design Modification (DM) Code Modification (CM) Integration (IM) Assessment (AA) Understanding (SU) Unfamiliarity (UNFAM) Scale Drivers Development Flexibility (FLEX) Process Maturity (PMAT) Precedentedness (PREC) Arch/Risk Resolution (RESL) Team Cohesion (TEAM) Product Effort Multipliers (EM) Required Reliability (RELY) Product Complexity (CPLX) Required Reuse (RUSE) Documentation (DOCU) Platform EM Platform Volatility (PVOL) Bandwidth (BAND) Personnel EM Senior Capability (SCAP) Developer Capability (DCAP) Personnel Continuity (PCON) Applications Experience (APEX) Platform Experience (PLEX) Development Tools Experience (DTEX) Project EM Lifecycle Tools (LIFE) Multisite Development (SITE) Required Development Schedule (SCED)

EM Effect on Project 15 Effort Multipliers Set to Nominal Extra High Nominal Very Low Course Hours Project Cost Project Cost = A * Course Hours (Person Months) (Constant) (Student Hours)

Answers Effect Project Cost 15 Effort Multipliers Other Than Nominal Project Cost Course Hours Nominal Cost Project Cost = A * EMi * Course Hours (Person Months) (Constant) (Modifiers) (Student Hours)

Range of Cost Variation Max = X 115 ? Course Hours Project Cost Flex From: X times larger to Y times smaller Min = Y 0.05 ?

COSCOMO Model Algorithm PM = A*(Size)E * PEMi 15 i=1 5 E = B + .01*PSFj j=1 Where: PM = effort in Person Months A = calibration constant derived from historical project data Size = Adjust Source Lines of Code E = represents diseconomy of scale (composed of 5 scale factors) EMi = effort multiplier for the ith cost driver. The geometric product results in an overall effort adjustment factor to the nominal effort. B = calibration constant derived from historical project data SFj = scale factor for the jth cost driver. Provides organization specific adjustments to the size of the project.

Join the Team Take the Survey (Provide Anteon Web Site for Survey) Contact us Roger.Smith@sparta.com or Kward@anteon.com Contact Joint ADL CoLab Bill.Pike@us.army.mil Leave Your Business Card Visit our Demo in the USDLA Pavilion (Time and Location for COSCOMO demo)