Please enable JavaScript.

Coggle requires JavaScript to display documents.

UML 2.5 Diagram (tructure Diagram (Componen Diagram (Elements…

- - - - Component
        A component is a class representing a modular part of a system with encapsulated content and whose manifestation is replaceable
        within its environment
        A component is shown as a classifier rectangle with the keyword «component»
        Optionally, a component icon similar to the UML 1.4 icon can be displayed in the top right corner of the component rectangle. If the
        icon symbol is shown, the keyword «component» may be omitted.
      - Inter face
        An interface is a classifier that declares of a set of coherent public features
        and obligations. An interface specifies a contract. Any instance of a
        classifier that realizes (implements) the interface must fulfill that contractand thus provides services described by contract
        
        Provide Instance
        A provided interface is the one that is either:
        Realized directly by the component itself, or
        Realized by one of the classifiers realizing component, or
        Is provided by a public port of the component
        
        Required Interface
        A required interface is either:
        Designated by usage dependency from the component itself, or
        Designated by usage dependency from one of the classifiers realizing
        component, or
        Is required by a public port of the component.
      - Port
        A port specifies an interaction point through which a classifier can communicate with its environment, with other
        classifiers, or with its internal parts. Encapsulated classifier is defined in UML as structured classifier with the
        ability to own ports, and thus port is a property of an encapsulated classifier. Port by default has public visibility
        Port is shown as a small square placed either overlapping the boundary of the rectangle denoting the
        encapsulated classifier, or it may be shown inside that rectangle symbol. . The name of the port is placed near the
        small square
      - Relationship
        Graphically, a component diagram is a collection of vertices and arcs and commonly containcomponents, interfaces and dependency, aggregation, constraint, generalization, association,
        and realization relationships. It may also contain notes and constraints
        
        Agreegation
        A kind of association that has one of its end marked shared as kind of
        aggregation, meaning that it has a shared aggregation
        
        Constraint
        A condition or restriction expressed in natural language text or in a machine
        readable language for the purpose of declaring some of the semantics of an
        element
        
        Composition
        Composite aggregation is a strong form of aggregation that requires a part instance be
        included in at most one composite at a time
        If a composite is deleted, all of its parts are normally deleted with it.
        
        Dependency
        A dependency is a relationship that signifies that a single or a set of model
        elements requires other model elements for their specification or implementation
        This means that the complete semantics of the depending elements is either
        semantically or structurally dependent on the definition of the supplier element(s)
        
        Assciation
        components, interfaces and dependency, aggregation, constraint, generalization, association,
        and realization relationships. It may also contain notes and constraints
        It has at least two ends represented by properties, each of which is connected to
        the type of the end.More than one end of the association may have the same
        type.
        
        Links
        A generalization is a taxonomic relationship between a more general classifier and
        a more specific classifier
        Each instance of the specific classifier is also an indirect instance of the general
        classifier
        Thus, the specific classifier inherits the features of the more general classifier.
  - - - Tagged Values
        Tagged values are used to extend the properties of UML so that you can add additional
        information in the specification of a model element. It allows you to specify keyword value pairs
        of a model where keywords are the attributes. Tagged values are graphically rendered as string
        enclose in brackets
      - Constraints
        They are the properties for specifying semantics or conditions that must be held true at all the
        time. It allows you to extend the semantics of UML building block by adding new protocols.
        Graphically a constraint is rendered as string enclose in brackets placed near associated
        element.
      - Stereotypes
        Stereotypes allow you to increase vocabulary of UML. You can add, create new model
        elements, derived from existing ones but that have specific properties that are suitable to your
        problem domain. Stereotypes are used to introduce new building blocks that speak the language
        of your domain and look primitive. It allows you to introduce new graphical symbols.
  - - - Object Names
        Offers the name from the object and its class underlined as well
        as divided with a colon. We use a rectangle to represent an
        object in an Object Diagram
      - Attributes List object attributes inside a separate compartment.
        However, unlike classes, object attributes should have values assigned for them.
      - Link We use a link to represent a
        relationship between two objects.
      - We use a Dependency Relationships to show
        when one element depends on another element.
      - Association is a reference relationship between
        two objects (or classes).
      - Aggregation Aggregation represents a “has a” relationship.
      - Composition is a type of association where
        the child cannot exist independent of the other
  - - - Stereotypes allow you to increase vocabulary of UML. You can add, create new model
        elements, derived from existing ones but that have specific properties that are suitable to your problem domain. Stereotypes are used to introduce new building blocks that speak the language
        of your domain and look primitive. It allows you to introduce new graphical symbols
      - Tagged Values
        Tagged values are used to extend the properties of UML so that you can add additional
        information in the specification of a model element. It allows you to specify keyword value pairs
        of a model where keywords are the attributes. Tagged values are graphically rendered as string
        enclose in brackets
      - Constraints They are the properties for specifying semantics or conditions that must be held true at all the
        time. It allows you to extend the semantics of UML building block by adding new protocols. Graphically a constraint is rendered as string enclose in brackets placed near associated
        element
- - - - <<import>> - one package imports the functionality of other package
      - <<access>> - one package requires help from functions of other package.
- - - - Behavioral state machines
        Shows discrete behavior of a part of designed system through finite state transitions
      - Protocol state machines : Shows usage protocolor a lifecycle of some classifier, e.g. which operations of the classifier may be called in each state of the classifier, under which specific conditions, and satisfying some optional post conditions after the classifier transitions to a target state.
  - - - Activity:is a parameterized behavior represented as coordinated flow of actions.
        Activity: contains activity nodes which could be:Action, Object Control.
        Activities may contain actions of various kinds:
        Occurrences of primitive functions, such as arithmetic functions.
        Invocations of behavior, such as activities. Communication actions, such as sending of signals. Manipulations of objects, such as reading or writing
        attributes or associations
      - An activity is activity group for actions that have some common characteristic
        Partitions often correspond to organizational units or business actors in a business model.
        Partitions provide a constrained view on the behaviors invoked in activities. Constraints could be selected according to the type of the element that
        the partition represents. The following constraints are normative (standard) in UML
      - Action is a named element which represents a single atomic step within activity, i.e. that is not further decomposed within the activity. Activity
        represents a behavior that is composed of individual elements that are actions.
      - An node is an abstract activity node that is used to define object flows in an activity. Object nodes include pin, central buffer, parameter,
        expansion nodes
      - Control node is an activity node used to coordinate the flows between other nodes. It includes: initial node, flow final node, activity final node decision node ,merge node ,fork node ,join
        node.
      - Activity Edge: is an abstract class for the directed connections along which tokens or data objects flow between activity nodes. It includes control edges
        and object flow edges. The source and target of an edge must be in the same activity as the edge.
  - - - To describe the message flow in the system.
      - To describe the structural organization of the objects.
      - To capture the dynamic behaviour of a system.
      - To describe the interaction among objects.
    - - Timing diagram
        
        Purpose : Shows interactions when a primary
        purpose of the diagram is to reason about time Timing diagrams focus on conditions changing within
        and among lifelines along a linear time axis.
        
        Element:
        
        Destruction occurrence is a message occurrence
        which represents the destruction of the instance
        described by the lifeline. It may result in the
        subsequent destruction of other objects that this object owns by composition. No other occurrence
        may appear after the destruction event on a given lifeline
        
        Duration constraint is an interval constraint that
        refers to a duration interval. The duration interval is duration used to determine whether the constraint is satisfied
        
        State or Condition Timeline Timing diagram could show states of the
        participating classifier or attribute, or some testable conditions, such as a discrete or enumerable value
        of an attribute
        UML also allows the state/condition dimension be
        continuous. It could be used in scenarios where
        entities undergo continuous state changes, such as
        temperature or density.
        
        Time constraint is an interval constraint that refers to a time interval. The time interval is time expression used to determine whether the constraint is satisfied
        
        Lifeline is a named element which represents an
        individual participant in the interaction. While parts
        and structural features may have multiplicity greater
        than 1, lifelines represent only one interacting entity.
      - Sequence diagram
        
        Purpose: Most common kind of interaction diagrams
        which focuses on the message interchange between lifelines (objects).
        
        Element:
        
        Combined fragment is an interaction fragment
        which defines a combination (expression) of interaction fragments. A combined fragment is
        defined by an interaction operator and corresponding interaction operands. Through the
        use of combined fragments the user will be able to describe a number of traces in a compact and
        concise manner
        
        Interaction use is an interaction fragment which
        allows to use (or call) another interaction. Large and complex sequence diagrams could be simplified with
        interaction uses. It is also common to reuse some interaction between several other interactions.
        
        Message is a named element that defines one
        specific kind of communication between lifelines ofan interaction. The message specifies not only the
        kind of communication, but also the sender and thereceiver. Sender and receiver are normally two
        occurrence specifications (points at the ends of messages).
        
        A state invariant is an interaction fragment which
        represents a runtime constraint on the participants of invariant is an interaction fragment which
        represents a runtime constraint on the participants of variables, internal or external states, etc.
        
        Execution (full name - execution specification,
        informally called activation) is interaction fragmen which represents a period in the participant's lifetime
        when it is executing a unit of behavior or action within the lifeline, sending a signal to another
        participant, waiting for a reply message from another participant
        
        Destruction occurrence is a message occurrence
        which represents the destruction of the instance described by the lifeline. It may result in the
        subsequent destruction of other objects that this object owns by composition. No other occurrence
        may appear below the destruction event on a given
        
        Lifeline is a named element which represents an
        individual participant in the interaction. While parts
        and structural features may have multiplicity greater
        than 1, lifelines represent only one interacting entity
      - Communication diagram
        
        Purpose: Focuses on the interaction between
        lifelines where the architecture of the internal structure and how this corresponds with the
        message passing is central. The sequencing of
        messages is given through a sequence numbering
        scheme.
        
        Element:
        
        Lifeline is a named element which represents an
        individual participant in the interaction. While parts
        and structural features may have multiplicity greater
        than 1, lifelines represent only one interacting entity
        
        Message is a named element that defines one
        specific kind of communication between lifelines of
        an interaction. The message specifies not only the
        kind of communication, but also the sender and the
        receiver. Sender and receiver are normally two
        occurrence specifications (points at the ends of
        messages)..
      - Interaction overview diagram
        
        Purpose : Defines interactions through a variant of
        activity diagrams in a way that promotes overview of
        the control flow. Interaction overview diagrams focus
        on the overview of the flow of control where the nodes are interactions or interaction uses. The
        lifelines and the messages do not appear at this overview level
        
        Element:
        
        Fork node is a control node that has one incoming
        edge and multiple outgoing edges and is used to split incoming flow into multiple concurrent flows.
        Fork nodes are introduced to support parallelism inactivities. As compared to UML 1.5, UML 2.0 activity
        forks model unrestricted parallelism.
        
        Join node is a control node that has multiple
        incoming edges and one outgoing edge and is used to synchronize incoming concurrent flows. Join nodes are introduced to support parallelism in activities
        
        Merge node is a control node that brings together
        multiple incoming alternate flows to accept single outgoing flow. There is no joining of tokens. Merge
        should not be used to synchronize concurrent flows.
        
        An interaction diagram of any kind may appear
        inline as an invocation action. The inline interaction diagrams may be either anonymous or named.
        
        Decision node is a control node that accepts
        tokens on one or two incoming edges and selects one outgoing edge from one or more outgoing flows.
        Decision nodes were introduced in UML to support conditionals in activities.
        
        An interaction use may appear as an invocation
        action.
        
        Activity final node is a control final node that stops
        all flows in an activity. Activity final was introduced in UML 2.0.
        
        Duration constraint is an interval constraint that
        refers to a duration interval. The duration interval is duration used to determine whether the constraint is satisfied
        
        Flow final node is a control final node that
        terminates a flow. It destroys all tokens that arrive at it but has no effect on other flows in the activity.
        Flow final was introduced in UML 2.0.
        
        Time constraint is an interval constraint that refers
        to a time interval. The time interval is time expression used to determine whether the constraint is satisfied
        
        Initial node is a control node at which flow starts
        when the activity is invoked