Home » Business Analyst Training  » IIBA Certified Business Analyst Professional CBAP

IIBA Certified Business Analyst Professional CBAP

For Professionals employed in Business Analysis, Project Management, Systems Analysis, Consulting or process improvement.

Course Contents

Stage 1: Core Concepts in Business Analysis

Stage 2: Enterprise Analysis and Making a Business Case

Stage 3: Introduction to Requirements Planning

Stage 4: Requirements Planning and Management

Stage 5: Eliciting Requirements

Stage 6: Analysing Requirements Using Models

Stage 7: Refining and Documenting Requirements

Stage 8: Communicating and Implementing Requirements

Course Code:

CBAP-2

Course Duration:

12 months

Typical Study Hours:

20 - 30 hours

Course Fees:

See our Fee Guide

Course Demo:

Request an online Course Demo

Study Prerequisite:

Business or Project Management experience.

Note that IIBA have their own requirement regarding minimum work experience, previous qualifications, references, etc, prior to taking the exam.

Additional Information for Stage 1:

• Core Concepts in Business Analysis
  • Business Analysis and Requirement Types
    • Describe the role of a business analyst.
    • Match the requirement types to their examples.
  • The Knowledge Areas of Business Analysis
    • Match the knowledge areas of business analysis to examples of their associated activities.
    • Identify how the knowledge areas of business analysis relate to one another.
  • Knowledge Skills in Business Analysis
    • Match the knowledge skill sets of business analysis to their associated skills.
  • Collaboration Skills in Business Analysis
  • Identify the skills associated with the collaboration skill sets of business analysis.
  • Leadership Skills in Business Analysis
    • Match the leadership skill sets to their associated skills.

^top

Additional Information for Stage 2:

• Enterprise Analysis and Making a Business Case
  • The Business Analyst and Enterprise Analysis
    • Match the strategic responsibilities of the business analyst to their associated activities.
    • Match the enterprise analysis activities performed by the business analyst to their descriptions.
  • The Business Architecture
    • Distinguish between the frameworks used to create and maintain the business architecture.
    • Distinguish among the techniques used to create and maintain the business architecture.
  • Conducting a Feasibility Study
    • Determine which techniques to use at various stages of a feasibility study
  • The Project Scope
    • Match the tasks involved in defining the scope of a project to examples of their associated activities.
  • Business Case Development
  • Identify examples of the types of activities undertaken during each stage of business case development.
  • Match the business case development techniques to the situations in which they are used.
  • Initial Risk Assessment
  • Match the steps involved in an initial risk assessment to the examples of their activities.
  • Project Assessment
  • Identify the activities associated with preparing a decision package.
  • Identify examples of how business analysts facilitate the project decision-making criteria of executive management.
  • Supporting a Business Analysis Project
    • Identify examples of how business analysts fulfill their responsibilities throughout the life of a project.

^top

Additional Information for Stage 3:

• Introduction to Requirements Planning
  • key Tasks for Planning and Managing Requirements
    • Identify the purpose of each of the key tasks involved in planning and managing requirements in a business analysis.
  • Planning Considerations
  • Identify the methodology-related best practices for planning and managing requirements for a project.
  • Identify the general considerations for planning and managing requirements for a project.
  • Planning Team Roles and Responsibilities
  • Use the criteria of the RACI matrix to determine the responsibilities of various roles during requirements planning and management.
  • Project Stakeholders
  • Match the techniques for drafting a stakeholder summary to their examples.
  • Work Division and Coordination
  • Determine the most appropriate work division strategy to apply to a project.
  • Match the strategies used to divide work to their examples.
  • Identify key concepts associated with the techniques used to implement a work division strategy for a project.

^top

Additional Information for Stage 4:

• Requirements Planning and Management
  • Identifying Risky Requirements
    • Identify requirements that appear to be a risk from a list of requirements.
  • Managing Requirements Risk
  • Identify the processes associated with the techniques used to define a risk response strategy.
  • Requirements Activities
  • Identify examples of activities associated with requirement-selection tasks.
  • Estimating Requirements
  • Match the tasks for estimating requirements activities to their descriptions.
  • Control Requirements Scope
  • Match the tasks for the maintenance of requirements scope to their purpose.
  • Identify examples of requirements problems that are highlighted in a traceability matrix.
  • Requirement Activity Metrics
  • Differentiate between product and project metrics.
  • Match the tasks for tracking metrics for projects to their activities.
  • Identify the key activities associated with tracking metrics for products.
  • Requirements Change
  • Identify the key tasks associated with the four stages of managing requirements change.

