CM Tools Common Resource Properties

Purpose

This page is being used to collect information about what are common properties of change request resources of type: defect, task and enhancement. The result of this will assist in understand what properties are used for what scenarios and ensure better alignment with current implementations in defining a common CM vocabulary.

Please contribute your property definitions directly into this page or create a new page and link it to here.

Change Request Property Definitions

For change requests of type: defect, enhancement and task

Scenarios:

• fixdefect - DefectScenario
• plan - CmScenariosAgilePlanningOfChangeRequests
• report - CmScenariosReporting
• ide - ScenariosMylyn
• <add more as appropriate>

Common Properties

Core Properties

This is a consolidated list of most frequently used properties on a change request resource from analyzed sources attached and referenced.

WG actions regarding updates to this table:

• Validate that your product is accurately represented into table, update accordingly
• Identify any additional scenarios where the properties are required
• Identify any properties that you feel should (or should not) be included into the core set

The approach to define the common core set of Change Request properties for OSLC-CM 2.0 will be:

• Prioritization of properties based on usage in scenarios
• How many tools already support the properties
• Complexity of defining specification (Children collection of references, etc)

Once a common core set is defined:

• Identify if there is any existing standard vocabulary (DOAP, DC, etc)
• Define the contraints on each property (open content, string with size limit, reference, complex context, etc)
• Need for enumeration and value mapping: Severity, Priority, etc

Possibly consider:

• Properties for specific users who performed operations: LastModifiedBy? , ResolvedBy? , ClosedBy? , etc
• Information specific to where change is targeted: Product, Release
• Better information on when state transitions occurred and by who
• Platform specific information: OS, Browser, etc

Planning Specific

Sources

Tasktop/Mylyn

Rational ClearQuest

Rational Team Concert

Bugzilla

Anatomy of a Bug

Rally Story Fields

Rally Defect Fields

Rational Change

These are some common attributes from the out-of-the-box "dev_process" process. Most customer don't use it directly, but use it as a starting place for their own process.

Other sources

Some other ontologies have been developed to represent bug reports, where some mappings were described :

• http://code.google.com/p/baetle/wiki/EvoOntBomMappings for EvoOnt? BOM
• http://code.google.com/p/baetle/wiki/Bugtrackers2baetleMappings for BAETLE

These may be reviewed in order to improve the properties for OSLC-CM.