[OASIS Issue Tracker] (OSLCPROMCO-3) Define change management scenario and model to be used in PROMCODE spec

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37542#comment-37542 ] 

Hiroyuki Yoshida commented on OSLCPROMCO-3:
-------------------------------------------

In addition to out discussion in the meeting on May 7, the reason I think why we should remove "Change" from our domain model is as follows.

In the model of our base document, a Change represents a relation between superseded and superseding ManagedItems.
But in our scenarios, most typical changes of ManagedItems are changes of  their properties, not replacements by another ManagedItems.
Changes of ManagedItems should be managed by versions of each item and configurations of them which is the way we expect the CCM Specification will provide.

(This issue may be closed now.)

> Define change management scenario and model to be used in PROMCODE spec
> -----------------------------------------------------------------------
>
>                 Key: OSLCPROMCO-3
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Improvement
>            Reporter: Masaki Wakao
>            Assignee: Hiroyuki Yoshida
>
> There are 2 different level of scenarios raised during meeting on April, 22.
> - Simple change log
> - Transactional change (baseline, change-set)
> We have to define our scenario and model for PROMCODE.
> There are candidate external definitions for each scenario:
> - TRS for simple change log
> - Configuration Management for transactional change



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)