Umple 
User Manual [Previous] [Next]
Important tips
The tips below will appear as the tips of the day in UmpleOnline. You can read them all here.
You can specify an association in a class or else by itself with the association keyword.
An association between two classes can be specified in either class (see an example in the user manual) or separately from either class, using the association keyword
You can generate code that ensures a class is a singleton (has only one instance).
If you specify singleton; in any class, then the singleton pattern will be applied, meaning that there will only be one instance.
Mark an attribute as lazy if you do not want it to create a constructor argument.
By default each attribute in a class becomes a constructor argument (along with associations that have a multiplicity of 1 at their other end).
If you want to avoid this, then add the keyword lazy before the association. The attribute will then be initialized with a null, empty or zero value.
The default data type for attributes in Umple is String.
In Umple you can specify a data type before any attribute. But if you do not, then attribute will default to type String.
Core datatypes in Umple include String, Integer, Boolean, Date, Time.
If you use the datatypes String, Double, Float, Integer, Boolean, Date or Time as the types of attributes, then Umple generates code tailored to the target language.
For example, when generating Java, an Integer attribute is implemented as an int variable. This is important to know, since the methods Umple generates to access those variables will use the Java type. If you specify Integer id; in Umple, and generate Java, then the API will have a method with signature setId(int)
Why does Umple then bother with an Integer datatype if it will be converted to int when generating Java? Because we want key types to be independent of the target programming language.
With UmpleOnline, you can create tasks to assign to others.
Under Tasks, you can create numerous assignments with different names, instructions, Umple models, and completion URLs (such as feedback quizzes) with the option of detailed logging. Simply create a task and distribute the participant URL or ask the responders to look up the name of the task under "Load Task" in order to start their submissions.
To acquire all the submissions, click "Request all Directories as a zip" under the task editing panel and all of the submissions will be saved on your local computer.