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 stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






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






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






7. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






11. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






15. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






18. A prototype developed to explore or verify requirements.






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






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






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






22. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






25. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






30. A partial or preliminary version of the system.






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






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






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






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






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






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






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






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






40. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






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






45. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






46. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






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






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