UML PROFILE FOR SAVECCM - Research

More documents

Recommendations

Info

SaveUML profile 6.3.3.18 SaveSwitchCondition This stereotype represents two elements from SaveCCM domain – connection pattern and connection condition. In SaveCCM, connection pattern and connection condition are used to model a switch behaviour. Switch connection pattern determines two ports that can be connected, while the switch connection condition defines the terms under which this connection is established. Although they model the behaviour, these two elements can also be looked upon as a property of a switch component. Therefore, SaveUML profile uses Property metaclass as the base classifier for SaveSwitchCondition stereotype. Each SaveSwitchCondition element is added to SaveSwitch component as its attribute. Base classifier: Property Tagged values: • SetPort : String. The name of the port used in a condition (this is a part of connection condition). • SetPortValue : String. The value of data on set port that needs to arrive for condition to become true (this is a part of connection condition). • ConnectFrom : String. The name of the input port that has to be connected to the port stated in "ConnectTo" tagged value (this is a part of connection pattern). • ConnectTo : String. The name of the output port that has to be connected to the port stated in "ConnectFrom" tagged value (this is a part of connection pattern). Constraints: [1] PropertyConnectors: see the SaveAttribute constraint [1]. [2] PropertyNumberOfStereotypes: see the SaveAssembly constraint [6]. [3] SwitchConditionEqualPorts: Ports stated in "SetPort", "ConnectFrom" and "ConnectTo" tagged values are not allowed to be equal. It is not allowed to connect a port to itself or to use a set port in connection pattern. [4] SwitchConditionFrom: Port stated in "ConnectFrom" tagged value must be an input port of a switch component (a port with a SaveTriggerInPort, SaveDataInPort or SaveCombinedInPort stereotype applied). [5] SwitchConditionPorts: Checks if the ports stated in "SetPort", "ConnectFrom" and "ConnectTo" tagged values exists (checks that the switch component owns the ports with the stated names). [6] SwitchConditionSetPort: Only a data or combined input port can be a set port. This constraint checks that the port stated in "SetPort" tagged value has an appropriate stereotype applied (SaveDataInport or SaveCombinedInPort stereotype). Also it checks that the port stated "SetPort" tagged value is marked as a set port (the "SetPort" tagged value of the port must be set to ‘true’). 59
SaveUML profile [7] SwitchConditionTo: Port stated in "ConnectTo" tagged value must be an output port of a switch component (a port with a SaveTriggerOutPort, SaveDataOutPort or SaveCombinedOutPort stereotype applied). 6.3.3.19 SaveToComplex A special kind of a connection is used to connect the port of a component to a complex connection. The usage relationship is used as the base classifier based on the same rationale with the basic component connection (see section 6.3.3.10). Base classifier: Usage Tagged values: This stereotype does not have tagged values defined. Constraints: [1] ComplexConnectionDirection: SaveToComplex is used to connect a component to a complex connection. This constraint checks if the client of a connection (starting point) is an output port (a port with SaveTriggerOutPort, SaveDataOutPort or SaveCombinedOutPort stereotype applied), and a supplier of a connection (ending point) must be a component with SaveComplexConnection stereotype applied. [2] NumberOfStereotypes: see the SaveAssembly constraint [6]. 6.3.3.20 SaveTriggerInPort This stereotype is used for modelling SaveCCM trigger in ports. The rationale behind using UML Port as the base classifier for the SaveCCM trigger input port element is the same as with the SaveCombinedInPort (see section 6.3.3.5). Base classifier: Port Tagged values: • External : String. A label mapping the port to external entity, in case a port is an external port. Constraints: [1] NumberOfStereotypes: see the SaveAssembly constraint [6]. [2] OwnerComponentStereotype: see the SaveCombinedInPort constraint [2]. [3] PortConnections: see the SaveCombinedInPort constraint [3]. [4] PortConnectionStereotype: see the SaveCombinedInPort constraint [4]. [5] PortsExternal: see the SaveCombinedInPort constraint [5]. [6] PortsInterfaces: see the SaveCombinedInPort constraint [6]. 6.3.3.21 SaveTriggerOutPort This stereotype is used for modelling SaveCCM trigger out ports. The rationale behind using UML Port as the base classifier for the SaveCCM trigger output port element is the same as with the SaveCombinedInPort (see section 6.3.3.5). 60
Page 1:
UNIVERSITY OF ZAGREB AND MÄLARDALE
Page 4 and 5:
4.6.2 Profile extension mechanism .
Page 6 and 7:
Definitions and acronyms API CASE C
Page 8 and 9:
Introduction 1. Introduction 1.1 Ov
Page 10 and 11:
Component - based software engineer
Page 12 and 13:
Page 14 and 15:
Page 16 and 17: Component - based software engineer
Page 18 and 19: Component - based software engineer
Page 20 and 21: Component models framework. A compo
Page 22 and 23: Component models Components in .NET
Page 24 and 25: UML 4. Unified Modeling Language Th
Page 26 and 27: UML referred to with the name of th
Page 28 and 29: UML 4.4 The UML Superstructure Arch
Page 30 and 31: UML Figure 4-5: A component with in
Page 32 and 33: UML Figure 4-6: Dependencies of the
Page 34 and 35: UML general classifier and a more s
Page 36 and 37: UML Figure 4-9: A component with pa
Page 38 and 39: UML However, this mechanism has som
Page 40 and 41: UML In four layer metamodel hierarc
Page 42 and 43: SaveCCM 5. SaveComp Component Model
Page 44 and 45: SaveCCM Quality attributes In addit
Page 46 and 47: SaveCCM Unlike components, switches
Page 48 and 49: SaveCCM Figure 5-3: SaveCCM model o
Page 50 and 51: SaveUML profile from a strict synta
Page 52 and 53: SaveUML profile 6.3 The SaveUML pro
Page 54 and 55: SaveUML profile [6] NumberOfStereot
Page 56 and 57: SaveUML profile connections. Althou
Page 58 and 59: SaveUML profile and only special To
Page 60 and 61: SaveUML profile [3] ComponentPorts:
Page 62 and 63: SaveUML profile Tagged values: For
Page 64 and 65: SaveUML profile Base classifier: Us
Page 68 and 69: SaveUML profile Base classifier: Po
Page 70 and 71: SaveUML profile Figure 6-3: Applyin
Page 72 and 73: SaveUML profile Figure 6-6: Connect
Page 74 and 75: SaveUML transformations 7. SaveUML
Page 76 and 77: SaveUML transformations support for
Page 78 and 79: SaveUML transformations Model objec
Page 80 and 81: SaveUML transformations [3] Target
Page 82 and 83: SaveUML transformations When transf
Page 84 and 85: SaveUML transformations Figure 7-8:
Page 86 and 87: References References [Åkerholm 05
show all

UML PROFILE FOR SAVECCM - Research

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?