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. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






5. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






9. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






11. The area covered by a particular activity or topic of interest.






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






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






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






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






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






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






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






19. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






21. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






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






26. A partial or preliminary version of the system.






27. A system trigger that is initiated by humans.






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






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






30. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






31. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






34. The problem area undergoing analysis.






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






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






37. The features and functions that characterize a product service or result.






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






39. A prototype developed to explore or verify requirements.






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






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






42. A description of the requirements management process.






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






44. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






48. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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