1. COSYSMO: Constructive Systems Engineering Cost Model Ricardo Valerdi USC CSE Workshop October 25, 2001

2. Outline COSYSMO The Challenge EIA632 Proposed Approach Data Output/Milestones Q & A COSYSMO

3. What is it? The purpose of COSYSMO is to enhance the current capability of the COCOMO II model by accounting for costs that are outside the realm of software engineering by introducing system engineering drivers. COSYSMO

4. The Challenge To develop a preliminary model for estimating the cost impact of front- end System Engineering tasks in the design of software intensive systems. These include system definition, integration, and test activities as defined in EIA632. COSYSMO

5. EIA632 33 requirements organized into 5 groups: 1.Acquisition and supply 2.Technical management Planning process Assessment process Control process 3.System design Requirements definition process Solution definition process 4.Product realization 5.Technical evaluation COSYSMO

6. Proposed Approach Begin with Increment I: front-end costs of information systems engineering Follow 7-step modeling methodology –Steps 5,6, & 7 (gather data and refine loop) Use model parameters compiled by TRW, SAIC, Raytheon, and USC/CSE –System size (functional reqs, TPMs, SIT) –Effort drivers (maturity, cohesion, stability) INCOSE/FAA, Rational COSYSMO

7. Proposed Approach (cont) Develop preliminary model using data from real projects that have been completed (2 or 3) Test the model on other projects that have been completed (2 or 3) COSYSMO

8. Data Need to find 4 to 6 projects that have been completed in order to build and test the model They can differ in size, scope Any volunteers? COSYSMO

9. Output/Milestones Findings will be presented in the form of a report or white paper Half of the work to be done prior to December, other half to be done prior to March Don Greenlee from SAIC/INCOSE in San Diego has volunteered to participate COSYSMO

10. Q & A Is this the right direction? Where can I get data? What are some resources? COSYSMO