Executable UML Profile
Executable UML is a profile of the UML, defining execution semantics for a subset of the UML. Notable aspects of the Executable UML profile include the following:
- No support for implementation specific constructs, like aggregation and composition.
- Generalizations are always notated as {complete, disjoint}.
- Associations between classes are always named, have verb phrases on both ends specifying the roles, and have multiplicity specified on both ends.
- Multiplicities on association ends are restricted to 0..1 (zero to one), * (zero to many), 1 (exactly one), or 1..* (one to many).
- Data types are restricted to the following core data types: boolean, string, integer, real, date, timestamp, and arbitrary_id, or one of the following domain-specific data types: numeric, string, enumerated, and composite. Domain-specific numeric and string data types can represent subsets of the core data types. The domain-specific composite data type is to always be treated as a single unit. e.g., a MailingAddress data type could be declared, but city information couldn't be extracted from it.
- Constraints on the Executable UML models can either be represented as Object Constraint Language (OCL) or action language.
- Domains are represented as a Package, and bridges are represented as a Dependency.
Read more about this topic: Executable UML
Famous quotes containing the word profile:
“Expecting rain, the profile of a day
Wears its soul like a hat....”
—John Ashbery (b. 1927)