Changing the way you learn

THINGS
1. Are the most important building blocks of UML.
2. STRUCTURAL THINGS
  1. Define the static part of the model. They represent the physical and conceptual elements.
  2. CLASS
    1. Class represents a set of objects having similar responsibilities.
  3. INTERFACE
    1. Interface defines a set of operations, which specify the responsibility of a class.
  4. COLLABORATION
    1. Collaboration defines an interaction between elements.
  5. USE CASE
    1. Use case represents a set of actions performed by a system for a specific goal.
  6. COMPONENT
    1. Component describes the physical part of a system.
  7. NODE
    1. A node can be defined as a physical element that exists at run time.
3. BEHAVIORAL THINGS
  1. Consists of the dynamic parts of UML models.
  2. INTERATION
    1. Interaction is defined as a behavior that consists of a group of messages exchanged among elements to accomplish a specific task.
  3. STATE MACHINE
    1. State machine is useful when the state of an object in its life cycle is important. It defines the sequence of states an object goes through in response to events. Events are external factors responsible for state change
4. GROUPING THINGS
  1. Can be defined as a mechanism to group elements of a UML model together.
  2. PACKAGE
    1. Package is the only one grouping thing available for gathering structural and behavioral things.
5. ANNOTATIONAL THINGS
  1. Can be defined as a mechanism to capture remarks, descriptions, and comments of UML model elements.
  2. NOTE
    1. It is the only one Annotational thing available. A note is used to render comments, constraints, etc. of an UML element.
RELATIONSHIPS
1. Is another most important building block of UML. It shows how the elements are associated with each other and this association describes the functionality of an application.
2. DEPENDENCY
  1. Dependency is a relationship between two things in which change in one element also affects the other.
3. ASSOCIATION
  1. Association is basically a set of links that connects the elements of a UML model. It also describes how many objects are taking part in that relationship.
4. GENERALIZATION
  1. Generalization can be defined as a relationship which connects a specialized element with a generalized element. It basically describes the inheritance relationship in the world of objects.
5. REALIZATION
  1. Realization can be defined as a relationship in which two elements are connected. One element describes some responsibility, which is not implemented and the other one implements them. This relationship exists in case of interfaces.
UML DIAGRAMS
1. UML diagrams are the ultimate output of the entire discussion. All the elements, relationships are used to make a complete UML diagram and the diagram represents a system.
2. STRUCTURAL MODELING
  1. Represents the framework for the system and this framework is the place where all other components exist.
  2. Classes diagrams
  3. Objects diagrams
  4. Deployment diagrams
  5. Package diagrams
  6. Composite structure diagram
  7. Component diagram
3. BEHAVIORAL MODELING
  1. Behavioral model describes the interaction in the system. It represents the interaction among the structural diagrams. Behavioral modeling shows the dynamic nature of the system.
  2. Activity diagrams
  3. Interaction diagrams
  4. Use case diagrams
4. ARCHITECTURAL MODELING
  1. Architectural model represents the overall framework of the system. It contains both structural and behavioral elements of the system. Architectural model can be defined as the blueprint of the entire system. Package diagram comes under architectural modeling.

Next up

UML - Elements

Description

Resource summary

Media attachments

Similar

	Created by José Alfredo Santes Benítez almost 7 years ago