11.02.2014 Views

UML PROFILE FOR SAVECCM - Research

UML PROFILE FOR SAVECCM - Research

UML PROFILE FOR SAVECCM - Research

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Save<strong>UML</strong> profile<br />

Base classifier: Usage<br />

Tagged values: This stereotype does not have tagged values defined.<br />

Constraints:<br />

[1] ComplexConnectionDirection: SaveFromComplex is used to connect a complex<br />

connection to a component. This constraint checks if the client of a connection<br />

(starting point) is a component with SaveComplexConnection stereotype applied,<br />

and a supplier of a connection (ending point) must be an input port (a port with<br />

SaveTriggerInPort, SaveDataInPort or SaveCombinedInPort stereotype applied).<br />

[2] NumberOfStereotypes: see the SaveAssembly constraint [6].<br />

6.3.3.16 SaveModel<br />

A model in the SaveCCM domain represents a software realization of a<br />

components behaviour, most likely in the form of a programming language<br />

function. <strong>UML</strong> Artifact represents a physical piece of information that is used,<br />

among other things, by the operation of a system. A <strong>UML</strong> artifact can therefore be<br />

a model or a software. This means that the <strong>UML</strong> artifact is a good base classifier<br />

for the SaveCCM model.<br />

A model is connected to a component through a <strong>UML</strong> manifestation relationship<br />

which indicates their semantically link. <strong>UML</strong> Manifestation is usually used for<br />

division between an abstraction and a manifestation, for example distinction<br />

between a class and an object, where the class is an abstraction and the object is<br />

a clear manifestation of that class. Most <strong>UML</strong> building blocks have this kind of<br />

class/object distinction, e.g. use case, use case instance etc. Therefore,<br />

manifestation relationship is suitable for this purpose. A component can have any<br />

number of models attached to it.<br />

Base classifier: Artifact<br />

Tagged values:<br />

• Type : String. Describes what type of model it is.<br />

• Filename : String. A file containing model implementation.<br />

• Body : String. Instead of using an external file, a model can be embedded as<br />

text within the element.<br />

Constraints:<br />

[1] ModelAttributes: <strong>UML</strong> allows for an Artifact metaclass having various attributes,<br />

however SaveCCM model element can not contain any attribute (property). Except<br />

attributes, this constraint checks that there are not any connections used for<br />

connecting this element to other elements, only a manifestation relationship is<br />

allowed.<br />

57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!