Issue 7628: definition of the stereotype CORBAPrimaryKey
Issue 7629: The (IDL) definition of the example is not correct
Issue 7632: Facet and Receptacles (ports)
Issue 7633: Event ports
Issue 7634: Figure6: associations described Event ports have to be composite associatio
Issue 7635: Association needed
Issue 9238: Section: Figure 13.9
Issue 7628: definition of the stereotype CORBAPrimaryKey (uml-ccm-ftf)
Click here for this issue's archive.
Source: Fraunhofer FOKUS (Mr. Tom Ritter, tom.ritter(at)fokus.fraunhofer.de)
Nature: Revision
Severity: Significant
Summary:
The definition of the stereotype CORBAPrimaryKey makes too strong restrictions. The CORBA Component Model defines a primary key as an ordinary valuetype, which is derived from Components::PrimaryKeyBase. Using the stereotype PrimaryKey would prevent me from using this valuetype in other parts of my application as a plain valuetype (e.g operation parameter). Suggestion: Remove stereotyp CORBAPrimaryKey. Use stereotype CORBAValueDef instead and refomulate the constraints accordingly. (e.g. inheritance)
The (IDL) definition of the example is not correct. The valuetyp for the key is not allowed to be abstract and it must have at least one public member. Furthermore, this key needs to be derived from Components::PrimaryKeyBase. The picture of the UML model should also be completely shown (i.e. including the member of the primary key). Suggestion: Modify example (IDL and picture)
Facet and Receptacles (ports) are specified as an UML association, but their names are specified as role names of the association end of the referenced interface. It means, the component refers directly to the external interface – it’s confusing and less intuitiv. Suggestion: Facet and Receptacle names are the names of the associations, describing ports.
Event ports are specified as an UML association, but their names are specified as role names of the association end of the referenced event. It means, the component refers directly to the external event – it’s confusing. Suggestion: Event port (such as Facet and Receptacle) names are the names of the associations.
Figure6: associations described Event ports have to be composite associations.
Association with <<CORBAManages>> between HomeImplDef and ComponentImplDef is needed, otherwise you can’t navigate and define what HomeImplDef manages what ComponentImplDef.
In the composition between Signal and Property, the reference (from Kernel) was omitted from the Property. Property does not seem to exist (nor has been incremented) in the CommonBehavior::Communications Package. In ptc/03-07-06, Property class is shown to be from the Classes::Kernel Package.