141) Which of the below are part of the seven basic quality tools (7QC)?
A. Fishbone diagrams
B. Flowcharts
C. Pareto diagrams
D. Checklists
1 . A
2. A, B
3. A, B, C
4. A, B, C, D
142) A state diagram is also known as:
a. State Machine Diagram
b. State Transition Diagram
c. Entity Life Cycle Diagram
d. SWOT diagram
143) Which of the below is not true of a state diagram?
a. It shows how the behavior of a concept, entity or object changes in response to events
b. It specifies a sequence of states that an object goes through during its lifetime, and defines which events cause a transition between those states
c. It shows strengths and weaknesses of the process
d. It is used to model the logic of usage scenarios, by showing the information passed between objects in the system through the execution
of the scenario
144) You are assessing a vendor based on his knowledge and expertise. Which of the below can you also use?
a. Product Reputation and Market Position
b. Terms and conditions
c. Vendor Experience and Reputation
d. Vendor Stability
145) Which of the below can lead to poor software cost estimation?
a. Frequent requirements changes
b. Missing requirements
c. Insufficient communication with users
d. Insufficient requirements analysis
146) You have learnt that some of the assumptions you made in the project are wrong. Which of the below can you do to achieve the objectives?
a. Change scope
b. Adjust the schedule
c. Launch other projects
d. Proceed with the initial assumptions
147) Which of the following is not true?
a. When resolving conflicts between requirements from different user classes or making priority decisions, favored user classes receive preferential treatment
b. Disfavored user classes are groups who aren’t supposed to use the product for legal, security, or safety reasons
c. You might build in features to deliberately make it hard for disfavored users to do things they aren’t supposed to do
d. Favored user classes and disfavored user classes should be treated the same when resolving conflicts between requirements from them
148) Which of the following is true about product champions?
a. They are a few key members of the user community that provide the requirements for the project
b. Each product champion serves as the primary interface between members of a single user class and the project’s business analyst
c. Ideally, the champions will be actual users, not surrogates such as funding sponsors, marketing staff, user managers, or software developers imagining themselves to be users
d. Product champions gather requirements from other members of the user classes they represent and reconcile inconsistencies
149) Planguage uses which of the following?
a. Tag
b. Ambition
c. Stretch
d. Wish
150) Which of the below is not true about requirement prioritization?
a. If you go through a prioritization process and all of the requirements come out with about the same priority, you really haven’t prioritized them at all
b. The highest priority requirements are those that provide the largest fraction of the total product value at the smallest fraction of the total cost
c. The prioritization can include considerations of customer value, business value, business or technical risk, cost, difficulty implementation, time to market, regulatory or policy compliance, competitive marketplace advantage, and contractual commitments
d. ‘Decibel prioritization’ and ‘Threat prioritization’ are best practices
151) You have dissatisfied customers who reject the product and provide bad reviews. Which of the below could be possible root causes?
a. Inadequate user involvement in requirements development
b. Unrealistic customer expectations
c. Mismatch between customer’s and developer’s perception of specific requirements
d. Poor problem definition
152) You have dissatisfied customers who reject the product and provide bad reviews. Which of the below could be possible solutions?
a. Build prototypes and have users evaluate them.
b. Have customer representatives review requirements.
c. Convene focus groups
d. Use collaborative requirements elicitation approaches
153) In your organization, requirements processes and document templates are inconsistent across projects. Which of the below could be possible solutions?
a. Adopt one or more standard templates for requirements deliverables
b. Provide guidance to help project teams tailor the standard templates as appropriate
c. Collect and share good examples of templates and actual requirements documents in a shared repository
d. Consider whether the templates are too complex for all projects; simplify them if you can
154) People performing the BA role don’t know how to do it well. Which of the below could be possible solutions?
a. Train prospective BAs in both requirements engineering and associated soft skills
b. Write a job description and a skills list for your BAs
c. Set up a mentoring program for new BAs
d. Develop a professional BA career path in the organization
155) The product you have developed doesn’t achieve business objectives. Which of the below could be possible solutions?
a. Develop business requirements with key stakeholders
b. Understand which success metrics are important to the project’s business stakeholders
c. Communicate business objectives to other stakeholders to achieve alignment
d. Convene focus groups
156) The requirements for your project are incomplete and insufficiently detailed. Construction begins before the requirements for a development iteration or enhancement cycle are sufficiently understood. Which of the below are possible root causes?
a. Inadequate user involvement in requirements development
b. Insufficient time spent on requirements development
c. Release date set before requirements are understood
d. Key marketing or business stakeholders are not engaged in the requirements process
157) More requirements are planned than can be implemented with available time and resources. Which of the below are possible root causes?
a. Schedule is set before requirements are defined
b. Project is committed to before scope is accurately assessed
c. Insufficient staff is allocated to project
d. Stakeholders are afraid they will have only one release opportunity
158) Scope is undocumented or poorly defined and releases are poorly planned. Which of the below are possible root causes?
a. Haste to begin construction
b. Lack of understanding of the importance of scope definition
c. Lack of agreement on scope among stakeholders
d. Volatile market or rapidly changing business needs
159) Scope is undocumented or poorly defined and releases are poorly planned. Which are the possible solutions?
a. Don’t begin a project without clear business objectives
b. Write a vision and scope document and obtain buy-in from key stakeholders
c. Postpone or cancel the project if sponsorship and scope definition are not achieved
d. Use shorter development iterations to adapt to rapidly changing requirements
160) Requirements questions and issues are not resolved for your project. Which are possible root causes?
a. Lack of coordination of questions and issues that arise about requirements
b. Responsibilities for resolving issues are not clear
c. No one is responsible for tracking issues and their status
d. Team is unable to obtain necessary information from a vendor, client, contractor, or other stakeholder
A. Fishbone diagrams
B. Flowcharts
C. Pareto diagrams
D. Checklists
1 . A
2. A, B
3. A, B, C
4. A, B, C, D
142) A state diagram is also known as:
a. State Machine Diagram
b. State Transition Diagram
c. Entity Life Cycle Diagram
d. SWOT diagram
143) Which of the below is not true of a state diagram?
a. It shows how the behavior of a concept, entity or object changes in response to events
b. It specifies a sequence of states that an object goes through during its lifetime, and defines which events cause a transition between those states
c. It shows strengths and weaknesses of the process
d. It is used to model the logic of usage scenarios, by showing the information passed between objects in the system through the execution
of the scenario
144) You are assessing a vendor based on his knowledge and expertise. Which of the below can you also use?
a. Product Reputation and Market Position
b. Terms and conditions
c. Vendor Experience and Reputation
d. Vendor Stability
145) Which of the below can lead to poor software cost estimation?
a. Frequent requirements changes
b. Missing requirements
c. Insufficient communication with users
d. Insufficient requirements analysis
146) You have learnt that some of the assumptions you made in the project are wrong. Which of the below can you do to achieve the objectives?
a. Change scope
b. Adjust the schedule
c. Launch other projects
d. Proceed with the initial assumptions
147) Which of the following is not true?
a. When resolving conflicts between requirements from different user classes or making priority decisions, favored user classes receive preferential treatment
b. Disfavored user classes are groups who aren’t supposed to use the product for legal, security, or safety reasons
c. You might build in features to deliberately make it hard for disfavored users to do things they aren’t supposed to do
d. Favored user classes and disfavored user classes should be treated the same when resolving conflicts between requirements from them
148) Which of the following is true about product champions?
a. They are a few key members of the user community that provide the requirements for the project
b. Each product champion serves as the primary interface between members of a single user class and the project’s business analyst
c. Ideally, the champions will be actual users, not surrogates such as funding sponsors, marketing staff, user managers, or software developers imagining themselves to be users
d. Product champions gather requirements from other members of the user classes they represent and reconcile inconsistencies
149) Planguage uses which of the following?
a. Tag
b. Ambition
c. Stretch
d. Wish
150) Which of the below is not true about requirement prioritization?
a. If you go through a prioritization process and all of the requirements come out with about the same priority, you really haven’t prioritized them at all
b. The highest priority requirements are those that provide the largest fraction of the total product value at the smallest fraction of the total cost
c. The prioritization can include considerations of customer value, business value, business or technical risk, cost, difficulty implementation, time to market, regulatory or policy compliance, competitive marketplace advantage, and contractual commitments
d. ‘Decibel prioritization’ and ‘Threat prioritization’ are best practices
151) You have dissatisfied customers who reject the product and provide bad reviews. Which of the below could be possible root causes?
a. Inadequate user involvement in requirements development
b. Unrealistic customer expectations
c. Mismatch between customer’s and developer’s perception of specific requirements
d. Poor problem definition
152) You have dissatisfied customers who reject the product and provide bad reviews. Which of the below could be possible solutions?
a. Build prototypes and have users evaluate them.
b. Have customer representatives review requirements.
c. Convene focus groups
d. Use collaborative requirements elicitation approaches
153) In your organization, requirements processes and document templates are inconsistent across projects. Which of the below could be possible solutions?
a. Adopt one or more standard templates for requirements deliverables
b. Provide guidance to help project teams tailor the standard templates as appropriate
c. Collect and share good examples of templates and actual requirements documents in a shared repository
d. Consider whether the templates are too complex for all projects; simplify them if you can
154) People performing the BA role don’t know how to do it well. Which of the below could be possible solutions?
a. Train prospective BAs in both requirements engineering and associated soft skills
b. Write a job description and a skills list for your BAs
c. Set up a mentoring program for new BAs
d. Develop a professional BA career path in the organization
155) The product you have developed doesn’t achieve business objectives. Which of the below could be possible solutions?
a. Develop business requirements with key stakeholders
b. Understand which success metrics are important to the project’s business stakeholders
c. Communicate business objectives to other stakeholders to achieve alignment
d. Convene focus groups
156) The requirements for your project are incomplete and insufficiently detailed. Construction begins before the requirements for a development iteration or enhancement cycle are sufficiently understood. Which of the below are possible root causes?
a. Inadequate user involvement in requirements development
b. Insufficient time spent on requirements development
c. Release date set before requirements are understood
d. Key marketing or business stakeholders are not engaged in the requirements process
157) More requirements are planned than can be implemented with available time and resources. Which of the below are possible root causes?
a. Schedule is set before requirements are defined
b. Project is committed to before scope is accurately assessed
c. Insufficient staff is allocated to project
d. Stakeholders are afraid they will have only one release opportunity
158) Scope is undocumented or poorly defined and releases are poorly planned. Which of the below are possible root causes?
a. Haste to begin construction
b. Lack of understanding of the importance of scope definition
c. Lack of agreement on scope among stakeholders
d. Volatile market or rapidly changing business needs
159) Scope is undocumented or poorly defined and releases are poorly planned. Which are the possible solutions?
a. Don’t begin a project without clear business objectives
b. Write a vision and scope document and obtain buy-in from key stakeholders
c. Postpone or cancel the project if sponsorship and scope definition are not achieved
d. Use shorter development iterations to adapt to rapidly changing requirements
160) Requirements questions and issues are not resolved for your project. Which are possible root causes?
a. Lack of coordination of questions and issues that arise about requirements
b. Responsibilities for resolving issues are not clear
c. No one is responsible for tracking issues and their status
d. Team is unable to obtain necessary information from a vendor, client, contractor, or other stakeholder
No comments:
Post a Comment