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. What are the characteristics of a Problem Record?






2. What are the output(s) of the task - Validate Solution?






3. What are the elements of Communication Skills?






4. What are the inputs to the Plan Business Analysis Approach?






5. What are the internal factors in a SWOT Analysis?






6. Two types of conflict.






7. What are the inputs to the task - Validate Requirements?






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






9. 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.






10. What is the output of the task - Organize Requirements?






11. This prototype seeks to quickly uncover and clarify interface requirements using simple tools - sometimes just paper and pencil. The focus is on functionality that is not easily elicited by other techniques - has conflicting viewpoints - or is diffic






12. A non-actionable directive that supports a business goal.






13. What are the characteristics of Interaction Skills?






14. What techniques are used in the task - Define Solution Scope?






15. What are some of the commonly used requirement attributes?






16. This knowledge area describes the problem definition and analysis - business case development - feasibility studies and the definition of solution scope.






17. Business rules require a defined glossary of terms and an understanding of the relationships between them - this is known as:






18. Describes the effect a new solution will have on an organization and whether the organization is prepared for the organizational change the solution implementation will cause.






19. Useful for ensuring that all stakeholders are in agreement on the format and content of relevant information. Capturing these definitions in a single model ensures that these terms will be used consistently.






20. The decomposition of activities and tasks creates?






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






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






23. Models a shallow - and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.






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






25. Elements of a Requirements Management Plan include?






26. What are the strategies for a negative risk?






27. Knowing the dependencies and relationships between requirements helps when determining the sequence in which requirements are to be addressed. Common relations are:






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






29. What are the inputs to the task - Specify & Model Requirements?






30. What is the output of the task - Define Transition Requirements?






31. What is the output of the task - Prepare Requirements Package?






32. Long-term - ongoing and qualitative statements of a state or condition that the organization is seeking to establish and maintain.






33. This knowledge area involves analyzing stakeholder needs to define solutions that meet those needs - assessing the current state of the business to identify and recommend improvements and the verification and validation of the resulting requirements.






34. Domain SME - End User - Implementation SME - and Sponsor: They Affected by analysis techniques used to organize requirements since they need to verify and validate the requirements.






35. The goal of this task is to meet with stakeholder(s) to gather information regarding their needs.






36. Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team.






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






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






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






40. What are the elements to the task - Define Business Case?






41. What are the techniques used in the task - Assess Capability Gaps?






42. To identify interfaces between solutions and/or solution components and define requirements that describe how they will interact.






43. Understanding of the business architecture of the organization that is being analyzed. Understanding business models (generates profit) - org structure - relationships between business units and the persons who occupy key stakeholder positions.






44. Describes all the possible outcomes of an attempt to accomplish a particular goal that the solution will support.






45. Name some commonly used financial valuation techniques.






46. Ability to find information - on-time completion of tasks - efficiency in the completion of work - ability to easily identify all outstanding work and the status of each work item.






47. What is the output of the task Conduct Elicitation Activity?






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






49. What are the inputs to the task - Validate Solution?






50. 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.