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
.
TWiki
>
Main Web
>
PmHome
>
MetricsHome
>
MetricsMeetings
>
MetricsMeeting20091016
(03 Mar 2010,
ArthurRyman
)
(raw view)
---+ Estimation and Measurement Telecon, 2009-10-16 <br />%TOC% See [[MetricsMeetings#Weekly_Meeting_Logistics][Weekly Meeting Logistics]] for telecon information. ---++ Attendees ArthurRyman, LawrencePutnamJr, LeeFischman, ScottBosworth, TackTong ---+++ Regrets AndyBerner ---++ Minutes ---+++ 1. [[ReportingHome][OSLC Reporting Workgroup]] - TackTong TackTong described the newly formed [[ReportingHome][Reporting]] workgroup and invited participation. ---+++ 2. Alternative XML Format for [[MetricsEmsFactTable][ !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. [[MetricsUseCases][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. [[MetricsEMS10Primer][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 [[MetricsEMS10PrimerInitiating][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://en.wikipedia.org/wiki/HTTP_ETag][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 [[MetricsDefinitions][Software Metrics Definitions]] spec. We will add to this list of metrics after we get implementation feedback. ---++ Comments Add your comments here: %COMMENT%
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r4 - 03 Mar 2010 - 19:38:01 -
ArthurRyman
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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