Issue 7798: notion of a constraint (uml-qos-ft-ftf) Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill(at)baesystems.com) Nature: Enhancement Severity: Significant Summary: I am struggling with the notion of a constraint, whereby operators (e.g. >, < and =) are used within an expression containing QoS characteristics and class attributes. I can see that QoSCharacteristic is a specialisation of QoSContext, although QoSDimensionSlot seems an odd place to declare operators. Should the model look like: Diagram Alternatively, I assume there is a pattern within the SysML parametric model. Resolution: Revised Text: Actions taken: September 30, 2004: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:15:12 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Kevin Dockerill Company: BAE SYSTEMS, Warton, Lancs UK mailFrom: Kevin.dockerill@baesystems.com Notification: No Specification: UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms Section: fig 8.6 FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 7/21/2004 Page: 15 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description I am struggling with the notion of a constraint, whereby operators (e.g. >, < and =) are used within an expression containing QoS characteristics and class attributes. I can see that QoSCharacteristic is a specialisation of QoSContext, although QoSDimensionSlot seems an odd place to declare operators. Should the model look like: Diagram Alternatively, I assume there is a pattern within the SysML parametric model.