UML for Business Analysis

* Summary
* Objectives
* Prerequisites
* Detailed Outline

Course Duration :

Summary:

UML is a graphical language; the remit of which has traditionally been object oriented design. UML can now be used to cover the full capture of business problems and solutions, from initial inception of a business idea through to the low level design of software. This course will focus on the capture of business requirements to produce a business model. In a typical project process, this business model would then be handed over to the software designers to act as the foundation of their object orientated software design.

The course will feature Business Process Modelling, Use Cases, and Domain Modelling Workshops to establish the requirements for a complex, real life business.

Objectives:

By the end of the course attendees will:

Be able to use the techniques supported by UML to produce a business requirements model
Be able to construct Business Process Models, Use Case Models, Domain (Class) Models and State Machines
Have gained an understanding of the techniques used in Object Orientated Design using the UML Interaction Diagrams
Be able to adapt the UML Interaction diagrams to general business analysis uses
Have an appreciation of the function of all UML 2.0 diagrams

Prerequisites:

There are no prerequistes to this course, although the course is targeted at experienced business analysts who need to apply the UML to their work in as efficient and comprehensive a way as possible. Those who have no business experience at all, may prefer our Introduction to Business Analysis Using UML course, which spends more time focusing on Facilitated Workgroups, Interviewing Skills and other general business analysis techniques.

Detailed Outline:

Introducing UML
- Models vs Diagrams
- What UML is and what it is not
- Modelling Notations
- The Waterfall Lifecycle
- The Unfied Process
- The Interative Lifecycle

Object Orientation Basics
- Pros and Cons Procedural Programming
- Pros and Cons of Object Orientation
- Classes
- Encapsulation
- Collaboration
- Object to Relational Mapping
- Persistence

Business Modelling
- Beginning the Analysis
- Business Model
- Business Processes
- Using the UML to model processes
- UML Stereotypes
- Eriksson-Penker extensions
- Business Process Overviews
- Business Actors
- Business Workers
- Case Workers
- Process Activity Diagram

Use Cases
- Use Cases as structured requirements
- Granularity of Use Cases
- Actors
- Discovering Use Cases from Business Processes
- Primary and Secondary Actors
- Ranking Use Cases
- Specifying Use Cases
- Use Case Descriptions
- Non functional requirements
- Preconditions
- Postconditions
- Main Flow
- Extension Flows
- Style Guidelines

The Domain Model
- Domain Modelling
- Finding Classes
- Notation in the UML
- Attributes
- Associations
- Multiplicities
- CRUD Matrices

The State Machine
- Capturing Business Rules
- Events and States
- Basic Notation
- Superstates and Substates
- Conditional Transitions
- Actions
- Finding Use Cases from the State Model

Detailed Use Case Descriptions
- Use Case Storyboards
- Preconditions
- Postconditions
- Main Flow
- Extension Flow
- Graphical Form

Interaction Modelling - The Communication Diagram
- Objects and Associations
- Method Calls
- Parameters
- Return Values
- Looping
- Creating Objects
- Mapping to the Design Class Diagram

Interaction Modelling - The Sequence Diagram

A Resume of all UML 2.0 Diagrams
- Behavioural Diagrams
- Structural Diagrams
- Interaction Overview Diagram
- Timing Diagram
- Component Diagram
- Composite Structure Diagram
- Deployment Diagram
- Object Diagram
- Model Driven Architecture (MDA)

Next >

Your are currently viewing: Home

Courses

UML Analysis and Design

UML for Business Analysis