ANSWERS
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 6.3.4.3 - Negative Impact to Value - Risks are expressed as conditions that increase the likelihood or severity of a negative impact on value.
Q.13 Answer: A - High.
Explanation: This is a common scenario BABoK V3.0 - Section 5.3.4.2 - 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 5.3.4.1 - 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 a customer's experience.
Q.11 Answer: C- Benefit
Explanation: Definition
BABoK V3.0 - Section 5.3.4.1 - 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, 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 7.1.4.2 - Analyze Requirements - Business analysis information is decomposed into components to further examine for:
- anything that must change to meet the business needs;
- anything that should stay the same to meet the business needs;
- 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 7.4.4.5 - 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 7.4.4.4 - 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 7.4.4.1 - 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 7.2.4.3 - 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 7.1.4.4 - 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 needs of different stakeholders. Business analysts take special care to maintain the meaning and intent of the requirements and overall representations
Q.1 Answer: D- Decision modeling
Explanation: BABoK V3.0 - Section 7.1.4.1 - 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.