Estimation and Measurement Telecon, 2010-04-16

See Weekly Meeting Logistics for telecon information.

Previous telecon 2010-04-09

Next telecon 2010-04-23

Attendees

AndyBerner, AndrewCanham, ArthurRyman, LawrenceMandel

Regrets

LeeFischman

Minutes

1. Implementation Status - All

No progress to report.

2. Review of REST API Data Models - ArthurRyman

We reviewed the following domain entities, and some of the metric entities they reference:

ems:Scenario

AndrewCanham raised the requirement for estimators to be able to record in a clean way any additional assumptions they made for an estimate. A proposal to satisfy this requirement by allowing one scenario to extend another was agreed to. This has been implemented by the addition of the ems:extendsScenario property.

The review of this resource is DONE.

ems:Estimate

No issues raised. With the addition of extended scenarios, estimates should refer to the extended scenario if applicable, not the base scenario.

The review of this resource is DONE.

ems:Baseline

AndrewCanham objected to the current text in the specification that requires all estimates within a baseline to refer to the same scenario given that we now have extended scenarios. See the ems:estimate property. Two estimates may be generated from different, but compatible, extensions of the same base scenario.

This objection exposes the possibility in the current design that a baseline may adopt conflicting estimates. The resolution to this problem is to guidance to the specification.

ACTION: Use the mailing list to discuss allowing different, but compatible, scenarios, all extending a common base, and resolve this next telecon.

Comments

Add your comments here: