Question 11. Requirements which are agreed to by stakeholders and ready for use in subsequent business analysis or implementation efforts are termed to be in what state?
A. Stated
B. Approved
C. Traced
D. Validated
The correct answer is D. Validated.
Here’s why:
• Stated: This refers to requirements that have been documented but are not yet analyzed or confirmed by stakeholders. They are simply the initial expressions of the needs.
• Approved: While this might seem correct, approval implies formal acceptance, typically at a later stage. Requirements must be validated before they can be officially approved for implementation.
• Traced: This refers to the process of linking requirements to other artifacts, like design, testing, and implementation items, to ensure completeness and coverage. It’s more of a tracking activity, not a state of readiness.
• Validated: Validation means that the requirements have been reviewed and confirmed by stakeholders to ensure they meet their needs and objectives. In business analysis, validation is the stage where stakeholders agree that the requirements are correct, complete, and ready for the next steps. Therefore, a validated requirement is ready for use in subsequent business analysis or implementation efforts.
So, “Validated” is the state in which requirements are agreed upon by stakeholders and are ready for further use.
Question 12. In managing requirements traceability, the value relationship describes:
A. One requirement affects the desirability of another, either positively or negatively.
B. A requirement links to a lower-level requirement.
C. One requirement is only pertinent when another is included.
D. A requirement is a decomposed outcome of another requirement.
The correct answer is A. One requirement affects the desirability of another, either positively or negatively.
Explanation:
The value relationship in requirements traceability refers to how the desirability or priority of one requirement is influenced by another. This means that the implementation of one requirement can increase or decrease the value of another requirement. For example, if Requirement A is fulfilled, Requirement B may become more or less desirable depending on the context.
Let’s briefly explain the other options:
• B refers to a hierarchical relationship, where a high-level requirement is broken down into more detailed, lower-level requirements.
• C describes a dependency relationship, where one requirement is relevant only if another requirement is included.
• D refers to a decomposition relationship, where one requirement is a detailed breakdown or outcome of another, larger requirement.
In managing requirements traceability, the value relationship emphasizes how the importance or benefit of one requirement can influence others.
Question 13. Ongoing requirements are those requirements that an organizational unit is required to be able to meet on a continuous basis. Which of the following is not an ongoing requirement?
A. Service Level Agreements
B. Business Rules
C. Strategic Initiative
D. Quality standards
The correct answer is C. Strategic Initiative.
Explanation:
• A. Service Level Agreements (SLAs): These are ongoing commitments between a service provider and a client that define the expected level of service. They need to be continuously met to maintain operations and service delivery, making them an ongoing requirement.
• B. Business Rules: These are the rules that guide day-to-day business operations, decisions, and behaviors. Since they govern how business processes should work, they need to be followed continuously, making them ongoing requirements.
• C. Strategic Initiative: A strategic initiative is a specific project or effort undertaken by an organization to achieve a long-term goal. It is typically time-bound with a start and an end, unlike ongoing processes or standards. Therefore, it is not a continuous or ongoing requirement.
• D. Quality Standards: These are the standards set to ensure the quality of products or services. They must be adhered to continuously to maintain quality, making them an ongoing requirement.
Thus, Strategic Initiative is not an ongoing requirement because it is a focused, time-limited effort rather than a continuous obligation.
Question 14. __ is generally used when the issuing organization is open to a number of alternative solutions and is seeking information to evaluate possible options.
A. RFQ
B. ROI
C. RFI
D. RFP
The correct answer is C. RFI (Request for Information).
Explanation:
• RFI (Request for Information) is generally used when an organization is exploring different options and seeking information from vendors or suppliers. It is issued when the organization doesn’t have a clear understanding of the potential solutions and needs more information to evaluate possible approaches.
• RFQ (Request for Quotation) is used when the organization knows exactly what they need and is asking vendors to provide pricing details for specific products or services.
• RFP (Request for Proposal) is issued when the organization knows its requirements but is looking for vendors to propose solutions and provide detailed bids or proposals.
• ROI (Return on Investment) is a financial metric used to evaluate the profitability of an investment and is not a document issued by organizations for sourcing or procurement.
Therefore, when the organization is open to exploring various alternative solutions and needs more information, an RFI is used.
Question 15. Meghan is the Senior BA in a manufacturing company. She uses Work Products during every requirements development process. Which of the following is NOT one of what she uses?
A. Interview questions and notes
B. Stakeholders list
C. Issues log
D. Traceability matrices.
The correct answer is B. Stakeholders list.
Explanation:
Meghan, as a Senior Business Analyst (BA), uses various Work Products during the requirements development process. Work Products refer to the outputs or deliverables generated during a project or process, often used to ensure proper documentation and communication throughout requirements development. Here’s a breakdown of the options:
• A. Interview questions and notes: These are key tools during requirements elicitation. They help BAs gather information from stakeholders, making them a work product related to the requirements development process.
• B. Stakeholders list: While important for identifying relevant people involved in the project, the stakeholders list itself is more of a reference document used to identify and manage stakeholders. It’s not typically classified as a “work product” directly linked to requirements development.
• C. Issues log: This document tracks problems or risks that arise during the project and ensures they are managed and resolved. It is part of the documentation a BA would work with in the requirements development process.
• D. Traceability matrices: These are essential for tracking the relationship between requirements and their fulfillment, ensuring that all requirements are addressed and validated. This is definitely a work product in the requirements development process.
Thus, the Stakeholders list is not considered a work product related to requirements development in the same sense as the others.
Question 16. Which of the following is used when the issuing organization understands the nature of the solution options available to it and is seeking vendors who can implement an option?
• a. REQ
• b. RFP
• c. RFI
• d. Either RFP or RFQ
The correct answer is b. RFP (Request for Proposal).
Explanation:
• REQ (Requirement): This is not a standard term in procurement processes and is likely a distractor in this context.
• RFP (Request for Proposal): An RFP is used when the organization understands the nature of the solution they need but requires vendors to propose how they would implement it. The organization knows its needs but is open to solutions and approaches offered by different vendors. This allows the vendors to present their strategies, experience, and costs, so the organization can choose the best option.
• RFI (Request for Information): An RFI is used when the organization does not fully understand the available solution options and seeks information from vendors to explore what’s available. It’s more exploratory than an RFP.
• RFQ (Request for Quote): An RFQ is typically used when the organization knows exactly what product or service it needs and is simply seeking pricing information from vendors.
In the case where the organization knows what it wants and is seeking proposals for how it can be implemented, an RFP is most appropriate. Therefore, the correct answer is b. RFP.
Question 17. Relationships, Impact Analysis, and Configuration Management System are elements associated with which task in the Requirements Management and Communications Knowledge Area?
• a. Manage Solution Scope and Requirements
• b. Prepare requirements Package
• c. Manage Requirements Traceability
• d. None of the Above
The correct answer is:
c. Manage Requirements Traceability
Explanation:
• Relationships refer to how different requirements are connected or interdependent.
• Impact Analysis involves assessing the effects of a change in requirements on the overall system, including scope, budget, and timeline.
• A Configuration Management System helps track changes and maintains the integrity of the requirements as they evolve.
These elements are closely associated with the task of managing Requirements Traceability, which ensures that each requirement is tracked throughout the project lifecycle and that any changes or impacts can be easily identified and managed.
Therefore, these tasks align with Manage Requirements Traceability rather than the other options.
Question 18. A business analyst in your organisation encourages teamwork and open communications among the business analysis team and the stakeholders. She wants stakeholders to drop by her office and freely discuss the requirements, the solution scope, and other concerns about the solution she is working on. She definitely prefers informal communications. What is the danger she may experience with informal communications?
• a. There is no danger; informal communications is a preferred business analysis technique.
• b. The stakeholders may not know who’s in charge of the solution.
• c. The stakeholders may address the business analysis team and the project team directly rather than communicate through him.
• d. Stakeholders may miss information and the requirements could become ambiguous.
The correct answer is d. Stakeholders may miss information and the requirements could become ambiguous.
Explanation:
While informal communication can foster an open and collaborative environment, it poses specific risks in the context of business analysis. Informal discussions can lead to:
• Lack of documentation: Key points may not be documented properly, leading to misunderstandings or incomplete requirements.
• Ambiguity: Since informal communications are often less structured, details may be forgotten, overlooked, or interpreted differently by different stakeholders.
• Missed information: Critical requirements or constraints might be missed if they are only discussed casually, without a formal follow-up to ensure that all important points are captured and agreed upon.
In contrast, formal communications typically involve documentation, meeting minutes, and structured processes to ensure that everyone has a clear understanding of the solution scope and requirements.
Therefore, while informal communication can support a more approachable environment, it must be balanced with formal processes to ensure clarity and completeness.
Question 19. A business analyst in your organisation encourages teamwork and open communications among the business analysis team and the stakeholders. She wants stakeholders to drop by her office and freely discuss the requirements, the solution scope, and other concerns about the solution she is working on. She definitely prefers informal communications. What is the danger she may experience with informal communications?
a. There is no danger; informal communications is a preferred business analysis technique.
b. The stakeholders may not know who’s in charge of the solution.
c. The stakeholders may address the business analysis team and the project team directly rather than communicate through him.
d. Stakeholders may miss information and the requirements could become ambiguous.
The correct answer is d. Stakeholders may miss information and the requirements could become ambiguous.
Explanation:
While informal communication can foster an open and collaborative environment, it poses specific risks in the context of business analysis. Informal discussions can lead to:
• Lack of documentation: Key points may not be documented properly, leading to misunderstandings or incomplete requirements.
• Ambiguity: Since informal communications are often less structured, details may be forgotten, overlooked, or interpreted differently by different stakeholders.
• Missed information: Critical requirements or constraints might be missed if they are only discussed casually, without a formal follow-up to ensure that all important points are captured and agreed upon.
In contrast, formal communications typically involve documentation, meeting minutes, and structured processes to ensure that everyone has a clear understanding of the solution scope and requirements.
Therefore, while informal communication can support a more approachable environment, it must be balanced with formal processes to ensure clarity and completeness.
Question 20. What is the primary reason for a business analyst to use a configuration management system?
• a. To trace large numbers of requirements
• b. To track changes
• c. To maintain versions of the software
• d. To maintain versions of the documentation
The primary reason for a business analyst to use a configuration management system (CMS) is:
b. To track changes
Explanation:
A configuration management system helps in tracking changes to various project artifacts such as requirements, documents, software versions, etc. It provides a way to ensure that all changes are recorded, organized, and traceable, ensuring consistency across the project lifecycle.
While options like maintaining versions of software (c) and documentation (d) are relevant, they are more specific to certain functions of configuration management. Tracking changes is the broader function that encompasses these activities. Tracing large numbers of requirements (a) can be done using specialized requirement management tools, which might integrate with configuration management but isn’t the CMS’s primary purpose.
Thus, tracking changes is the most accurate and comprehensive answer.