161) Requirements questions and issues are not resolved for your project. Which of the below are possible solutions?
a. Assign each open issue to an individual for resolution
b. Use an issue-tracking tool for tracking requirements issues to closure
c. Monitor open issues as part of project tracking
d. Obtain commitment from all stakeholders early on for open and timely information exchange and for answering questions and resolving issues
162) Your project participants don’t share the same vocabulary. Which of the below are possible solutions?
a. Define terms in a glossary.
b. Define data structures and elements in a data dictionary.
c. Train development team in the business domain.
d. Train user representatives in requirements engineering
163) You notice that there is ambiguity in how different users understand the requirements. Which of the below can help clear ambiguities in requirements?
a. Writing tests against the requirements
b. Building prototypes
c. Collaborative elicitation
d. Collaborative validation
164) You have prepared a set of requirements that has been reviewed and agreed upon and serves as the basis for further development. This is called:
a. Requirement baseline
b. Initial scope
c. Preliminary requirements
d. Project scope
165) You have decided to implement a commercial off-the-shelf (COTS) system. You want to develop additional functionality with custom code to enhance the package’s capabilities to close needs gaps. Which of the below is the type of COTS implementation you are implementing?
a. Out-of-the-box
b. Configured
c. Integrated
d. Extended
166) Requirements management tools are underutilized in your organization. Which of the below could be root causes?
a. Inadequate training in tool capabilities
b. Processes and culture haven’t been modified to take full advantage of tools
c. No one is responsible for leading the use of the tool
d. Amount of time needed to configure, learn how to use, and employ the tool is underestimated
167) More requirements are planned than can be implemented with available time and resources. Which of the below are possible solutions?
a. Prioritize requirements based on business objectives
b. Plan for multiple delivery cycles to accommodate lower-priority requirements
c. Document vision and scope, aligned with business objectives, before making commitments
d. Timebox the development or deliver product features incrementally
168) The team can’t get customer representatives to participate in elicitation. Which of the below could be root causes?
a. Customer representatives don’t have time to participate in requirements development
b. Customers don’t understand the need to participate
c. Customers don’t know what BAs need from them
d. Customers aren’t committed to the project
169) The team can’t get customer representatives to participate in elicitation. Which of the below could be possible solutions?
a. Educate customers and managers about requirements and the need for their participation
b. Describe the risks from insufficient user involvement to customers and managers
c. Identify a product champion for each user class
d. Obtain customer management commitment to an effective requirements process
170) Wrong user representatives are involved in requirement elicitation. Which of the below could be possible solutions?
a. Define user classes
b. Identify and empower appropriate and effective product champions
c. Develop user personas as stand-ins for real users
d. Decline requirement requests from unauthorized or inappropriate sources
171) Users are unsure about their needs. Which of the below could be possible solutions?
a. Compile a list of generic questions as a starting point for elicitation activities
b. Develop use cases or user stories
c. Build prototypes and have users evaluate them
d. Use incremental development to clarify requirements a bit at a time
172) Users are unsure about their needs. Which of the below could be root causes?
a. Users don’t understand or can’t describe their business process well
b. System is being built to support a new, incompletely defined business process
c. Users aren’t committed to the project, perhaps are threatened by it
d. Business objectives are not well defined or communicated
173) Too many people are involved in requirements elicitation. Which of the below could be root causes?
a. Everyone wants to be represented for political reasons
b. User classes aren’t clearly defined
c. Lack of delegation to specific user representatives
d. There really are a lot of different user classes
174) Too many people are involved in requirements elicitation. Which of the below could be possible solutions?
a. Define user classes
b. Identify product champions or product owners
c. Identify requirements decision makers
d. Focus on the needs of favored user classes
175) Implemented “requirements” don’t meet user needs. Which of the below could be possible solutions?
a. Ask “why” several times to understand the real user needs behind the presented requirements and the rationale behind design constraints.
b. Understand user requirements before addressing user interface specifics.
c. Develop skilled BAs who can ask the right questions and elicit true needs.
d. Educate customers about requirements development.
176) Needed requirements are missed. Which of the below could be root causes?
a. Users don’t know what they need
b. BA didn’t ask the right questions
c. Insufficient time was provided for elicitation
d. Some user classes aren’t represented
177) Needed requirements are missed. Which of the below could be root causes?
a. Appropriate, knowledgeable user representatives did not participate in elicitation
b. Elicitation participants make incorrect assumptions
c. Insufficient communication between developers and customers
d. Users don’t express their implicit and assumed requirements
178) Needed requirements are missed. Which of the below could be possible solutions?
a. Develop skilled BAs who can ask the right questions
b. Elicit use cases or user stories
c. Use multiple elicitation techniques
d. Represent requirements in multiple ways, emphasizing visual models, to look for gaps
179) Needed requirements are missed. Which of the below could be possible solutions?
a. Conduct requirements reviews. Use multiple, incremental reviews
b. Build prototypes and have users evaluate them
c. Build the product incrementally and incorporate new requirements in later iterations
d. Create and use a requirements traceability matrix to find missing requirements
180) Requirements specified are incorrect or inappropriate. Which of the below could be possible solutions?
a. Determine what was wrong with the flawed requirements and why they were specified
b. Define user classes
c. Identify appropriate product champions, educate them, and empower them
d. Have a multifunctional team review requirements
a. Assign each open issue to an individual for resolution
b. Use an issue-tracking tool for tracking requirements issues to closure
c. Monitor open issues as part of project tracking
d. Obtain commitment from all stakeholders early on for open and timely information exchange and for answering questions and resolving issues
162) Your project participants don’t share the same vocabulary. Which of the below are possible solutions?
a. Define terms in a glossary.
b. Define data structures and elements in a data dictionary.
c. Train development team in the business domain.
d. Train user representatives in requirements engineering
163) You notice that there is ambiguity in how different users understand the requirements. Which of the below can help clear ambiguities in requirements?
a. Writing tests against the requirements
b. Building prototypes
c. Collaborative elicitation
d. Collaborative validation
164) You have prepared a set of requirements that has been reviewed and agreed upon and serves as the basis for further development. This is called:
a. Requirement baseline
b. Initial scope
c. Preliminary requirements
d. Project scope
165) You have decided to implement a commercial off-the-shelf (COTS) system. You want to develop additional functionality with custom code to enhance the package’s capabilities to close needs gaps. Which of the below is the type of COTS implementation you are implementing?
a. Out-of-the-box
b. Configured
c. Integrated
d. Extended
166) Requirements management tools are underutilized in your organization. Which of the below could be root causes?
a. Inadequate training in tool capabilities
b. Processes and culture haven’t been modified to take full advantage of tools
c. No one is responsible for leading the use of the tool
d. Amount of time needed to configure, learn how to use, and employ the tool is underestimated
167) More requirements are planned than can be implemented with available time and resources. Which of the below are possible solutions?
a. Prioritize requirements based on business objectives
b. Plan for multiple delivery cycles to accommodate lower-priority requirements
c. Document vision and scope, aligned with business objectives, before making commitments
d. Timebox the development or deliver product features incrementally
168) The team can’t get customer representatives to participate in elicitation. Which of the below could be root causes?
a. Customer representatives don’t have time to participate in requirements development
b. Customers don’t understand the need to participate
c. Customers don’t know what BAs need from them
d. Customers aren’t committed to the project
169) The team can’t get customer representatives to participate in elicitation. Which of the below could be possible solutions?
a. Educate customers and managers about requirements and the need for their participation
b. Describe the risks from insufficient user involvement to customers and managers
c. Identify a product champion for each user class
d. Obtain customer management commitment to an effective requirements process
170) Wrong user representatives are involved in requirement elicitation. Which of the below could be possible solutions?
a. Define user classes
b. Identify and empower appropriate and effective product champions
c. Develop user personas as stand-ins for real users
d. Decline requirement requests from unauthorized or inappropriate sources
171) Users are unsure about their needs. Which of the below could be possible solutions?
a. Compile a list of generic questions as a starting point for elicitation activities
b. Develop use cases or user stories
c. Build prototypes and have users evaluate them
d. Use incremental development to clarify requirements a bit at a time
172) Users are unsure about their needs. Which of the below could be root causes?
a. Users don’t understand or can’t describe their business process well
b. System is being built to support a new, incompletely defined business process
c. Users aren’t committed to the project, perhaps are threatened by it
d. Business objectives are not well defined or communicated
173) Too many people are involved in requirements elicitation. Which of the below could be root causes?
a. Everyone wants to be represented for political reasons
b. User classes aren’t clearly defined
c. Lack of delegation to specific user representatives
d. There really are a lot of different user classes
174) Too many people are involved in requirements elicitation. Which of the below could be possible solutions?
a. Define user classes
b. Identify product champions or product owners
c. Identify requirements decision makers
d. Focus on the needs of favored user classes
175) Implemented “requirements” don’t meet user needs. Which of the below could be possible solutions?
a. Ask “why” several times to understand the real user needs behind the presented requirements and the rationale behind design constraints.
b. Understand user requirements before addressing user interface specifics.
c. Develop skilled BAs who can ask the right questions and elicit true needs.
d. Educate customers about requirements development.
176) Needed requirements are missed. Which of the below could be root causes?
a. Users don’t know what they need
b. BA didn’t ask the right questions
c. Insufficient time was provided for elicitation
d. Some user classes aren’t represented
177) Needed requirements are missed. Which of the below could be root causes?
a. Appropriate, knowledgeable user representatives did not participate in elicitation
b. Elicitation participants make incorrect assumptions
c. Insufficient communication between developers and customers
d. Users don’t express their implicit and assumed requirements
178) Needed requirements are missed. Which of the below could be possible solutions?
a. Develop skilled BAs who can ask the right questions
b. Elicit use cases or user stories
c. Use multiple elicitation techniques
d. Represent requirements in multiple ways, emphasizing visual models, to look for gaps
179) Needed requirements are missed. Which of the below could be possible solutions?
a. Conduct requirements reviews. Use multiple, incremental reviews
b. Build prototypes and have users evaluate them
c. Build the product incrementally and incorporate new requirements in later iterations
d. Create and use a requirements traceability matrix to find missing requirements
180) Requirements specified are incorrect or inappropriate. Which of the below could be possible solutions?
a. Determine what was wrong with the flawed requirements and why they were specified
b. Define user classes
c. Identify appropriate product champions, educate them, and empower them
d. Have a multifunctional team review requirements
No comments:
Post a Comment