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. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






6. A temporary endeavor undertaken to create a unique product service or result.






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






8. Ability of systems to communicate by exchanging data or services.






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






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






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






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






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






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






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






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






17. An informal solicitation of proposals from vendors.






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






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






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






21. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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






25. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






27. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






30. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






32. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






35. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






38. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






41. An analysis model describing the data structures and attributes needed by the system.






42. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






45. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






47. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






48. The work that must be performed to deliver a product service or result with the specified features and functions.






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






50. A system trigger that is initiated by time.