Question 21. The requirements elicitation process requires that the business analyst and team prepare for the requirements elicitation activities. There are three specific inputs that the business analyst will need in preparing for the requirements elicitation. Which of the following is NOT one of the three inputs the business analyst will use as he prepares for requirements elicitation?
A. Business need
B. Solution scope
C. Stakeholder list
D. Change request
The correct answer is D. Change request.
Here’s an explanation for each option:
• A. Business need: This is an important input for the requirements elicitation process. The business need helps the business analyst understand what problem needs to be solved or what opportunity is being pursued, which is essential for eliciting relevant requirements.
• B. Solution scope: The solution scope defines the boundaries of the solution that is to be developed. It provides clarity on what is included and excluded in the project, helping to focus the elicitation on the appropriate requirements.
• C. Stakeholder list: A stakeholder list identifies the individuals, groups, or organizations that have an interest in the project or will be affected by it. Understanding the stakeholders is critical for the elicitation process, as it helps the business analyst determine who to engage and gather requirements from.
• D. Change request: This is not typically one of the initial inputs in preparing for requirements elicitation. Change requests are generally used during the project to manage modifications to existing requirements, rather than as an input for initially gathering requirements.
Thus, D. Change request is not one of the three inputs needed for preparing for requirements elicitation.
Question 22. You are preparing for elicitation. You have just selected the individuals to participate in the elicitation events. While selecting the elicitation events, one of the considerations you need to make is whether you would have open-ended or closed ended questions. You also need to determine the best method for distributing those questions. What technique have you selected for the elicitation events?
A. Survey/Questionnaire
B. Prototyping
C. Interviews
D. Requirement Workshop
The technique you have selected for the elicitation events is A. Survey/Questionnaire.
Explanation:
• A Survey/Questionnaire typically involves asking participants a series of questions. These questions can be open-ended (allowing for detailed, subjective responses) or closed-ended (where the participant chooses from predefined responses).
• A key part of survey design is deciding the format of the questions (open-ended vs. closed-ended) and how to distribute them (e.g., through email, online forms, or printed copies).
• In contrast, other techniques like Interviews (C) are more conversational, Prototyping (B) focuses on creating a tangible model for feedback, and Requirement Workshops (D) are collaborative group sessions. None of these methods place the same emphasis on structuring and distributing predefined sets of questions.
This fits your scenario where you’re focused on selecting the type of questions and how to distribute them.
Question 23. You have just discovered that the business process expert for the existing system currently being upgraded is no longer employed by the company. Which elicitation technique might you apply in this situation?
A. Document analysis
B. Reverse engineering
C. Interface analysis
D. Elicitation workshop
The most suitable elicitation technique in this scenario is A. Document analysis.
Here’s why:
1. Absence of Business Process Expert: Since the primary individual (business process expert) familiar with the existing system is no longer employed, it becomes difficult to gather knowledge directly from people. Document analysis is an effective approach to retrieve information about the system’s functionality, processes, and requirements from existing documents. These could include system manuals, specifications, process workflows, and other documentation related to the system.
2. Existing Documentation: Often, systems have a wealth of documentation—whether it’s design documents, user manuals, or process workflows—that can provide valuable insights into the business processes and help bridge the knowledge gap.
3. Avoiding Knowledge Gaps: While other techniques like Reverse engineering (B) could help in understanding the technical functionality of the system, it doesn’t necessarily capture the business processes or requirements that the system was intended to fulfill. Interface analysis (C) is focused more on how different systems interact, but it might not help directly with understanding internal processes. Elicitation workshops (D) are valuable, but without the key expert, running such a workshop would lack necessary business process knowledge.
Thus, Document analysis is the most appropriate and effective elicitation technique to apply in this situation.
Question 24. You have documented an unfamiliar business process and there seem to be gaps in the workflow, despite the fact you got the flow from subject matter experts (SMEs). Which Requirements Elicitation method will be most effective at understanding the process?
A. Interview the SMEs again
B. Bring the SMEs into a facilitated session and talk about the process to uncover the gaps
C. Observe some SMEs to uncover the gaps.
D. Brainstorm with the SMEs to uncover the gaps.
The most effective Requirements Elicitation method for understanding the gaps in the business process is C. Observe some SMEs to uncover the gaps.
Explanation:
1. Observation is a powerful method because it allows you to see the process in action, capturing the nuances and real-world practices that may not be communicated clearly during interviews or discussions. Sometimes, SMEs might not be aware of gaps or deviations in their workflow because they are used to their daily routine and might overlook certain steps or shortcuts they take.
2. Interviews (A) or Facilitated Sessions (B) rely on verbal communication, which can lead to misunderstandings, misinterpretations, or missing details. Even if SMEs are well-versed in the process, they may not fully explain or articulate everything, especially if they assume certain steps are obvious.
3. Brainstorming (D) can be helpful for generating ideas but may not be structured enough to identify specific gaps in an existing process. It is better suited for generating new ideas rather than analyzing current workflows.
By observing the SMEs, you can identify discrepancies between documented workflows and actual practices, revealing gaps that might not be obvious through discussion alone.
Question 25. Preparing for elicitation yields two distinct deliverables namely:
A. Scheduled resources and Requirement Workshop
B. Supporting resources and Scheduled Materials
C. Readiness Assessment and Scheduled Resources
D. Scheduled Resources and Supporting Materials
The correct answer is D. Scheduled Resources and Supporting Materials.
Explanation:
When preparing for elicitation, two main deliverables are typically produced:
1. Scheduled Resources: This refers to the people, time, and other resources necessary for conducting the elicitation activities. It includes arranging meetings, ensuring the availability of stakeholders, and scheduling appropriate sessions (such as interviews, workshops, or surveys).
2. Supporting Materials: These are any preparatory documents or resources required to facilitate the elicitation process. This might include agenda, questionnaires, templates, tools, and any reference materials to guide discussions or gather information efficiently.
Other options do not capture this combination accurately:
• A mentions a “Requirement Workshop,” which is only one elicitation method, rather than a broad set of supporting materials.
• B misrepresents the relationship by suggesting “Scheduled Materials,” which is unclear.
• C talks about a “Readiness Assessment,” which is a preliminary activity before scheduling and resource gathering.
Thus, D captures the essence of preparing for elicitation.
Question 26. You are trying to gather quantitative data in your survey. What should you do?
A. Ask closed-ended questions
B. Ask open-ended questions.
C. Ask both open-ended and closed-ended questions.
D. Ask specific financial questions.
The correct answer is A. Ask closed-ended questions.
Explanation:
• Closed-ended questions have specific, predefined answers, often in the form of multiple choices, yes/no options, or numerical values. This format allows you to collect quantitative data because responses are structured and easily measurable (e.g., percentages, ratings, or counts).
• Open-ended questions (Option B), on the other hand, encourage more detailed, free-form responses, which typically generate qualitative data that is harder to analyze statistically. While open-ended questions provide deeper insights, they are not ideal for gathering quantitative data.
• Option C suggests using both types of questions, but while this may give you both qualitative and quantitative data, it is not necessary if your goal is strictly quantitative data.
• Option D focuses on financial data, which may be quantitative, but doesn’t address the format of the question. You can still ask non-financial closed-ended questions to gather quantitative data.
Question 27. Which of the following can take part in requirement elicitation activities?
A. Project team
B. End User
C. Subject matter experts
D. Any stakeholder
The correct answer is D. Any stakeholder.
Explanation:
Requirement elicitation is the process of gathering and understanding the needs and expectations of stakeholders for a project. This activity involves multiple parties who can provide insights into the system’s desired functionality. Here’s why each group mentioned can participate:
• Project team (A): The project team, including business analysts, developers, and project managers, plays a key role in organizing and conducting elicitation activities. They help define the scope, ask the right questions, and interpret the requirements.
• End User (B): End users are crucial because they directly interact with the product or system. Their input ensures that the final product meets the actual needs and preferences of the people using it.
• Subject Matter Experts (C): SMEs bring deep expertise and specialized knowledge. They understand the domain in which the system operates and can provide valuable insights into specific business rules, industry standards, and complex requirements.
• Any stakeholder (D): Stakeholders, in general, are anyone with an interest or stake in the project. This includes sponsors, regulators, or customers. Since stakeholders have varying levels of influence and interest, all of them should be involved in the requirement elicitation process to ensure a comprehensive understanding of expectations and needs.
In practice, requirement elicitation should involve all relevant stakeholders to gather comprehensive and accurate requirements.
Question 28. Which statement about how User Interfaces (UI) and prototypes help with requirements elicitation and documentation is LEAST true?
A. They will uncover additional data attributes and relationships
B. They will help to refine processing requirements for navigation of interfaces.
C. Use cases help provide the foundation for UIs, including how they should respond to actors.
D. Documenting user interfaces is not a requirements activity, but should be left to interface designers.
The statement that is LEAST true is D. Documenting user interfaces is not a requirements activity, but should be left to interface designers.
Explanation:
1. Statement A: “They will uncover additional data attributes and relationships.”
• This statement is true. User interfaces and prototypes often lead to discussions with users that reveal additional data needs and how different elements of data relate to one another.
2. Statement B: “They will help to refine processing requirements for navigation of interfaces.”
• This statement is also true. Prototyping and UI design can clarify user workflows, helping to refine processing requirements and navigation.
3. Statement C: “Use cases help provide the foundation for UIs, including how they should respond to actors.”
• This statement is true as well. Use cases are integral in defining user interactions with the system, which directly informs UI design and functionality.
4. Statement D: “Documenting user interfaces is not a requirement activity, but should be left to interface designers.”
• This statement is the least true because documenting user interfaces is indeed a crucial part of the requirements elicitation and documentation process. It ensures that all stakeholders have a clear understanding of the system’s functionality and usability, and it bridges the gap between technical requirements and user needs. While interface designers play a significant role in creating UIs, their work should be informed by the requirements process, which includes documenting user interfaces.
Question 29. Which of the following elicitation tasks has a single input and must be done solely by the Business analyst?
A. Document elicitation results
B. Prepare for elicitation
C. Conduct elicitation
D. Confirm elicitation
The correct answer is B. Prepare for elicitation.
Explanation:
• A. Document elicitation results: This involves compiling information gathered during elicitation sessions. While the Business Analyst may take the lead, this task can also involve input from stakeholders to ensure completeness.
• B. Prepare for elicitation: This is the only task in the list that typically has a single input (the requirements or goals) and is done by the Business Analyst alone. It involves organizing and determining the techniques and tools to use during the elicitation process. It requires planning and preparing, not direct interaction with stakeholders.
• C. Conduct elicitation: This involves interacting with stakeholders to gather information. It requires multiple inputs from various stakeholders and is not done solely by the Business Analyst.
• D. Confirm elicitation: This task is about validating the information gathered during elicitation with stakeholders. It involves stakeholder participation to ensure that the information captured is accurate.
Thus, B. Prepare for elicitation is the task that has a single input and is done solely by the Business Analyst.
Question 30. Sandra is the Business Analyst in a Paper Company, She is discussing with the project sponsor as regards what the business expects from a proposed new system. What type of elicitation interview is she conducting?
A. Discussion
B. Structured
C. Unstructured
D. Transition
The type of elicitation interview Sandra is conducting is C. Unstructured.
Explanation:
Sandra, as a Business Analyst, is discussing what the business expects from a proposed new system with the project sponsor. This kind of discussion likely involves open-ended questions where she lets the sponsor speak freely about the expectations and needs of the business. In an unstructured interview, there is no strict format or predetermined set of questions, allowing the interviewee to provide more comprehensive insights.
• Unstructured interviews are flexible and allow for free-flowing conversations, which helps to gather qualitative data about expectations, requirements, and opinions.
• Structured interviews would involve a predefined set of questions, which isn’t indicated here. Sandra is more likely focusing on gathering broader insights rather than following a strict questionnaire.
Thus, the best choice here is Unstructured.