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






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






3. What are the techniques used in the task - Define Business Case?






4. Two types of conflict.






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






6. Name some commonly used financial valuation techniques.






7. Gathering information relevant to a decision - breaking down the information relevant to a decision - making comparisons and tradeoffs between similar and dissimilar options and identifying the option that is most desirable.






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






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






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






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






12. What are the characteristics of a Problem Record?






13. Are used to model the logic of usage scenarios - by showing the information passed between objects in the system through the execution of the scenario. Shows how classes and objects interact during a scenario.






14. Combination of expert judgment and history. Individual estimates - sharing the estimates with experts - and having several rounds until consensus is reached. An average of the three estimates is used






15. The purpose is to measure the performance of solutions - solution components - and other matters of interest to stakeholders.






16. Techniques used in the task Plan Requirements Management Process.






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






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






19. Maps the level of stakeholder influence and interest in a project.






20. What is the output of the task - Verify Requirements?






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






22. States the business need - identifies key stakeholders and briefly describes the positive impact that meeting the business need will have on those stakeholders.






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






24. What are the likely sources of transition requirements?






25. Use of a similar project as the basis for developing estimates for the current project. Also known as "top-down" estimating. This is usually done at the beginning of the project or project phase and more detailed estimates follow as more is known.






26. Characteristics that are common to all organizations with a similar purpose and structure - whether or not the are in the same industry.






27. Three key factors when assessing the quality of indicators and their metrics






28. Name the 2 types of Stakeholder maps.






29. What are the inputs for the task Prepare for Elicitation?






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






31. What are the inputs to the task Conduct Elicitation Activity?






32. What is the output to the task - Evaluate Solution Performance?






33. What are the tasks in the knowledge area - Solution Assessment & Validation?






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






35. What are the attributes of a Data Model?






36. The process of informing stakeholders of metrics of indicators in specified formats at specified intervals.






37. A specific - actionable - testable directive that is under the control of an organization and supports a business policy.






38. Means of eliciting information from many people - sometimes anonymously - in a relatively short period of time






39. This technique represents the types of peoples - places - things and concepts that are important to the business - attributes associated with them and the significant business relationships among them.






40. What is the output of the task - Assess Proposed Solution?






41. The people involved - the interactions between them - the external forces affecting their behavior and all other relevant elements and factors.






42. What are the techniques used in the task Conduct Stakeholder Analysis?






43. Strengths - Weaknesses - Opportunities - Threats - A valuable tool to quickly analyze various aspects of the current state of the business process undergoing change.






44. Two effective trade-off methods.






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






46. What are the inputs to the task - Prioritize Requirements?






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






48. What stakeholder receives noticeable negative impact if information is incorrectly transferred from the old to new solution?






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






50. Uses history as a basis for estimating. It is similar to analogous estimation - but is used not only for the top-down estimate - but for the detailed tasks as well.