直播班
(1人评价)
CBAP®商业分析师(高级)认证培训课程

CBAP提升业务思考能力与分析水平,培养商业头脑。

价格 ¥ 5000.00
承诺服务
该课程属于 CBAP®国际商业分析师认证备考班
请加入后再学习

系统介绍课程

需要记忆每个领域包含的任务名称,及输入输出

领域的相关方/技巧等重在理解

需求分析的旧版定义:一组任务和技术如何应用到工作中的组织架构/流程/运作方式等分析,在分析中发现问题,提供解决方案解决问题,为组织带来价值 。

需求分析的新版定义:Business analysis is the practice of enabling change in an enterprise(包含公司外的上下有) by defining  needs and recommending solutions that deliver value to stakeholders. 
 
needs:工作中需要解决的问题,或机会。通常不清晰,需要和干系人调研。调研干系人,干系人可能说的是解决方案,或有误解。需求分析需要定义问题,需要用ppt等方式呈现问题。
requirements:是收集问题后的分析结果
 
stakeholders:工作中的相关方/人(包含解决方案的施加方)
 
BA这个工作是做什么的:是客户和解决团队之间沟通的桥梁。为解决方案的设计和实施提供输入,也就是requirements。
 
Business analysis may be performed within the boundaries of a project or throughout enterprise evolution and continuous improvement. 
 
BABOK领域内定位BA是在项目中或在公司中(业务顾问)
PMI领域内定位BA是在项目中的角色
 
It can be used to understand the current state, to define the future state, and to determine the activities required to move from the current to the future state.
分析现有流程或未来希望达成的流程
[展开全文]

课程分成12个单元,基本参考BABOK书籍

第一单元对应第一章

介绍背景/结构/重要概念

第二单元对应第二章

介绍重要概念:需求/干系人

第三到第八章

需求分析的六大领域,每个领域有任务,任务的输入输出是什么

第九章

基本能力:沟通/协调

第十章

六大领域工作中需要的方式方法:interview

考试实际占了比重

第十一章 视角

在特别行业的应用:IT 敏捷 业务流程管理 商业智能 商业架构

第十二单元

不是BABOK书内容,是考试指导 

[展开全文]

Agile-iteration-just enough, just in time

Prective-requirement are define at a rather early stage-deliverables at the final stage

[展开全文]

Roles and permission matrix

use case

Crud: create read update delete

[展开全文]

Define, validate

focus group: qualitative measures

current

Acceptance (one solution, pass/fail) and evaluation (multiple solutions, assign different weights, ranking) criteria 

[展开全文]

The previous chapters about requirements: elicitation, analysis.

In use-existing, in varying stages of development: proto, beta, operational release

[展开全文]

Opportunity cost--by opting A you can't enjoy the benefits from choosing B and C

constraints on solutions: time, budget

Dependencies on other initiatives-about consideration

Sponsor: usually important decision maker

[展开全文]

prioritisation: Must Could Should What

Identify improvement opportunities 

better access to information

identify additional capabilities

Requirement allocation-solution components / release

Determing solution approach-understanding of requirements , solution architecture

Design options: personnel, section, operational structures, policy, rules, relationships, aapplications

Mind mapping

RFI-information, RFQ-quotation, RFT-Tender, RFP-Prposal

[展开全文]

Can adopt various formality based on differing needs of the stkhldrs

audit and security-non functional requirements

more than one viewpoints, interrelated with each other-tracing requirements

User stories or use case--functional requirements 

Elicitstion results-business analysis

[展开全文]

Assumption 

Alignment with solution scope

Tracing requirements-new requirements, change requirements

[展开全文]

Review 
Walkthrough-predictive-group

single issue review

ad hoc-temporary 

[展开全文]

Use case

Main success flow

Alternative and exception flow

1 sprint (1-4wks)

[展开全文]

Metadata repository

Primitive data elements

Composite data elements

[展开全文]

business policy, directive, broadly

business rule specific, testable directive

Definition rules (can only be misapplied)

Behavioral rules (can be violated)

override by authorised actor, with explanation, with no active enforcement

Business Rules Catalogue

 

 

 

[展开全文]

Model

Mactrices

Diagram

People & roles

Rationale (scope model, root cause analysis)

Activity flow (use case, user stores, processes)

Capability (functions)

Data & information (Data dictionary, Glossary, interface)

attributes: prioritisation, value, source

Notations (UML, informal)

[展开全文]

授课教师

国际商业分析协会
IIBACHINA分会会长

课程特色

视频(103)