The ECBA exam covers four knowledge areas of BABOK, techniques, glossary and underlying competencies.
The 4 knowledge areas are : Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, and Requirements Analysis and Design Definition. The 2 excluded knowledge areas are Strategy Analysis and Solution Evaluation. Perspectives are not part of the ECBA exam scheme.
You should have a good understanding of the concepts, tools, and techniques in each of these knowledge areas.
Practice with a good number of sample questions. Joining a ECBA training course can be helpful in preparing for the CBAP exam.
Answers provided at the end
#Q15.Tools that facilitate recording; organizing; storing and sharing requirements and designs are _________.
- Requirements (traced)
- Modeling notations/ standards
- Requirements management tools
- Modeling tools
#Q14. Which of the following is expressed as conditions that increase the likelihood or severity of a negative impact to value?
#Q13. Stakeholders usually prioritize their requirements into which of the following categories?
- Very Low
#Q12. Which of the following prioritization factors considers consequences resulting from not implementing a requirement?
#Q10. Which of the following provides a plan to transition from the current state to the future state?
- Business policies
- Change strategy
- Current state description
- BA performance assessment
#Q9. Business analyst A has decomposed BA information into components to further examine constraints or assumptions that impact the components. What is A doing?
- Modeling requirements
- Analyzing requirements
- Implementing requirements
- Representing attributes
#Q8. Which of the following describes how all of the business analysis information for a change relates including the relationship between various types of information?
- Business analysis information architecture
- Architectural framework
#Q7. If there are no relationships between requirements that link elements in two different and conflicting ways; then the relationship satisfies which of the following quality criteria?
#Q6. A set of conventions that define how requirements will be represented; organized and related is known as:
#Q5. Which of the following stakeholders can participate in specify and model requirements tasks?
- Only Sponsor and PM
- Only developers and implementation SME
- Only technical architect and PM
- Any stakeholders
#Q4. Which of the following can be used for quality control when verifying requirements and designs?
- Data model
- Information management approach
#Q3. Which of the following is used to record the meaning of relevant business terms while analyzing requirements?
- Scope model
- State model
- Data dictionary
#Q2.The main reason for implementing appropriate levels of abstraction is because:
- Not all stakeholders find value in the entire set of requirements
- Requirements do not have necessary attributes
- Requirements have missing components
- Stakeholders don’t have an interest
Q.15 Answer: C - Requirements management tools
Explanation: Purpose of the tool
BABoK V3.0 - Section 5.1.5 - Guidelines and Tools #4 - Requirements Management Tools/Repository: used to store and manage business analysis information. The tool may be as simple as a text document or as complex as a dedicated requirements management tool.
Q.14 Answer: D - Risks
Explanation: BABoK V3.0 - Section 188.8.131.52 - Negative Impact to Value - Risks are expressed as conditions that increase the likelihood or severity of a negative impact to value.
Q.13 Answer: A - High.
Explanation: This is a common scenario BABoK V3.0 - Section 184.108.40.206 - Stakeholders may also have difficulty characterizing any requirement as a lower priority, and this may impact the ability to make necessary trade-offs. In addition; stakeholders may (intentionally or unintentionally) indicate a priority to influence the result to their desired outcome.
Q.12 Answer: B- Penalty
Explanation: Definition: BABoK V3.0 - Section 220.127.116.11 - Paragraph 2 - Point #2 -Penalty: the consequences that result from not implementing a given requirement. This includes prioritizing requirements in order to meet regulatory or policy demands imposed on the organization; which may take precedence over other stakeholder interests. Penalty may also refer to the negative consequence of not implementing a requirement that improves the experience of a customer.
Q.11 Answer: C- Benefit
BABoK V3.0 - Section 18.104.22.168 - Paragraph 2 - Point #1 -Benefit: the advantage that accrues to stakeholders as a result of requirement implementation; as measured against the goals and objectives for the change. The benefit provided can refer to a specific functionality; desired quality; or strategic goal or business objective.
BABoK V3.0 - Section 6.4.6 - Techniques - Process Modelling: used to describe how work would occur in the solution scope or during the change.
Q.10 Answer: B- Change strategy
Explanation: Definition BABoK V3.0 - Glossary - Change strategy: A plan to move from the current state to the future state to achieve the desired business objectives.
Q.9 Answer: B - Analyzing requirements
Explanation: BABoK V3.0 - Section 22.214.171.124 - Analyze Requirements - Business analysis information is decomposed into components to further examine for:
- anything that must change to meet the business need;
- anything that should stay the same to meet the business need;
- missing components;
- unnecessary components; and
- any constraints or assumptions that impact the components.
Q.8 Answer: A- Business analysis information architecture
Explanation: BABoK V3.0 - Section 126.96.36.199 - Business Analysis Information Architecture - The structure of the business analysis information is also an information architecture. This type of architecture is defined as part of the task Plan Business Analysis Information Management (p. 42). The information architecture is a component of the requirements architecture because it describes how all of the business analysis information for a change relates. It defines relationships for types of information such as requirements; designs; types of models; and elicitation results.
Q.7 Answer: A- Unambiguous
Explanation: BABoK V3.0 - Section 188.8.131.52 - Relate and Verify Requirements Relationships - Unambiguous: there are no relationships that link elements in two different and conflicting ways.
Q.6 Answer: A- Viewpoints
Explanation: BABoK V3.0 - Section 184.108.40.206 - Requirements Viewpoints and Views A viewpoint is a set of conventions that define how requirements will be represented; how these representations will be organized; and how they will be related. Viewpoints provide templates for addressing the concerns of particular stakeholder groups.
Q.5 Answer: D- Any stakeholders
Explanation: BABoK V3.0 - Section 7.1.7 - Any stakeholder: business analysts may choose to perform this task themselves and then separately package and communicate the requirements to stakeholders for their review and approval, or they might choose to invite some or all stakeholders to participate in this task.
Q.4 Answer: D- Checklists
Explanation: BABoK V3.0 - Section 220.127.116.11 - Checklists - Checklists are used for quality control when verifying requirements and designs.
Q.3 Answer: A- Glossary
Explanation: BABoK V3.0 - Section 7.1.6 - Techniques - Glossary: used to record the meaning of relevant business terms while analyzing requirements.
Q.2 Answer: A- Not all stakeholders find value in the entire set of requirements
Explanation: BABoK V3.0 - Section 18.104.22.168 - Implement the Appropriate Levels of Abstraction - The level of abstraction of a requirement varies based on the type of requirement and audience for the requirement. Not all stakeholders require or find value in the complete set of requirements and models. It may be appropriate to produce different viewpoints of requirements to represent the same need for different stakeholders. Business analysts take special care to maintain the meaning and intent of the requirements overall representations
Q.1 Answer: D- Decision modeling
Explanation: BABoK V3.0 - Section 22.214.171.124 - Model Requirements - Paragraph 3 - Point #2 - Rationale: models represent the ‘why’ of a change. Techniques used to represent the rationale include Decision Modelling; Scope Modelling; Business Model Canvas; Root Cause Analysis; and Business Rules Analysis.