This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Estimation and Measurement Telecon, 2010-01-08

See Weekly Meeting Logistics for telecon information.

Previous telecon 2009-12-11

Next telecon 2010-01-15

Attendees

AndyBerner, ArthurRyman, LawrencePutnamJr, LeeFischman, ScottBosworth

Minutes

1. Implementation Status - ArthurRyman

ArthurRyman: Members of the Rational Project Conductor development team have started a prototype implementation of an EMS 1.0 service provider based on the Jazz Foundation Server in order to help validate our specification. A member of the Rational Financier development team has expressed interest in using the EMS 1.0 XML formats for probability distributions. Planning discussions for 2010 Rational PPM product content are underway now.

LawrencePutnamJr: My developers have two questions:

1) Should we be developing the service provider or consumer?

2) What does a user get from the integration - the ability to exchange WBS or just numerical metric estimates?

ArthurRyman:

1) The EMS 1.0 spec defines a service provider REST API and resource formats that enable the collaboration of the multiple tools that participate in estimation and measurement across the application development lifecycle. EMS 1.0 does not specify models for how estimates are generated or processes for how estimates are used. Other tools, e.g. software estimation, portfolio management, project management, performance management, etc. are responsible for generating and using estimates and measurements. Since multiple tools are involved, the EMS 1.0 specification has been written from the point of view that the EMS 1.0 API provides access to a common, shared respository of estimation and measurement resources, and that all the other tools consume EMS 1.0 services. However, any tool may directly implement the EMS 1.0 service provider API. The current thinking at Rational is that we will develop a common EMS 1.0 service provider implementation based on Jazz and will incorporate that into any product configuration that requires it. As an initial implementation step, software estimation tool vendors should implement clients that consume the EMS 1.0 services, especially the ability to create ems:Estimate resources.

2) The scenarios in the primer have only illustrated the interchange of numeric metric estimates. However, the interchange of WBS is also useful for project initiation and reestimation. Our alternatives for WBS formats are either to use MS Project 2007 XML, or to define a domain specific OSLC format that is aligned with software project estimation.

2. Primer Status - ArthurRyman

ArthurRyman reviewed Act 2. Estimation of the Monitoring and Controlling scenario.

LeeFischman: There may be too much detail on the calculation of the defect arrival rate estimate.

ArthurRyman: It's just there to for illustration, but it can be moved out if you feel it detracts from the presentation.

AndyBerner: What is the format of the measurement data returned when you GET the URI of the ems:observationSource property?

ArthurRyman: I'll give a concrete example in Act 3.

3. Software Metrics Definition Status - LawrencePutnamJr

LeeFischman: I completed my Action to describe linear calibration.

4. Other Business

Comments

Add your comments here:

 
Topic revision: r3 - 08 Jan 2010 - 19:36:42 - ArthurRyman
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback