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 continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






2. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






3. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






6. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






7. A description of the requirements management process.






8. Software developed and sold for a particular market.






9. The problem area undergoing analysis.






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






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






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






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






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






15. A stakeholder who provides products or services to an organization.






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






17. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






18. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






23. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






25. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






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






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






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






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






32. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






35. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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






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






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






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






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






43. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






45. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






46. An analysis model showing the life cycle of a data entity or class.






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






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






49. Any effort undertaken with a defined goal or objective.






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