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 graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






6. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






9. A group of related tasks that support a key function of business analysis.






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






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






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






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






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






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






16. The problem area undergoing analysis.






17. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






18. A practitioner of business analysis.






19. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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






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






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






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






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






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. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






30. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






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






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






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






36. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






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






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






41. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






42. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






43. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






44. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






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






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






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