[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=37482#comment-37482 ] 

Masaki Wakao commented on OSLCPROMCO-3:
---------------------------------------

In the meeting on May 7, we have discussed about Change 

- Change is common notion among any resources though PROMCODE has unique for contract between supplier and customer like SOW (Statement of Work)
- We should focus on the core model of project management for software contract
- It seems we can utilize OSLC Configuration Management as optional to manage the changes in PROMCODE

The conclusion at the time was that we should remove the Change from initial model of PROMCODE. 

Yoshida-san will remove the Change from the spec.

> 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)