UML PROFILE FOR SAVECCM - Research

More documents

Recommendations

Info

SaveUML profile Figure 6-3: Applying stereotype – editing tagged values 6.4.3 Modelling UML models using SaveUML profile SaveUML profile extends several UML metaclasses which can be used for modelling SaveCCM elements, those are: Component, Property, Port, Usage, Dependency and Artifact. This section provides examples of using some of those elements. Component For modelling SaveCCM architectural elements (using UML Component metaclass) it is necessary to add a UML component to the model. Then one of the available stereotypes has to be applied depending on SaveCCM element that is modelled. Applying a stereotype to a UML component is described in previous section. Property and Port Property is used for modelling component attributes, while Port is used for modelling component ports. They can be added to a component in the Properties view under "Attributes" tab, this is shown in Figure 6-4. It is possible to choose either a Port or an Attribute property. Figure 6-4: Adding a property to a component 63
SaveUML profile When modelling SaveCCM port it is necessary to add a port to a component and when modelling SaveCCM bind port, attribute or switch condition it is needed to add an attribute to a component. After the property or a port is added, the procedure of applying stereotype and setting tagged values is the one described in section 6.4.2. Figure 6-5 shows a screenshot of Project explorer view of ACC system model. It provides an example of a component (Object recognition) with three properties, one with SaveAttribute stereotype applied (attribute1) and two with SaveBindPort (bindDin1 and bindDin2). Also on this example there are various ports shown. Figure 6-5: UML model of ACC system – Project explorer view Artifact In SaveUML profile Artifact is used for modelling SaveCCM model element. It is attached to a component with a manifestation relationship. First it is necessary to add an artifact to the model, the SaveModel stereotype can be applied to the artifact (the procedure is equal to the one described in section 6.4.2). Finally a model has to be connected to the component using manifestation relationship. An example of a SaveComponent with SaveModel attached is shown in Figure 6-6. 64
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:
Page 18 and 19:
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 66 and 67: SaveUML profile 6.3.3.18 SaveSwitch
Page 68 and 69: SaveUML profile Base classifier: Po
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

Create successful ePaper yourself

Delete template?

Save as template?