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 requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






2. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






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






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






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






7. A partial or preliminary version of the system.






8. A structured examination of an identified problem to understand the underlying causes.






9. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






15. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






17. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






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






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






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






24. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






27. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






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






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. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






38. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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






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






44. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






45. The product capabilities or things the product must do for its users.






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






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






48. A state or condition the business must satisfy to reach its vision.






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






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