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. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






3. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






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






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






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






9. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






14. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






15. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






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






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






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






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






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






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






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






24. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






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






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






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






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






32. Any recognized association of people in the context of an organization or enterprise.






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






34. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






35. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






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






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






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






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






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






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






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






46. A description of the requirements management process.






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






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






49. A person with specific expertise in an area or domain under investigation.






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