OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCCM-28) Need a decomposition reference

    [ https://issues.oasis-open.org/browse/OSLCCCM-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65224#comment-65224 ] 

James Amsden edited comment on OSLCCCM-28 at 2/8/17 8:09 PM:

Added oslc_cm:parent property to ChangeRequest which is inherited by all the subclasses. I this sufficient?

was (Author: jamsden):
Added oslc_cm:parent property to ChangeRequest which is inherited by all the subclasses.

> Need a decomposition reference
> ------------------------------
>                 Key: OSLCCCM-28
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-28
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Change Management
>            Reporter: Martin Sarabura
> There is currently an attribute called "relatedChangeRequest" which is described as a loose coupling to some other resource. By its name it seems to suggest that the other resource is likely going to be a "Change Request". While not stated explicitly, here "change request" is probably intended to be a generic reference to either the explicit type ChangeRequest or any of its subtypes.
> An "informational" link to some other resource is perfectly fine so this attribute has its place. However the PTC CM tools have the notion of a waterfall decomposition where the initial defect or enhancement is translated from "voice of the customer" to internal voice as a change request, which gets authorized via workflow to be a change notice. Finally, change notices contain one or more ordered tasks that must be completed in order for the initial request to be satisfied. This kind of decomposition link has a very different meaning than an informative link - it encapsulates a workflow. As such, and since I'm confident that this is a reasonably common feature, I believe a new relationship should be added to the spec.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]