1. Working Group Meeting (Outbrief) Ricardo Valerdi, Indrajeet Dixit, Garry Roedler [rvalerdi@mit.edu] [idixit@usc.edu] [garry.j.roedler@lmco.com] Tuesday February 13, 2007 Los Angeles, CA CSSE Annual Research Review

2. Yesterday’s Agenda 1:00 Update on recent work Recent myths • "why can't we all just get along?“ • Pronunciation • Interfaces • Function points Results from November survey COSYSMO Risk module 2:30 <<BREAK>> 3:00 Continuity in systems engineering SystemStar update 5:00 adjourn

3. Attendees (25) Ali Nikolai (SAIC) Cindy Nikolai (US AF/Notre Dame) Barbara Park (Boeing) Shawn Rahani (Boeing) Karen Richardson (Aerospace Corp) Scott Rigby (Raytheon) Garry Roedler (Lockheed Martin) Howard Schimmoller (Lockheed Martin) George Stratton (Raytheon) Gary Thomas (Raytheon) Richard Turner (SSCI) Gan Wang (BAE Systems) Da Yang (USC) Barry Boehm (USC) Jim Cain (BAE Systems) Robert Culbertson (Cisco) Indrajeet Dixit (USC) Madeline Ellis (Boeing) Allan Fong (MIT) Gary Hafen (Lockheed Martin) Ray Hunnicutt (Lockheed Martin) Tony Jordano (SAIC) Jim Lambert (Cisco) Dan Ligett (SoftStar Systems) Miles Nesman (Boeing) RED = attended a previous workshop

4. Recent Work • Valerdi, R., Gaffney, J., Roedler, G., Rieff, J., “Extensions of COSYSMO to Represent Reuse,” 21st Forum on COCOMO and Software Cost Modeling, November 2006. • Valerdi, R., Gaffney, J., “Reducing Risk and Uncertainty in COSYSMO Size and Cost Drivers: Some Techniques for Enhancing Accuracy,” Conference on Systems Engineering Research, April 2007. • Valerdi, R., Rieff, J., Roedler, G., Wheaton, M., Wang, G., “Lessons Learned from Industrial Validation of COSYSMO,” INCOSE Symposium 2007. • Boehm, B., Valerdi, R., Honour, E., “The ROI of Systems Engineering: Some Quantitative Results,” INCOSE Symposium 2007. • Valerdi, R., Miller, C., “From Research to Reality: Making COSYSMO A Trusted Estimation Tool In Your Organization,” INCOSE Symposium 2007. (plus tutorial) • Valerdi, R., “Cognitive Limits of Software Cost Estimation,” submitted to Empirical Software Engineering and Measurement, 2007. • Valerdi, R., academicCOSYSMO User Manual v1.0, MIT Technical Report, July 2006. • Valerdi, R., Systems Engineering Cost Estimation with COSYSMO, in progress. www.valerdi.com/cosysmo

5. Conceptualize and Develop Conceptualize, Develop, and OT&E Conceptualize Practitioners Students

6. COSYSMO = 100 PM Historical data = 110 PM COSYSMO = 1,000 PM Historical data = 1,100 PM Practitioners COSYSMO = 100 PM Historical data = 110 PM COSYSMO = 1,000 PM Historical data = 1,100 PM Students

7. Results from November Survey

8. Personnel/team capability Basic intellectual capability of a Systems Engineer (compared to the national pool of SEs) to analyze complex problems and synthesize solutions. Personnel experience/continuity The applicability and consistency of the staff at the initial stage of the project with respect to the domain, customer, user, technology, tools, etc.

9. Two key questions • What inhibits the continuity of a systems engineer? • What facilitates the continuity of a systems engineer?

10. Key Points • Communication Problems • Geographical Location • Project/System Preference • Domain Expertise • Small vs. Big Organizations • Continuity is a double edged sword • Personnel criteria should not be “personal”, but instead needs to be “team”

11. Upcoming Events • COSYSMO knowledge exchange event • Tuesday March 6, 2007 (Cambridge, MA) • COSYSMO Adoption tutorial • week of June 25, 2007 (San Diego, CA) • COSYSMO workshop • week of October 22, 2007 (Los Angeles, CA) • Possibly week of October 29, 2007?