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 set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






3. A system trigger that is initiated by time.






4. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






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






10. A model that defines the boundaries of a business domain or solution.






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






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






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






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






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






16. The problem area undergoing analysis.






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






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






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






20. An informal solicitation of proposals from vendors.






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






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






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






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






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






26. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






30. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






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






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






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






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






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






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






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






42. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






45. A prototype developed to explore or verify requirements.






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






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






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






49. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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