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 approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






2. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






3. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






4. Ability of systems to communicate by exchanging data or services.






5. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






6. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






7. A practitioner of business analysis.






8. Something that occurs to which an organizational unit system or process must respond.






9. A measure of the profitability of a project or investment.






10. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






11. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






14. An actor who participates in but does not initiate a use case.






15. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






16. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






17. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






18. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






19. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






22. Software requirements that limit the options available to the system designer.






23. A unit of work performed as part of an initiative or process.






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






25. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






26. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






28. The product capabilities or things the product must do for its users.






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






30. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






31. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






33. An analysis model showing the life cycle of a data entity or class.






34. A function of an organization that enables it to achieve a business goal or objective.






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






36. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






37. A fixed period of time to accomplish a desired outcome.






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






39. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






41. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






42. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






43. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






46. A model that defines the boundaries of a business domain or solution.






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






48. A system of programming statements symbols and rules used to represent instructions to a computer.






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






50. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.