1 of 12

Towards Estimating Schedule for COSYSMO:�A Workshop

2023 BCSSE & PSM Forum

1

v5 of 11/14

Jim Alstad

Boehm Center for Systems and Software Engineering

Jim Alstad

310/344-0894

Alstad.home@computer.org

Boehm COCOMO Forum

Aerospace@Chantilly & Online

November 15, 2023 at 14:25 Eastern

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

2 of 12

Agenda

The Problem

  • Background
  • Comparison to Software Projects
  • What We Have: Valerdi & Wheaton provide hints
  • Jim tries an analysis

Workshop proper

  • Jim states issues

Appendix

Bibliography

2023 BCSSE & PSM Forum

2

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

3 of 12

Background: There’s No Schedule Estimation Model

  • COSYSMO (”COSYSMO 1.0”) was developed by Ricardo Valerdi in 2005 [1]. It is a cost model for systems engineering projects.
  • The most recent model is my COSYSMO 3.0 [2]; it includes the features of previously published models.
  • Neither of these (nor any other full COSYSMO model) includes a schedule estimation model.
    • But one would be useful.

2023 BCSSE & PSM Forum

3

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

4 of 12

Comparison to Software Projects

  •  

2023 BCSSE & PSM Forum

4

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

5 of 12

Valerdi & Wheaton’s “Staffing Profile Chart”

  • [3] includes this “staffing profile chart” as its Figure 2 “Systems Engineering Effort Profile”:

  • The horizontal axis must be time, divided into Life Cycle Process phases
  • The chart therefore may be interpreted as providing duration information

2023 BCSSE & PSM Forum

5

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

6 of 12

Analysis of Staffing Profile Chart

  • Two kinds of information displayed in the chart may perhaps be interpreted to provide duration information:
    • The width of each of the four ISO/IEC 15288 phases (duration information);
    • The shapes (height = staffing level, vs time) of each phase for each ANSI/EIA 632 fundamental process (staffing level over time information)
  • Unfortunately, the paper doesn’t explain how this potential duration information was determined
    • Perhaps some organization’s view of a “standard” systems engineering project?
    • Based on project experience?
  • At best, the chart by itself would only provide relative information (e.g., relative staffing levels)

2023 BCSSE & PSM Forum

6

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

7 of 12

An Important Caveat

  • The scope of this schedule model is “system engineering”
    • Not “the whole project”

2023 BCSSE & PSM Forum

7

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

8 of 12

Jim’s Notional Schedule Diagram

  • System Engineering effort for new development is expended in a mostly bimodal distribution, where during a Consult phase system engineers merely support other disciplines.

2023 BCSSE & PSM Forum

8

v5 of 11/14

Conceptualize; Develop

Operational Test & Evaluation; Transition to Operation

Consult

Time

Headcount

Example issues:

  • What duration is needed for Conceptualize + Develop? For OT&E + Transition? (These can be absolute, or %ages.) Alternatively, what average headcount?
  • How should effort be divided among the three phases?
  • What headcount is needed for Consulting? Zero?

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

9 of 12

Jim’s Notional Schedule Diagram (Expanded)

2023 BCSSE & PSM Forum

9

v5 of 11/14

Conceptualize; Develop

Operational Test & Evaluation; Transition to Operation

Consult

Time

Sys Eng

Headcount

Time

Subsys Eng

Headcount

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

10 of 12

Issues toward Determining a Schedule Estimator for Systems Engineering

  • Is there better information in the literature?
  • How can the Staffing Profile Chart be used to make a schedule estimator (partial or full)?
  • Is Jim’s concept of a Consult phase useful?
  • Could we get companies to provide us schedule information on projects?
    • With effort information

2023 BCSSE & PSM Forum

10

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

11 of 12

Appendix: More from [3]

  • This is extracted from Table 5 of [3]. Each row describes how the effort of that Fundamental Process is distributed across the Phases.

2023 BCSSE & PSM Forum

11

v5 of 11/14

Fundament. Process

Conceptu-alize

Develop

Operational Test & Eval

Transition to Operation

Acquistion & Supply

28%

51%

13%

8%

Technical Mgmt

22%

38%

25%

15%

System Design

34%

40%

17%

9%

Product Realization

13%

30%

32%

25%

Technical Evaluation

18%

27%

40%

15%

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction

12 of 12

Bibliography

  1. Valerdi, R. The Constructive Systems Engineering Cost Model. Los Angeles, CA: University of Southern California, 2005.
  2. Alstad, J.P., “Development of COSYSMO 3.0: An Extended, Unified Cost Estimating Model for Systems Engineering”, Procedia Computer Science 2019, pp 55-62.
  3. R.Valerdi, M.Wheaton, “ANSI/EIA632 As a Standard WBS for COSYSMO,” AIAA 1st Infotech@Aerospace Conference, Arlington, VA, September 2005.
  4. B. Boehm, et al, Software Cost Estimating with COCOMO®️ II, Prentice Hall, 2000

2023 BCSSE & PSM Forum

12

v5 of 11/14

Boehm CSSE

Center for Systems and Software Engineering

ESSE: Introduction