Question 1. Sam has asked you to trace a particular requirement for him. What does ‘to trace a requirement’ mean?
A. Tracing a requirement means to look at a requirement and the other related requirements. It links risk, cost, quality, and scope elements to stakeholder and solution requirements and to other artifacts created by the team and to solution components.
B. Tracing a requirement means to look at a requirement and the others to which it is related. It links business requirements to stakeholders and solution requirements to other artifacts created by the team and to solution components.
C. Tracing a requirement means to look at a requirement and the others to which it is related. It links business requirements to components in the project’s work breakdown structure
D. Tracing a requirement means to track a requirements from its first identification all the way to its completion to see what issues, risks, costs, quality, and defects have surrounded the requirement
The correct answer is B.
Explanation:
Requirement tracing is the process of identifying and documenting the relationships between a requirement and other project elements, such as business requirements, stakeholders, solution requirements, and artifacts created during the project lifecycle. This helps ensure that all requirements are accounted for in the development process and that no requirements are overlooked.
• A is incorrect because it emphasizes risk, cost, quality, and scope elements, which are not typically the focus of tracing. The main goal is to ensure requirements are related to business needs, stakeholders, and solution components.
• C is incorrect because it only mentions the work breakdown structure (WBS), which is just one element of a project, and doesn’t capture the full scope of requirement tracing.
• D is incorrect because it refers to tracking a requirement’s progression from identification to completion, which is more aligned with requirements management rather than tracing. Tracing focuses on the relationships between requirements and project components.
Thus, B best captures the essence of requirement tracing.
Question 2. Which of the following is NOT an input into the Communicate Requirements task?
A. Requirements
B. BA Communication plan
C. BA Performance metrics
D. Requirements package
The correct answer is C. BA Performance metrics.
Here’s an explanation for each option:
• A. Requirements: These are a key input to the “Communicate Requirements” task. Business analysts need to communicate the requirements that have been gathered and validated.
• B. BA Communication plan: This outlines how requirements and other deliverables will be communicated to stakeholders. Therefore, it is an input to the task of communicating requirements.
• C. BA Performance metrics: These are related to evaluating the performance of the business analyst, such as time taken, efficiency, and accuracy. They are not directly related to the task of communicating requirements, so this is the correct answer.
• D. Requirements package: This is a formal document or set of documents that compiles all the requirements for a project, and it is definitely an input when communicating those requirements to stakeholders.
Thus, BA Performance metrics is not an input into the “Communicate Requirements” task.
Question 3. Jane is a BA working on business analysis using a plan-driven approach. The Marketing team stakeholder group has introduced new requirements, claiming that they will not be able to perform detailed customer analysis unless their requirements are added. However, these new requirements are not within the approved solution scope. Which of the following actions is Jane LEAST likely to take?
A. Amend the new requirements.
B. Change the BA approach to be more change-driven.
C. Amend the solution scope.
D. Facilitate communication between conflicting stakeholders.
In the given scenario, Jane is using a plan-driven approach for business analysis, which is structured, emphasizes documentation, and tends to resist changes once the plan is approved.
Let’s analyze the options:
• A. Amend the new requirements.
Jane might consider amending the new requirements if they align with the broader business goals and if the proper change management process is followed. However, since the plan-driven approach tends to limit the incorporation of new requirements after approval, this option could be difficult to implement without significant effort.
• B. Change the BA approach to be more change-driven.
This is LEAST likely because switching from a plan-driven approach to a change-driven one would imply a fundamental shift in the methodology Jane is using. Plan-driven approaches are rigid, and they do not easily transition to change-driven, which is more adaptive and iterative. Switching approaches mid-project would be highly disruptive and unlikely in this context.
• C. Amend the solution scope.
Jane might amend the solution scope, but only after thorough analysis and stakeholder agreement. While this isn’t a frequent action in a plan-driven approach, it can be done following a formal change request process.
• D. Facilitate communication between conflicting stakeholders.
Jane is likely to facilitate discussions between stakeholders to ensure everyone understands the limitations of the approved scope and any potential impacts of introducing new requirements. This aligns with her role as a BA.
Conclusion:
The action Jane is LEAST likely to take is B. Change the BA approach to be more change-driven, as this would represent a fundamental shift away from the structured plan-driven approach she is following.
Question 4. Fred works in the internal audit department at his company. He is in charge of working with a selected group of people that make the decisions regarding the disposition and treatment of changing requirements. What group does Fred work with?
A. Change control board
B. Internal Audit Group
C. Change driven methodology team
D. Change initiative council
Fred likely works with the Change Control Board (CCB) (Answer: A).
The Change Control Board (CCB) is a group typically responsible for making decisions about the approval, rejection, or deferral of change requests within an organization, especially concerning project requirements, systems, or processes. They ensure that all changes are reviewed in a controlled and systematic way, taking into account their potential impacts on cost, quality, and schedule.
Since Fred is described as working with a group of people responsible for decision-making about changing requirements, this aligns with the function of a CCB. Other options, like the internal audit group or the change initiative council, don’t specifically focus on the control and approval of changes to requirements.
Question 5, Requirements packages can include all of the following formats EXCEPT:
A. Informal documentation
B. Presentation
C. Models
D. Formal documentation
The correct answer is B. Presentation.
Here’s why:
Requirements packages are a means to organize and communicate requirements information. They typically include formats like:
• A. Informal documentation: This could be casual or less structured documentation, often used for quick communication among team members.
• C. Models: Visual representations like diagrams, workflows, or use cases that help clarify complex systems and relationships.
• D. Formal documentation: Structured, detailed, and official documents that provide comprehensive requirements for stakeholders and teams.
However, B. Presentations are generally not considered part of the formal structure of requirements packages. Presentations are used to summarize or convey high-level information, but they are not a medium where detailed requirements are documented or stored for reference.
Therefore, presentations would be the format least likely included in a requirements package, as the package focuses on detailed, structured formats.
Question 6. _ is used to help familiarize the project team with the existing solution scope:
A. Brainstorming
B. Context scope diagram
C. Requirements workshop
D. Structured walkthrough
The correct answer is D. Structured walkthrough.
Explanation:
A structured walkthrough is a formal review process used to guide a project team through the existing solution scope. During a walkthrough, the team systematically reviews documentation, processes, or models to ensure that everyone understands the current solution, any issues, and the path forward. This approach is particularly useful for familiarizing the team with the solution in a structured and comprehensive manner.
Here’s a breakdown of why the other options don’t fit as well:
• A. Brainstorming is a creative problem-solving technique used to generate new ideas or solutions. It is not specifically used for familiarizing a team with an existing scope.
• B. Context scope diagram visually represents the boundaries of a system but does not necessarily help the team understand the existing solution in detail.
• C. Requirements workshop is focused on gathering, refining, or validating requirements rather than familiarizing the team with an existing solution.
Hence, D. Structured walkthrough is the best choice as it directly addresses familiarizing the team with the solution scope.
Question 7. When communicating requirements, which of the following stakeholders usually prefers to have high-level summaries to help them understand the impact of the requirements?
A. Implementation SME.
B. Sponsor.
C. Regulator.
D. Domain SME.
The stakeholder who usually prefers to have high-level summaries to help them understand the impact of the requirements is B. Sponsor.
Explanation:
• Sponsor: Sponsors are typically senior leaders or executives responsible for approving and providing resources for a project. They are more interested in understanding the overall impact, benefits, and alignment with organizational goals rather than getting into detailed technical or operational aspects. High-level summaries help them grasp the strategic importance and the business value of the requirements without being overwhelmed by the specifics.
• Implementation SME (Subject Matter Expert): This stakeholder is typically focused on the technical or operational aspects of implementing the requirements. They would need detailed and precise information about the requirements to ensure successful implementation.
• Regulator: Regulators are concerned with compliance, legal, and policy requirements. They often require detailed information to ensure that the requirements align with laws and regulations.
• Domain SME (Subject Matter Expert): The domain SME has in-depth knowledge of the specific area related to the project. They often need detailed information to validate that the requirements meet industry or domain standards.
Therefore, the sponsor prefers high-level summaries, as they focus on the broader impact rather than the intricacies of the requirements.
Question 8. Which of the following statements best describe traceability?
A. Traceability metrics are used by the Change Management Board to approve or deny request for change.
B. Traceability assists in managing changes to the requirements that will occur after the requirements are base lined
C. Traceability requirements supplement business requirements and functional requirements.
D. Traceability assists in managing accountability for requirements activities that are performed by stakeholders outside of the requirements team.
The statement that best describes traceability is:
B. Traceability assists in managing changes to the requirements that will occur after the requirements are baselined.
Explanation:
• Traceability refers to the ability to link requirements through the development lifecycle, ensuring that each requirement can be traced back to its origin (such as business needs, stakeholder input) and forward to its implementation (such as design, testing, and deployment). This process is crucial for managing changes after requirements are baselined.
• Baselined requirements are those that have been formally agreed upon and serve as the foundation for subsequent project phases. Once the requirements are baselined, traceability helps track changes, ensure that any changes are justified, and monitor their impact on the project.
• Option A refers to metrics used by the Change Management Board, but this is more related to change management processes, not specifically traceability.
• Option C implies that traceability supplements other types of requirements, but traceability itself doesn’t create or supplement requirements; it connects them across the lifecycle.
• Option D involves accountability for activities by stakeholders outside the requirements team, which could relate to governance or project roles, but it doesn’t directly capture the concept of traceability.
Question 9. Which of the following must happen to enable requirements re-use?
A. The requirements must be in a document repository
B. The requirements have to be packaged and stored
C. The requirements need to be approved and baselined.
D. The requirements must be clearly named and defined
The correct answer is:
B. The requirements have to be packaged and stored.
Explanation:
For requirements re-use, certain key steps must be followed to ensure that previously used requirements can be effectively reused in future projects or phases of development. Here’s why B is the best option:
• Packaged and stored: Requirements need to be systematically organized, tagged, and stored in a way that makes them easily retrievable for future use. This means putting them into a repository with clear metadata that makes them reusable for other projects, modules, or teams.
Why the other options are less suitable:
• A. The requirements must be in a document repository: While storing requirements in a document repository is important, merely placing them there doesn’t ensure they are reusable. They must be appropriately structured and packaged for future applications.
• C. The requirements need to be approved and baselined: Approval and baselining are important for the current project, but this doesn’t directly contribute to reusability. A baselined requirement might not be reusable in its exact form unless it’s specifically structured for reuse.
• D. The requirements must be clearly named and defined: Although clear naming and definition are crucial for understanding, this alone is not sufficient for enabling re-use. Packaging and proper storage (as in B) are still required to facilitate reusability across projects.
Question 10. You are being tested by a senior BA in your firm and she wants to know which is not true of these statements.
A. Allocation is forward traceability of a requirement
B. Requirement allocation allows the business analyst to trace the subset of requirement that are allocated to each of the solution component
C. Cover relationship between requirement is when a requirement comes from another requirement
D. Communicating requirement is performed in conjunction with most of the task in the other knowledge areas.
The statement that is not true is C.
Here’s the breakdown:
A. True – Allocation refers to the forward traceability of a requirement, meaning it traces the requirement into the solution components.
B. True – Requirement allocation allows a business analyst to identify which subset of the overall requirements is assigned to various solution components.
C. False – A “cover” relationship is not a recognized term in business analysis in the way it is described here. Typically, a requirement that originates from another requirement is known as a “derivation” or “decomposition” relationship, not a “cover” relationship.
D. True – Communicating requirements is indeed performed in conjunction with many tasks across different knowledge areas, as it is essential for ensuring that stakeholders understand and agree on the requirements throughout the project.
Thus, C is the incorrect statement.