Uml Tutorial

• Interview Questions
• Practice Test
• Pragnyameter Exam
• All Tutorials
• Job Search

What is UML tutorial?

UML stands for Unified Modeling Language which is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems. UML was initially developed by the Object Management Group (OMG) in January 1997. This tutorial provides indepth understanding on UML.

Audience

This tutorial is mainly prepared for beginners to make them understand about the basic concepts of UML. Once you learn this tutorial you will become expertise in UML.

Prerequisites

To learn this tutorial no specific skill is required and basic enthusiasm to learn and acquire knowledge on UML is enough.

UML Tutorial: List of Topics

• Object-oriented Analysis And Design
  • What Will You Learn? Is It Useful?
  • The Most Important Learning Goal?
  • What Is Analysis And Design?
  • What Is Object - Oriented Analysis And Design?
  • What Is The Uml?
  • Visual Modeling Is A Good Thing
  • History
• Iterative, Evolutionary, And Agile
  • What Is The Up? Are Other Methods Complement
  • What Is Iterative And Evolutionary Development?
  • What About The Waterfall Life Cycle?
  • How To Do Iterative And Evolutionary Analysis And Design?
  • What Is Risk-driven And Client-driven Iterative Planning?
  • What Are Agile Methods And Attitudes?
  • What Is Agile Modeling?
  • What Is An Agile Up?
  • What Are The Up Phases?
  • What Are The Up Disciplines?
  • How To Customize The Process? The Up Development Case
• Case Studies
  • What Is And Isn't Covered In The Case Studies?
  • Case Study Strategy: Iterative Development + Iterative Learning
  • Case One: The Nextgen Pos System
  • Case Two: The Monopoly Game System
• Inception Is Not The Requirements Phase
  • What Is Inception?
  • How Long Is Inception?
  • What Artifacts May Start In Inception?
  • How Much Uml During Inception?
• Evolutionary Requirements
  • Definition: Requirements
  • Evolutionary Vs. Waterfall Requirements
  • What Are Skillful Means To Find Requirements?
  • What Are The Types And Categories Of Requirements?
  • How Are Requirements Organized In Up Artifacts?
• Use Cases
  • Definition: What Are Actors, Scenarios, And Use Cases?
  • Use Cases And The Use-case Model
  • Motivation: Why Use Cases?
  • Definition: Are Use Cases Functional Requirements?
  • Example: Process Sale, Fully Dressed Style
  • What Do The Sections Mean?
  • Notation: Are There Other Formats? A Two-column Variation
  • Applying Uml: Use Case Diagrams
  • Motivation: Other Benefits Of Use Cases? Requirements In Context
  • Process: How To Work With Use Cases In Iterative Methods?
• Other Requirements
  • How Complete Are These Examples?
  • Guideline: Should We Analyze These Thoroughly During Inception?
  • Guideline: Should These Artifacts Be At The Project Website?
  • Commentary: Supplementary Specification
  • Nextgen Example: (partial) Vision
  • Commentary: Vision
  • Commentary: Glossary (data Dictionary)
  • Commentary: Domain Rules
• Iteration 1 Basics
  • Iteration 1 Requirements And Emphasis: Core Ooa/d Skills
  • Process: Inception And Elaboration
  • Process: Planning The Next Iteration
• Domain Models
  • What Is A Domain Model?
  • Motivation: Why Create A Domain Model?
  • Guideline: How To Create A Domain Model?
  • Guideline: How To Model The Unreal World?
  • Associations
  • Attributes
  • Example: Attributes In The Domain Models
  • Process: Iterative And Evolutionary Domain Modeling
• System 'sequence Diagrams
  • Example: Nextgen Ssd
  • What Are System Sequence Diagrams
  • Motivation: Why Draw An Ssd?
  • Applying Uml: Sequence Diagrams
  • What Is The Relationship Between Ssds And Use Cases?
  • How To Name System Events And Operations?
  • How To Model Ssds Involving Other External Systems?
  • Process: Iterative And Evolutionary Ssds
• Operation Contracts
  • Definition: What Are The Sections Of A Contract?
  • Definition: What Is A System Operation?
  • Definition: Postconditions
  • Guideline: Should We Update The Domain Model?
  • Guideline: When Are Contracts Useful?
  • Guideline: How To Create And Write Contracts
  • Applying Uml: Operations, Contracts, And The Ocl
  • Process: Operation Contracts Within The Up
  • Uml Evolution
• Requirements To Design-iteratively
  • Iteratively Do The Right Thing, Do The Thing Right
  • Provoking Early Change
  • Didn't All That Analysis And Modeling Take Weeks To Do?
• Logical Architecture And Uml Package Diagrams
  • What Is The Logical Architecture? And Layers?
  • What Is Software Architecture?
  • Applying Uml: Package Diagrams
  • Guideline: Design With Layers
  • Guideline: The Model-view Separation Principle
• On To Object Design
  • Agile Modeling And Lightweight Uml Drawing
  • Uml Case Tools
  • Designing Objects: What Are Static And Dynamic Modeling?
  • Other Object Design Techniques: Crc Cards
• Uml Interaction Diagrams
  • Sequence And Communication Diagrams
  • Novice Uml Modelers Don't Pay Enough Attention To Interaction Diagrams!
  • Common Uml Interaction Diagram Notation
  • Basic Sequence Diagram Notation
  • Basic Communication Diagram Notation
