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 set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






4. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






8. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






9. Metadata related to a requirement used to assist with requirements development and management.






10. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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 description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






15. A structured examination of an identified problem to understand the underlying causes.






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






17. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






21. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






23. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






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






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






28. A person with specific expertise in an area or domain under investigation.






29. A solution or component of a solution that is the result of a project.






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






31. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






32. Work carried out or on behalf of others.






33. A stakeholder who provides products or services to an organization.






34. A practitioner of business analysis.






35. A data element with a specified data type that describes information associated with a concept or entity.






36. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






38. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






41. Software developed and sold for a particular market.






42. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






44. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






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






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






49. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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