uml training courses > integrated courses > business analysis system requirements definition

BPMN Poll
Should CRaG Systems provide courses using the Business Process Modelling Notation (BPMN)?
Yes
No
Business Analysis and System Requirements Definition using UML and Use Cases - Training Course - 3 Days Download a pdf version of this page
This UML training course teaches the use of the Unified Modelling Language v2.0 for business analysis and use cases for detailed system requirements definition within the context of a model-driven software development process. Industry best practice is taught for business process modelling, conceptual data modelling, business role modelling and system use case modelling at every appropriate level of abstraction. The strict approach ensures that the results satisfy the needs of both technical and non-technical stakeholders. The resulting models are traceable from individual elements of the business process through to each primitive system function. The techniques are taught to the level required for competence on a real project. Understanding is tested and improved with exercises based on a real-world project example and using a suitable case tool.
Delegates will learn:
  • The basics and the necessary detail of the Unified Modelling Language for business modelling
  • How to model a business process at multiple levels of abstraction using a hierarchy of UML activity diagrams (flow charts)
  • How to structure a business process model using activity diagrams, business use case diagrams and packages for multi-user access and change management
  • How to model business concepts and facts using classes and their relationships on class diagrams
  • How to model business worker roles together with line and operational relationships using classes, packages and their relationships
  • How to integrate business modelling techniques into a conventional approach to project documentation
  • How to map a business model into a system requirements model using actors, use cases and classes such that each element is traceable from one model to the other
  • How to create a first cut overview of functional requirements with actors and use cases on a use case diagram
  • How to write an effective use case description in a way that satisfies both non-technical and technical stakeholders
  • How to specify the flow of events as a basic flow and alternate flows
  • How to restructure the use case diagram to handle complex relationships between use cases without bloating the use case model
  • How to integrate the use case model with non-functional requirements, data requirements, business rules and screen prototyping
  • How a use case driven approach to requirements gathering improves estimation, project planning, test development and traceability
Suitable for:
Business Analysts, Business Consultants, Business Process Engineers, System Analysts and Project Managers with at least 2 years experience. This course is not suitable for those seeking certification as a step towards a qualification. See UML Certification for a detailed discussion.
On-Site Courses:
Training courses are delivered at the clients' site and attendance is limited to 12 students. Courses normally start at 9.30am on the first day and 9.00am on subsequent days. Courses normally finish at 5.00pm each day. The client is expected to provide an appropriate venue, equipment and refreshments. Required equipment includes an SVGA/XGA projector and screen, whiteboard or flipchart and at least one computer per two students loaded with a UML case tool. For a discussion on case tool use please see Case Tool Use on Courses. Printed course manuals for each student with copies of all presentations, exercises and solutions are provided. For a full discussion of on-site course issues please see On-Site Course Logistics.
Scheduled Public Courses:
This course is available as scheduled public training at our London Training Centre. Please see the Scheduled Public Courses page for details.


Training Course Outline

Day 1

Introduction
People - Course Structure - Object Orientation - Unified Modelling Language - Business Process Modelling - Use Cases and System Analysis - An Incremental Process for Modelling
Modelling Process Flow
Writing a Textual Description - Activity Diagrams - Activities and Control Flows - Conditions - Selection and Iteration - Swimlanes - Hierarchy and Concurrency - Modelling Primitive Process Steps
Modelling Process Flow Workshop
Modelling Process Structure
Modelling Hi-level and Group Processes - Modelling Process Structure with Packages - Business Use Cases and Business Actors - Business Use Case Diagrams - The Business Modelling Process

Day 2

Modelling Process Structure Workshop
Modelling Business Structure
The Conceptual Data Model - Business Entities - Relationships - Business Workers - Responsibilities - Organisation Structure
Business Structure Workshop
Mapping into System Requirements
Business versus System Use Cases - Mapping Actors - Mapping Activities and Swimlanes - Mapping Business Workers - Mapping the Conceptual Data Model
Mapping Workshop

Day 3

Specifying Functional Requirements with Use Cases
System Use Cases and Actors - Primitive Use Cases and the Basic Flow - Writing Effective Use Case Descriptions - Writing Sub-flows and Alternate Flows - 'Include' and 'Extend' Relationships - Modelling Browser-Based Applications
System Use Case Workshop
Requirements Gathering
Collecting Requirements Information - Mapping from the Business Model - Proof of Concept Prototypes - Requirements Documents - Estimating and Traceability - Incremental Development - Gaining Agreement
Requirements Gathering Workshop