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 model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






4. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






5. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






7. A partial or preliminary version of the system.






8. Work carried out or on behalf of others.






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






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






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






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






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






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






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






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






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






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






19. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






21. Limitations on the design of a solution that derive from the technology used in its implementation.






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






23. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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. An analysis model describing the data structures and attributes needed by the system.






29. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






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






33. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






34. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






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






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






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






41. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






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






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






46. Any unique and verifiable work product or service that a party has agreed to deliver.






47. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






50. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.