-
Key: ALF-5
-
Legacy Issue Number: 4906
-
Status: closed
-
Source: International Business Machines ( Mr. Sridhar Iyengar)
-
Summary:
[Sridhar Iyengar] 15.Page 2-238: Figure 2-41. Looking at the metamodel,
it looks like the same 'Clause' can be owned by a LoopAction and a
ConditionalAction. For pragmatic reasons, there should be an OCL
constraint preventing this from happening - unless the submitters feel
the same clause can be 'owned' by both types of Actions. (I tried to
find the constraint and did not see one). I usually see a red flag when
multiple composite associations point to the same Class. (In this case
both LoopAction and ConditionalAction have a composite Association to
Clause. In other parts of the spec where this pattern recurs, I did see
the OCL constraint! (See Figure 3, Page 15 and related well formedness
rule on Page 21 that makes sure an 'input pin must be owned by either an
Action or a Procedure but not both'. -
Reported: ALF 1.0a — Tue, 5 Mar 2002 05:00 GMT
-
Disposition: Resolved — ALF 1.0b1
-
Disposition Summary:
accept
-
Updated: Fri, 6 Mar 2015 20:57 GMT