What is the use of UML

UML - a graphic modeling language

UML (level M2) defines the rules for its own semantics. The language units are terms that are defined in the UML 2.0 superstructure. This enables a formal representation that everyone involved can understand. Language units, in English language units, abstract similarly structured and functioning objects and processes and give them a visually representable form. Depending on the hierarchy level within the model, elements take on more specialized tasks or define other elements in more detail.

class: As a unit of language, classes are a core aspect of UML. They define what defines a class and how classes interact with each other. These language unit has four levels, ranging from simple elements to more complex relationships:

  • Kernel (describes elements from the UML 2.0 Infrastructure such as package, namespace, attribute, etc.)
  • AssociationClasses (defines association classes)
  • Interfaces (defines interfaces)
  • Powertypes (class whose instances are subclasses within this class)

component: Components are parts of their Separate content from the external system. There is only a connection to the outside through interfaces or ports. A composition connector connects to another component through the interface. The delegation connector links internal elements with an interface on the external border. Components have a modular structure and are interchangeable.

Composition structure: The language unit of composition structure describes elements that are shielded from the inside and outside like components. Only ports connect the content to the external system. The so-called encapsulated classifier are made up of elements den Parts, together. Parts communicate via connectors.

profile: A profile configures UML 2.0 for specific needs. Abstract terms such as activity or object have to be specified for some projects in order to increase understanding. You can adapt loosely set semantics and notations in places with a profile.

model: The model includes all elements that are necessary to represent a specific view of the structure or behavior of a system. This also includes external influences such as actors.

action: When it comes to depicting behavior, actions are central. They accept values ​​via input pins and output them to output pins. These are the thematic groups that UML defines for actions:

  • Manipulate objects
  • Manipulate object relationships
  • Manipulate structural features
  • Call actions
  • Generate values
  • Actions on objects
  • Receiving events

behavior: The language unit behavior or behavior description means the modeling of dynamic aspects within a system. It comprises three specifications:

  • activity: Actions interact through data and control flows. This creates a complex system of behaviors - the activities.
     
  • interaction: This metamodel describes how message flows are exchanged between objects, when a message is sent to which object and which other elements are influenced by it.
     
  • State machines: In a state diagram, this metamodel models states (situations with unchangeable properties) as well as pseudo states (states without value assignment) and their transitions. Objects in a state can be assigned to actions or activities.

distribution: A network consists of objects that are connected to each other in a mesh. A special use case exists when these elements are executable software or Artifacts represent. These artifacts run on execution environments or devices that use UML 2.0 as a node categorized. The artifact is therefore dependent on the node. The distribution represents this Dependency relationship that is created during installation.

Use case: The use case (as a unit of language) represents system requirements. The actor (a person or a system) is an element that describes who or what should carry out a certain activity with the aid of the system. The system can also be a class or a component and is therefore described as a subject. The use case (as a model element) merely communicates that a specified behavior that is externally visible to actors is expected. It usually does not represent the exact actions. Within a behavior description, the modeling assigns the detailed requirements to the use case.

Information flows: This UML language unit describes the elements information unit and information flow. These model elements abstract techniques for describing behavior, which can be very detail-oriented, such as activities or interactions. This simplified representation allows the universal use of these modeling elements in all UML diagram types. In contrast to the class, the information unit is therefore never described in more detail by attributes or integrated into methods. The flow of information therefore also connects all possible elements that exchange some kind of information with one another.