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 group of related tasks that support a key function of business analysis.






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






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






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






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






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






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






8. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






9. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






12. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






13. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






14. A stakeholder who provides products or services to an organization.






15. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






17. The degree to which a set of inherent characteristics fulfills requirements.






18. An informal solicitation of proposals from vendors.






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






20. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






25. A measure of the profitability of a project or investment.






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






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






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






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






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






31. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






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






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






37. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






39. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






40. The problem area undergoing analysis.






41. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






42. The process of examining new business opportunities to improve organizational performance.






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






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






45. A description of the requirements management process.






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






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






48. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






49. A data element with a specified data type that describes information associated with a concept or entity.






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