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. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






5. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






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






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






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






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






13. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






16. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






17. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






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






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






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






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






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






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






28. An informal solicitation of proposals from vendors.






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






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






31. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






32. Work carried out or on behalf of others.






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






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






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






36. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






38. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






39. A stakeholder who uses products or services delivered by an organization.






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






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






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






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






44. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






45. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






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






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






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