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

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

I've just uploaded a revised version of domain model.
https://www.oasis-open.org/apps/org/workgroup/oslc-promcode/download.php/53099/PROMCODE%20Domain%20Model%2020140521.pptx

Changes are:
1. remove "Change" and related links
2. rename the link between Measurement and Measure as "observes" from "has"

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