Chapter |
Section Heading |
Errata Reported |
Correction |
|
4. Elicitation and Collaboration |
4.2 Conduct Elicitation>Figure 4.2.1: Conduct Elicitation Input/Output Diagram |
7.1. Specify and Model Requirements missing from Tasks Using this Output. |
Add 7.1. Specify and Model Requirements to Tasks Using this Output. |
|
4. Elicitation and Collaboration |
4.3 Confirm Elicitation Figure>4.3.1: Confirm Elicitation Input/Output Diagram |
7.1. Specify and Model Requirements missing from Tasks Using this Output. |
Add 7.1. Specify and Model Requirements to Tasks Using this Output. |
|
5. Requirements Life Cycle Management |
5.1.5 Guidelines and Tools |
The term Requirements Management Tools / Repository is inconsistent with 7.1.5 Guidelines and Tools: Requirements Life Cycle Management Tools. |
Change 5.1.5 Guidelines and Tools: "Requirements Management Tools / Repository" to "Requirements Life Cycle Management Tools". |
|
5. Requirements Life Cycle Management |
5.3 Prioritize Requirements>5.3.7 Stakeholders |
Domain Subject Matter Expert not included in Stakeholders. |
Add Domain Subject Matter Expert to stakeholders. |
|
5. Requirements Life Cycle Management |
5.4 Assess Requirements Changes>Figure 5.4.1 Assess Requirements Changes Input/Output Diagram |
Outputs "5.1 Requirements Change Assessment" and "5.1. Designs Change Assessment" are misnumbered. |
"5.4 Requirements Change Assessment" and "5.4. Designs Change Assessment". |
Chapter |
Section Heading |
Errata Reported |
Correction |
|
6. Strategy Analysis |
6.1.3 Inputs |
Elicitation Results should be (confirmed). |
Elicitation Results (confirmed). |
|
6. Strategy Analysis |
Figure 6.2.1: Define Future State Input/Output Diagram |
Constraints mistakenly added in Guidelines and Tools section. |
Remove Constraints from in Figure 6.2.1. |
|
6. Strategy Analysis |
Figure 6.2.1: Define Future State Input/Output Diagram |
The input Business Requirements does not have the task number. |
Add 6.1 to Business Requirements. |
|
6. Strategy Analysis |
6.3 Assess Risks>6.3.3 Inputs |
Designs (prioritized) is not included in the list of Inputs. |
Add Designs (prioritized) as an Input. |
|
6. Strategy Analysis |
6.3 Assess Risks>6.3.8 Outputs |
Risk Analysis Results is not formatted like other Ouputs. |
• Risk Analysis Results: an understanding of the risks associated with achieving the ... |
|
7. Requirements Analysis and Design Definition |
The Requirements Analysis and Design Definition knowledge area includes the following tasks: |
The task list • Define Solution Options is incorrect. |
• Define Design Options |
Chapter |
Section Heading |
Errata Reported |
Correction |
|
8. Solution Evaluation |
Figure 8.0.2: Solution Evaluation Input/Output Diagram |
The Ouput 8.5 Recommend Actions is inconstant with the output in 8.5.8. |
8.5 Recommended Action |
|
8. Solution Evaluation |
8.5 Recommend Actions to Increase Solution Value >8.5.4 Elements>.2 Recommendations |
The bullet list item "• Some additional factors that may impact the decision regarding the replacement or retirement of a solution include:" is incorrectly indented. |
"• Some additional factors that may impact the decision regarding the replacement or retirement of a solution include:" and the following list items should be indented 1 tab. |
|
9. Underlying Competencies |
9.4.3 Written Communication>.1 Purpose |
Repeated word "to" |
Business analysts use written communication to convey ideas, concepts, facts, and opinions to variety of stakeholders. |
|
10. Techniques |
10.1 Acceptance and Evaluation Criteria>10.1.4 Usage Considerations |
In the list item "• Evaluation criteria helps in defining priorities." help is pluralized. |
• Evaluation criteria help in defining priorities. |
|
10. Techniques |
10.12 Data Dictionary>Figure 10.12.1: Example of a Data Dictionary |
In the Name row "Last Name" is used. |
Family Name |
Chapter |
Section Heading |
Errata Reported |
Correction |
|
10. Techniques |
10.13 Data Flow Diagrams>10.13.2 Description |
The use of terminators is incorrect in the following sentence: The data flow diagram also illustrates the temporary or permanent repositories (referred to as data stores or terminators) |
The data flow diagram also illustrates the |
|
10. Techniques |
10.14 Data Mining>.4 Modeling Techniques |
support sector machines should be support vector machines. |
support vector machines |
|
10. Techniques |
10.16 Decision Analysis>10.16.3. Elements>.2 Decision Matrices |
In the sentence "In this example, Alternate 3 would likely be selected due to its high weighted score." Alternate 3 is incorrect. Do to an error in calculations in Table 10.16.2: Weighted Decision Matrix the selected Alternate 3 should be be Alternate 2. |
In this example, Alternate 2 would likely be selected due to its high weighted score. |
|
10. Techniques |
10.16 Decision Analysis>10.16.3. Elements>.2 Decision Matrices>Table 10.16.2: Weighted Decision Matrix |
There are two incorrect values in the table. Row: Criterion 2 Colum: Alt 3 Value of 8 is incorrect and thereby impacted the weighted score: Row: Weighted score Column: Alt 3 Value 40. |
Row: Criterion 2 Colum: Alt 3 Value should be 3. Row: Weighted score Column: Alt 3 Value should be 35. |
|
10. Techniques |
10.25 Interviews>10.25.3 Elements> .5 Interview Flow |
practices active listening to confirm what the interviewer has said, and |
practices active listening to confirm what the interviewee has said, and |
|
10. Techniques |
10.41 Scope Modelling>10.41.4 Usage Considerations>.1 Strengths |
Inaccurate indentation of list. |
Indent the last 4 list items. |
|
10. Techniques |
10.44 State Modelling>Figure 10.44.1: State Transition Diagram |
The State 3 arrows are all pointing as leaving. |
Change the arrow between State 2 and State 3 as entering State 3. |
Chapter |
Section Heading |
Errata Reported |
Correction |
|
11.5 Business Process Management Perspective |
11.5.3 Frameworks, Methodologies, and Techniques> .1 Frameworks |
The BPM Framework ACCORD is misspelled. |
ACORD |
|
11.2 Business Intelligence Perspective |
11.2.1 Change Scope> .1 Breath of Change |
The sentence "The business intelligence promotes an enterprise-wide view of information management." should not begin with "The" |
Business intelligence promotes promotes an enterprise-wide view of information management. |
|
Appendix B: Techniques to Task Mapping |
|
3.1 Plan Business Analysis Approach is not included in the mapping for 10.37 Reviews. |
Add 3.1 Plan Business Analysis Approach to the mapping for 10.37 Reviews. |
|
Appendix D: Summary of Changes from BABOK Guide v 2.0 |
Underlying Competencies/Behaviour Characteristics |
Error: Ethics—removed. |
The Behavioural Characteristic Ethics has not been removed. |
|
Appendix B: Techniques to Task Mapping |
10.26 Item Tracking |
3.2 Plan Stakeholder Engagement included in mapping table but 10.26 Item Tracking is not listed in the task. |
Remover 3.2 Plan Stakeholder Engagement from 10.26 Item Tracking mapping. |
Chapter |
Section Heading |
Errata Reported |
Correction |
|
Appendix B: Techniques to Task Mapping |
10.32 Organizational Modeling |
3.2 Plan Stakeholder Engagement missing. |
Add 33.2. Plan Stakeholder Engagement . |
|
Appendix B: Techniques to Task Mapping |
10.35 Process Modelling |
5.1 Trace Requirements missing. |
Add 5.1 Trace Requirements. |
|
Appendix B: Techniques to Task Mapping |
10.37 Reviews |
3.2 Plan Stakeholder Engagement incorrectly mapped. |
Remove 3.2. Plan Stakeholder Engagement. |
|
Appendix B: Techniques to Task Mapping |
10.38 Risk Analysis and Management |
3.1 Plan Business Analysis Approach missing. |
Add 3.1. Plan Business Analysis Approach. |
|
Appendix B: Techniques to Task Mapping |
10.39 Roles and Permissions Matrix |
7.1 Specify and Model Requirements missing. |
Add 7.1 Specify and Model Requirements. |
|
Appendix B: Techniques to Task Mapping |
10.40 Root Cause Analysis |
3.1 Plan Business Analysis incorrectly mapped. |
Remove 3.1. Plan Business Analysis Approach. |
|
Appendix B: Techniques to Task Mapping |
10.43 Stakeholder List, Map, or Personas |
3.2 Plan Stakeholder Engagement missing. |
Add 3.2. Plan Stakeholder Engagement. |
|
Appendix C: Contributors |
Appendix C: Contributors |
Anne Fomim, CBAP misspell Fomim, should be Fomin. |
Change Anne Fomin, CBAP. |