Delphi and COCOMO are techniques used for estimating:

CONCEPT: Software estimation techniques predict, before or during project planning, the effort (person-months), time, and cost needed to build a software system. Broadly two families exist: expert-judgment methods (e.g., the Delphi technique, where a panel of experts iteratively and anonymously converges on a consensus estimate) and algorithmic/model-based methods (e.g., COCOMO -- the COnstructive COst MOdel -- which computes effort and schedule from an estimated program size).

APPLICATION: Both Delphi and COCOMO exist to answer the same planning question -- how much effort, time, and money it will take to develop this software. Delphi supplies that estimate via structured expert consensus; COCOMO supplies it via a regression-based formula. So both are, at their core, software development cost/effort estimation techniques.

CROSS-CHECK: The other properties belong to different techniques entirely:

• Software size (lines of code or function points) is a measured INPUT fed into COCOMO's formula -- it is not the quantity Delphi or COCOMO themselves are used to estimate.

• Software reliability is judged with reliability-growth or defect-prediction models, unrelated to Delphi/COCOMO.

• Software complexity is quantified with metrics such as cyclomatic complexity or Halstead measures -- again a different concern.

So the correct answer is: Software development cost.