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. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






2. A system trigger that is initiated by time.






3. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






5. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






6. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






7. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






8. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






9. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






10. A stakeholder with legal or governance authority over the solution or the process used to develop it.






11. An informal solicitation of proposals from vendors.






12. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






14. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






17. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






18. An analysis model that shows user interface dialogs arranged as hierarchies.






19. A prototype that is continuously modified and updated in response to feedback from users.






20. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






21. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






22. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






23. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






25. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






26. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






27. Software developed and sold for a particular market.






28. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






30. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






32. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






33. An assessment of the costs and benefits associated with a proposed initiative.






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. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






36. A use case composed of a common set of steps used by multiple use cases.






37. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






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






41. Information that is used to understand the context and validity of information recorded in a system.






42. The human and nonhuman roles that interact with the system.






43. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






44. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






46. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






47. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






49. A partial or preliminary version of the system.






50. A shared boundary between any two persons and/or systems through which information is communicated.