Introduction to UML Flashcards
What is UML?
Unified Modeling Language
A notation/diagraming standard used to describe the architecture and behavior of software systems
Two Main Types of
UML Diagrams
Structural Diagrams
Behavioral Diagrams
Structural Diagrams:
Summary
Focused on displaying the structure and organization of a system.
Created when discussing and designing the system architecture.
Emphasizes the “things” that are in the system being modeled.
Such as System Architecture, Components, Classes
Behavioral Diagrams:
Summary
Represent the Behavior of a system.
Emphasis on “what will happen” in the system being modeled.
Activities, Functionality, Use cases, etc.
UML Diagrams:
Major Structural Diagrams (7)
Important in this class:
- Class Diagram
Others:
- Package Diagram
- Profile Diagram
- Object Diagram
- Component Diagram
- Composite Structure Diagram
- Deployment Diagrams
UML Diagrams:
Major Behavioral Diagrams (7)
Important in this class:
- Use Case Diagram
- Activity Diagram
- Sequence Diagram
- State Machine Diagram
Others:
- Communication Diagram
- Timing Diagram
- Interaction Overview Diagram
Major Consideration Areas when
Modeling a Software System (4)
System Perspectives
Context Model
Structural Model
Behavioral Model
System Perspectives:
Perspectives to consider and model (4)
External Perspective
Interaction Perspective
Structural Perspective
Behavioral Perspective
System Perspectives:
Diagrams used for the
External Perspective
Context Diagram
Activity Diagram
System Perspectives:
Diagrams used for the
Interaction Perspective
Use Case Diagram
Sequence Diagram
System Perspectives:
Diagrams used for the
Structural Perspective
Class Diagram
Data Diagrams(Schemas?)
System Perspectives:
Diagrams used for the
Behavioral Perspective
State Diagram
Sequence Diagram
Context Diagram/Model:
Basic Description
Used to show the Operational Context of a system.
Shows various services and external systems that the system will interact with.
Represents the entire system as a single box with a boundary, connected to other systems that lie outside of the boundary.
Pareto Principle
Applied to UML diagrams
80% of problems
can be modeled
by 20% of UML
