Pages

Monday, 28 September 2015


UML


UML is a standard, visual modeling language that comes into play in all stages of the software development life cycle: modeling business processes, conceptualizing system functions, visualizing and documenting software artifacts, developing object-oriented software. In other words, UML is a language that allows the writing of a software system’s blueprint in a way that can be easily understood by various stakeholders, including business analysts, project managers, system and database architects, etc. This introduction, by VTC author and corporate trainer Nancy Conner, covers UML basics and goes into detail about the most common kinds of UML diagrams. To begin learning, simply click the links.

Introduction

Welcome to the UML
Object Orientation 1: Objects & Classes
Object Orientation 2: Relationships
Object Orientation 3: Polymorphism

Types of Diagrams: An Overview

The 4+1 Model
Static & Dynamic Approaches
Use Case & Class Diagrams
Object & Package Diagrams
State & Activity Diagrams
Sequence & Communication Diagrams
Component & Deployment Diagrams

Use Case Diagrams

Use Case Basics
Modeling Use Case Elements
A Use Case Diagram for an ATM
The<> Dependency
The<> Dependency
Generalization
Putting It All Together

Class Diagrams: Basic Concepts

Classifiers: Classes & Objects
Attributes & Operations
Stereotypes
Associations & Multiplicity
Association Classes
Aggregation & Composition
Generalization
Realization
Dependency
Constraints & Notes
Finding Classes

Advanced Class Diagrams

Abstract Classes & Operations
Interfaces
Collaborations
Templates

Object Diagrams

Objects/Instances
Connecting Objects
From Class Diagram to Object Diagram

Package Diagrams

Packages
Visibility
Relationships among Packages
Accessing & Importing Packages
Merging Packages
Use Case Packages
When to Use Package Diagrams

State Diagrams

States & Transitions
State Activities
Pseudostates: Initial & Terminate
Pseudostates: Junction & Choice
Composite States
Pseudostates: Fork & Join
Pseudostates: Entry & Exit Points
Pseudostates: Deep & Shallow History
Protocol State Machines

Activity Diagrams

Activity Diagrams: Basic Symbols
Alternative & Parallel Paths
Object Nodes
Pins
Subactivity Diagrams
Signals
Handling Exceptions
Interruptible Activity Regions
Expansion Regions
Using Swim Lanes

Sequence Diagrams

Objects, Lifelines & Messages
Kinds of Messages
Create & Destroy Messages
Boundary, Entity & Control Elements
Interaction Frames
Fragments: Options
Fragments: Alternatives
Fragments: Loops
Fragments: Parallels
Sequence Diagrams & Use Cases

Communication Diagrams

Objects, Links & Messages
Nested Messages
Self-Messages
Conditional Messages
Looping Messages
Parallel Messages
Sequence vs Communication Diagrams

Component Diagrams

Introducing Components
Components & Interfaces
Realizations & Dependencies
Component Compartments
Black Box & White Box Views
Ports & Delegation Connectors
Component Stereotypes

Deployment Diagrams

What a Deployment Diagram Shows
Nodes
Artifacts
Manifestation
Communication Paths
Deployment Specifications

Wrap up

Choosing a Modeling Tool
Wrap Up

Credits

About the Author

No comments:

Post a Comment