Test your basic knowledge |

CBAP Business Analysis And Planning

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. States the business need - identifies key stakeholders and briefly describes the positive impact that meeting the business need will have on those stakeholders.






2. Divides requirements into 4 categories - Must - Should - Could - Won't






3. A means to elicit requirements by studying available documentation on existing and comparable solutions and identifying relevant information. - Not starting from a blank page.- Leveraging existing materials to discover and/or confirm requirements. -






4. Prioritizes requirements based on a allocated fixed amount of money.






5. Rules that the organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the organization. They may oblige people to take certain actions - prevent people from taking actions - or prescribe






6. This knowledge area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate successful implementation.






7. What are the elements of the task - Define Solution Scope?






8. Investigating how a solution is actually used after it is deployed and assessing the effect it has had - both positive and negative.






9. What is a STAKEHOLDER requirement - according to the BABOK 2.0?






10. Involves assessing a situation - understanding it as fully as possible - and making judgments about possible solutions to the problem.






11. What are the techniques used in the task - Determine Solution Approach?






12. What are the inputs to the task Manage Requirements Traceability?






13. While eliciting requirements it is important to guard against scope creep - This activity will ensure that the requirements should be included since they meet the business goal/objectives.






14. Technique involving refinement of estimates. Estimate the details for activities in the current iteration or increment and provide an analogous estimate for the entire scope of work. As the end of the iteration approaches - estimates for the next ite






15. What are the techniques used in the task - Evaluate Solution Performance?






16. Models a deep - and usually narrow slice of the entire system's functionality.






17. When performing root cause analysis as part of the Validate Solution task - what stakeholder may be involved?






18. What are the inputs for the task - Prepare Requirements Package?






19. What is the output of the task Plan Requirements Management Process?






20. What is the output of the Plan Business Analysis Approach?






21. What is the output of the task Conduct Stakeholder Analysis?






22. Familiarity with the range of commercially available solutions or suppliers can assist with the identification of possible alternatives.






23. What are the techniques for the task - Verify Requirements?






24. What techniques are used in the task Manage Requirements Traceability?






25. Creates a conceptual model of the work that needs to be completed to deliver the new business solution.






26. Understanding of how a change to a component affects the system as a whole - identification of reinforcing and compensating feedback loops - understanding of how systems adapt to external pressures and changes - A system as a whole will have properti






27. Business value can be delivered through requirements that support _______________ - alignment with internal standards or policies of the organization - or increased satisfaction for stakeholders - even if those things do not have a direct measurable






28. Requires the team to focus on examining the premises - assumptions - observations and expectations of the team members. This type of conflict can have a beneficial effect of strengthening the foundations of the analysis and the solution.






29. Limited to "as-is" perspective. - Existing documentation may not be up-to-date or valid. - Can be a time-consuming and even tedious process to locate the relevant information






30. The goal of this task is to ensure that all requirements support the delivery of value to the business - fulfill its goal and objectives and meet a stakeholder need.






31. Defines what must be delivered in order to meet the business need - and the effect of the proposed change initiation on the business and technology operations and infrastructure.






32. What is the output of the task - Specify & Model Requirements?






33. Decisions are made with the interest of all stakeholders considered - reasons for a decision are cleared articulated - prompt and full disclosure of conflicts of interest - honesty regarding one's abilities and the performance of one's work.






34. What are the inputs to the task - Organize Requirements?






35. The purpose is to describe the required qualities of a system - such as its usability and performance characteristics.






36. Shows how the behavior of a concept - entity or object changes in response to events during its lifetime - and defines which events cause a transition between those states.






37. A package should contain a consistent - cohesive and coherent set of requirements. This describes the ____________.






38. A structured way to capture requirements. May be used to scope - discover - define - prioritize and reach closure on requirements for the target system. Considered one of the most effective ways to deliver high quality requirements quickly.






39. Industry Knowledge - Organization Knowledge - Solution Knowledge What are the elements of Business Knowledge?






40. What are the techniques used in the task - Define Transition Requirements?






41. When a requirement is changed - the BA can easily review all the related requirements and software components in order to understand the impact of the change.






42. Defines the key terms and data relevant to a business domain.






43. What are the techniques used in Plan Business Analysis Activities?






44. The objective of this technique is to determine how companies achieve their superior performance levels and use that information to design projects to improve operations of the enterprise.






45. A structured examination of the aspects of a situation to establish the root causes and resulting effects of the problem. A critical element is to ensure that the current business thinking and processes are challenged. The purpose is to determine the






46. Checklist of characteristics to consider when considering non-functional requirements.






47. Provides an organized approach to tracking - management - and resolution of defects - issues - problems - and risks throughout business analysis activities. Management of issues is important so that they can be resolved in a timely manner to ensure s






48. What are the tasks in Business Analysis Planning & Monitoring?






49. What are the Composite Data Elements?






50. What is the output of the task - Maintain Requirements for Re-use?