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






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






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






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






5. A prototype developed to explore or verify requirements.






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






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






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






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






10. A system trigger that is initiated by humans.






11. Software requirements that limit the options available to the system designer.






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






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






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






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






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






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






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






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






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






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






22. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






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






27. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






30. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






32. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






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






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






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






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






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






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






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






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






44. A unit of work performed as part of an initiative or process.






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






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






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






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






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






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