PMI workshop 200609

PMI workshop 200609

Location: Mandriva
Date: 5 September 2006, 14h30-17h

Objectives

• Current status of the PMI
• Methodology
• Next steps
• Cross workpackage dissemination
• Link with metrics
• Implementation

Outcome

The PMI provides 2 things:

• the PMI is an information model of OSS artifacts (ex: Actor, Code, Unit, Developer, Maintainer, etc.) and their relationships
• the PMI is a description of OSS activities (ex: SubmitPatch activity, SubmitTestReport activity, ProduceSoftware etc.). It may also be a framework for dealing with processes in the sense that you can compose PMI activities for creating new activities.

Decisions:

1. We will first put into practice the PMI in the QA context
2. We will separate the information model from the process description: we will have on the one hand abstract Java classes describing the information model, and on the other hand individual descriptions of atomic processes perhaps based on BPML
3. We will look into BPML for process description
4. We will implement following use case of the PMI in the QA context:

• Someone enters a new test description manually online, conformant with the EDOS Testing XML specification
• During the next run of the EDOS testrunner, the new test is run automatically
• A test report is generated and is sent to the EDOS TestReportStoreService (web service)
• If the test failed, a defect is created automatically by the TestReportStoreService
• Information can be added to the defect (comments etc.)
• Someone submits a patch to the production system, which then notifies the PMI about the fact that a patch was submitted. This notification consists in calling a web service called "http://xxx//ProposePatch" with following arguments: URL of the defect, URL of the submitted patch
• The testing system runs the test again
• It the test passes, the defect is updated to fixed

Regading package naming, we will use following package names:

• edos.pmi.artifacts
• edos.pmi.process

Preliminary object model (simplified version of the current PMI information model) that we will implement (may be extended by additional attributes):

Test
creators
subtests (subpages)
targetConfiguration
targets
testedFunctionalities
type (internal/public)

TestReport
referenceTest
abstract
author
fulldescription
platformConfiguration (url)

Actor
name
publicKey
interest (Topics)
knowledge (Topics)

Topics

Defect

HardwareConfiguration
lshw output

SoftwareConfiguration
rpm -qa output

Defect
testReport
description (textual comment)
status
severity
priority

Patch
defects this patch relates to

WebServices:
SubmitTestReport
SubmitDefect
ProposePatch