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 stakeholder with legal or governance authority over the solution or the process used to develop it.






2. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






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






9. A description of the requirements management process.






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






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






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






13. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






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






17. Work carried out or on behalf of others.






18. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






21. The area covered by a particular activity or topic of interest.






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






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






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






25. A system trigger that is initiated by humans.






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






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






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






29. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






32. Formal approval of a set of requirements by a sponsor or other decision maker.






33. The problem area undergoing analysis.






34. Ability of systems to communicate by exchanging data or services.






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






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






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






38. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






41. Software developed and sold for a particular market.






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






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






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






45. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






47. An informal solicitation of proposals from vendors.






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






49. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






50. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.