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, 2009-10-16


See Weekly Meeting Logistics for telecon information.

Attendees

ArthurRyman, LawrencePutnamJr, LeeFischman, ScottBosworth, TackTong

Regrets

AndyBerner

Minutes

1. OSLC Reporting Workgroup - TackTong

TackTong described the newly formed Reporting workgroup and invited participation.

2. Alternative XML Format for Fact Tables - SteveAbrams

SteveAbrams was absent. This item will be removed from the agenda. We will revise the XML formats of all resources after we get some implementation feedback.

3. Software Estimation Use Cases Status - LawrencePutnamJr

LawrencePutnamJr reported that this document has been updated. The workgroup has declared the Draft done.

ScottBosworth explained the lifecycle of OSLC specification: Scoping, Draft, Convergence, and Finalization. We need to complete all of our specs before entering the Convergence phase.

4. Primer Status - ArthurRyman

ArthurRyman reviewed the updated structure of the Primer. Each scenario will be divided into acts in order to avoid very long wiki pages. This has been done for the Initiating scenario.

ArthurRyman also reviewed the revised REST API architecture. The EMS 1.0 service has several resource types, e.g. Project, Scenario. Each resource type can be created or listed using an associated List resource, e.g. ProjectList, ScenarioList. All of the List URIs are given in a Service document that describes the whole EMS 1.0 service. All resources are modelled using RDF.

The scope of a resource for the purpose of versions is limited to its immediate properties, i.e. if an immediate property is modified then a new version of the resource is created in the sense that its HTTP ETag will change. The properties will be very lean, e.g. a Scenario will refer to its Project, but the Project will only indirectly refer to its Scenario's via a query on the ScenarioList resource, filtered for the given Project. We will include immutable helper query URIs in, e.g. the Project resource, to list its related collections of other resources. Creating a new resource modifies its associated List resource, but not any other resources referenced by the new resource.

5. Other Business

We need to define URIs for the most important standard metrics. LawrencePutnamJr will act as editor of the Software Metrics Definitions spec. We will add to this list of metrics after we get implementation feedback.

Comments

Add your comments here:

 
Topic revision: r4 - 03 Mar 2010 - 19:38:01 - 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