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 defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






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






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






7. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






11. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






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






16. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






17. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






18. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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






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






22. Limitations on the design of a solution that derive from the technology used in its implementation.






23. An informal solicitation of proposals from vendors.






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






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






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






27. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






29. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






30. Software developed and sold for a particular market.






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






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






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






34. A practitioner of business analysis.






35. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






37. A system of programming statements symbols and rules used to represent instructions to a computer.






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






39. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






40. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






42. Work carried out or on behalf of others.






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






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






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






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






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






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






49. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






50. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.