Issue 6269: Technical sections 2.3.3 and 2.3.4 (deployment-ftf) Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com) Nature: Uncategorized Issue Severity: Summary: 2.3.3 ComponentPackageDescription 2.3.4 ComponentImplementationDescription There should be a constraint stated for the configproperties? What should they relate to? Resolution: Revised Text: Add "english" constraint statements. Due to the abstract nature of the property type (of type DataType), and therefore the inability to determine type equivalency, the constraints cannot be written in OCL. Add the following text to sections 6.4.2.4 (PackageConfiguration constraints), 6.4.3.4 (ComponentPackageDescription constraints), 6.4.5.4 (ComponentImplementationDescription constraints), and 6.4.7.4, (SubcomponentInstantiationDescription constraints): Configuration properties must match configurable properties, as identified by the component interface(ComponentInterfaceDescription element), in name and type. Actions taken: September 9, 2003: received issue May 9, 2005: closed issue Discussion: Resolution: There are currently no (formal or english) constraints that match configuration properties (in the PackageConfiguration, ComponentPackageDescription, ComponentImplementationDescription and SubcomponentInstantiationDescription classes) to configurable properties as identified by the component interface. That's why constraints are added End of Annotations:===== 5. Technical 2.3.3 ComponentPackageDescription 2.3.4 ComponentImplementationDescription There should be a constraint stated for the configproperties? What should they relate to? Jerry Bickle Senior Principal Software Engineer Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 260-429-5060 Fax5. Technical 2.3.3 ComponentPackageDescription 2.3.4 ComponentImplementationDescription There should be a constraint stated for the configproperties? What should they relate to? Jerry Bickle Senior Principal Software Engineer Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 260-429-5060 Fax Subject: Proposed Resolution for Issue 6269 Date: Fri, 9 Apr 2004 14:55:06 -0400 Thread-Topic: Proposed Resolution for Issue 6269 Thread-Index: AcQeZCw/JdRkfin8TZeSTzK/vimt1g== From: "Pilhofer, Frank" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i39Iv9qq009647 There are currently no (formal or english) constraints that match configuration properties (in the PackageConfiguration, Component- PackageDescription, ComponentImplementationDescription and SubcomponentInstantiationDescription classes) to configurable properties as identified by the component interface. Proposed resolution: Add "english" constraint statements. Due to the abstract nature of the property type (of type DataType), and therefore the inability to determine type equivalency, the constraints cannot be written in OCL. Add the following text to sections 6.4.2.4 (PackageConfiguration constraints), 6.4.3.4 (ComponentPackageDescription constraints), 6.4.5.4 (ComponentImplementationDescription constraints), and 6.4.7.4, (SubcomponentInstantiationDescription constraints): Configuration properties must match configurable properties, as identified by the component interface (ComponentInterfaceDescription element), in name and type.