Issue 4515: Make ChangeRequest useful (cwm-rtf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Enhancement
Severity: Minor
Summary: This should be part of BusinessInformation: it is not at all specific to WarehouseOperations since one could request changes to database schemas, transformations or pretty much anything. 

'isActive' would be better than 'completed' for ChangeRequest, and would observe the convention of using 'is' for booleans. Moreover it should be a derived nonchangeable attribute to avoid inconsistency with 'status'. 

The reference from ChangeRequest to ModelElement should be 0..* since the request might be to create something new that cannot yet be referred to! 

The following are considered essential for most ChangeRequests: 1) two multivalued optional references to ResponsibleParty to indicate: a) raiser b) actionee 2) optional single-valued integer attribute 'priority' (larger value = more important), constrained to be non-negative. 3) optional single-valued string attributes 'raisersIdentifier' and 'identifier' (representing an id allocated by the raiser and that used internally by the warehouse management system). 4) optional multivalued string attribute 'history' to describe events in managing the request. 5) optional string attribute 'resolution' to decribe what actually happened (e.g. how the modelElements were changed, why the request was rejected etc). 

Resolution: 
Revised Text: 
Actions taken:
August 19, 2001: received issue
Discussion: 

End of Annotations:=====
From: webmaster@omg.org
Message-Id: <200108192124.f7JLO3t00197@emerald.omg.org>
Date: 19 Aug 2001 17:27:32 -0400
To: <juergen@omg.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Issue/Bug Report
Content-Type: Text/html; charset=windows-1252
X-UIDL: 9aY!!6dH!![<J!!Q-bd9



Name: Pete Rivett 
Company: Adaptive 
mailFrom: pete.rivett@adaptive.com 
Notification: Yes 
Specification: CWM 
Section: 19 
FormalNumber: ad/01-02-01 
Version: 1.0 
RevisionDate: 02/02/01 
Page: various 
Nature: Enhancement 
Severity: Minor 
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) 


Description

Make ChangeRequest useful 

This should be part of BusinessInformation: it is not at all specific
to WarehouseOperations since one could request changes to database
schemas, transformations or pretty much anything. 

'isActive' would be better than 'completed' for ChangeRequest, and
would observe the convention of using 'is' for booleans. Moreover it
should be a derived nonchangeable attribute to avoid inconsistency
with 'status'. 

The reference from ChangeRequest to ModelElement should be 0..* since
the request might be to create something new that cannot yet be
referred to! 

The following are considered essential for most ChangeRequests: 1) two
multivalued optional references to ResponsibleParty to indicate: a)
raiser b) actionee 2) optional single-valued integer attribute
'priority' (larger value = more important), constrained to be
non-negative. 3) optional single-valued string attributes
'raisersIdentifier' and 'identifier' (representing an id allocated by
the raiser and that used internally by the warehouse management
system). 4) optional multivalued string attribute 'history' to
describe events in managing the request. 5) optional string attribute
'resolution' to decribe what actually happened (e.g. how the
modelElements were changed, why the request was rejected etc). 

<end/>