Test your basic knowledge |

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. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






2. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






3. Influencing factors that are believed to be true but have not been confirmed to be accurate.






4. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






5. A state or condition the business must satisfy to reach its vision.






6. Any effort undertaken with a defined goal or objective.






7. The degree to which a set of inherent characteristics fulfills requirements.






8. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






9. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






10. A specific actionable testable directive that is under the control of the business and supports a business policy.






11. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






12. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






13. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






14. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






15. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






16. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






17. A group of related tasks that support a key function of business analysis.






18. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






19. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






20. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






21. The features and functions that characterize a product service or result.






22. The quality attributes design and implementation constraints and external interfaces that the product must have.






23. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






24. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






25. A prototype that dives into the details of the interface functionality or both.






26. Limitations on the design of a solution that derive from the technology used in its implementation.






27. The problem area undergoing analysis.






28. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






29. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






30. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






31. A prototype developed to explore or verify requirements.






32. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






33. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






34. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






35. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






36. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






37. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






38. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






39. A type of data model that depicts information groups as classes.






40. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






41. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






42. An analysis model that illustrates the architecture of the system's user interface.






43. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






44. Software developed and sold for a particular market.






45. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






46. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






47. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






48. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






49. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






50. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.