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






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






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






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






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






6. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






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






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






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






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






15. A practitioner of business analysis.






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






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






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






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






20. A prototype that is continuously modified and updated in response to feedback from users.






21. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






23. The problem area undergoing analysis.






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






25. The set of capabilities a solution must deliver in order to meet the business need.






26. An assessment of the costs and benefits associated with a proposed initiative.






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






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






29. A link between two elements or objects in a diagram.






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






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






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






33. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






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






41. A unit of work performed as part of an initiative or process.






42. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






46. A specific actionable testable directive that is under the control of the business and supports a business policy.






47. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






49. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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