For the PM: learn what UML artifacts to expect from your BAs over the lifecycle of an iterative, incremental IT project using Unified Process – the open source process upon which IBM RUP was developed.

For the BA: learn how and when to produce UML documentation on an iterative project and how to use UML techniques to guide and improve requirements workshop sessions.

This is not just a theory course: you’ll gain practical experience facilitating and documenting with the UML over the course of a RUP project as you work through a case study.

You’ll begin by learning the basics of the iterative, incremental approach to managing IT projects, the disciplines and roles of the Unified Process (UP) and how these map to the PM and BA roles. Then you’ll learn and experience how the BA uses UML concepts and techniques during the project lifecycle to elicit, analyze and document requirements.


BAs and PMs working on projects managed using iterative, incremental development and that follow the UML standard




2 Days

Outline for UML for the IT BA Overview (with Unified Process) Training

1. Introduction to UP

  • What is the Unified Process?
  • Properties of iterative, incremental development
  • Unified Process roles, artifacts, activities and disciplines
  • UP and the PM
  • UP and the BA: Mapping the BA to Unified Process roles and disciplines

2. Projects and the Application of UP

  • use-cases and UP disciplines
  • UP phases and iterations
  • Iteration strategies

3. Analyzing business services with business use-cases

  • Business use-case, Worker, Business Actor
  • Business use-case diagram
  • Documenting the business use-case using activity diagrams with partitions

4. Analyzing user requirements with use-cases

  • Deriving use-cases from business use-case
  • Tips for modeling and describing use-cases
  • Definition of actors, use-cases
  • Use-case diagram
  • Documenting the use-case: Basic and Alternate Flows
  • Introduction to inclusion and extension use-cases

5. Analyzing workflow and complex requirements

  • Using activity diagrams to describe complex flows within a use-case
  • Control flow, decision, guard, merge, activity, fork and join

6. Analyzing Lifecycle of Business Objects with State Machine Diagrams

  • Use of state machine diagrams to describe business objects across use-cases
  • Business objects
  • The lifecycle of a business object
  • Modeling states, transitions, events and guards

7. Analyzing Business Rules using Structural Object-Oriented Modeling (Class Diagrams)

  • Structural analysis
  • Entity classes, generalization, aggregation, association
  • Using class diagrams to define rule that apply across system use-cases

8. Putting it all together

  • Linking the structural and dynamic models: Adding class diagrams to system use-case descriptions
  • Verifying the 2 models against each other
  • Review of UML tools over the course of a UP project: case study