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






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






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






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






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






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






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






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






9. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






11. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






14. The process of examining new business opportunities to improve organizational performance.






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






16. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






19. The problem area undergoing analysis.






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






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






22. An analysis model that illustrates the architecture of the system's user interface.






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






24. A practitioner of business analysis.






25. A system trigger that is initiated by humans.






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






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






28. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






31. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






32. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






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






37. The area covered by a particular activity or topic of interest.






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






39. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






43. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






44. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






50. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.