Profile (UML): Difference between revisions
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
{{UML}} |
{{UML}} |
||
{{DEFAULTSORT: |
{{DEFAULTSORT:KKJKNKJNKNKJ}} |
||
[[Category:Unified Modeling Language]] |
[[Category:Unified Modeling Language]] |
||
[[Category:Systems Modeling Language]] |
[[Category:Systems Modeling Language]] |
||
Revision as of 17:42, 6 September 2012
A pBKJBKJKrofile in the Unified Modeling Language TATOBAY provides a generic extension mechanism for customizing UML models for particular domains and platforms. Extension mechanisms allow refining standard semantics in strictly additive manner, so that they can't contradict standard semantics.[1]
Profiles are defined using stereotypes, tag definitions, and constraints that are applied to specific model elements, such as Classes, Attributes, Operations, and Activities. A Profile is a collection of such extensions that collectively customize UML for a particular domain (e.g., aerospace, healthcare, financial) or platform (J2EE, .NET).
Examples
The UML Profile for XML is defined by David Carlson in the book "Modeling XML Applications with UML" pp. 310 and describes a set of extensions to basic UML model elements to enable accurate modeling of XSD schemas.
SysML is an Object Management Group (OMG)-standardized profile of Unified Modeling Language that is used for system engineering applications.
MARTE is the OMG standard for modelling real-time and embedded applications with UML2.
Footnotes
- ^ Si Alhir, S: Guide to applying the UML, page 350. Springer, 2002
References
- Si Alhir, Sinan (2002). Guide to applying the UML. Springer. ISBN 0-387-95209-8.
External links
| Actors |
|  | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Concepts |
| ||||||||||||
| Diagrams |
| ||||||||||||
| Derived languages | |||||||||||||
| Other topics | |||||||||||||
 | This Unified Modeling Language article is a stub. You can help Wikipedia by expanding it. |