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






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






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






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






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






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






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






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






9. Formal approval of a set of requirements by a sponsor or other decision maker.






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






11. A temporary endeavor undertaken to create a unique product service or result.






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






13. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






15. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






19. Any recognized association of people in the context of an organization or enterprise.






20. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






22. Software developed and sold for a particular market.






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






24. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






28. All materials used by groups within an organization to define tailor implement and maintain their processes.






29. The problem area undergoing analysis.






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






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






32. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






33. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






35. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






36. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






38. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






40. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






41. An analysis model describing the data structures and attributes needed by the system.






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






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






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






45. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






49. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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