Q: Is a floating license configurable to allow check out a key for offline-working?
A: Yes, the floating license system is configurable to allow you to checkout a key and hold it for offline use if needed. If you planned on using a laptop system for example and knew you would need to work away from the office the next day, you could checkout the key before leaving the office and be able to use it the next day without having to re-connect to the network.

Q: How can i configure a period for a floating license?
A: The period that the license can remain checked-out for is configurable by the license administrator using SSKeyStore.

Q: What is the Auto-Check-In-option?
A: An Auto Checkin option configurable which forces EA clients to automatically return the key to the license pool upon closing EA. With this option enabled, the maximum possible unused licenses should always be available. To hold a license for offline use while operating in this mode, the user must disconnect from the network while EA is still running, or otherwise prevent access to the shared key file before EA is shut down.
If you choose to have the Auto Checkin option disabled, then the license will always be held by the user until it’s expiry is reached. The license ‘lease’ will be renewed each time the user connects to the keystore (automatic upon opening EA).

Q: How do other users handle the floating license?
A: “We have configured it for automatic release and a 1 day retention period (although we might extend this if we ahver a lot of off-site work).”

Basic information of the EA license and floating license can be found on Sparxsystems Europe.

“The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system.
The UML offers a standard way to write a system’s blueprints, including conceptual things such as business processes and system functions as well as concrete things such as programming language statements, database schemas, and reusable software components.”

The most important thing to understand is, that UML is a language for specifying! It is not a method or procedure. With UML you define a software system -  UML is the language who writes the blueprint and does not specify itself in that methodology or process.

Following domains can be defined with notation and semantics:
- Use case model
- Communication model
- State or dynamic model
- Logical or class model
- Physical component model
- Physical deployment model

UML also offers the possibility for extending the UML for your specialized needs (for example Business Process Modeling extensions). For further information on Business Process Modeling take a look at the whitepapers BPM.