• Uml Class Diagrams
  • Applying Uml: Common Class Diagram Notation
  • Definition: Design Class Diagram
  • Definition: Classifier
  • Operations And Methods
  • Uml Keywords
  • Stereotypes, Profiles, And Tags
  • Uml Properties And Property Strings
  • Dependency
  • Uml Interfaces
  • Constraints In Uml Diagrams
  • Association Class
  • User-defined Compartments
• Grasp: Designing Objects With Responsibilities
  • Object Design: Example Inputs, Activities, And Outputs
  • Responsibilities And Responsibility-driven Design
  • Grasp: A Methodical Approach To Basic Oo Design
  • Define Patterns
  • Where Are We Now?
  • Applying Grasp To Object Design
• Object Design Examples With Grasp
  • What Is A Use Case Realization?
  • Artifact Comments
  • What's Next?
  • Use Case Realizations For The Monopoly Iteration
  • Process: Iterative And Evolutionary Object Design
• Designing For Visibility
  • What Is Visibility?
• Mapping Designs To Code
  • Programming And Iterative, Evolutionary Development
  • Mapping Designs To Code
  • Creating Methods From Interaction Diagrams
  • Collection Classes In Code
  • Defining The Sale.makelineitem Method
  • Test-driven Or Test-first Development
• Test - Driven Development And Refactoring
  • Test-driven Development
  • Refactoring
• Uml Tools And Uml As Blueprint
  • Forward, Reverse, And Round - Trip Engineering
  • What Is A Common Report Of Valuable Features?
  • What To Look For In A Tool?
• Iteration 2 - More Patterns
  • From Iteration 1 To 2
  • Iteration - 2 Requirements And Emphasis: Object Design And Patterns
• Quick Analysis Update
  • Case Study: Nextgen Pos
  • Case Study: Monopoly
• Grasp: More Objects With Responsibilities
  • Polymorphism
  • Pure Fabrication
  • Indirection
  • Protected Variations
• Applying Gof Design Patterns
  • Adapter (gof)
  • "analysis" Discoveries During Design: Domain Model
  • Factory
  • Singleton (gof)
  • Strategy (gof)
  • Composite (gof) And Other Design Principles
  • Facade (gof)
  • Observer/publish - Subscribe/delegation Event Model (gof)
• Iteration 3 Intermediate Topics
  • Nextgen Pos
  • Monopoly In Uml
• Uml Activity Diagrams And Modeling
  • How To Apply Activity Diagrams?
  • More Uml Activity Diagram Notation
  • Guidelines
  • Process: Activity Diagrams In The Up
• Uml State Machine Diagrams And Modeling
  • Definitions: Events, States, And Transitions
  • How To Apply State Machine Diagrams?
  • More Uml State Machine Diagram Notation
  • Process: State Machine Diagrams In The Up
• Relating Use Cases
  • The Include Relationship
  • The Extend Relationship
  • The Generalize Relationship
• Domain Model Refinement
  • New Concepts For The Nextgen Domain Model
  • Generalization
  • Defining Conceptual Superclasses And Subclasses
  • When To Define A Conceptual Subclass?
  • When To Define A Conceptual Superclass?
  • Modeling Changing States
  • Association Classes
  • Aggregation And Composition
  • Association Role Names
  • Derived Elements
  • Qualified Associations
  • Reflexive Associations
• More Ssds And Contracts
  • New System Sequence Diagrams
• Architectural Analysis
  • Process: When Do We Start Architectural Analysis?
  • Architectural Analysis
  • Common Steps In Architectural Analysis
  • The Art : Resolution Of Architectural Factors
  • Process: Iterative Architecture In The Up
• Logical Architecture Refinement
  • Example: Nextgen Logical Architecture
  • Collaborations With The Layers Pattern
  • Other Layer Pattern Issues
  • Model - View Separation And
• Package Design
  • Package Organization Guidelines
• More Object Design With Gof Patterns
  • Example: Nextgen Pos
  • Handling Failure
  • Failover To Local Services With A Proxy (gof)
  • Designing For Non-functional Or Quality Requirements
  • Accessing External Physical Devices With Adapters
  • Abstract Factory (gof) For Families Of Related Objects
  • Handling Payments With Polymorphism And Do It Myself
• Designing A Persistence Framework With Patterns
  • The Problem: Persistent Objects
  • Frameworks
  • Key Ideas
  • Uml Data Modeling Profile
  • Accessing A Persistence Service With A Facade
  • Mapping Objects: Database Mapper Or Database Broker Pattern
  • Configuring Mappers With A Mapperfactory
  • Consolidating And Hiding Sql Statements In One Class
  • Transactional States And The State Pattern
  • Designing A Transaction With The Command Pattern
  • Lazy Materialization With A Virtual Proxy
  • How To Represent Relationships In Tables
  • Unresolved Issues
• Uml Deployment And Component Diagrams
  • Deployment Diagrams
  • Component Diagrams
• Documenting Architecture: Uml & The N+1 View Model
  • The Sad And Its Architectural Views
  • Example: A Nextgen Pos Sad
  • Example: A Jakarta Struts Sad
  • Process: Iterative Architectural Documentation
• More On Iterative Development And Agile Project Management
  • How To Plan An Iteration?
  • Adaptive Versus Predictive Planning
  • Phase And Iteration Plans
  • How To Plan Iterations With Use Cases And Scenarios?
  • The (in)validity Of Early Estimates
  • Organizing Project Artifacts