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






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






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






4. All materials used by groups within an organization to define tailor implement and maintain their processes.






5. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






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






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






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






11. The number of employees a manger is directly (or indirectly) responsible for.






12. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






14. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






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






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






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






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






23. A stakeholder who uses products or services delivered by an organization.






24. Software developed and sold for a particular market.






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






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






27. A practitioner of business analysis.






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






29. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






31. A system trigger that is initiated by humans.






32. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






35. An analysis model that illustrates the architecture of the system's user interface.






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






37. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






40. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






45. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






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






50. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.