UML PROFILE FOR SAVECCM - Research
UML PROFILE FOR SAVECCM - Research
UML PROFILE FOR SAVECCM - Research
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Save<strong>UML</strong> profile<br />
• Entry : String. The name of an entry function that realizes the component’s<br />
behaviour.<br />
• Filename : String. The path to the file containing the entry function.<br />
Constraints:<br />
[1] ComponentAttributes: <strong>UML</strong> enables a Component to contain several types of<br />
attributes: ports, attributes and operations. SaveComponent component may own<br />
ports, quality attributes (properties with the SaveAttribute stereotype applied) and<br />
bind port descriptions (properties with the SaveBindPort stereotype applied). Other<br />
attributes are not allowed.<br />
[2] ComponentConnections: see the SaveAssembly constraint [2].<br />
[3] ComponentIntefraces: see the SaveClock constraint [4].<br />
[4] ComponentPackagedElements: see the SaveClock constraint [5].<br />
[5] ComponentPortNames: This constraint checks if all ports owned by a component<br />
have a unique name. This is important in order to use bind port descriptions where<br />
the name of the port has to be entered (see section 6.3.3.3).<br />
[6] ComponentPorts: All ports owned by a component must have appropriate<br />
stereotype applied. By appropriate stereotype it is considered to be one of the<br />
stereotypes defined by Save<strong>UML</strong> profile that are used to model SaveCCM ports. If<br />
some of the ports would not have stereotype applied it would be ambiguous what<br />
SaveCCM port it represents (as SaveCCM distinguishes several types of ports).<br />
[7] NumberOfStereotypes: see the SaveAssembly constraint [6].<br />
6.3.3.9 SaveComposite<br />
SaveComposite stereotype represents a SaveCCM composite component. The<br />
rationale for using the <strong>UML</strong> Component as the base classifier for the SaveCCM<br />
composite component is very similar to the situation with the basic component.<br />
The difference between the basic and the composite component is in the internal<br />
structure, i.e. components realization. While simple components are mostly<br />
realized by a single programming language function, composite components have<br />
their internal structure built from other components, connections etc.<br />
The subelements of SaveComposite can be other components and are added<br />
using metaclass PackageableElement.<br />
Base classifier: Component<br />
Tagged values: This stereotype does not have tagged values defined.<br />
Constraints:<br />
[1] ComponentConnections: see the SaveAssembly constraint [2].<br />
[2] ComponentInterfaces: see the SaveClock constraint [4].<br />
52