Issue 4830: Combine classes for Goal and Precondition                                                                                                                                                               (spem-ftf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: Goal and Precondition do not need to be separate classes. Could not the same
object 'Design Model in state Ready' be used for both the Goal of one
Activity and the Precondition of the following activity? By using exactly
the same object one can more easily follow state-driven transitions.

Proposed resolution: make use of ClassifierInState (added as part of the
Activity metamodel extensions)

Resolution: Withdrawn by Pete: reject.
Revised Text: 
Actions taken:
February 12, 2002: received issue
October 23, 2002: closed issue
Discussion: 

End of Annotations:=====
From: "Pete Rivett" <pete.rivett@adaptive.com>
To: <issues@omg.org>
Cc: <spem-ftf@omg.org>
Subject: New SPEM Issues
Date: Tue, 12 Feb 2002 18:16:59 -0000
Message-ID: <003b01c1b3f1$76e69e00$5da823d9@CHIMAY>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To:
<OF92159934.5746918B-ON80256B4F.00520570@portsmouth.uk.ibm.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Type: text/plain;
	      charset="us-ascii"
X-UIDL: !<C!!%9Ee9_NNe9DN?!!


.... Combine classes for Goal and Precondition
Goal and Precondition do not need to be separate classes. Could not
the same
object 'Design Model in state Ready' be used for both the Goal of one
Activity and the Precondition of the following activity? By using
exactly
the same object one can more easily follow state-driven transitions.

Proposed resolution: make use of ClassifierInState (added as part of
the
Activity metamodel extensions)