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-27) New type ChangeAuthorization needed for CM spec

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

Martin Sarabura commented on OSLCCCM-27:

After thinking about this I believe it is not enough. We also need to capture some notion of containership - but see my note on issue 28 regarding additional relationship attributes. Also we need to assign work to a Person which is perhaps more critical on Task than the other classes but could be on all of them too. For instance a change notice may be assigned initially to a change review board for approval.

The other issue is whether we should deconstruct the domain into three meaningful classes - request, task, "task collection" (aka change notice) - rather than lumping everything into a single class "sub-instance of change request" and allowing the implementer to fill out all of the notional details. If this were merely a reorganization of the types into a different configuration then I agree it does not warrant support or even mention in the spec. But it's adding significant meaning and is therefore conspicuous in its absence. The audience we're trying to reach needs to know we understand and can support their conceptual models.

> New type ChangeAuthorization needed for CM spec
> -----------------------------------------------
>                 Key: OSLCCCM-27
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-27
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Change Management
>            Reporter: Martin Sarabura
> Notwithstanding issue #26 which I just posted, I feel that change notice should be added explicitly to the spec.
> There are two classes of type in the current spec: Request and Task.
> Requests include Change Request (which is also drawn up as the base type in the UML diagram), Enhancement and Defect.
> Tasks include Task (which is drawn up as the base type in the UML diagram) and ReviewTask.
> A change notice in certain tools is neither a request nor a task: It is an authorization to perform multiple tasks. Thus it is more of a "command" than a request and it is a container of tasks. Since it has a different meaning than the available Types and since it is found in a number of CM tools, I believe it should be listed as its own type.

This message was sent by Atlassian JIRA

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