The ícons for GeoProfile can be found here: Now, just copy the profile files (.PRF and icons) to this folder. Therefore, to our profile be recognized by the tool, simply create a new folder in this subdirectory, let's call it staruml-geoprofile. Which is the default installation directory of the operating system used. Note that in the figure above the path to the desired directory is:Ĭ:\Arquivos de Programas\StarUML\modules orĬ:\Program Files\StarUML\modules in english. It is advisable to create a new folder inside the subdirectory modules containing the files from the profile, the. If the profile file is invalid or your extension is not. The StarUML looks for and reads the profiles that are in the folder modules in your installation directory and registers automatically when the program starts. To the profile to be automatically recognized, we must put it in a subdirectory of the tool: \modules. PRF extension so that it can be recognized by StarUML.
#STARUML MULTIPLICITY CODE#
Now, copy the XML code above to a text editor of your choice and save it with the. Recalling that the file with the XML code must be saved with the. With this definition and the XML elements defined above, we can now create the GeoProfile to be used in the tool StarUML. The profile GeoProfile is shown in the figure below. Unfortunately, this tool does not support the definition of constraints on OCL language for profiles. LITERALS: Defines the literals if the type of tag is Enumeration.
This can be defined as being of the types: Integer, Boolean, Real, String, Enumeration, Reference or Collection.ĭEFAULTDATAVALUE: Default value of the tag. This must be unique within the set of tags to which this tag belongs (TagDefinitionSet). Can be "True" in the case of not being able to change, or "False" otherwise. Lock (TAGDEFINITION element): Sets whether the value of the tag may or may not be changed by the user. The section sets a TaggedValue section of a set of lists of tags. TAGDEFINITIONLIST: Contains multiple definitions of tags included in the set. If the TagDefinition is interested in a particular stereotype, it is advised to use the name of the stereotype.īASECLASSES: Contains the names of the UML elements to be applied in TagDefinitionSet. The section defines a set of TaggedValues that may be related to a stereotype, this has the following structure: The icon file must be located in the same directory as the document profile. This element contains the name of the icon file for the stereotype. ICON: A stereotype can also be indicated by an icon. RELATEDTAGDEFINITIONSET: Contains the name of TagDefinitionSet related to the stereotype (name of stereotype attribute set). The PARENT element containing the name of the parent element of the stereotype. PARENT: The stereotype might have relationship type inheritance. If the stereotype of top-level (parent element) is defined, this section will not be defined any definition of this section is ignored and the value BASECLASSES stereotype is applied. Note: If the name of an abstract class as UMLClassifier is used, all elements inherited this will be applied. The name of the elements used here are the names of the UML elements (UMLClass, UMLAssociation, UMLClassifier, UMLAttribute, UMLPackage, UMLAbstractClass. The section defines the information of the stereotype and the inheritance structure, may contain the following elements:ĭESCRIPTION: Description of the stereotype.īASECLASSES: May contain names of multiple UML elements that can be applied to the stereotype. For defining data types, see the section. ĭATATYPELIST: Define multiple data types. TAGDEFINITIONSETLIST: Defines multiple tag definitions. For defining stereotypes see the section. STEREOTYPELIST: List of stereotypes of the profile. The section can contain the following elements: The section can contain the following elements :ĭISPLAYNAME: This is the caption used in the profile dialog and other user interfaces.ĭESCRIPTION: Contain the description of the profile.ĪUTOINCLUDE: Specifies whether to include the profile automatically when you create new project. Where the section defines the profile description and is the body of the profile itself, which will be defined stereotypes, classes, attributes and data types of the profile. The basic structure of an XML document to create a profile for StarUML is shown below:
In this tutorial we will focus only on the XML elements that will be useful in creating of Geoprofile. For this tutorial we used version 5.0 of StarUML. The following will be shown step by step the creation process and an example of using GeoProfile for modeling geographic database. StarUML - UML/MDA Plataform - Tutorial for GeoProfile
0 kommentar(er)
