Business Analysis in Practice: The Complete Lifecycle
(BA101, Live Instructor-Led Training, 5 days)


This SETC Certified Business Analysis course provides business professionals with a good overview of the end to end roles and responsibilities of a business analyst in the context of an application development project. The course begins with a discussion of the differences between a waterfall methodology and an iterative methodology as it applies to the business analyst role. It is worth noting that the Rational Unified Process is emphasized and discussed in detail in this course. Having situated business analysis within the larger context of the overarching methodology, a thorough discussion of information gathering techniques, requirements gathering, business use case development and the role of the business use case is undertaken. The focus is on the development of high quality business requirements and business use case documents in support of an organization’s business process reengineering or systems development activities. The course concludes with a discussion of the testing and change management disciplines and of their relationship to the overall business development lifecycle. Participants qualify for 35 PDU credits upon successful completion of this course.

Dates and Pricing

Nov 27 to Dec 1, 2017$2,500/person Jan 8 to Jan 12, 2018$2,500/person Feb 5 to Feb 9, 2018$2,500/person Mar 5 to Mar 9, 2018$2,500/person


Business Analysis
Overview of Business Analysis
Best Practices in Business Analysis
Benefits of Business Analysis
IIBA Knowledge Areas and Competencies
Preparing the Business Case
Business Analysis versus Project Management
Use Cases and the Analysis Process
Positioning Business Analysis within the Overall Project Lifecycle
Management of Requirements and Use Cases
A Bit of Terminology
The Business Analysis Process
Project Definition and Scoping
Choosing a Methodology
The Rational Unified Process
The Inception Phase
The Elaboration Phase
The Construction Phase
The Transition Phase
The MSF for Agile Software Development
Planning a Requirements Project
Why do we need a Requirements Work Plan?
Requirements throughout the Organization
The Business Architecture
Conducting a Feasibility Study
Determining Project Scope
Preparing the Business Case
Risk Management and Risk Response Strategies
Preparing the Decision Package
Profiling Stakeholders
Elements of a Requirements Work Plan
Elicitation Techniques: Towards Success
Elicitation Keys to Success
Elicitation Techniques
Constructing Questions that Deliver Results
JAD Sessions
Identifying Other Data Sources
One-On-One Meetings
Group Meetings
Dysfunctional Meetings
Meetings with Senior Executives
Some Challenges in Multicultural and Multilingual Environments
Interviewing for Results
Editing and Validating Requirements
The Requirements Shell
The Quality Gateway
Validating and Testing Requirements
Editing and Rewriting Requirements
Writing Test Cases
The Business Requirements Document
Validation Checklists
Conducting a Walkthrough
Types of Walkthroughs
Performing Walkthroughs
Writing Use Cases
Use Cases Revisited
Modeling Diagrams to Help Document and Analyze - Use Case Diagrams
Use Case Formats
Use Case Sections
The Supplementary Specification
When Are We Done?
Modeling Requirements
Process Mapping Procedure and Materials
Creating Process Maps
Alternative Graphical Models
Gap Analysis
Prioritizing Requirements
Assembling the Requirements Document
The Requirements Lifecycle
The Requirements Analysis Worksheet
Writing Test Cases for Requirements
Testing Documentation
Creating a Traceability Strategy for the Organization
Templates for Documents
Planning Document Distribution
Managing Changes
Types of Changes
Conducting a Change Meeting
Managing Change Requests
Implementing a Change Management Process
Test Plans, Test Cases and Bugs
A Traceability Strategy for the Organization
The Test Plan and Test Cases
The Master Plan
Components of a Master Test Plan
The Test Design Specification
Writing Test Cases
Test Metrics
About Defects
Reporting Bugs