Issue 1473: Names of these meta types are confusing (boca-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: identifiable BocaEventConsumer{ attribute boolean before=FALSE; // attribute Expression path_expression; relationship path_expression Uses Expression; }; /* TriggerElement */ identifiable CallConsumer: BocaEventConsumer{ attribute boolean failure=FALSE; relationship producer References 1..1 BocaOperation inverse consumer; }; identifiable ChangeConsumer: BocaEventConsumer{ attribute boolean remove=FALSE; relationship producer References 1..1 BocaStructuralFeature inverse consumer; }; identifiable StateConsumer: ChangeConsumer{ attribute boolean on_exit=FALSE; }; The names of these meta-types are confusing. Recommendation: The meta-type names should be changed as indicated in the following table: Old Name New Name BocaEventConsumer BocaTrigger CallConsumer BocaCallTrigger ChangeConsumer BocaChangeTrigger StateConsumer BocaStateChangeTrigger Resolution: Revised Text: Actions taken: June 3, 1998: received issue June 23, 1998: closed issue Discussion: End of Annotations:===== *ISSUE 43* Section 2.2.4 (BOCA Meta-Model in CDL) identifiable BocaEventConsumer{ attribute boolean before=FALSE; // attribute Expression path_expression; relationship path_expression Uses Expression; }; /* TriggerElement */ identifiable CallConsumer: BocaEventConsumer{ attribute boolean failure=FALSE; relationship producer References 1..1 BocaOperation inverse consumer; }; identifiable ChangeConsumer: BocaEventConsumer{ attribute boolean remove=FALSE; relationship producer References 1..1 BocaStructuralFeature inverse consumer; }; identifiable StateConsumer: ChangeConsumer{ attribute boolean on_exit=FALSE; }; The names of these meta-types are confusing. Recommendation: The meta-type names should be changed as indicated in the following table: Old Name New Name BocaEventConsumer BocaTrigger CallConsumer BocaCallTrigger ChangeConsumer BocaChangeTrigger StateConsumer BocaStateChangeTrigger Also make these changes in the corresponding UML diagram (section 2.2.2.5).