UML for Business Analysis

Course Description:

This course is aimed at business analysts who are new to UML. Delegates are taught how to create activity diagrams to understand business processes, capture end user requirements using use cases and define data with domain models. Practical exercises and workshops help to reinforce the theory.

UML

Duration:

3 days

Prerequisites:

No prior UML experience is required.
A background in business analysis is helpful.

Equipment:

Webinar

For on-site delivery the customer should provide a suitable training room with a screen or projector to connect to our trainer’s laptop and a whiteboard or flipchart. All delegates require a PC or laptop running Enterprise Architect.

For webinar delivery delegates require a PC or laptop running Enterprise Architect with an Internet connection (a headset can be helpful). If you wish to test your environment join a test WebEx meeting: www.webex.com/test-meeting.html

Course Style:

40% theory, 60% practical.
Each module is accompanied by targeted exercises to allow delegates to apply the theory and become confident with new concepts and notation.

Delegate Handouts:

Each delegate receives a folder containing all the course slides and comprehensive theory notes which form excellent reference material. Folders also contain exercises and suggested solutions. Following successful completion of the course each delegate receives a certificate.

Course Modules:

  • Delegate background and objectives
  • Timetable and course outline

UML Teaching – 0.5 hour

  • Advantages of graphical notations
  • History of UML
  • Key UML diagrams
  • Business process models
  • Requirements capture
  • Static and dynamic models

UML Teaching – 0.5 hour

  • Importance of managing requirements
  • Differentiate needs from solutions
  • Requirements traceability
  • Strategies to control scope creep
  • Document requirements
  • Requirements levels and relationships
  • Categorise requirements

UML/SysML Teaching – 0.5 hour

  • What information to gather
  • Sources of information
  • Top 8 requirements elicitation techniques
  • When to use each technique
  • Common problems with elicitation

UML/SysML Teaching – 1 hour

Paper Exercises – 1.5 hours

  • Comparison with traditional requirements
  • Workshops and GUI prototypes
  • Model users as actors
  • External systems and timers
  • Actor definition and notation
  • Actor generalisation
  • Use case and scenario definition
  • Use case notation
  • Use case diagrams

UML/SysML Teaching – 1 hour

Paper Exercises – 1 hour

  • Use case specification
  • Use cases drive development
  • Include relationship
  • Extend relationship
  • Use case inheritance

UML/SysML Teaching – 0.5 hour

Paper Exercises – 0.5 hour

  • Document business activities and workflow
  • Model Sequential activities
  • Nested and structured activities
  • Decision and merge (conditional logic)
  • Fork and join (parallel logic)
  • Object states and action pins
  • Send, accept and time signals
  • Swimlanes for responsibility

UML Teaching – 1 hour

Paper Exercises – 1.5 hours

  • Model real world concepts
  • Classes and objects
  • Object identity and responsibilities
  • Encapsulation of attributes
  • Objects as intelligent black boxes
  • What makes a good class
  • How to discover classes
  • Whole-part relationships (aggregation)
  • Generalisation-specialisation (inheritance)
  • Polymorphism

UML Teaching – 1 hour

Paper Exercises – 1 hour

  • Domain classes and notation
  • Attributes
  • Associations and multiplicity
  • Whole-part relationships (aggregation)
  • Generalisation-specialisation (inheritance)

Paper Exercises – 2.5 hours

  • Quick reminder of UML notation
  • Role play to identify processes and activities
  • Build business process model

Paper Exercises – 1 hour

  • Quick reminder of UML notation
  • Create use case model
  • Planning session
  • Capture requirements details
  • Map non-functional requirements to use cases

Paper Exercises – 1 hour

  • Quick reminder of UML notation
  • Model use case logic as an activity diagram
  • Construct domain model