Ôn tập CCBA có hệ thống
Tổng hợp kiến thức CCBA (Certification of Capability in Business Analysis) theo BABOK Guide v3: 6 Knowledge Areas, BACCM, Techniques, Stakeholders và 100+ câu quiz kèm giải thích.
BACCM — 6 Core Concepts
Sự thay đổi
Nhu cầu
Giải pháp
Bên liên quan
Giá trị
Bối cảnh
BACCM — Business Analysis Core Concept Model
6 core concepts — mỗi concept được định nghĩa bởi 5 concepts còn lại. Dùng để đánh giá chất lượng và tính hoàn chỉnh của công việc BA.
🔄 ChangeSự thay đổi
Act of transformation in response to a need. Change works to improve enterprise performance. Can be strategic, tactical, or operational.
🎯 NeedNhu cầu
A problem or opportunity to be addressed. Needs can cause changes, and changes can cause needs.
💡 SolutionGiải pháp
A specific way of satisfying one or more needs in a context. A solution satisfies needs in the context where it is implemented.
👥 StakeholderBên liên quan
A group or individual with a relationship to the change, the need, or the solution. Stakeholders are defined by their interest.
💎 ValueGiá trị
The worth, importance, or usefulness of something to a stakeholder within a context. Value can be tangible or intangible.
🌐 ContextBối cảnh
The circumstances that influence, are influenced by, and provide understanding of the change. Includes attitudes, behaviors, beliefs, culture, and agreements.
6 Knowledge Areas
Mỗi KA là tập hợp các tasks liên quan logic (không theo thứ tự). Tasks có thể thực hiện sequentially, iteratively, hoặc simultaneously.
📋 BA Planning & Monitoring
Organize & coordinate BA efforts.
- Plan BA Approach (predictive vs adaptive)
- Plan Stakeholder Engagement
- Plan BA Governance
- Plan BA Information Management
- Identify BA Performance Improvements
🗣 Elicitation & Collaboration
Prepare, conduct elicitation & confirm results.
- Prepare for Elicitation
- Conduct Elicitation
- Confirm Elicitation Results
- Communicate BA Information
- Manage Stakeholder Collaboration
🔄 Requirements Life Cycle Management
Manage requirements from inception to retirement.
- Trace Requirements
- Maintain Requirements
- Prioritize Requirements
- Assess Requirements Changes
- Approve Requirements
🎯 Strategy Analysis
Identify business need, define change strategy.
- Analyze Current State
- Define Future State
- Assess Risks
- Define Change Strategy
📐 Requirements Analysis & Design Definition
Structure, model, validate requirements & designs.
- Specify and Model Requirements
- Verify Requirements
- Validate Requirements
- Define Requirements Architecture
- Define Design Options
- Analyze Potential Value & Recommend Solution
📊 Solution Evaluation
Assess performance & value of solution in use.
- Measure Solution Performance
- Analyze Performance Measures
- Assess Solution Limitations
- Assess Enterprise Limitations
- Recommend Actions to Increase Solution Value
Requirements Classification Schema
4 loại requirements + distinction giữa Requirements vs Designs.
Goals, objectives, outcomes mô tả WHY a change is initiated. Apply to whole enterprise, business area, or initiative.
Needs of stakeholders that must be met to achieve business requirements. Bridge giữa business & solution requirements.
Capabilities & qualities of solution. Chia thành:
• Functional — behavior & information
• Non-functional (QoS) — conditions, qualities
Capabilities for transition from current → future state. Temporary — not needed once change complete. E.g.: data conversion, training, business continuity.
Requirement = usable representation of a NEED (what value if fulfilled).
Design = usable representation of a SOLUTION (how value realized if built).
BA continuously asks "why?"
Requirements focus on need. Designs focus on solution. Same techniques used for both. A requirement leads to a design which may drive more requirements.
Techniques chính
BABOK v3 có 50 techniques. Dưới đây là những technique quan trọng nhất cho CCBA.
🗣 Elicitation
- Brainstorming
- Interviews
- Workshops
- Observation
- Surveys/Questionnaires
- Document Analysis
- Focus Groups
- Prototyping
📊 Modeling
- Process Modelling (BPMN)
- Use Case Diagrams
- Data Flow Diagrams
- Entity Relationship Diagrams
- State Diagrams
- Sequence Diagrams
- Data Modelling
📈 Analysis
- SWOT Analysis
- Root Cause Analysis (Fishbone)
- Risk Analysis & Management
- Decision Analysis
- Financial Analysis (ROI, NPV, IRR, Payback)
- MoSCoW Prioritization
- Estimation
📋 Documentation
- User Stories + Acceptance Criteria
- Business Rules Analysis
- Acceptance & Evaluation Criteria
- Data Dictionary
- Glossary
- Non-Functional Requirements
👥 Stakeholder
- Stakeholder List, Map, Personas
- RACI Matrix
- Organizational Modelling
- Mind Mapping
- Balanced Scorecard
- Business Model Canvas
🔍 Validation
- Reviews (walkthroughs, inspections)
- Acceptance Criteria
- Traceability Matrix
- Item Tracking
- Metrics & KPIs
- Benchmarking
Stakeholders trong BABOK
11 generic stakeholder roles theo BABOK v3.
👤 Business Analyst
Responsible & accountable for BA activities. May perform other stakeholder roles.
🛒 Customer
Uses/may use products or services. Has contractual or moral rights.
🧠 Domain SME
In-depth knowledge of topic relevant to business need or solution scope.
🖥 End User
Directly interacts with the solution. All participants in business process.
🔧 Implementation SME
Specialized knowledge regarding implementation (architect, developer, DBA, trainer...).
⚙️ Operational Support
Day-to-day management & maintenance of system/product.
📊 Project Manager
Manages work to deliver solution. Balances scope, budget, schedule, quality, risk.
⚖️ Regulator
Defines & enforces standards (legislation, governance, audit).
💰 Sponsor
Initiates effort, authorizes work, controls budget & scope.
🏭 Supplier
External — provides products/services. Has contractual obligations.
✅ Tester
Determines how to verify solution meets requirements. Ensures quality standards.
Glossary — Thuật ngữ BABOK
Flashcards
Click vào thẻ để lật. Dùng phím ← → để chuyển thẻ.
Quiz luyện thi CCBA
100+ câu hỏi theo BABOK v3, có giải thích đáp án.