^top

Additional Information for Stage 5:

• Eliciting Requirements
  • The Task of Eliciting Requirements
    • Identify the key tasks for preparing for requirements elicitation.
    • Identify the key tasks associated with conducting requirements elicitation.
  • Recommended Practices for Eliciting Requirements
  • Evaluate a description of a requirements-elicitation process for its use of recommended practices.
  • Match requirements-elicitation best practices to the challenges that they overcome.
  • Document and Interface Analysis
  • Recognise scenarios in which document analysis is appropriate.
  • Match the task examples to the stages of interface analysis that they are associated with.
  • Prototyping and Reverse Engineering
  • Select the appropriate prototyping strategies for a given scenario.
  • Recognise situations where it would be appropriate to use reverse engineering to elicit requirements.
  • Observation
  • Analyse the use of the observation technique to elicit requirements for a project.
  • Distinguish between the two basic approaches for observation.
  • Surveys
  • Recognise key concepts associated with conducting surveys as a means of eliciting requirements.
  • Interviewing
  • Identify key concepts associated with each stage of requirements-elicitation interviews.
  • Brainstorming
  • Recognise examples of each of the tasks associated with the stages of brainstorming.
  • Focus Groups and Requirements Workshops
  • Identify best practices for running and reporting on focus group sessions.
  • Identify examples of best practices for running a requirements workshop.

^top

Additional Information for Stage 6:

• Analysing Requirements Using Models
  • Solution Development Methodologies
    • Match each analysis technique to the solution development methodology with which it is most closely associated.
  • Business Rules
  • Differentiate between the different types of business rules.
  • Process and Flow Modeling Techniques
  • Distinguish between the different types of process and flow modeling techniques.
  • Data Flow Diagrams
    • interpret key relationships in a data flow diagram.
  • Activity Diagrams
  • Determine the appropriate depiction of components in an activity diagram.
  • Data and Behavior Modeling Techniques
  • Distinguish between the different types of data and behavior modeling techniques.
  • Entity Relationship Diagrams
  • Perform key data modeling tasks.
  • Sequence examples of ERD modeling by stage.
  • Class Diagrams
  • Identify the components of a class diagram.
  • Usage Modeling Techniques
  • Distinguish between the different types of usage modeling techniques.
  • Use Case Modeling
  • Distinguish between user stories and use case descriptions.
  • Interpret the relationships among the elements depicted in a use case diagram.

^top

Additional Information for Stage 7:

• Refining and Documenting Requirements
  • Requirements Decomposition
    • Identify key concepts associated with decomposition techniques.
  • Functional Requirements
    • Match the functional requirements documentation techniques to the situations in which they are typically selected.
  • Quality of Service Requirements
  • Classify quality of service requirements according to type.
  • Assumptions and Constraints
  • Distinguish between the assumptions and constraints typically documented by a business analyst.
  • Requirements Attributes
  • Determine the most appropriate attributes to attach to a requirement.
  • Requirements Documents
  • Differentiate between the most common types of requirements documents.
  • Requirements Validation and Verification
  • Identify the characteristics of each of the three techniques for validating requirements.
  • Distinguish between examples of valid and invalid requirements.

^top

Additional Information for Stage 8:

• Communicating and Implementing Requirements
  • Requirements Communication and Conflict Management
    • Identify the considerations for developing a requirements communication plan.
    • Recognise how to manage conflicting requirements appropriately.
  • Requirements Package Formatting
    • Determine the appropriate format for a requirements package.
  • Requirements Packages and Presentations
  • Make key decisions when creating a requirements package.
  • Differentiate between situations that require formal and informal requirements presentations.
  • Formal Requirements Review
  • Sequence the steps for conducting a formal requirements review.
  • Solution Review and Revision
  • Recognise tasks associated with the steps involved in reviewing and revising solutions.
  • Solution Selection
  • Identify situations that typically call for a certain type of software solution.
  • Solution Testing
  • Evaluate a test strategy for a solution.
  • Solution Implementation
  • Identify key concepts associated with the best practices for implementing a solution.
  • Post-implementation Activities
  • Identify the best practices for closing a project.
  • Identify best practices associated with the three stages of a post-implementation review.

^top

<< back to previous page