26 October 2001 DRAFT 1

COSYSMO: Constructive Systems Engineering Cost Model

USC CSC Workshop

25-26 October 2001

USC

C S E University of Southern CaliforniaCenter for Software Engineering

26 October 2001 DRAFT 2

Participants• Elliot Axelband, USC

• Kim Bell, Aerospace

• Joe Betser, Aerospace

• Barry Boehm, USC

• Linda Brooks, TRW

• Gary Hafen, LMCO

• Cheryl Jones, US Army

• Tony Jordano, SAIC

• Dan Ligett, Softstar

• Ray Kile, CSM• Karen Lum, JPL• Karen Owens,

Aerospace• Don Reifer, USC• Gary Thomas, Raytheon• Ariel Tonnu, US Air

Force• Ricardo Valerdi, USC• Marilee Wheaton, TRW

USC

C S E University of Southern CaliforniaCenter for Software Engineering

26 October 2001 DRAFT 3

Agenda• Introductions

• Goals of effort

• Review of previous work and contributions

• Agreement on scope and approach

• Proposed plan of action and milestones

• Assignment of responsibilities

• Summary and conclusions

USC

C S E University of Southern CaliforniaCenter for Software Engineering

26 October 2001 DRAFT 4

Goals of Effort• Build a COCOMO-like model for estimating

system engineering resources– Member of the COCOMO family of models

• COSYSMO (Constructive System Engineering Model) fills in the holes not covered by COCOMO II

USC

C S E University of Southern CaliforniaCenter for Software Engineering

Inception Elaboration Construction Transition

26 October 2001 DRAFT 5

Scope and Approach

USC

C S E University of Southern CaliforniaCenter for Software Engineering

COSYSMOSize

CostDrivers

Effort

Duration

Calibration

# Requirements# Interfaces# TPM’s# Scenarios# Modes# Platforms# Algorithms

- Application factors-7 factors

- Team factors-8 factors

WBS guidedBy EIA 632

26 October 2001 DRAFT 6

Agreements• Use USC seven step model building process• Keep things simple

– Start with Inception phase first– Use EIA 632 to bound effort– Focus on software intensive systems

• Build on previous work• Shoot for having something meaningful done by

mid-March 2002– Much of the work done by volunteers, so must be

conservative in estimates

USC

C S E University of Southern CaliforniaCenter for Software Engineering

26 October 2001 DRAFT 7

Plan of Action & Milestones

USC

C S E University of Southern CaliforniaCenter for Software Engineering

TaskTask Due DateDue Date Responsible*Responsible*1. Develop reference system 11//01/01 Reifer/Valerdi2. Define cost drivers 11/16/01 Wheaton/Valerdi3. Define size drivers 11/16/01 Hafen/Thomas4. Define effort scope 11/16/01 Hafen/Thomas5. Finalize survey instrument 11/30/01 Thomas/Valerdi6. Send materials out for review 12/03/01 All focal points7. Hold net meeting/discuss results 12/11/01 All focal points8. Updates done/Delphi defined 01/14/02 Reifer/Valerdi9. Send Delphi out 01/15/02 All focal points10. Complete Delphi round 02/15/02 Reifer/Valerdi11. Update done based on results 03/05/02 Reifer/Valerdi12. Present results at annual review 03/12/02 Valerdi

* Axelband/Boehm involved in all activities

26 October 2001 DRAFT 8

Summary and Conclusions

• Had a productive meeting

• Everyone contributed

• Plan of action and milestones defined

• Looking forward to results

USC

C S E University of Southern CaliforniaCenter for Software Engineering

Thanks to our group for a job well done