How to Develop and Use UML Models for Business Analysis

1. The Challenge of Business Systems and the Unified Modeling Language (UML)

• Business Views
• Changing How the Business Works
• Analysis of Business Systems Analysis
• Tracking What You Know You Don’t Know
• A Brief History of Methods
• The Reality of Current Methods
• The Critical Business Analyst Role
• Project Roles and Responsibilities
• Requirements Categorization
• Project Roles and Need to Know

2. Capturing Business Use Cases

• The Difference between Use Cases
• Introducing the Actor
• Naming Actors
• Use Case Diagram Symbols and Rules
• Naming Use Cases
• Use Case Diagram Conventions
• Drawing a Use Case Diagram
• Advanced Use Case Diagrams
• Of Business Events and Use Cases
• From Business Events to Use Cases
• Identifying Business Use Cases
• Inside the Use Case
• Purpose of a Business Use Case
• Purpose of a System Use Case
• Business Use Case Example: Process Payment
• First Cut Use Case
• Paths in a Use Case
• Numbering Schemata {Best Practices}
• Second Cut Use Case
• User Scenarios:
• A Bottom-Up Approach to Use Cases
• The Advantage of Scenarios
• Use Case Scenario Structure:
• Donald Pays For Insurance
• Extracting Use Cases from Scenarios
• Basic Use Case Documentation
• Requirements Categories Addressed

3. Using Business Events and Responses

• Nothing Happens Until Something Happens
• Our Area of Interest
• Business Events Defined
• Business Event Naming Convention
• Defining Business Events
• Finding Business Events
• Identifying Project Scope
• Confirming Project Scope
• Determining Event Responses
• Event Response Naming Convention
• Documenting Business Events
• Event/Response Table (v 1.0)
• Understanding Triggers
• Non-Triggered Events
• Scheduled Events
• Adding Event Triggers
• Event/Response Table (v 1.1)
• Additional Event/Response Information
• Event/Response Table (v 1.2)
• Visual Tools
• Event/Response Symbols and Conventions
• Event/Response Example Diagram
• Creating Event/Response Models
• Requirements Categories Addressed

4. The Static Structure of Things

• Business Views
• Why Object?
• What is a Class?
• Naming Classes
• Classes in the Real World
• Classes in Business Use Cases
• Elements of the Order
• Order Form Classes
• Order Form Methods
• Class Identification
• Associations vs Relationships
• Finding Associations
• Order Form Associations
• Association Adornments
• Adorned Associations
• Invoice Class Model
• Inheritance Relationships
• Creating Super- and Subclasses
• Inheriting Attributes and Methods
• Recognizing Inheritance Relationships
• Inheritance Class Exercise
• Aggregation and Composition
• Understanding Aggregation
• Finding Aggregate Relationships
• Aggregation and Composition
• Dependency Relationships
• Finding Dependencies
• Class Diagram of Website
• Dealing with Complexity
• Encapsulation and
• Information Hiding
• Polymorphic Methods
• Finding Classes, Attributes and Methods
• Adorning Class Diagrams
• Requirements Categories Addressed

5. Modeling Dynamic Behaviors

• Communications Channels
• Activity Diagramming Conventions
• Example of an Activity Diagram
• Creating an Activity Diagram
• Concurrency and More
• Modeling Concurrent Activities
• Introducing Swimlanes
• Activity Diagram with Swimlanes
• Modeling Swimlanes
• From Data Flow to Object Flow
• Introducing Object Flow
• Modeling Object Flow
• When to Use Activity Diagrams
• What’s Wrong with This Diagram?
• Understanding Object States
• Symbols and Conventions of State Diagrams
• State Diagram of the Book Class
• When do you Need a State Diagram?
• How To Find States and Triggers
• States versus Attributes
• Determining States and Attributes
• Modeling States of the Order Class
• Errors on a State Diagram
• Requirements Categories Addressed

6. Recap and Lessons Learned

• Review of UML Diagrams Covered
• Common UML Symbols
• Selecting the Right Models for the Project
• A New Language
• On Changing Requirements
• Requirements Categories Final Exam

7. Appendixes

3 days

Business Managers
Business Systems Analysis
Designers
Developers
Requirements Engineers
Systems Analysts
Test Engineers

How to Gather, Analyze, and Define Business System Requirements

How to Model, Analyze, and Improve Business Processes

How to Discover and Develop Use Cases

or equivalent training (or experience)

Our instructors have extensive experience in applying these techniques on projects with business experts from a wide variety of fields.